[jira] [Updated] (COUCHDB-1376) enable JaegerMonkey features
[ https://issues.apache.org/jira/browse/COUCHDB-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds updated COUCHDB-1376: --- Attachment: v1-0001-COUCHDB-1376-enable-JaegerMonkey-features.patch > enable JaegerMonkey features > > > Key: COUCHDB-1376 > URL: https://issues.apache.org/jira/browse/COUCHDB-1376 > Project: CouchDB > Issue Type: Improvement > Components: JavaScript View Server >Reporter: Randall Leeds >Assignee: Randall Leeds >Priority: Minor > Fix For: 1.3 > > Attachments: v1-0001-COUCHDB-1376-enable-JaegerMonkey-features.patch > > > In recent versions of SpiderMonkey, the method JIT (sometimes referred to as > JaegerMonkey) is considered stable for use and ships on by default in Firefox > builds. Newer, unreleased, upstream versions also have type inference. -- 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] [Created] (COUCHDB-1376) enable JaegerMonkey features
enable JaegerMonkey features Key: COUCHDB-1376 URL: https://issues.apache.org/jira/browse/COUCHDB-1376 Project: CouchDB Issue Type: Improvement Components: JavaScript View Server Reporter: Randall Leeds Assignee: Randall Leeds Priority: Minor Fix For: 1.3 In recent versions of SpiderMonkey, the method JIT (sometimes referred to as JaegerMonkey) is considered stable for use and ships on by default in Firefox builds. Newer, unreleased, upstream versions also have type inference. -- 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] [Updated] (COUCHDB-111) Javascript Error Tracebacks
[ https://issues.apache.org/jira/browse/COUCHDB-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds updated COUCHDB-111: -- Attachment: v4-0002-COUCHDB-111-JavaScript-Error-Tracebacks.patch v4-0001-COUCHDB-111-handle-multiple-files-in-couchjs.patch > 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 >Assignee: Chris Anderson > 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 > > > 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] [Updated] (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 updated COUCHDB-1338: --- Attachment: v2-0002-Fix-JS-tests-for-COUCHDB-1338.patch v2-0001-COUCHDB-1338-run-js-tests-with-port-0.patch > 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] [Updated] (COUCHDB-111) Javascript Error Tracebacks
[ https://issues.apache.org/jira/browse/COUCHDB-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds updated COUCHDB-111: -- Attachment: v3-0002-COUCHDB-111-JavaScript-Error-Tracebacks.patch v3-0001-COUCHDB-111-handle-multiple-files-in-couchjs.patch > 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 >Assignee: Chris Anderson > 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 > > > 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] [Updated] (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 updated COUCHDB-410:
--
Attachment: v2-0001-COUCHDB-410-graceful-validate_doc_update-errors.patch
> 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] [Updated] (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 updated COUCHDB-410:
--
Attachment: v1-0001-COUCHDB-410-graceful-validate_doc_update-errors.patch
> 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
>
>
> 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] [Updated] (COUCHDB-111) Javascript Error Tracebacks
[ https://issues.apache.org/jira/browse/COUCHDB-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds updated COUCHDB-111: -- Attachment: v2-0002-COUCHDB-111-JavaScript-Error-Tracebacks.patch v2-0001-COUCHDB-111-handle-multiple-files-in-couchjs.patch > 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 >Assignee: Chris Anderson > 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 > > > 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] [Updated] (COUCHDB-111) Javascript Error Tracebacks
[ https://issues.apache.org/jira/browse/COUCHDB-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds updated COUCHDB-111: -- Attachment: v1-0002-COUCHDB-111-JavaScript-Error-Tracebacks.patch v1-0001-COUCHDB-111-handle-multiple-files-in-couchjs.patch > 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 >Assignee: Chris Anderson > Attachments: > v1-0001-COUCHDB-111-handle-multiple-files-in-couchjs.patch, > v1-0002-COUCHDB-111-JavaScript-Error-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
Re: couchdb meetup in SF
On Sat, Jan 7, 2012 at 01:21, Benoit Chesneau wrote: > Hi all, > > I will be in San Francisco this month, and it would be cool to meet > other CouchDB developers over a beer or two while I am there. > > I've no idea for suitable locations so if any natives of the area have > suggestions, please give a shout. > > Anyone interested? Yes. I'm variously available for talk/work and beverage flexible.
[jira] [Updated] (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 updated COUCHDB-1338: --- Attachment: v1-0002-Fix-JS-tests-for-COUCHDB-1338.patch v1-0001-COUCHDB-1338-run-js-tests-with-port-0.patch > 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 > > > 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] [Updated] (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 updated COUCHDB-1338: --- Attachment: (was: v1-0001-COUCHDB-1338-run-js-tests-with-port-0.patch) > 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 > > > 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] [Updated] (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 updated COUCHDB-1338: --- Attachment: (was: v1-0002-Fix-JS-tests-for-COUCHDB-1338.patch) > 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 > > > 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] [Updated] (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 updated COUCHDB-1338: --- Attachment: v1-0002-Fix-JS-tests-for-COUCHDB-1338.patch v1-0001-COUCHDB-1338-run-js-tests-with-port-0.patch > 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 > > > 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-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
Re: git commit: Add heartbeat parameter to all _changes requests
On Sat, Jan 7, 2012 at 8:55 PM, Randall Leeds wrote:
> I'm cherry-picking this for 1.2. Especially with a brand new
> replicator, it would be very nice if no-one gets bitten by this doing
> filtered replication.
> Applies cleanly.
Fine for me.
>
> On Sat, Jan 7, 2012 at 05:48, wrote:
>> Updated Branches:
>> refs/heads/master 975ea08c7 -> a2d57c8bb
>>
>>
>> Add heartbeat parameter to all _changes requests
>>
>> Even non-continuous _changes requests, particularly filtered
>> ones, can cause long periods of inactivity.
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/couchdb/repo
>> Commit: http://git-wip-us.apache.org/repos/asf/couchdb/commit/a2d57c8b
>> Tree: http://git-wip-us.apache.org/repos/asf/couchdb/tree/a2d57c8b
>> Diff: http://git-wip-us.apache.org/repos/asf/couchdb/diff/a2d57c8b
>>
>> Branch: refs/heads/master
>> Commit: a2d57c8bb34f4621fed00f4e65191a1531bc3110
>> Parents: 975ea08
>> Author: Filipe David Borba Manana
>> Authored: Sat Jan 7 13:44:45 2012 +
>> Committer: Filipe David Borba Manana
>> Committed: Sat Jan 7 13:44:45 2012 +
>>
>> --
>> .../src/couch_replicator_api_wrap.erl | 6 --
>> 1 files changed, 4 insertions(+), 2 deletions(-)
>> --
>>
>>
>> http://git-wip-us.apache.org/repos/asf/couchdb/blob/a2d57c8b/src/couch_replicator/src/couch_replicator_api_wrap.erl
>> --
>> diff --git a/src/couch_replicator/src/couch_replicator_api_wrap.erl
>> b/src/couch_replicator/src/couch_replicator_api_wrap.erl
>> index a29fe94..d287fcb 100644
>> --- a/src/couch_replicator/src/couch_replicator_api_wrap.erl
>> +++ b/src/couch_replicator/src/couch_replicator_api_wrap.erl
>> @@ -306,13 +306,15 @@ update_docs(Db, DocList, Options, UpdateType) ->
>>
>> changes_since(#httpdb{headers = Headers1} = HttpDb, Style, StartSeq,
>> UserFun, Options) ->
>> + HeartBeat = erlang:max(1000, HttpDb#httpdb.timeout div 3),
>> BaseQArgs = case get_value(continuous, Options, false) of
>> false ->
>> [{"feed", "normal"}];
>> true ->
>> - [{"feed", "continuous"}, {"heartbeat", "1"}]
>> + [{"feed", "continuous"}]
>> end ++ [
>> - {"style", atom_to_list(Style)}, {"since",
>> couch_util:to_list(StartSeq)}
>> + {"style", atom_to_list(Style)}, {"since",
>> couch_util:to_list(StartSeq)},
>> + {"heartbeat", integer_to_list(HeartBeat)}
>> ],
>> DocIds = get_value(doc_ids, Options),
>> {QArgs, Method, Body, Headers} = case DocIds of
>>
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
Re: git commit: Add heartbeat parameter to all _changes requests
I'm cherry-picking this for 1.2. Especially with a brand new
replicator, it would be very nice if no-one gets bitten by this doing
filtered replication.
Applies cleanly.
On Sat, Jan 7, 2012 at 05:48, wrote:
> Updated Branches:
> refs/heads/master 975ea08c7 -> a2d57c8bb
>
>
> Add heartbeat parameter to all _changes requests
>
> Even non-continuous _changes requests, particularly filtered
> ones, can cause long periods of inactivity.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/couchdb/repo
> Commit: http://git-wip-us.apache.org/repos/asf/couchdb/commit/a2d57c8b
> Tree: http://git-wip-us.apache.org/repos/asf/couchdb/tree/a2d57c8b
> Diff: http://git-wip-us.apache.org/repos/asf/couchdb/diff/a2d57c8b
>
> Branch: refs/heads/master
> Commit: a2d57c8bb34f4621fed00f4e65191a1531bc3110
> Parents: 975ea08
> Author: Filipe David Borba Manana
> Authored: Sat Jan 7 13:44:45 2012 +
> Committer: Filipe David Borba Manana
> Committed: Sat Jan 7 13:44:45 2012 +
>
> --
> .../src/couch_replicator_api_wrap.erl | 6 --
> 1 files changed, 4 insertions(+), 2 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/couchdb/blob/a2d57c8b/src/couch_replicator/src/couch_replicator_api_wrap.erl
> --
> diff --git a/src/couch_replicator/src/couch_replicator_api_wrap.erl
> b/src/couch_replicator/src/couch_replicator_api_wrap.erl
> index a29fe94..d287fcb 100644
> --- a/src/couch_replicator/src/couch_replicator_api_wrap.erl
> +++ b/src/couch_replicator/src/couch_replicator_api_wrap.erl
> @@ -306,13 +306,15 @@ update_docs(Db, DocList, Options, UpdateType) ->
>
> changes_since(#httpdb{headers = Headers1} = HttpDb, Style, StartSeq,
> UserFun, Options) ->
> + HeartBeat = erlang:max(1000, HttpDb#httpdb.timeout div 3),
> BaseQArgs = case get_value(continuous, Options, false) of
> false ->
> [{"feed", "normal"}];
> true ->
> - [{"feed", "continuous"}, {"heartbeat", "1"}]
> + [{"feed", "continuous"}]
> end ++ [
> - {"style", atom_to_list(Style)}, {"since",
> couch_util:to_list(StartSeq)}
> + {"style", atom_to_list(Style)}, {"since",
> couch_util:to_list(StartSeq)},
> + {"heartbeat", integer_to_list(HeartBeat)}
> ],
> DocIds = get_value(doc_ids, Options),
> {QArgs, Method, Body, Headers} = case DocIds of
>
dev@couchdb.apache.org
Thanks for bringing this up. Regardless of whether we eventually store our own applications in individual git repositories I think the ability to pull in external repos will prove useful in tracking upstream changes from third party applications like mochiweb and ibrowse. The current approach of copy/pasting source code is error-prone and has caused some breakage in the past. I certainly understand the importance of the build system being self-contained, but I think the source release described by Benoit covers that. Adam On Jan 7, 2012, at 9:25 AM, Benoit Chesneau wrote: > Hi all, > > I would like to start some work on my own to test how I can merge our > autotool build system and rebar to provide an erlang release and > distribute couchdb more easily. In refuge I consider that all the apps > in src/ are standalone app and each have their own history (old > couchdb history is kept) . To create a release, the make distdir > collect all the deps and in one source dir and the archive is created > from that source directory. At the end the created release is the same > you have with couchdb and you don't need to have git installed to > build it. Packages created (deb, rpm & osx) are based on this source > release. > > Can we do the same in the apache project ? Ie having one git repo / > app ? Or do we still need to handle them in the same repo ? Just > wanted to ask to know how I should handle that or at least start the > integration of rebar. > > Let me know, > > - benoît
dev@couchdb.apache.org
Thanks for bringing this up. Regardless of whether we eventually store our own applications in individual git repositories I think the ability to pull in external repos will prove useful in tracking upstream changes from third party applications like mochiweb and ibrowse. The current approach of copy/pasting source code is error-prone and has caused some breakage in the past. I certainly understand the importance of the build system being self-contained, but I think the source release described by Benoit covers that. Adam On Jan 7, 2012, at 9:25 AM, Benoit Chesneau wrote: > Hi all, > > I would like to start some work on my own to test how I can merge our > autotool build system and rebar to provide an erlang release and > distribute couchdb more easily. In refuge I consider that all the apps > in src/ are standalone app and each have their own history (old > couchdb history is kept) . To create a release, the make distdir > collect all the deps and in one source dir and the archive is created > from that source directory. At the end the created release is the same > you have with couchdb and you don't need to have git installed to > build it. Packages created (deb, rpm & osx) are based on this source > release. > > Can we do the same in the apache project ? Ie having one git repo / > app ? Or do we still need to handle them in the same repo ? Just > wanted to ask to know how I should handle that or at least start the > integration of rebar. > > Let me know, > > - benoît
dev@couchdb.apache.org
Hi all, I would like to start some work on my own to test how I can merge our autotool build system and rebar to provide an erlang release and distribute couchdb more easily. In refuge I consider that all the apps in src/ are standalone app and each have their own history (old couchdb history is kept) . To create a release, the make distdir collect all the deps and in one source dir and the archive is created from that source directory. At the end the created release is the same you have with couchdb and you don't need to have git installed to build it. Packages created (deb, rpm & osx) are based on this source release. Can we do the same in the apache project ? Ie having one git repo / app ? Or do we still need to handle them in the same repo ? Just wanted to ask to know how I should handle that or at least start the integration of rebar. Let me know, - benoît
Re: javascript ./run
Sorry. javascript tests are now running. I forgot to make a `git clean -fdx` . - benoît On Sat, Jan 7, 2012 at 3:06 PM, Benoit Chesneau wrote: > On Sat, Jan 7, 2012 at 2:55 PM, Jason Smith wrote: >> On Sat, Jan 7, 2012 at 6:19 PM, Benoit Chesneau wrote: >>> Does javascript console testts work for you on 1.2 ? >>> >>> I tried after a clean -fdx : >>> >>> $ cd test/javascript/ >>> $ ./run >>> [couchjs] SyntaxError: missing } after property list >>> Failed to compile script. >> >> That is due to the syntax error I mentioned on IRC. The >> users_db_security.js looks like it got some random code copy/pasted >> into it. >> >> -- >> Iris Couch > > mm no I still have the error. This is in one of js loaded before > starting the test loop. not sure which though... > > - benoit
Re: javascript ./run
On Sat, Jan 7, 2012 at 2:55 PM, Jason Smith wrote: > On Sat, Jan 7, 2012 at 6:19 PM, Benoit Chesneau wrote: >> Does javascript console testts work for you on 1.2 ? >> >> I tried after a clean -fdx : >> >> $ cd test/javascript/ >> $ ./run >> [couchjs] SyntaxError: missing } after property list >> Failed to compile script. > > That is due to the syntax error I mentioned on IRC. The > users_db_security.js looks like it got some random code copy/pasted > into it. > > -- > Iris Couch mm no I still have the error. This is in one of js loaded before starting the test loop. not sure which though... - benoit
[jira] [Commented] (COUCHDB-1367) update_seq does not always reflect the seq of the latest document update
[ https://issues.apache.org/jira/browse/COUCHDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181968#comment-13181968 ] Robert Newson commented on COUCHDB-1367: FYI: I've fixed couchdb-lucene. Instead of using "update_seq" from GET /dbname I instead grab "last_seq" from GET /dbname/_changes?limit=0&descending=true. > update_seq does not always reflect the seq of the latest document update > > > 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 > > Certain operations, (currently _revs_limit and _security changes) cause the > database header's update_seq to increase when the by_seq index (and therefore > _changes) has not changed, which is confusing in light of the naming > consistency. -- 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
Re: javascript ./run
On Sat, Jan 7, 2012 at 6:19 PM, Benoit Chesneau wrote: > Does javascript console testts work for you on 1.2 ? > > I tried after a clean -fdx : > > $ cd test/javascript/ > $ ./run > [couchjs] SyntaxError: missing } after property list > Failed to compile script. That is due to the syntax error I mentioned on IRC. The users_db_security.js looks like it got some random code copy/pasted into it. -- Iris Couch
[jira] [Resolved] (COUCHDB-188) _bulk_docs fails when deleting and adding a doc with the same id
[
https://issues.apache.org/jira/browse/COUCHDB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana resolved COUCHDB-188.
---
Resolution: Fixed
Fix applied to master (6d1d23b7d0eba4de3c4097907adc37b09191196e).
> _bulk_docs fails when deleting and adding a doc with the same id
>
>
> Key: COUCHDB-188
> URL: https://issues.apache.org/jira/browse/COUCHDB-188
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
>Affects Versions: 0.9
> Environment: CouchDB revision 730414.
>Reporter: Matt Goodall
>Assignee: Filipe Manana
>Priority: Blocker
> Fix For: 1.3
>
> Attachments:
> 0001-Allow-doc-delete-and-creation-in-the-same-bulk-updat.patch
>
>
> CouchDB returns a "412 Precondition Failed" when the list of changes sent to
> _bulk_docs deletes a document and later creates a document with the same id
> as the deleted document:
> {"docs": [
> {"_id": "docid", "_rev": "", "_deleted": true},
> {"_id": "docid"}
> ]}
> Once fixed, the response JSON document will return the same docid twice in
> the list but it's presumably ordered consistently with the request data so
> any client should be able to understand the response.
> Demonstrating the problem using curl is easy enough:
> $ curl -X PUT http://localhost:5984/test
> {"ok":true}
> $ curl -X PUT -d "{}" http://localhost:5984/test/docid
> {"ok":true,"id":"docid","rev":"4140747751"}
> $ curl -X POST -d '{"docs": [{"_id": "docid", "_rev": "4140747751",
> "_deleted": true}, {"_id": "docid"}]}' http://localhost:5984/test/_bulk_docs
> {"error":"conflict","reason":"Document update conflict."}
> Note: this is likely related to COUCHDB-172.
--
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
Re: javascript ./run
I don't get the same error as you, but the changes made to master (by Jan) to make the JavaScript CLI tests work, were not applied to 1.2.x. On Sat, Jan 7, 2012 at 11:28 AM, Bob Dionne wrote: > I see the same behavior, it's built in to make check now also. I thought > maybe it was SM because I'm running 1.7.x > > On Jan 7, 2012, at 6:19 AM, Benoit Chesneau wrote: > >> Does javascript console testts work for you on 1.2 ? >> >> I tried after a clean -fdx : >> >> $ cd test/javascript/ >> $ ./run >> [couchjs] SyntaxError: missing } after property list >> Failed to compile script. >> >> >> - benoît > -- Filipe David Manana, "Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men."
Re: javascript ./run
I see the same behavior, it's built in to make check now also. I thought maybe it was SM because I'm running 1.7.x On Jan 7, 2012, at 6:19 AM, Benoit Chesneau wrote: > Does javascript console testts work for you on 1.2 ? > > I tried after a clean -fdx : > > $ cd test/javascript/ > $ ./run > [couchjs] SyntaxError: missing } after property list > Failed to compile script. > > > - benoît
javascript ./run
Does javascript console testts work for you on 1.2 ? I tried after a clean -fdx : $ cd test/javascript/ $ ./run [couchjs] SyntaxError: missing } after property list Failed to compile script. - benoît
couchdb meetup in SF
Hi all, I will be in San Francisco this month, and it would be cool to meet other CouchDB developers over a beer or two while I am there. I've no idea for suitable locations so if any natives of the area have suggestions, please give a shout. Anyone interested? - benoît
