[GitHub] couchdb pull request: Improved Query Options
Github user garrensmith commented on the pull request: https://github.com/apache/couchdb/pull/180#issuecomment-38259646 This has been merged. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: Improved Query Options
Github user garrensmith closed the pull request at: https://github.com/apache/couchdb/pull/180 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: 1870 add language option to mapreduce editor
Github user garrensmith commented on the pull request: https://github.com/apache/couchdb/pull/137#issuecomment-38260382 Refactoring the ViewEditor is a great idea, unfortunately @BigBlueHat this PR is not ready to be merged into master. Two things need to be done to make it usable. I've added the `session.trigger(authenticated);` so that we can check the config only once the user has logged in. Could you add that in. The second fix is when a user creates a new view. If a user creates a view for an existing design doc, then they cannot choose the language for the new view but must use the language that the design doc is set as (unless the design doc is empty, then they can choose which language to write the new view in). If a user selects a new design doc then the language option should appear and they can then choose what language this design doc is written in. Once those two are implemented we should be ready to merge this in. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-2041) upgrade ibrowse to next tag
[ https://issues.apache.org/jira/browse/COUCHDB-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13942961#comment-13942961 ] Dave Cottlehuber commented on COUCHDB-2041: --- thanks [~benoitc] pretty sure this is the crash I was seeing, thanks for the ping, I'll update the branch here as needed. upgrade ibrowse to next tag --- Key: COUCHDB-2041 URL: https://issues.apache.org/jira/browse/COUCHDB-2041 Project: CouchDB Issue Type: Improvement Components: HTTP Interface Reporter: Dave Cottlehuber ibrowse 4.0.3 pre (as it hasn't been released yet) has a couple of useful fixes for us. This branch passes distcheck and I've asked upstream for a tagged release. -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: Fix/build2
Github user deathbearbrown commented on the pull request: https://github.com/apache/couchdb/pull/190#issuecomment-38301742 +1 Thank you for writing tests Robert! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: Fix/build2
Github user robertkowalski closed the pull request at: https://github.com/apache/couchdb/pull/190 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: Fauxton: fix global var
GitHub user robertkowalski opened a pull request: https://github.com/apache/couchdb/pull/191 Fauxton: fix global var just a fix peel-off commit from COUCHDB-2125 You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertkowalski/couchdb tasks/global Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb/pull/191.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #191 commit 89eb4a6d627e1f4e15a998319ac92210e7a1faba Author: Robert Kowalski r...@kowalski.gd Date: 2014-03-21T19:49:41Z Fauxton: fix global var --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-2125) Filter active tasks by database
[ https://issues.apache.org/jira/browse/COUCHDB-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943467#comment-13943467 ] ASF GitHub Bot commented on COUCHDB-2125: - GitHub user robertkowalski opened a pull request: https://github.com/apache/couchdb/pull/191 Fauxton: fix global var just a fix peel-off commit from COUCHDB-2125 You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertkowalski/couchdb tasks/global Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb/pull/191.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #191 commit 89eb4a6d627e1f4e15a998319ac92210e7a1faba Author: Robert Kowalski r...@kowalski.gd Date: 2014-03-21T19:49:41Z Fauxton: fix global var Filter active tasks by database --- Key: COUCHDB-2125 URL: https://issues.apache.org/jira/browse/COUCHDB-2125 Project: CouchDB Issue Type: Improvement Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin Labels: beginners Imagine that you have 100+ active replications and you need to figure out status for some specific database. -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: Fix/build2
Github user andywenk commented on the pull request: https://github.com/apache/couchdb/pull/190#issuecomment-38321678 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: Fauxton: fix global var
Github user andywenk commented on the pull request: https://github.com/apache/couchdb/pull/191#issuecomment-38322196 +1 merged - would you close the PR? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: Fauxton: fix global var
Github user robertkowalski closed the pull request at: https://github.com/apache/couchdb/pull/191 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-2125) Filter active tasks by database
[ https://issues.apache.org/jira/browse/COUCHDB-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943522#comment-13943522 ] ASF GitHub Bot commented on COUCHDB-2125: - Github user robertkowalski closed the pull request at: https://github.com/apache/couchdb/pull/191 Filter active tasks by database --- Key: COUCHDB-2125 URL: https://issues.apache.org/jira/browse/COUCHDB-2125 Project: CouchDB Issue Type: Improvement Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin Labels: beginners Imagine that you have 100+ active replications and you need to figure out status for some specific database. -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: advance the documentation in DELETE db with ...
GitHub user andywenk opened a pull request: https://github.com/apache/couchdb/pull/192 advance the documentation in DELETE db with ?ref= You can merge this pull request into a Git repository by running: $ git pull https://github.com/andywenk/couchdb master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb/pull/192.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #192 commit ebbee3c58390430b5095ba9977720f7f409bab3f Author: Andy Wenk a...@nms.de Date: 2014-01-30T21:00:28Z fix wording in json-structure commit 29256149029714af6379dadd62022ee6f46b58ec Author: Andy Wenk a...@nms.de Date: 2014-03-21T21:57:04Z fix documentation explain why the HTTP status code 400 will be returned when ?rev= is included in the request URL --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: advance the documentation in DELETE db with ...
Github user wohali commented on the pull request: https://github.com/apache/couchdb/pull/192#issuecomment-38329421 +1, LGTM. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: advance the documentation in DELETE db with ...
Github user andywenk commented on the pull request: https://github.com/apache/couchdb/pull/192#issuecomment-38329971 merged --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: advance the documentation in DELETE db with ...
Github user andywenk closed the pull request at: https://github.com/apache/couchdb/pull/192 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (COUCHDB-2205) 400 bad_request on DELETE /db/
Dale Harvey created COUCHDB-2205: Summary: 400 bad_request on DELETE /db/ Key: COUCHDB-2205 URL: https://issues.apache.org/jira/browse/COUCHDB-2205 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: HTTP Interface Reporter: Dale Harvey During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2205) 400 bad_request on DELETE /db/
[ https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943890#comment-13943890 ] Dale Harvey commented on COUCHDB-2205: -- Here is a failing test with the CouchDB log in debug mode, I dont see it actually spitting out a 400 at any point https://travis-ci.org/daleharvey/pouchdb/jobs/21293717 (raw is @ https://s3.amazonaws.com/archive.travis-ci.org/jobs/21293717/log.txt) for comparison sake, here is a log of a passing local run against 1.3.1 https://gist.github.com/daleharvey/9700938 400 bad_request on DELETE /db/ -- Key: COUCHDB-2205 URL: https://issues.apache.org/jira/browse/COUCHDB-2205 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: HTTP Interface Reporter: Dale Harvey During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2205) 400 bad_request on DELETE /db/
[ https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943892#comment-13943892 ] Dale Harvey commented on COUCHDB-2205: -- For some extra information about what is happening during the logs, https://github.com/daleharvey/pouchdb/blob/master/tests/test.bulk_docs.js is the client code 400 bad_request on DELETE /db/ -- Key: COUCHDB-2205 URL: https://issues.apache.org/jira/browse/COUCHDB-2205 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: HTTP Interface Reporter: Dale Harvey During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow -- This message was sent by Atlassian JIRA (v6.2#6252)
