[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=13937542#comment-13937542 ] Dave Cottlehuber commented on COUCHDB-2041: --- Sadly it doesn't, going for the big git bisect today. 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)
Re: [VOTE] Release Apache CouchDB 1.6.0-rc.1
I'm up for some (more) debugging to try to track down the large attachments problem. This is a fairly busy week, but I am free all day Wednesday if that works. I'm also setting up a local FreeBSD machine to try it out myself, but Windows Hyper-V is giving some problems. Nick On 14 March 2014 18:57, Dave Cottlehuber d...@jsonified.com wrote: On 14 March 2014 14:53, Benoit Chesneau bchesn...@gmail.com wrote: On Wed, Mar 5, 2014 at 12:24 PM, Klaus Trainer klaus_trai...@posteo.de wrote: On 03/05/2014 11:06 AM, Andy Wenk wrote: * I tested against master 5989bb324a and all tests pass * I tested against 1986-fix-ibrowse-infinite-async-timeout b35884580 and ./test/etap/200-view-group-no-db-leaks.t fails * rerun with the last one results also in the same error * I tested against 1.6 branch and 04-replication-large-atts.t fails Does anybody have an idea about what change that is in master but not in the 1.6 branch could make 04-replication-large-atts.t not fail anymore? did you figured? Also what is the status of this release? - benoit FWIW I still get the replication failures on FreeBSD + master, even if we sprinkle in the various possible fixes out there. I'm concerned that there's some underlying issue that is worse on FreeBSD but still exists on other platforms -- one of the symptoms is an exploding RSS memory set during replication. If somebody feels like doing some peer debugging next week we might be able to track this down. Worth noting, master works for me fine on OSX but not 1.6. I propose to the illustrious Release Manager (Long May They Reign) to dump the 1.6.x branch unceremoniously cut a new one from current master, assuming Fauxton etc are able to work with this? A+ Dave
[jira] [Commented] (COUCHDB-1592) Free space check for automatic compaction doesn't follow symlinks
[
https://issues.apache.org/jira/browse/COUCHDB-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937634#comment-13937634
]
Nils Breunese commented on COUCHDB-1592:
This issue is still impacting us. Any idea how much work this would be to fix?
Sounds like it should be easy to dereference symlinks, but sadly I don't know
Erlang myself. It would be the equivalent of running {{readlink -f
/path/to/file}} in a shell, right?
Free space check for automatic compaction doesn't follow symlinks
-
Key: COUCHDB-1592
URL: https://issues.apache.org/jira/browse/COUCHDB-1592
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 1.2
Reporter: Nils Breunese
We've got a problem with automatic compaction not running due to low
diskspace according to CouchDB. According to our system administrators there
is more than enough space (more than twice the currently used space), but the
data directory is a symlink to the real data storage. It seems CouchDB is
checking the diskspace on the filesystem on which the symlink resides instead
of the diskspace on the linked filesystem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[GitHub] couchdb pull request: Improved Query Options
Github user garrensmith commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/180#discussion_r10650864
--- Diff: src/fauxton/app/addons/documents/views.js ---
@@ -1090,20 +1117,48 @@ function(app, FauxtonAPI, Components, Documents,
Databases, pouchdb, resizeColum
this.hasReduce = hasReduce;
this.render();
},
+getKeys: function(val){
+ var keys = val.value.replace(/\s/g,);
+
+ var regKeys = keys.match(/(\[.*?\])/g);
--- End diff --
@kxepal this is correct. What we get from the user is a list of keys e.g
1,2,3 or [1,2],[3,4]. We then need to split that string up into individual keys
and put it in an array for `keys` to work. That is what we are doing. The idea
around this is so that the user doesn't need to create an array when adding
keys elements. Just a comma separated list.
---
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 commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/180#discussion_r10650925
--- Diff: src/fauxton/app/addons/documents/views.js ---
@@ -1090,20 +1117,48 @@ function(app, FauxtonAPI, Components, Documents,
Databases, pouchdb, resizeColum
this.hasReduce = hasReduce;
this.render();
},
+getKeys: function(val){
+ var keys = val.value.replace(/\s/g,);
+
+ var regKeys = keys.match(/(\[.*?\])/g);
+ if (regKeys) {
+keys = regKeys;
+ } else {
+keys = keys.split(',');
+ }
+
+ keys = _.map(keys, function (key) { return JSON.parse(key); });
--- End diff --
See my previous comment to explain why we do all of this. Its because we
changing way the user inputs keys (to make it simpler) to the way Couchdb
requires the keys parameter.
---
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 commented on a diff in the pull request: https://github.com/apache/couchdb/pull/180#discussion_r10650943 --- Diff: src/fauxton/app/addons/documents/views.js --- @@ -1178,6 +1233,17 @@ function(app, FauxtonAPI, Components, Documents, Databases, pouchdb, resizeColum } this.updateFiltersFor(key, $ele); break; + case keys: --- End diff -- No, a user sees a comma separated list when viewing keys. However the url is an array of keys so we need to remove the array and make it a string. --- 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: 2116 remove cache
Github user deathbearbrown commented on the pull request: https://github.com/apache/couchdb/pull/182#issuecomment-37809521 It's merged in, you can close this and the Jira ticket :) --- 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] [Resolved] (COUCHDB-2164) Attachments with slashes in name escaped incorrectly
[ https://issues.apache.org/jira/browse/COUCHDB-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sue Lockwood resolved COUCHDB-2164. --- Resolution: Fixed merged in Attachments with slashes in name escaped incorrectly Key: COUCHDB-2164 URL: https://issues.apache.org/jira/browse/COUCHDB-2164 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin Assignee: Sue Lockwood Attachment name: /foo/bar/baz URL in Futon: http://localhost:5984/test/doc/%2ffoo%2fbar%2fbaz URL in Fauxton: http://localhost:5984/test/doc//foo/bar/baz -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (COUCHDB-2140) DBname suggestion on replication page is extremely slow
[ https://issues.apache.org/jira/browse/COUCHDB-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sue Lockwood closed COUCHDB-2140. - Resolution: Fixed I think I can close this one now... DBname suggestion on replication page is extremely slow --- Key: COUCHDB-2140 URL: https://issues.apache.org/jira/browse/COUCHDB-2140 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin Assignee: Sue Lockwood I have to wait for 5-10 seconds to receive the suggestion. Futon shows it instantly. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (COUCHDB-2024) fauxton favicon should be the couchdb one
[ https://issues.apache.org/jira/browse/COUCHDB-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sue Lockwood resolved COUCHDB-2024. --- Resolution: Fixed This should be all set fauxton favicon should be the couchdb one - Key: COUCHDB-2024 URL: https://issues.apache.org/jira/browse/COUCHDB-2024 Project: CouchDB Issue Type: Bug Components: Fauxton Affects Versions: 1.6.0 Reporter: Benoit Chesneau Assignee: Sue Lockwood Actually the favicon in the source is the cloudant one where it should be the couchdb logo. -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: spell checking my-first-couchdb-plugin's REA...
GitHub user marianoguerra opened a pull request: https://github.com/apache/couchdb/pull/185 spell checking my-first-couchdb-plugin's README this pull request only fix spelling mistakes, but there's a part I would like to improve also the opening note of the plugin README says: NOTE: This is incomplete, barely tested, works only with the 1867-feature-plugin branch of Apache CouchDB and expects that you understand some Erlang. This is mostly for early review, but if you are daring, you can learn someting already :) the branch name may be outdated since this works on 1.5.0, also the incomplete, barely tested part seems outdated, maybe this feature is considered alpha/beta/subject to change? can you recommend a better warning note? You can merge this pull request into a Git repository by running: $ git pull https://github.com/marianoguerra/couchdb my-first-couch-plugin-readme-typos Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb/pull/185.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 #185 commit 1db70b8c8037deb3ab64a4e43e4a7c5f80f7038e Author: Mariano Guerra luismarianogue...@gmail.com Date: 2014-03-17T12:43:20Z spell checking my-first-couchdb-plugin's README --- 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: spell checking my-first-couchdb-plugin's REA...
Github user andywenk commented on the pull request: https://github.com/apache/couchdb/pull/185#issuecomment-37811065 You are right about the 1.5 branch so feel free to change this sentence also. this feature is considered alpha/beta/subject to change sounds good to me. Would you update the PR? Thanks :) --- 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: 2116 remove cache
Github user garrensmith commented on the pull request: https://github.com/apache/couchdb/pull/182#issuecomment-37811322 Thanks. --- 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: 2116 remove cache
Github user garrensmith closed the pull request at: https://github.com/apache/couchdb/pull/182 --- 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: spell checking my-first-couchdb-plugin's REA...
Github user marianoguerra commented on the pull request: https://github.com/apache/couchdb/pull/185#issuecomment-37811517 @andywenk updated opening note and git clone url to point to this repo since this works on main couchdb --- 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-1202) Function 'require' undefined in reduce functions, cannot require CommonJS module
[
https://issues.apache.org/jira/browse/COUCHDB-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937800#comment-13937800
]
James Dingwall commented on COUCHDB-1202:
-
The ability to require() in reduce functions still seems to be broken in
CouchDB 1.5.0. Is this an oversight of this bug or is there a good reason not
to support require() in reduce and this should be closed as won't fix?
[Mon, 17 Mar 2014 13:27:51 GMT] [info] [0.5226.0] OS Process #Port0.7704
Log :: function raised exception (new ReferenceError(require is not defined,
undefined, 11))
Function 'require' undefined in reduce functions, cannot require CommonJS
module
Key: COUCHDB-1202
URL: https://issues.apache.org/jira/browse/COUCHDB-1202
Project: CouchDB
Issue Type: Bug
Components: JavaScript View Server
Affects Versions: 1.1
Environment: Mac OS X 10.6.8, CouchDB 1.1.0 (homebrew), Erlang R14B03
Reporter: Gabor Ratky
Priority: Minor
Labels: commonjs, reduce, views
Attachments: reduce_lib.patch
CouchDB 1.1.0 views can require CommonJS modules according to the Modules
1.1.1 specification when defined in the design document under views/lib. In
CouchDB 1.1.0 this works in map functions, but the require is undefined in
reduce functions. See the shell transcript along with the design document and
log output. Also available at [1].
ddoc.json:
{
views: {
lib: {
foo: exports.bar = 42;
},
test: {
map: function(doc) { emit(doc._id, require('views/lib/foo').bar);
},
reduce: function (keys, values, rereduce) { return
require('views/lib/foo').bar; }
}
}
}
require_test.sh:
$ curl http://localhost:5984
{couchdb:Welcome,version:1.1.0}
$ curl -X PUT http://localhost:5984/reduce_test
{ok:true}
$ curl -X PUT http://localhost:5984/reduce_test/_design/test --data @ddoc.json
{ok:true,id:_design/test,rev:1-5a587aeb82027657db334265037a4692}
$ curl -X POST http://localhost:5984/reduce_test -H Content-Type:
application/json -d '{}'
{ok:true,id:cd5869297d813d45d3e9f8016f001834,rev:1-967a00dff5e02add41819138abb3284d}
$ curl
http://localhost:5984/reduce_test/_design/test/_view/test?reduce=false;
{total_rows:1,offset:0,rows:[
{id:cd5869297d813d45d3e9f8016f001834,key:cd5869297d813d45d3e9f8016f001834,value:42}
]}
$ curl http://localhost:5984/reduce_test/_design/test/_view/test;
{rows:[
{key:null,value:null}
]}
^^^ Expected {key:null,value:42}
couch.log:
[info] [0.313.0] OS Process #Port0.2368 Log :: function raised exception
(new ReferenceError(require is not defined, ))
[info] [0.14096.0] 127.0.0.1 - - 'GET' /reduce_test/_design/test/_view/test
200
[1] https://gist.github.com/1049231
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[GitHub] couchdb pull request: My first couch plugin readme improvements
GitHub user marianoguerra opened a pull request: https://github.com/apache/couchdb/pull/186 My first couch plugin readme improvements rephrase the opening note and update git clone url. You can merge this pull request into a Git repository by running: $ git pull https://github.com/marianoguerra/couchdb my-first-couch-plugin-readme-typos Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb/pull/186.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 #186 commit 868e17114cff46db38791c5abb382e465722ccbd Author: Mariano Guerra luismarianogue...@gmail.com Date: 2014-03-17T12:51:15Z update opening note commit 266020fe541e46150f0fecd9df0ef3ab629be341 Author: Mariano Guerra luismarianogue...@gmail.com Date: 2014-03-17T12:52:14Z update clone command to clone from github repo since this already works on main couchdb. --- 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: My first couch plugin readme improvements
Github user asfgit closed the pull request at: https://github.com/apache/couchdb/pull/186 --- 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-1202) Function 'require' undefined in reduce functions, cannot require CommonJS module
[
https://issues.apache.org/jira/browse/COUCHDB-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937861#comment-13937861
]
Alexander Shorin commented on COUCHDB-1202:
---
Not with current query server protocol, but we have plans to improve it.
Function 'require' undefined in reduce functions, cannot require CommonJS
module
Key: COUCHDB-1202
URL: https://issues.apache.org/jira/browse/COUCHDB-1202
Project: CouchDB
Issue Type: Bug
Components: JavaScript View Server
Affects Versions: 1.1
Environment: Mac OS X 10.6.8, CouchDB 1.1.0 (homebrew), Erlang R14B03
Reporter: Gabor Ratky
Priority: Minor
Labels: commonjs, reduce, views
Attachments: reduce_lib.patch
CouchDB 1.1.0 views can require CommonJS modules according to the Modules
1.1.1 specification when defined in the design document under views/lib. In
CouchDB 1.1.0 this works in map functions, but the require is undefined in
reduce functions. See the shell transcript along with the design document and
log output. Also available at [1].
ddoc.json:
{
views: {
lib: {
foo: exports.bar = 42;
},
test: {
map: function(doc) { emit(doc._id, require('views/lib/foo').bar);
},
reduce: function (keys, values, rereduce) { return
require('views/lib/foo').bar; }
}
}
}
require_test.sh:
$ curl http://localhost:5984
{couchdb:Welcome,version:1.1.0}
$ curl -X PUT http://localhost:5984/reduce_test
{ok:true}
$ curl -X PUT http://localhost:5984/reduce_test/_design/test --data @ddoc.json
{ok:true,id:_design/test,rev:1-5a587aeb82027657db334265037a4692}
$ curl -X POST http://localhost:5984/reduce_test -H Content-Type:
application/json -d '{}'
{ok:true,id:cd5869297d813d45d3e9f8016f001834,rev:1-967a00dff5e02add41819138abb3284d}
$ curl
http://localhost:5984/reduce_test/_design/test/_view/test?reduce=false;
{total_rows:1,offset:0,rows:[
{id:cd5869297d813d45d3e9f8016f001834,key:cd5869297d813d45d3e9f8016f001834,value:42}
]}
$ curl http://localhost:5984/reduce_test/_design/test/_view/test;
{rows:[
{key:null,value:null}
]}
^^^ Expected {key:null,value:42}
couch.log:
[info] [0.313.0] OS Process #Port0.2368 Log :: function raised exception
(new ReferenceError(require is not defined, ))
[info] [0.14096.0] 127.0.0.1 - - 'GET' /reduce_test/_design/test/_view/test
200
[1] https://gist.github.com/1049231
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Reopened] (COUCHDB-2140) DBname suggestion on replication page is extremely slow
[ https://issues.apache.org/jira/browse/COUCHDB-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Shorin reopened COUCHDB-2140: --- Sorry, no. It has the same issue that was for database search field - request per entered char. DBname suggestion on replication page is extremely slow --- Key: COUCHDB-2140 URL: https://issues.apache.org/jira/browse/COUCHDB-2140 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin Assignee: Sue Lockwood I have to wait for 5-10 seconds to receive the suggestion. Futon shows it instantly. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2140) DBname suggestion on replication page is extremely slow
[ https://issues.apache.org/jira/browse/COUCHDB-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937876#comment-13937876 ] Alexander Shorin commented on COUCHDB-2140: --- Just tested with master [HEAD|https://github.com/apache/couchdb/commit/304c144606594d16b74bfac9e6d9c61fdfbc4264]. DBname suggestion on replication page is extremely slow --- Key: COUCHDB-2140 URL: https://issues.apache.org/jira/browse/COUCHDB-2140 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin Assignee: Sue Lockwood I have to wait for 5-10 seconds to receive the suggestion. Futon shows it instantly. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2203) Hang when uploading a JSON document
[
https://issues.apache.org/jira/browse/COUCHDB-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937881#comment-13937881
]
Robert Newson commented on COUCHDB-2203:
This worked for me first time, with default settings. (304c144, OS X 10.9.2)
curl -XPUT localhost:5984/db1/foo -d @body.debug
{ok:true,id:foo,rev:1-db15615f41065c61ef2c947a3e6816bb}
I'll note that -T body.debug is better, as -d is not 8-bit safe.
Hang when uploading a JSON document
---
Key: COUCHDB-2203
URL: https://issues.apache.org/jira/browse/COUCHDB-2203
Project: CouchDB
Issue Type: Bug
Security Level: public(Regular issues)
Components: Database Core
Affects Versions: 1.5.0
Reporter: Kirill Pertsev
Attachments: body.debug
CouchDB 1.5.0 MacOS/X build from the website. OS/X is 10.9.2
I'm building a couchapp using node.couchapp.js. The size of the couchapp is
about 4MB, and I can not upload it to the Couch. I've dumped the JSON itself
and tried to PUT it with CURL, without any luck either.
JSON is attached.
Upload with
curl -XPUT http://root:root123@localhost:5984/rmaze2/_design/rmaze-kanso -H
Content-Type: application/json -d @body.debug
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[GitHub] couchdb pull request: Improved Query Options
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/180#discussion_r10659543
--- Diff: src/fauxton/app/addons/documents/views.js ---
@@ -1090,20 +1117,48 @@ function(app, FauxtonAPI, Components, Documents,
Databases, pouchdb, resizeColum
this.hasReduce = hasReduce;
this.render();
},
+getKeys: function(val){
+ var keys = val.value.replace(/\s/g,);
+
+ var regKeys = keys.match(/(\[.*?\])/g);
--- End diff --
@garrensmith the idea is ok, but if I just copy my `keys` value to Fauxton
without any braces striping it'll fail to search anything.
And even if so, here is another test case:
[[1,2,3]],[[4,5,6]].match(/(\[.*?\])/g)
[[[1,2,3], [[4,5,6]]
---
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-2203) Hang when uploading a JSON document
[ https://issues.apache.org/jira/browse/COUCHDB-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937890#comment-13937890 ] Alexander Shorin commented on COUCHDB-2203: --- [~rnewson] COUCHDB-1986 doesn't happens on OSX for master and 1.6.x branches due to multipart parser improvements. Hang when uploading a JSON document --- Key: COUCHDB-2203 URL: https://issues.apache.org/jira/browse/COUCHDB-2203 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Database Core Affects Versions: 1.5.0 Reporter: Kirill Pertsev Attachments: body.debug CouchDB 1.5.0 MacOS/X build from the website. OS/X is 10.9.2 I'm building a couchapp using node.couchapp.js. The size of the couchapp is about 4MB, and I can not upload it to the Couch. I've dumped the JSON itself and tried to PUT it with CURL, without any luck either. JSON is attached. Upload with curl -XPUT http://root:root123@localhost:5984/rmaze2/_design/rmaze-kanso -H Content-Type: application/json -d @body.debug -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: Improved Query Options
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/180#discussion_r10659855
--- Diff: src/fauxton/app/addons/documents/views.js ---
@@ -1090,20 +1117,48 @@ function(app, FauxtonAPI, Components, Documents,
Databases, pouchdb, resizeColum
this.hasReduce = hasReduce;
this.render();
},
+getKeys: function(val){
+ var keys = val.value.replace(/\s/g,);
+
+ var regKeys = keys.match(/(\[.*?\])/g);
+ if (regKeys) {
+keys = regKeys;
+ } else {
+keys = keys.split(',');
+ }
+
+ keys = _.map(keys, function (key) { return JSON.parse(key); });
--- End diff --
How about to a bit simplify the logic: try `JSON.parse(val.value)` first.
If it fails - wrap it with `[` and `]` and try again? No need to regex, no need
to map and make multiple `JSON.parse` calls.
---
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 navigating back to previous pag...
GitHub user robertkowalski opened a pull request: https://github.com/apache/couchdb/pull/187 Fauxton: fix navigating back to previous page Fixes #COUCHDB-2169 Had this still on the stash from sunday. :) You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertkowalski/couchdb 2169-noAccess-page Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb/pull/187.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 #187 commit 6f23ad403d8669abedc5f090284450793b2a77e5 Author: Robert Kowalski r...@kowalski.gd Date: 2014-03-17T17:20:44Z Fauxton: fix navigating back to previous page Fixes #COUCHDB-2169 --- 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-2169) There is no way back from noAccess page
[ https://issues.apache.org/jira/browse/COUCHDB-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938067#comment-13938067 ] ASF GitHub Bot commented on COUCHDB-2169: - GitHub user robertkowalski opened a pull request: https://github.com/apache/couchdb/pull/187 Fauxton: fix navigating back to previous page Fixes #COUCHDB-2169 Had this still on the stash from sunday. :) You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertkowalski/couchdb 2169-noAccess-page Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb/pull/187.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 #187 commit 6f23ad403d8669abedc5f090284450793b2a77e5 Author: Robert Kowalski r...@kowalski.gd Date: 2014-03-17T17:20:44Z Fauxton: fix navigating back to previous page Fixes #COUCHDB-2169 There is no way back from noAccess page --- Key: COUCHDB-2169 URL: https://issues.apache.org/jira/browse/COUCHDB-2169 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin If you somehow get on noAccess page, you couldn't click on Back button since in browser history the previous url is that one which redirected you on noAccess page. So actually you're trapped inside and have to navigate to prev-prev page in history. Also it would be awesome if noAccess page will provide url to way back without using browser history. -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: Fauxton: fix navigating back to previous pag...
Github user kxepal commented on the pull request: https://github.com/apache/couchdb/pull/187#issuecomment-37845307 +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. ---
[jira] [Commented] (COUCHDB-2169) There is no way back from noAccess page
[ https://issues.apache.org/jira/browse/COUCHDB-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938088#comment-13938088 ] ASF subversion and git services commented on COUCHDB-2169: -- Commit 6f23ad403d8669abedc5f090284450793b2a77e5 in couchdb's branch refs/heads/master from [~robertkowalski] [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=6f23ad4 ] Fauxton: fix navigating back to previous page Fixes #COUCHDB-2169 There is no way back from noAccess page --- Key: COUCHDB-2169 URL: https://issues.apache.org/jira/browse/COUCHDB-2169 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin If you somehow get on noAccess page, you couldn't click on Back button since in browser history the previous url is that one which redirected you on noAccess page. So actually you're trapped inside and have to navigate to prev-prev page in history. Also it would be awesome if noAccess page will provide url to way back without using browser history. -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: Fauxton: fix navigating back to previous pag...
Github user deathbearbrown commented on the pull request: https://github.com/apache/couchdb/pull/187#issuecomment-37846124 Pushed! Could you close this and the jira? You're the best Robert! :purple_heart: --- 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] [Resolved] (COUCHDB-2169) There is no way back from noAccess page
[ https://issues.apache.org/jira/browse/COUCHDB-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Shorin resolved COUCHDB-2169. --- Resolution: Fixed There is no way back from noAccess page --- Key: COUCHDB-2169 URL: https://issues.apache.org/jira/browse/COUCHDB-2169 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin If you somehow get on noAccess page, you couldn't click on Back button since in browser history the previous url is that one which redirected you on noAccess page. So actually you're trapped inside and have to navigate to prev-prev page in history. Also it would be awesome if noAccess page will provide url to way back without using browser history. -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: Fauxton: fix navigating back to previous pag...
Github user asfgit closed the pull request at: https://github.com/apache/couchdb/pull/187 --- 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-2169) There is no way back from noAccess page
[ https://issues.apache.org/jira/browse/COUCHDB-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938146#comment-13938146 ] ASF GitHub Bot commented on COUCHDB-2169: - Github user asfgit closed the pull request at: https://github.com/apache/couchdb/pull/187 There is no way back from noAccess page --- Key: COUCHDB-2169 URL: https://issues.apache.org/jira/browse/COUCHDB-2169 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin If you somehow get on noAccess page, you couldn't click on Back button since in browser history the previous url is that one which redirected you on noAccess page. So actually you're trapped inside and have to navigate to prev-prev page in history. Also it would be awesome if noAccess page will provide url to way back without using browser history. -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: COUCHDB-2164 encoded attachment name
Github user deathbearbrown closed the pull request at: https://github.com/apache/couchdb/pull/179 --- 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-2164) Attachments with slashes in name escaped incorrectly
[ https://issues.apache.org/jira/browse/COUCHDB-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938160#comment-13938160 ] ASF GitHub Bot commented on COUCHDB-2164: - Github user deathbearbrown closed the pull request at: https://github.com/apache/couchdb/pull/179 Attachments with slashes in name escaped incorrectly Key: COUCHDB-2164 URL: https://issues.apache.org/jira/browse/COUCHDB-2164 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin Assignee: Sue Lockwood Attachment name: /foo/bar/baz URL in Futon: http://localhost:5984/test/doc/%2ffoo%2fbar%2fbaz URL in Fauxton: http://localhost:5984/test/doc//foo/bar/baz -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (COUCHDB-2170) Weird error if anonymous user will try to create new admin
[
https://issues.apache.org/jira/browse/COUCHDB-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Shorin resolved COUCHDB-2170.
---
Resolution: Fixed
Weird error if anonymous user will try to create new admin
--
Key: COUCHDB-2170
URL: https://issues.apache.org/jira/browse/COUCHDB-2170
Project: CouchDB
Issue Type: Bug
Security Level: public(Regular issues)
Components: Fauxton
Reporter: Alexander Shorin
Assignee: Sue Lockwood
When admin party is fixed and anonymous user trying to create new admin he'll
get the next error: {{Could not create admin. Reason[object Object].}}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[GitHub] couchdb pull request: Some work on Config
Github user robertkowalski closed the pull request at: https://github.com/apache/couchdb/pull/174 --- 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-2008) CI: Create repeatable images for different operating system configurations
[ https://issues.apache.org/jira/browse/COUCHDB-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938780#comment-13938780 ] Christopher Rigor commented on COUCHDB-2008: I had texlive-latex-base but I needed to install texlive-latex-recommended and texlive-latex-extra as well. Jan, how did you install latex on the current VMs? From APT or source? CI: Create repeatable images for different operating system configurations -- Key: COUCHDB-2008 URL: https://issues.apache.org/jira/browse/COUCHDB-2008 Project: CouchDB Issue Type: New Feature Components: Infrastructure Reporter: Jan Lehnardt Dave suggests to look into Ansible Packer to create images for CI. The idea would be to run these configurations on the CI server and controlled by Jenkins. It should also be possible to set up a configuration locally that matches the CI box exactly, so one can do debugging under the same circumstances the CI server runs tests. The requirement for now is that it all needs to work with a set of VMs that we have SSH access to, but we don’t manage the host. I’m not too familiar with all the automation and VM image packaging tools, so I don’t know if one or another is useful in that context or not. -- This message was sent by Atlassian JIRA (v6.2#6252)
