[jira] [Closed] (COUCHDB-602) Cannot use NFS for storage
[ https://issues.apache.org/jira/browse/COUCHDB-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-602. - Resolution: Not A Problem Cannot use NFS for storage -- Key: COUCHDB-602 URL: https://issues.apache.org/jira/browse/COUCHDB-602 Project: CouchDB Issue Type: Bug Components: Test Suite Affects Versions: 0.10 Reporter: Nils Breunese Attachments: error.gz Our hosting provider claims they cannot upgrade our CouchDB installation from version 0.9.1 to 0.10 as the test suite for 0.10 is failing. This is a translation from their report: CouchDB can't handle having its data directory on NFS. It seems CouchDB tries to do this: 1 mkdir test 2 start process X with fd under test/foo 3 do the work 4 rm test/foo 5 rmdir test 6 kill process X When test/ is on NFS: In step 4 an open file is being removed. NFS doesn't really support this and the workaround is that the client implementation does mv file .nfsXXX However, the 'rmdir test' in step 5 then cannot succeed anymore, since the directory is not empty. This eventually causes CouchDB to crash. In earlier versions of CouchDB the open/rm/rmdir/kill order may have been different, for instance open/rm/kill/rmdir. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1389) Improve JS CLI test error reports
[ https://issues.apache.org/jira/browse/COUCHDB-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1389. -- Resolution: Fixed Fix Version/s: 1.3 Fixed in 32a1113. Paul, if you want to apply your one-liner to 1.2 to help with debugging tests during voting or for the future of 1.2.x that's fine by me. Just update the Fix Version/s if you do. Improve JS CLI test error reports - Key: COUCHDB-1389 URL: https://issues.apache.org/jira/browse/COUCHDB-1389 Project: CouchDB Issue Type: Improvement Reporter: Paul Joseph Davis Fix For: 1.3 Attachments: COUCHDB-1389.patch About to attach a simple patch that gives better error output when JS tests fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1338) JS CLI test suite: have CouchDB start with port=0
[ https://issues.apache.org/jira/browse/COUCHDB-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1338. -- Resolution: Fixed Fixed in d20e792..127cbe3 JS CLI test suite: have CouchDB start with port=0 -- Key: COUCHDB-1338 URL: https://issues.apache.org/jira/browse/COUCHDB-1338 Project: CouchDB Issue Type: Improvement Components: Test Suite Affects Versions: 1.3 Reporter: Jan Lehnardt Assignee: Randall Leeds Priority: Blocker Fix For: 1.3 Attachments: v1-0001-COUCHDB-1338-run-js-tests-with-port-0.patch, v1-0002-Fix-JS-tests-for-COUCHDB-1338.patch, v2-0001-COUCHDB-1338-run-js-tests-with-port-0.patch, v2-0002-Fix-JS-tests-for-COUCHDB-1338.patch The JS CLI test suite that now runs with make check (post 1.2.x master only) starts CouchDB using make dev utils/run -b and stops it with utils/run -d. One issue with this is that one might have CouchDB already running on the default port 5984. The suggestion here is to start CouchDB with an additional .ini file that sets the port number to 0 to let the TCP stack figure out a free port for us. The tests then need to be updated to discover the automatic port using the couch.uri file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-410) JavaScript errors in validate_doc_update should be handled more gracefully
[
https://issues.apache.org/jira/browse/COUCHDB-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-410.
-
Resolution: Fixed
Incorporated into COUCHDB-111.
JavaScript errors in validate_doc_update should be handled more gracefully
--
Key: COUCHDB-410
URL: https://issues.apache.org/jira/browse/COUCHDB-410
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 0.9.1, 0.10
Reporter: Jason Davies
Fix For: 1.3
Attachments: util.js.diff,
v1-0001-COUCHDB-410-graceful-validate_doc_update-errors.patch,
v2-0001-COUCHDB-410-graceful-validate_doc_update-errors.patch
For example, if I create validate_doc_update:
function (oldDoc, newDoc, userCtx) {
doc.foo;
}
I am greeted by an OS process timed out message. In the logs, all I see is:
OS Process :: Error converting object to JSON: TypeError: {Array:function (v)
{var buf = [];for (var i = 0; i v.length; i++)
{buf.push(toJSON(v[i]));}return [ + buf.join(,) + ];}, Boolean:function
(v) {return v.toString();}, Date:function (v) {var f = function (n) {return n
10 ? 0 + n : n;};return \ + v.getUTCFullYear() + - +
f(v.getUTCMonth() + 1) + - + f(v.getUTCDate()) + T + f(v.getUTCHours()) +
: + f(v.getUTCMinutes()) + : + f(v.getUTCSeconds()) + Z\;},
Number:function (v) {return isFinite(v) ? v.toString() : null;},
Object:function (v) {if (v === null) {return null;}var buf = [];for (var k
in v) {if (!v.hasOwnProperty(k) || typeof k !== string || v[k] ===
undefined) {continue;}buf.push(toJSON(k, val) + : + toJSON(v[k]));}return
{ + buf.join(,) + };}, String:function (v) {if
(/[\\\x00-\x1f]/.test(v)) {v = v.replace(/([\x00-\x1f\\])/g, function (a,
b) {var c = subs[b];if (c) {return c;}c = b.charCodeAt();return \\u00 +
Math.floor(c / 16).toString(16) + (c % 16).toString(16);});}return \ + v +
\;}}[val != null ? val.constructor.name : Object] is not a function
When really the problem is a ReferenceError (I should have used newDoc.foo or
oldDoc.foo). The attached patch modifies toJSON() in utils.js so that it
converts anything that isn't a String, Array, Date, Object etc. into a
String. This makes the error appear in the popup in Futon when saving.
This isn't necessarily the best thing to do as it modifies the semantics of
toJSON(), and also we might want to keep the exception info in the logs, and
not propagate it to the user. Perhaps it would be better to modify
respond(obj) to produce a better error message in the logs (simply adding
something that tried to log obj.toString() would suffice).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-111) Javascript Error Tracebacks
[ https://issues.apache.org/jira/browse/COUCHDB-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-111. - Resolution: Fixed Fix Version/s: 1.3 Assignee: (was: Chris Anderson) Fixed by 5f55e9f..0c619ed Javascript Error Tracebacks --- Key: COUCHDB-111 URL: https://issues.apache.org/jira/browse/COUCHDB-111 Project: CouchDB Issue Type: Improvement Components: JavaScript View Server Reporter: Paul Joseph Davis Fix For: 1.3 Attachments: v1-0001-COUCHDB-111-handle-multiple-files-in-couchjs.patch, v1-0002-COUCHDB-111-JavaScript-Error-Tracebacks.patch, v2-0001-COUCHDB-111-handle-multiple-files-in-couchjs.patch, v2-0002-COUCHDB-111-JavaScript-Error-Tracebacks.patch, v3-0001-COUCHDB-111-handle-multiple-files-in-couchjs.patch, v3-0002-COUCHDB-111-JavaScript-Error-Tracebacks.patch, v4-0001-COUCHDB-111-handle-multiple-files-in-couchjs.patch, v4-0002-COUCHDB-111-JavaScript-Error-Tracebacks.patch, v4-0003-COUCHDB-111-CommonJS-module-names-in-tracebacks.patch Improve the errors reported by the javascript view server to provide a more friendly error report when something goes wrong. Ideally a complete traceback but anything would be better than the erlang traceback informing the user that the server died. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1383) Futon view editor won't allow you to save original view (reverting) after saving a revision
[ https://issues.apache.org/jira/browse/COUCHDB-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1383. -- Resolution: Fixed Fix Version/s: 1.3 1.2 Thanks, Sam. Fixed 851e041..ea01eaa 1.2.x - 1.2.x 5cece68..ce48342 master - master Futon view editor won't allow you to save original view (reverting) after saving a revision --- Key: COUCHDB-1383 URL: https://issues.apache.org/jira/browse/COUCHDB-1383 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.1, 1.2 Reporter: Sam Bisbee Priority: Minor Fix For: 1.2, 1.3 Attachments: 0001-Fixing-COUCHDB-1383-update-the-in-memory-state-of-th.patch Steps to reproduce: 1. Load a view that was already created. 2. Change the view in some way (add space or whatever). 3. Click Save. 4. Revert your change (remove the space or whatever). Expected Result: You should be able to click Save, thereby essentially reverting back to the original view code. Actual Result: You cannot click Save - the button is still disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-960) Have configure work without flags on Debian/Ubuntu
[
https://issues.apache.org/jira/browse/COUCHDB-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-960.
-
Resolution: Not A Problem
Fix Version/s: 1.1.1
As of CouchDB 1.1.1 I think this works fine on sufficiently new Ubuntu/Debian.
We test for 3 different versions of spidermonkey and do so in a way that should
work with any properly configured paths.
I'll open a new ticket to support js-config at some point, but I think there
were issues with it last I checked (some options when building spidermonkey
break js-config, so it cannot be relied upon to exist).
Have configure work without flags on Debian/Ubuntu
--
Key: COUCHDB-960
URL: https://issues.apache.org/jira/browse/COUCHDB-960
Project: CouchDB
Issue Type: Wish
Components: Build System
Affects Versions: 1.0.1
Reporter: A. Bram Neijt
Priority: Minor
Fix For: 1.1.1
On a Debian/Ubuntu system, you have to help configure to find the JS library:
xulrunner_gre_version=`xulrunner --gre-version`
./configure
--with-js-lib=/usr/lib/xulrunner-devel-${xulrunner_gre_version}/lib/
--with-js-include=/usr/lib/xulrunner-devel-${xulrunner_gre_version}/include/
make
It seems that Yelp is able to do this on it's own using special m4 macros[1].
I would like the CouchDB configure script to be able to find the JS library
without requiring extra arguments.
[1]
http://www.google.com/codesearch/p?#ErvFMsc8kPE/pub/GNOME/desktop/2.16/2.16.0/sources/yelp-2.16.0.tar.gz|U-t_e2pgMiw/yelp-2.16.0/configure.in
http://www.google.com/codesearch/p?#ErvFMsc8kPE/pub/GNOME/desktop/2.16/2.16.0/sources/yelp-2.16.0.tar.gz|U-t_e2pgMiw/yelp-2.16.0/m4/gecko.m4d=8
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-336) Would like errors in map function to be reported to client
[
https://issues.apache.org/jira/browse/COUCHDB-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-336.
-
Resolution: Won't Fix
No update in well over a year. I looked into this in light of my recent
attempts to clean up JS error reporting. I think it's debatable whether or not
this type of error should be sent to the client at all.
It's not a matter of evalcx not reporting the error. The error is reported,
it's just not reported through to HTTP. Doing so would require a major change
to the way errors behave in the map/reduce indexer. Since re-requesting a view
like this does not cause the error to be logged in the couch.log if the index
is already built, in order to really change this we would have to cause the
whole index to be invalid whenever any errors are throw while mapping any
documents. That seems to me like a nasty thing to do to people.
Would like errors in map function to be reported to client
--
Key: COUCHDB-336
URL: https://issues.apache.org/jira/browse/COUCHDB-336
Project: CouchDB
Issue Type: Wish
Environment: svn trunk 0.10.0a768591
Reporter: Brian Candler
Priority: Minor
At the moment, if a runtime error occurs in a map function, the document is
silently excluded from the view and the client is none the wiser.
$ curl -X PUT http://127.0.0.1:5984/test
{ok:true}
$ curl -d '{foo:bar}' -X PUT http://127.0.0.1:5984/test/doc1
{ok:true,id:doc1,rev:1-3413565576}
$ curl -d '{food:bar}' -X PUT http://127.0.0.1:5984/test/doc2
{ok:true,id:doc2,rev:1-2088327893}
# Example 1: map function calls undefined function
$ curl -d '{map:function(doc) { emitt(null,null); }}' -H 'Content-Type:
application/json' -X POST http://127.0.0.1:5984/test/_temp_view
{total_rows:0,rows:[]}
# Example 2: map function attempts to emit 'undefined'
$ curl -d '{map:function(doc) { emit(doc._id,doc.foo); }}' -H
'Content-Type: application/json' -X POST http://127.0.0.1:5984/test/_temp_view
{total_rows:1,offset:0,rows:[
{id:doc1,key:doc1,value:bar}
]}
Of course, errors are available in the server log:
[Tue, 28 Apr 2009 08:40:39 GMT] [info] [0.1276.0] OS Process Log Message:
function raised exception (ReferenceError: emitt is not defined) with doc._id
doc1
[Tue, 28 Apr 2009 08:43:44 GMT] [info] [0.1276.0] OS Process Log Message:
function raised exception (Cannot encode 'undefined' value as JSON) with
doc._id doc2
But the client cannot see these, and worse, gets what appears to be a valid
result set.
I think there are two cases to consider.
- in temporary views, it ought to be easy to do something: e.g. (1) return
the full set of failed docs with their errors, or (2) return a count of
failed docs, or (3) just abort on the first error
- in permanent views, it might also be useful to return this information, but
it could be expensive to persist. Also, when you're querying for key X you
might not want to see a whole load of errors for unrelated docs. An error
count might be OK though, similar to total_rows.
The current behaviour may be useful, although I personally wouldn't want to
rely on it, especially as it generates errors in the log. That is, I would
rather be forced to rewrite example 2 as
function(doc) { if (doc.foo) { emit(doc._id, doc.foo); } }
or
function(doc) { emit(doc._id, doc.foo || null); }
as appropriate.
Workaround: users can manually wrap each of their map functions in a catcher
which emits a sentinel key/value pair containing the error. However they
would still have to query the key range which includes the error messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1121) Signup error is shown after creating an administrator account
[
https://issues.apache.org/jira/browse/COUCHDB-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-1121.
--
Resolution: Cannot Reproduce
Fix Version/s: 1.1.1
Cann't reproduce on 1.1.1.
Signup error is shown after creating an administrator account
-
Key: COUCHDB-1121
URL: https://issues.apache.org/jira/browse/COUCHDB-1121
Project: CouchDB
Issue Type: Bug
Components: Futon
Affects Versions: 1.0.2
Environment: Mac OS X 10.6.7, Max OS X 10.7.preview2, Ubuntu 10.10,
all systems are running in x86_64 mode.
Reporter: Denny Trebbin
Priority: Minor
Fix For: 1.1.1
Attachments: Apache CouchDB - Futon Overview - Google Chrome_001.png,
couch.log
A fresh new installation of CouchDB comes with no pre defined admin account.
Futon shows a little message and provides a Link to fix this.
If I try to add an user named as root and give him a password then Futon will
show an error after saving this account.
Signup error: {gen_server,call,
[couch_query_servers,
{get_proc,{doc,_design/_auth,
{1,
[196,79,177,42,38,118,212,129,210,53,82,48,
146,224,206,196]},
{[{language,javascript},
{validate_doc_update,
\nfunction(newDoc, oldDoc, userCtx) {\n
if (newDoc._deleted === true) {\n// allow deletes by
admins and matching users\n// without checking the other fields\n
if ((userCtx.roles.indexOf('_admin') !== -1) ||\n
(userCtx.name == oldDoc.name)) {\nreturn;\n} else
{\nthrow({forbidden: 'Only admins may delete other user
docs.'});\n}\n}\n\nif ((oldDoc oldDoc.type !==
'user') || newDoc.type !== 'user') {\nthrow({forbidden :
'doc.type must be user'});\n} // we only allow user docs for now\n\n
if (!newDoc.name) {\nthrow({forbidden: 'doc.name is
required'});\n}\n\nif (newDoc.roles
!isArray(newDoc.roles)) {\nthrow({forbidden: 'doc.roles must be
an array'});\n}\n\nif (newDoc._id !== ('org.couchdb.user:' +
newDoc.name)) {\nthrow({\nforbidden: 'Doc ID must
be of the form org.couchdb.user:name'\n});\n}\n\n
if (oldDoc) { // validate all updates\nif (oldDoc.name !==
newDoc.name) {\nthrow({forbidden: 'Usernames can not be
changed.'});\n}\n}\n\nif (newDoc.password_sha
!newDoc.salt) {\nthrow({\nforbidden: 'Users with
password_sha must have a salt.' +\n'See
/_utils/script/couch.js for example code.'\n});\n}\n\n
if (userCtx.roles.indexOf('_admin') === -1) {\nif (oldDoc) {
// validate non-admin updates\nif (userCtx.name !==
newDoc.name) {\nthrow({\n
forbidden: 'You may only update your own user document.'\n
});\n}\n// validate role updates\n
var oldRoles = oldDoc.roles.sort();\nvar newRoles =
newDoc.roles.sort();\n\nif (oldRoles.length !==
newRoles.length) {\nthrow({forbidden: 'Only _admin may
edit roles'});\n}\n\nfor (var i = 0; i
oldRoles.length; i++) {\nif (oldRoles[i] !== newRoles[i])
{\nthrow({forbidden: 'Only _admin may edit
roles'});\n}\n}\n} else if
(newDoc.roles.length 0) {\nthrow({forbidden: 'Only _admin
may set roles'});\n}\n}\n\n// no system roles in
users db\nfor (var i = 0; i newDoc.roles.length; i++) {\n
if (newDoc.roles[i][0] === '_') {\nthrow({\n
forbidden:\n'No system roles (starting with
underscore) in users db.'\n});\n}\n}\n\n
// no system names as names\nif (newDoc.name[0] === '_') {\n
throw({forbidden: 'Username may not start with underscore.'});\n
}\n}\n}]},
[],false,[]},
{_design/_auth,
1-c44fb12a2676d481d235523092e0cec4}}]}
The admin account will be created and I can log in with the admin account
root. This problem showed up every time I installed
[jira] [Closed] (COUCHDB-1339) JS CLI Test Suite: use shell trap to catch dying beam processes during test runs
[ https://issues.apache.org/jira/browse/COUCHDB-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1339. -- Resolution: Fixed 8f0b4e6..2921c78 master - master JS CLI Test Suite: use shell trap to catch dying beam processes during test runs Key: COUCHDB-1339 URL: https://issues.apache.org/jira/browse/COUCHDB-1339 Project: CouchDB Issue Type: Improvement Components: Test Suite Affects Versions: 1.3 Reporter: Jan Lehnardt Assignee: Randall Leeds Priority: Blocker Fix For: 1.3 The JS CLI test suite that now runs with make check (post 1.2.x master only) starts CouchDB using make dev utils/run -b and stops it with utils/run -d. One issue with this is that the CouchDB process might terminate in the background. The shell trap command allows the test suite to act on that accordingly, otherwise the test suite would just freeze. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1042) make libcurl a soft (optional) dependency
[ https://issues.apache.org/jira/browse/COUCHDB-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1042. -- Resolution: Fixed Resolved again by 39d81d5..bf7c74e make libcurl a soft (optional) dependency - Key: COUCHDB-1042 URL: https://issues.apache.org/jira/browse/COUCHDB-1042 Project: CouchDB Issue Type: Improvement Components: Build System Affects Versions: 1.0.1 Reporter: Randall Leeds Assignee: Randall Leeds Priority: Minor Fix For: 1.2, 2.0 Attachments: 0001-make-cURL-an-optional-dependency.patch, 0001-no-lcurl-if-no-curl-support.patch, curl_as_soft_dep.patch, curl_as_soft_dep_v2.patch CouchDB currently uses libcurl only in couchjs to expose HTTP client functions to the JavaScript environment. This functionality is used by the JavaScript unit tests. For idempotent views it is discouraged to perform I/O in a view function. Therefore, I propose that libcurl be made an optional dependency, automatically detected at build time, and a flag added to couchjs so it can be explicitly enabled in the unit tests (but disabled, by default, for the query server). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1152) Windows ICU DLL version is hardcoded to 4.2 in makefiles
[ https://issues.apache.org/jira/browse/COUCHDB-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1152. -- Resolution: Fixed Fix Version/s: (was: 1.0.4) (was: 1.1.1) 1.1.2 1.2 Fixed again: de0f784..d59d1c0 1.1.x - 1.1.x 7c303b9..4f2a079 1.2.x - 1.2.x e3651ec..1054f94 master - master Windows ICU DLL version is hardcoded to 4.2 in makefiles Key: COUCHDB-1152 URL: https://issues.apache.org/jira/browse/COUCHDB-1152 Project: CouchDB Issue Type: Improvement Components: Build System Environment: Windows only. Reporter: Dave Cottlehuber Priority: Trivial Labels: windows Fix For: 1.2, 1.1.2 Attachments: COUCHDB-1152_move_to_ICU-4_4_2.patch, COUCHDB-1152_move_to_ICU-4_4_2_diff_1.0.x.patch, COUCHDB-1152_remove_icu_version_dependency_diff_1.1.x.patch, COUCHDB-1152_remove_icu_version_dependency_diff_1.2.x.patch, COUCHDB-1152_remove_icu_version_dependency_diff_master.patch src/couchdb/priv/Makefile.am has hardcoded dependency on ICU DLL 4.2 which is untidy nor is it documented in INSTALL.Windows or release notes. Latest version, ICU 4.8 will be released end May 2011. Makefile should support recent versions of ICU where required, same as on unix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1232) trunk does not build with spidermonkey 1.7
[ https://issues.apache.org/jira/browse/COUCHDB-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1232. -- Resolution: Fixed Assignee: (was: Paul Joseph Davis) Fixed by Paul Davis in 4a6ac6. trunk does not build with spidermonkey 1.7 -- Key: COUCHDB-1232 URL: https://issues.apache.org/jira/browse/COUCHDB-1232 Project: CouchDB Issue Type: Improvement Components: Build System Affects Versions: 1.2 Environment: Gentoo Linux Reporter: James Marca Priority: Minor Fix For: 1.2 Original Estimate: 4h Remaining Estimate: 4h Original bug report: configure does not require spidermonkey 1.8.5, but trunk (1.2) failed to build without it. Trunk should fall back to a slightly older spidermonkey and configure definitely fails if you don't have either. However, by popular demand I'm told I should make trunk compile with 1.7 again, so I will. I'm changing this ticket to track that. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1350) run javascript unit tests on a random port
[ https://issues.apache.org/jira/browse/COUCHDB-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1350. -- Resolution: Duplicate Assignee: (was: Randall Leeds) run javascript unit tests on a random port -- Key: COUCHDB-1350 URL: https://issues.apache.org/jira/browse/COUCHDB-1350 Project: CouchDB Issue Type: Improvement Components: Test Suite Reporter: Randall Leeds Priority: Trivial -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1371) configure erroneously warns against using a new spidermonkey with old spidermonkeys
[ https://issues.apache.org/jira/browse/COUCHDB-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1371. -- Resolution: Fixed To https://git-wip-us.apache.org/repos/asf/couchdb.git 65c3961..3816108 1.1.x - 1.1.x 7aa74fc..b148b5b 1.2.x - 1.2.x f599ba7..ee00d81 master - master configure erroneously warns against using a new spidermonkey with old spidermonkeys --- Key: COUCHDB-1371 URL: https://issues.apache.org/jira/browse/COUCHDB-1371 Project: CouchDB Issue Type: Bug Reporter: Randall Leeds Assignee: Randall Leeds Priority: Minor Fix For: 1.2, 1.3, 1.1.2 Attachments: 0001-fix-bad-configure-warning-on-old-SpiderMonkey.patch Paul added the check for JSOPTION_ANONFUNFIX in 7ce9e103e, but js-1.7 doesn't have this constant so configure gives a warning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1367) When settings revs_limit on db - the db increases its update_seq counter when viewing stats - but not when getting changes
[ https://issues.apache.org/jira/browse/COUCHDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1367. -- Resolution: Not A Problem Assignee: (was: Bob Dionne) Closing as Not A Problem as per Robert Newson's last comment. If this is incorrect, please re-open with a compelling argument to change this behavior. When settings revs_limit on db - the db increases its update_seq counter when viewing stats - but not when getting changes -- Key: COUCHDB-1367 URL: https://issues.apache.org/jira/browse/COUCHDB-1367 Project: CouchDB Issue Type: Bug Components: HTTP Interface Affects Versions: 1.1.1 Environment: Any Reporter: Henrik Hofmeister Priority: Minor Labels: revs_limit If you put a number to _revs_limit on a db (to update it) - the http://host/dbname/ info document gets an increase in update_seq number - however the changes feed does not contain this change (while its not a change). This causes the update_seq in the dbinfo doc and the last seq in the changes feed to differ - which breaks any application depending on the update_seq number as the expected sequence size of the db (in my case - couchdb-lucene that will only respond to stale requests because it thinks its not up to date) I know this is an edge case - but still its something fairly fundamental - that clearly is not working as intended. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1363) callback invocation for docs added during couch_changes startup can be delayed by race condition
[ https://issues.apache.org/jira/browse/COUCHDB-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1363. -- Resolution: Fixed Fix Version/s: 1.1.2 1.0.4 Assignee: (was: Filipe Manana) Fixed. To https://git-wip-us.apache.org/repos/asf/couchdb.git 9c377a1..e82a0c9 1.0.x - 1.0.x c9b20f2..6a04e33 1.1.x - 1.1.x 7f9376c..1bbe619 1.2.x - 1.2.x 2d90a12..573a7bb master - master callback invocation for docs added during couch_changes startup can be delayed by race condition Key: COUCHDB-1363 URL: https://issues.apache.org/jira/browse/COUCHDB-1363 Project: CouchDB Issue Type: Bug Components: Database Core Affects Versions: 1.0.3, 1.1.1 Reporter: Randall Leeds Priority: Minor Fix For: 1.0.4, 1.2, 1.3, 1.1.2 Attachments: 0001-Fix-a-race-condition-starting-replications.patch After subscribing to notifications it's necessary to re-open the #db a so that the header points at all updates for which the updater notifier has already fired events. In practice, this is rarely problematic because the next change will cause everything to catch up, but if a quick burst of changes happens while, e.g., replication is starting the replication can go stale. Detected by intermittent replicator_db js test failures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-282) Abort views that have exceptions in the view server
[ https://issues.apache.org/jira/browse/COUCHDB-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-282. - Resolution: Won't Fix I'm closing this as Won't Fix because, while it's possible to catch syntax errors when compiling the view functions, it's not easy to know whether a syntax error may have been thrown by a user calling eval or something else tricky. In other words, it's hard to disambiguate between errors caused by the view code and errors caused by the input data. Also, this hasn't been updated in a long time. Abort views that have exceptions in the view server --- Key: COUCHDB-282 URL: https://issues.apache.org/jira/browse/COUCHDB-282 Project: CouchDB Issue Type: Bug Components: JavaScript View Server Affects Versions: 0.8, 0.8.1 Environment: All Reporter: kowsik I'm incrementally experimenting with new views on a 100K document db. If there's a typo in the javascript view or some other exception, there's a spew of logs in couch.log while each of the couch documents continue to go through the map/reduce code (which is buggy). This takes about 15 minutes before I can update the view and re-query again. It would be awesome if couch can handle exceptions in the view server and stop processing so that the fix can be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-326) Occasional {error:error,reason:eacces} errors deleting a database on Windows
[
https://issues.apache.org/jira/browse/COUCHDB-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-326.
-
Resolution: Fixed
Fix Version/s: 1.0
According to dch, this hasn't been reproducible since 1.0.
Occasional {error:error,reason:eacces} errors deleting a database on
Windows
Key: COUCHDB-326
URL: https://issues.apache.org/jira/browse/COUCHDB-326
Project: CouchDB
Issue Type: Bug
Affects Versions: 0.9
Environment: Windows, couch 0.9, erlang R12B 5.6.5
Reporter: Mark Hammond
Fix For: 1.0
On Windows, occasionally you will see errors attempting to delete a database.
This manifests itself by 10-30% of the test suite failing on Windows. If
you retry the tests that failed, they will usually pass on subsequent
attempts. Running the tests individually causes them to fail roughly 10% of
the time.
The log output shown is:
[debug] [0.18650.6] httpd 500 error response:
{error:error,reason:eacces}
[info] [0.18650.6] 127.0.0.1 - - 'DELETE' /test_suite_db/ 500
A slightly snipped transcript from IRC:
(2:58:32 PM) markh: I see a number of INFO logs Shutting down view group
server, monitored db is closing. directly before the error. I was guessing
the file may be unlink'd before one of those workers actually closes its
handle?
(2:58:54 PM) alisdair: yeah, it's probably a race condition
(2:59:13 PM) alisdair: where the delete is tried before the fd is let go
(2:59:26 PM) alisdair: the reader fd that is
(2:59:32 PM) markh: yeah
...
(3:11:47 PM) alisdair: i can't find an obvious deadlock
(3:12:18 PM) alisdair: couch_server:delete explicitly waits for the db
process to exit
(3:12:23 PM) alisdair: before deleting it
(3:15:15 PM) alisdair: i think i found the problem
(3:15:23 PM) alisdair: but i need a windows machine to confirm
(3:15:30 PM) alisdair: i'll look into it tomorrow
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1277) refactoring couch_httpd_db for better query parameter support and code clarity
[ https://issues.apache.org/jira/browse/COUCHDB-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1277. -- Resolution: Fixed Fix Version/s: 1.3 refactoring couch_httpd_db for better query parameter support and code clarity -- Key: COUCHDB-1277 URL: https://issues.apache.org/jira/browse/COUCHDB-1277 Project: CouchDB Issue Type: Improvement Components: HTTP Interface Reporter: Randall Leeds Assignee: Randall Leeds Priority: Minor Fix For: 1.3 Attachments: 0001-some-refactoring-in-couch_httpd_db.erl.patch In the process of adding ?rev= support for PUT updates I cleaned up some code in couch_httpd_db and added support for some options that weren't honored before. I'm posting this here for a code review in case I missed something. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-860) Futon appends wrong version number to files
[ https://issues.apache.org/jira/browse/COUCHDB-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-860. - Resolution: Fixed Fix Version/s: 1.3 I took out the max-age directive. Firefox and Chrome both get 304s after sending an If-Modified-Since with every request. There are most certainly user agents out there who behave worse, but I think this is probably strictly an improvement. Futon appends wrong version number to files --- Key: COUCHDB-860 URL: https://issues.apache.org/jira/browse/COUCHDB-860 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.0.1 Reporter: Volker Mische Assignee: Randall Leeds Priority: Minor Fix For: 1.3 Attachments: 0001-remove-version-number-from-futon-static-resources.patch, 0002-Futon-Cache-Control.patch Futon appends the CouchDB version number to the JavaScript files it loads. In 1.0.1 it still appends 0.11 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-642) Support rev in PUT URL
[
https://issues.apache.org/jira/browse/COUCHDB-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-642.
-
Resolution: Duplicate
Fix Version/s: 1.2
Duplicate of 1268.
Support rev in PUT URL
--
Key: COUCHDB-642
URL: https://issues.apache.org/jira/browse/COUCHDB-642
Project: CouchDB
Issue Type: New Feature
Components: HTTP Interface
Environment: trunk 08 Feb 2010
Reporter: Brian Candler
Assignee: Randall Leeds
Priority: Minor
Fix For: 1.2
Attachments: 0001-Allow-for-the-current-revision-number-to-be.patch
A DELETE request lets you append ?rev= to the URL. But this doesn't work
with a PUT request; you have to put the _rev in the body instead (even though
the _id is taken from the URL path)
$ curl -X PUT -d {}
http://brianadmin:brianadmin@127.0.0.1:5984/briantest/foo
{ok:true,id:foo,rev:1-967a00dff5e02add41819138abb3284d}
$ curl -X PUT -d {}
http://brianadmin:brianadmin@127.0.0.1:5984/briantest/foo?rev=1-967a00dff5e02add41819138abb3284d
{error:conflict,reason:Document update conflict.}
$ curl -X PUT -d '{_rev:1-967a00dff5e02add41819138abb3284d}'
http://brianadmin:brianadmin@127.0.0.1:5984/briantest/foo
{ok:true,id:foo,rev:2-7051cbe5c8faecd085a3fa619e6e6337}
Allowing ?rev in the URL would make PUT and DELETE more consistent, and would
allow you to replace an existing JSON doc with another one without having to
merge the _rev into it first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-860) Futon appends wrong version number to files
[ https://issues.apache.org/jira/browse/COUCHDB-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-860. - Resolution: Cannot Reproduce I don't see any indication of this problem going back as far as the current 1.0.x branch. Futon appends wrong version number to files --- Key: COUCHDB-860 URL: https://issues.apache.org/jira/browse/COUCHDB-860 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.0.1 Reporter: Volker Mische Priority: Minor Futon appends the CouchDB version number to the JavaScript files it loads. In 1.0.1 it still appends 0.11 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-191) Bad javascript syntax in Futon's custom query editor doesn't show an error when run.
[ https://issues.apache.org/jira/browse/COUCHDB-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-191. - Resolution: Invalid Fix Version/s: (was: 1.2) As per the first comment, this issue is not well described, but other tickets do describe the real problem. Bad javascript syntax in Futon's custom query editor doesn't show an error when run. - Key: COUCHDB-191 URL: https://issues.apache.org/jira/browse/COUCHDB-191 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 0.9 Environment: OS: EEEubuntu (based on Ubuntu 8.10). Hardware: EEE PC 904hd. Browser: Firefox 3.0.5. Reporter: Luke Venediger Priority: Minor Original Estimate: 48h Remaining Estimate: 48h In the custom view editor, Futon doesn't report an error when there is bad syntax in the javascript. To reproduce: 1. Browse to http://localhost:5984/_utils/ 2. Open a database 3. Change the view to Custom Query... 4. In the view code section: change: emit(null, doc); to: emit(null, doc 5. Click Run Actual results: The page returns with an empty table below the query editor. Expected results: The page should return showing a message like Error in view. Missing ')' after doc, line 3 Notes: The http response was 200 OK, where it should've been a 400 - Bad Request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-827) Replication hangs on streeming documents with inline attachments.
[
https://issues.apache.org/jira/browse/COUCHDB-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-827.
-
Resolution: Fixed
Fix Version/s: 0.11.1
1.0
According to comments, this is fixed in 0.11.1 and 1.0.
Replication hangs on streeming documents with inline attachments.
-
Key: COUCHDB-827
URL: https://issues.apache.org/jira/browse/COUCHDB-827
Project: CouchDB
Issue Type: Bug
Environment: CouchDB 1.0 Mac OSX 10.6 , Win XP
Reporter: Nikolai Teofilov
Assignee: Filipe Manana
Fix For: 1.0, 0.11.1
The problem apear to exist onliy on replication 0.11 to 1.0
How to reproduce the bug:
On couchdb 0.11 create a database with a document that contains inline base64
encoded attachment.
{
_id : test,
_attachments:
{
foo.txt:
{
content_type:text\/plain,
data: VGhpcyBpcyBhIGJhc2U2NCBlbmNvZGVkIHRleHQ=
}
}
}
replication 0.11 - (CouchDBX) 1.0 will hang with following error log:
1 [info] [0.1028.0] starting new replication
5427f9ab10e93ee8b02bd9a3e0050c58 at 0.1069.0
1 [error] [0.1083.0] streaming att. ended but more data requested
{1279,225570,362980}
1 [info] [0.1083.0] request for test/foo.txt timed out, retrying in 0.5
seconds
1 [error] [0.1083.0] streaming att. ended but more data requested
{1279,225571,40192}
1 [info] [0.1083.0] request for test/foo.txt timed out, retrying in 0.5
seconds
1 [error] [0.1083.0] streaming att. ended but more data requested
{1279,225574,323477}
1 [info] [0.1083.0] request for test/foo.txt timed out, retrying in 0.5
seconds
1 [error] [0.1083.0] streaming att. ended but more data requested
{1279,225575,24131}
1 [info] [0.1083.0] request for test/foo.txt timed out, retrying in 0.5
seconds
1 [error] [0.1083.0] streaming att. ended but more data requested
{1279,225575,688384}
1 [info] [0.1083.0] request for test/foo.txt timed out, retrying in 0.5
seconds
1 [error] [0.1083.0] streaming att. ended but more data requested
{1279,225576,382178}
1 [info] [0.1083.0] request for test/foo.txt timed out, retrying in 0.5
seconds
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-616) 0.9-0.10 upgrade rebuilds views rather than just updating headers
[
https://issues.apache.org/jira/browse/COUCHDB-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-616.
-
Resolution: Won't Fix
Out of date. Sorry, Josh! :)
0.9-0.10 upgrade rebuilds views rather than just updating headers
--
Key: COUCHDB-616
URL: https://issues.apache.org/jira/browse/COUCHDB-616
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 0.10.1
Environment: Linux melkjug-xen 2.6.30.1-pv #1 SMP Thu Jul 9 08:12:56
EDT 2009 x86_64 Intel(R) Xeon(R) CPU E5430 @ 2.66GHz GenuineIntel GNU/Linux
Erlang (BEAM) emulator version 5.6.5 [source] [64-bit] [smp:2]
[async-threads:0] [hipe]
Reporter: Joshua Bronson
It looks like there is code that is supposed to upgrade the headers of 0.9
views to 0.10 style when a 0.10 couch reads a 0.9 view to avoid having to
rebuild them (see
http://github.com/halorgium/couchdb/blob/v0.10.1/src/couchdb/couch_view_group.erl#L379).
However, they are indeed getting rebuilt.
I have a test environment set up where I can trigger this behavior. I've
added the debug output at http://paste.pocoo.org/show/163023/ and here is
what's getting printed:
before upgrade_old_header
after upgrade_old_header
Pos: 0
Error: {'EXIT',{{badmatch,eof},
[{couch_file,load_header,2},
{couch_file,find_header,2},
{couch_file,handle_call,3},
{gen_server,handle_msg,5},
{proc_lib,init_p_do_apply,3}]}}
read_header: no_valid_header
calling reset_file
truncating
For some reason the file:position(Fd, eof) call is return 0, indicating a
0-length file, but the view file in question is 188M.
I spent a while debugging this with Jan in #couchdb today but we couldn't
find the fix.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1311) {os_process_error,{exit_status,127}} repeats in the logs, the views are not working
[
https://issues.apache.org/jira/browse/COUCHDB-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-1311.
--
Resolution: Not A Problem
This error, especially on Ubuntu, is usually due to linking problems. Please
follow carefully the installation instructions paying special attention to the
parts about library paths. In other words, if you built with --with-js-lib and
--with-js-include, you will need to either run CouchDB with LD_LIBRARY_PATH
modified in your environment or change add the file as described to
/etc/ld.so.conf.d. Please re-open the ticket if you think I have closed it in
error. For interactive help, feel free to join #couchdb on chat.freenode.net.
{os_process_error,{exit_status,127}} repeats in the logs, the views are not
working
---
Key: COUCHDB-1311
URL: https://issues.apache.org/jira/browse/COUCHDB-1311
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 1.1
Environment: Ubuntu 10.04.3 LTS
Reporter: alFReD NSH
I installed couchdb using apt-get, but the version was 0.10.0 so did a
apt-get remove and then I built couchdb 1.10 from the source using this guide:
http://wiki.apache.org/couchdb/Installing_on_Ubuntu.
localhost:5984 returns {couchdb:Welcome,version:1.1.0} but The
problem is that the views are not working. Here are some of the logs(it's all
same and reapeating):
{exit_status,127}}
[Tue, 18 Oct 2011 10:27:40 GMT] [error] [0.745.0] OS Process Error
0.18840.1 :: {os_process_error,
{exit_status,127}}
[Tue, 18 Oct 2011 10:27:40 GMT] [error] [0.745.0] OS Process Error
0.18843.1 :: {os_process_error,
{exit_status,127}}
[Tue, 18 Oct 2011 10:27:40 GMT] [error] [0.745.0] OS Process Error
0.18846.1 :: {os_process_error,
{exit_status,127}}
[Tue, 18 Oct 2011 10:27:40 GMT] [error] [0.745.0] OS Process Error
0.18849.1 :: {os_process_error,
{exit_status,127}}
[Tue, 18 Oct 2011 10:27:40 GMT] [error] [0.18864.1] OS Process died with
status: 127
[Tue, 18 Oct 2011 10:27:40 GMT] [error] [0.18864.1] ** Generic server
0.18864.1 terminating
** Last message in was {#Port0.30492,{exit_status,127}}
** When Server state == {os_proc,/usr/local/bin/couchjs
/usr/local/share/couchdb/server/main.js,
#Port0.30492,
#Funcouch_os_process.0.107304434,
#Funcouch_os_process.1.53339349,5000}
** Reason for termination ==
** {exit_status,127}
[Tue, 18 Oct 2011 10:27:41 GMT] [error] [0.18864.1] {error_report,0.32.0,
{0.18864.1,crash_report,
[[{initial_call,
{couch_os_process,init,['Argument__1']}},
{pid,0.18864.1},
{registered_name,[]},
{error_info,
{exit,
{exit_status,127},
[{gen_server,terminate,6},
{proc_lib,init_p_do_apply,3}]}},
{ancestors,
[couch_query_servers,couch_secondary_services,
couch_server_sup,0.33.0]},
{messages,
[{'EXIT',#Port0.30492,normal},
{'$gen_call',
{0.745.0,#Ref0.0.0.138129},
{prompt,
[reset,
{[{reduce_limit,true},
{timeout,5000}]}]}}]},
{links,[0.94.0]},
{dictionary,[]},
{trap_exit,true},
{status,running},
{heap_size,987},
{stack_size,24},
{reductions,773}],
[]]}}
[Tue, 18 Oct 2011 10:27:41 GMT] [error] [0.745.0] OS Process Error
0.18868.1 :: {os_process_error,
{exit_status,127}}
[Tue, 18 Oct 2011 10:27:41 GMT] [error] [0.745.0] OS Process Error
0.18871.1 :: {os_process_error,
{exit_status,127}}
[Tue, 18 Oct 2011 10:27:41 GMT] [error] [0.745.0] OS Process Error
0.18874.1 :: {os_process_error,
{exit_status,127}}
[jira] [Closed] (COUCHDB-1136) cleanup views does not work when a database has no design documents
[ https://issues.apache.org/jira/browse/COUCHDB-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds closed COUCHDB-1136. -- cleanup views does not work when a database has no design documents --- Key: COUCHDB-1136 URL: https://issues.apache.org/jira/browse/COUCHDB-1136 Project: CouchDB Issue Type: Bug Components: Build System Affects Versions: 1.0.2 Reporter: Randall Leeds Assignee: Randall Leeds Priority: Minor Fix For: 1.1.1, 1.2 Attachments: fix_empty_ddoc_cleanup.patch, view_cleanup_etap.patch When a database has no design documents the cleanup code creates an empty regex which matches everything, thus saving all the index files. In this case it should delete everything instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1285) Allow configuration of vendor and module version in the welcome message
[
https://issues.apache.org/jira/browse/COUCHDB-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-1285.
--
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Randall Leeds
Vendor information included on master and will land in 1.3. Will open another
ticket with module patch.
Allow configuration of vendor and module version in the welcome message
---
Key: COUCHDB-1285
URL: https://issues.apache.org/jira/browse/COUCHDB-1285
Project: CouchDB
Issue Type: Improvement
Reporter: Jan Lehnardt
Assignee: Randall Leeds
Fix For: 1.3
Attachments: vendor_and_modules.patch,
vendor_and_modules_objects.patch, vendor_only.patch
The patch below allows to configure vendor and module version information
into the GET / welcome message.
E.g.
[vendor]
name = refuge
version = 2.0.0
[modules]
geocouch = 1.2.1
would produce:
{couchdb:Welcome,version:1.2.0,refuge:2.0.0,modules:{geocouch:1.2.1}}
--
--- a/src/couchdb/couch_httpd_misc_handlers.erl
+++ b/src/couchdb/couch_httpd_misc_handlers.erl
@@ -30,9 +30,23 @@
% httpd global handlers
handle_welcome_req(#httpd{method='GET'}=Req, WelcomeMessage) -
+Vendor = case couch_config:get(vendor) of
+ [] - [];
+ Vendor1 - [{
+proplists:get_value(name, Vendor1),
+?l2b(proplists:get_value(version, Vendor1))
+ }]
+end,
+
+Modules = lists:map(fun({Key, Value}) -
+ {Key, ?l2b(Value)}
+end, couch_config:get(modules)),
+
send_json(Req, {[
{couchdb, WelcomeMessage},
-{version, list_to_binary(couch_server:get_version())}
+{version, list_to_binary(couch_server:get_version())}]
+++ Vendor
+++ [{modules, {Modules}}
]});
handle_welcome_req(Req, _) -
send_method_not_allowed(Req, GET,HEAD).
--
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-648) _update handler ignores code in response doc
[
https://issues.apache.org/jira/browse/COUCHDB-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-648.
-
Resolution: Fixed
Fixed on trunk in r1177890.
Fixed on 1.2.x in r1177891.
Fixed on 1.1.x in r1177892.
_update handler ignores code in response doc
--
Key: COUCHDB-648
URL: https://issues.apache.org/jira/browse/COUCHDB-648
Project: CouchDB
Issue Type: Bug
Components: Database Core
Environment: CouchDB from HEAD
Reporter: Cliff Stanford
Assignee: Randall Leeds
Labels: update
Fix For: 1.1.1, 1.2
Attachments:
0001-Document-update-handlers-now-honor-code-in-response-.patch, test.diff
When using an _update handler, it should be possible to return a response
code.
return [ doc, {
headers : { Location : / },
code : 303,
body : 'Redirecting'
}];
Should return 303 (the redirect for POST) but in fact, on a successful create
returns 201. This means it is not possible to use the browser to POST as you
cannot redirect on return. This feels like a bug.
In any case, I would respectfully suggest that the syntax of the _update
handler be changed so that there is a store(doc) call (or similar) which
returns a JSON object to the update handler so that the handler may redirect
appropriately. That would make it possible to do updates client-side with
little or no client-side javascript.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-990) Update handlers ignore HTTP status codes in responses
[
https://issues.apache.org/jira/browse/COUCHDB-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-990.
-
Resolution: Fixed
Fix Version/s: 1.2
1.1.1
Fixed on trunk in r1177890.
Fixed on 1.2.x in r1177891.
Fixed on 1.1.x in r1177892.
Update handlers ignore HTTP status codes in responses
-
Key: COUCHDB-990
URL: https://issues.apache.org/jira/browse/COUCHDB-990
Project: CouchDB
Issue Type: Bug
Components: JavaScript View Server
Affects Versions: 1.0.1
Environment: OSX, built using brew
Reporter: Nick Fisher
Fix For: 1.1.1, 1.2
The following update handler will always return 200
'''
function(doc, req){
return [null, {code: 400, body: 'bad user request'];
}
'''
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-752) InternalError: script stack space quota is exhausted
[
https://issues.apache.org/jira/browse/COUCHDB-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-752.
-
Resolution: Fixed
Paul Davis fixed this as part of the work to integrate support for SpiderMonkey
1.8.5. Fixed on 1.1.1 and 1.2. Thanks, Paul!
InternalError: script stack space quota is exhausted
Key: COUCHDB-752
URL: https://issues.apache.org/jira/browse/COUCHDB-752
Project: CouchDB
Issue Type: Bug
Components: JavaScript View Server
Affects Versions: 0.11
Reporter: Benoit Chesneau
Assignee: Randall Leeds
Priority: Critical
Fix For: 1.1.1, 1.2
Attachments: ddoc.patch
Couchdb freeze and use full CPU after accessing to a 93MB designdoc:
debug] [0.91.0] Spawning new group server for view group _design/aimpl in
database aimpl.
[debug] [0.94.0] request_group {Pid, Seq} {0.116.0,61}
[debug] [0.81.0] New task status for aimpl _design/aimpl: Finishing.
[debug] [0.126.0] OS Process Start :: #Port0.2040
[debug] [0.87.0] Teach ddoc to new proc {proc,0.126.0,javascript,[],
{couch_os_process,prompt},
{couch_os_process,set_timeout},
{couch_os_process,stop}} with DDocKey:
{_design/aimpl,
30-2ab623a62b83b0d9f2616ee209f62659}
InternalError: script stack space quota is exhausted
Most of data are in attachments :
enlil:couchapp benoitc$ du -sh aimpl
93M aimpl
enlil:couchapp benoitc$ du -sh aimpl/_attachments/
93M aimpl/_attachments/
about 100k in views/shows/...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-893) Error: os_process_error {exit_status,0} when rendering view on 17 mb doc, couchapp and data attached
[
https://issues.apache.org/jira/browse/COUCHDB-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-893.
-
Resolution: Fixed
Paul Davis fixed this as part of the work to integrate support for SpiderMonkey
1.8.5. Fixed on 1.1.1 and 1.2. Thanks, Paul!
Error: os_process_error {exit_status,0} when rendering view on 17 mb doc,
couchapp and data attached
---
Key: COUCHDB-893
URL: https://issues.apache.org/jira/browse/COUCHDB-893
Project: CouchDB
Issue Type: Bug
Affects Versions: 1.0.1
Environment: I repeated this on windows and linux (64 bit)
Reporter: Michael Schneider
Assignee: Randall Leeds
Fix For: 1.1.1, 1.2
Attachments: bugdoc.tar.gz
I have a large set of documents that I harvesting data from. All docs 9mb
render fine (with doc size increased)
Attached is a simple couchapp and one doc.
To reproduce, untar and:
reproduce
1) untar file
2) cd bugdoc/couchapp/bugreport
3) couchapp push bugreport
4) cd bugdoc
5) python submitbadjson.py
open url
http://127.0.0.1:5984/_utils/database.html?bugreport/_design/bugreport/_view/buggy
You should see a popup
(Error: os_process_error
{exit_status,0})
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
