[jira] [Updated] (COUCHDB-1421) Wrong X-Forwarded-For address chosen as "peer"
[ https://issues.apache.org/jira/browse/COUCHDB-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Vander Wilt updated COUCHDB-1421: Summary: Wrong X-Forwarded-For address chosen as "peer" (was: Wrong X-Forwarded-For address chosen as "peer"?) > Wrong X-Forwarded-For address chosen as "peer" > -- > > Key: COUCHDB-1421 > URL: https://issues.apache.org/jira/browse/COUCHDB-1421 > Project: CouchDB > Issue Type: Bug >Reporter: Nathan Vander Wilt > > I noticed that in the Mochiweb code, it uses the last item of the > X-Forwarded-For list as the peer: > https://github.com/apache/couchdb/blob/master/src/mochiweb/mochiweb_request.erl#L82 > But shouldn't this snag the *first* item of the list instead? > http://tools.ietf.org/html/draft-petersson-forwarded-for-02#section-5.2 says > "the first for-parameter will disclose the user agent where the request first > was made" — the user agent is what I'd want as an app developer, not the > second-nearest proxy. -- 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-1423) Peer not set by X-Forwarded-For when using IPv6
Peer not set by X-Forwarded-For when using IPv6 --- Key: COUCHDB-1423 URL: https://issues.apache.org/jira/browse/COUCHDB-1423 Project: CouchDB Issue Type: Bug Reporter: Nathan Vander Wilt Priority: Minor CouchDB transparently handles an X-Forwarded-For header, using the actual client value for the request's "peer" property and logging (albeit modulo [#COUCHDB-1421]). However this does not seem to be working with IPv6 connections. When bound on 0.0.0.0 `curl -H "X-Forwarded-For: 123.45.6.7" localhost:5984` logs a peer address of 123.45.6.7. But when bound on :: the same request logs :::127.0.0.1 -- 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] [Commented] (COUCHDB-966) More explicit error messages when there are file access errors due to lack of permission
[
https://issues.apache.org/jira/browse/COUCHDB-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216287#comment-13216287
]
Mike Baranczak commented on COUCHDB-966:
1. Regarding Filipe's patch: I don't know if it's a good idea to send the full
path of the problematic file to a potentially untrusted client. This
information should definitely be written to the log, but the HTTP response can
be a little less informative. "Something went wrong, check the log" is
perfectly OK. If I can't read the log, then I wouldn't be able to fix the
permissions anyway.
2. I'm using CouchDB 1.1.1 (installed on Mac OS via MacPorts), and I ran into
something just like this. The directory /opt/local/var/run/couchdb didn't
exist, and CouchDB didn't have the permissions to create it. Start-up failed
with a completely non-descriptive error message. Should I open a separate
ticket for this?
> More explicit error messages when there are file access errors due to lack of
> permission
>
>
> Key: COUCHDB-966
> URL: https://issues.apache.org/jira/browse/COUCHDB-966
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
>Affects Versions: 1.0
> Environment: Any
>Reporter: MC Brown
>Assignee: Filipe Manana
>Priority: Minor
> Fix For: 1.1, 1.2
>
> Attachments: COUCHDB-966.patch, COUCHDB-966.patch
>
>
> If you try to update the configuration settings, either through the API or
> Futon, but the underlying configuration files are not writable by the CouchDB
> process, the API response is '500', and the Futon response is just to appear
> to have frozen.
> Checking the log, you get this output:
> [Thu, 25 Nov 2010 12:51:45 GMT] [error] [<0.31700.81>] ** Generic server
> couch_config terminating
> ** Last message in was {set,"uuids","algorithm","random",true}
> ** When Server state == {config,[{<0.31726.81>,#Fun},
> {<0.31719.81>,#Fun},
> {<0.31719.81>,#Fun},
> {<0.31717.81>,#Fun},
> {<0.31715.81>,#Fun},
> {<0.31714.81>,#Fun},
> {<0.31714.81>,#Fun},
> {<0.31712.81>,#Fun},
> {<0.31711.81>,#Fun},
> {<0.31709.81>,#Fun},
> {false,#Fun},
> {<0.31706.81>,#Fun},
> {<0.31706.81>,#Fun},
> {<0.6.0>,#Fun}],
> "/etc/couchdb/local.ini"}
> ** Reason for termination ==
> ** {{badmatch,{error,eacces}},
> [{couch_config_writer,save_to_file,2},
> {couch_config,handle_call,3},
> {gen_server,handle_msg,5},
> {proc_lib,init_p_do_apply,3}]}
> [Thu, 25 Nov 2010 12:51:45 GMT] [error] [<0.31700.81>] {error_report,<0.32.0>,
> {<0.31700.81>,crash_report,
>[[{initial_call,{couch_config,init,['Argument__1']}},
> {pid,<0.31700.81>},
> {registered_name,couch_config},
> {error_info,{exit,{{badmatch,{error,eacces}},
> [{couch_config_writer,save_to_file,2},
> {couch_config,handle_call,3},
> {gen_server,handle_msg,5},
> {proc_lib,init_p_do_apply,3}]},
>[{gen_server,terminate,6},
> {proc_lib,init_p_do_apply,3}]}},
> {ancestors,[couch_server_sup,<0.33.0>]},
> {messages,[]},
> {links,[<0.79.0>]},
> {dictionary,[]},
> {trap_exit,false},
> {status,running},
> {heap_size,6765},
> {stack_size,24},
> {reductions,52930}],
> []]}}
> [Thu, 25 Nov 2010 12:51:45 GMT] [error] [<0.79.0>] {error_report,<0.32.0>,
> {<0.79.0>,supervisor_report,
> [{supervisor,{local,couch_server_sup}},
> {errorContext,child_terminated},
> {reason,
> {{badmatch,{error,eacces}},
>[{couch_config_writer,save_to_file,2},
> {couch_config,handle_call,3},
> {gen_server,handle_msg,5},
> {proc_lib,init_p_do_apply,3}]}},
> {offender,
> [{pid,<0.31700.81>},
>{name,couch_config},
>{mfa,
>{couch_server_sup,couch_config_start_link_wrapper,
>[["/etc/couchdb/default.ini","/etc/couchdb/local.ini",
Re: Web site in git
Yeah. Delete away! On Fri, Feb 24, 2012 at 7:26 PM, Noah Slater wrote: > Deferring to Paul, but sounds okay. > > On Sat, Feb 25, 2012 at 1:25 AM, Randall Leeds wrote: > >> Okay if I just delete the branch? >> On Feb 24, 2012 3:36 PM, "Noah Slater" wrote: >> >> > Randal, can you rewind your changes please? >> > >> > On Tue, Feb 21, 2012 at 4:45 PM, Paul Davis > > >wrote: >> > >> > > Indeed. Infra is requiring website code to remain in SVN for the time >> > > being and use the svnpubsub stuff they have configured. >> > > >> > > On Tue, Feb 21, 2012 at 2:49 AM, Randall Leeds < >> randall.le...@gmail.com> >> > > wrote: >> > > > On Tue, Feb 21, 2012 at 00:00, Noah Slater >> > wrote: >> > > >> Hey, >> > > >> >> > > >> I appreciate the gesture. But I think we may need to leave the >> website >> > > in >> > > >> Subversion for now. The infrastructure side of things hooks in to >> it. >> > We >> > > >> may be able to move to Git, but we should clarify that with infra >> > first. >> > > > >> > > > I had the same thought, but went ahead anyway knowing it would have >> no >> > > > integration. >> > > > Probably a silly gesture. >> > > > >> > > >> >> > > >> On Tue, Feb 21, 2012 at 7:27 AM, Randall Leeds < >> > randall.le...@gmail.com >> > > >wrote: >> > > >> >> > > >>> I just pulled the site/htdocs directory from svn and put it up into >> > > >>> the htdocs branch on git. >> > > >>> >> > > >>> I goofed and didn't have site checked out, only htdocs, but rather >> > > >>> than make more noise right now I won't correct that, since I don't >> > > >>> know how much that code will change anyway. >> > > >>> It's a small gesture to help push its development. >> > > >>> >> > > >> > >>
Re: Web site in git
Deferring to Paul, but sounds okay. On Sat, Feb 25, 2012 at 1:25 AM, Randall Leeds wrote: > Okay if I just delete the branch? > On Feb 24, 2012 3:36 PM, "Noah Slater" wrote: > > > Randal, can you rewind your changes please? > > > > On Tue, Feb 21, 2012 at 4:45 PM, Paul Davis > >wrote: > > > > > Indeed. Infra is requiring website code to remain in SVN for the time > > > being and use the svnpubsub stuff they have configured. > > > > > > On Tue, Feb 21, 2012 at 2:49 AM, Randall Leeds < > randall.le...@gmail.com> > > > wrote: > > > > On Tue, Feb 21, 2012 at 00:00, Noah Slater > > wrote: > > > >> Hey, > > > >> > > > >> I appreciate the gesture. But I think we may need to leave the > website > > > in > > > >> Subversion for now. The infrastructure side of things hooks in to > it. > > We > > > >> may be able to move to Git, but we should clarify that with infra > > first. > > > > > > > > I had the same thought, but went ahead anyway knowing it would have > no > > > > integration. > > > > Probably a silly gesture. > > > > > > > >> > > > >> On Tue, Feb 21, 2012 at 7:27 AM, Randall Leeds < > > randall.le...@gmail.com > > > >wrote: > > > >> > > > >>> I just pulled the site/htdocs directory from svn and put it up into > > > >>> the htdocs branch on git. > > > >>> > > > >>> I goofed and didn't have site checked out, only htdocs, but rather > > > >>> than make more noise right now I won't correct that, since I don't > > > >>> know how much that code will change anyway. > > > >>> It's a small gesture to help push its development. > > > >>> > > > > > >
Re: Web site in git
Okay if I just delete the branch? On Feb 24, 2012 3:36 PM, "Noah Slater" wrote: > Randal, can you rewind your changes please? > > On Tue, Feb 21, 2012 at 4:45 PM, Paul Davis >wrote: > > > Indeed. Infra is requiring website code to remain in SVN for the time > > being and use the svnpubsub stuff they have configured. > > > > On Tue, Feb 21, 2012 at 2:49 AM, Randall Leeds > > wrote: > > > On Tue, Feb 21, 2012 at 00:00, Noah Slater > wrote: > > >> Hey, > > >> > > >> I appreciate the gesture. But I think we may need to leave the website > > in > > >> Subversion for now. The infrastructure side of things hooks in to it. > We > > >> may be able to move to Git, but we should clarify that with infra > first. > > > > > > I had the same thought, but went ahead anyway knowing it would have no > > > integration. > > > Probably a silly gesture. > > > > > >> > > >> On Tue, Feb 21, 2012 at 7:27 AM, Randall Leeds < > randall.le...@gmail.com > > >wrote: > > >> > > >>> I just pulled the site/htdocs directory from svn and put it up into > > >>> the htdocs branch on git. > > >>> > > >>> I goofed and didn't have site checked out, only htdocs, but rather > > >>> than make more noise right now I won't correct that, since I don't > > >>> know how much that code will change anyway. > > >>> It's a small gesture to help push its development. > > >>> > > >
[jira] [Created] (COUCHDB-1422) Let _show/_list functions prevent caching
Let _show/_list functions prevent caching
-
Key: COUCHDB-1422
URL: https://issues.apache.org/jira/browse/COUCHDB-1422
Project: CouchDB
Issue Type: Bug
Reporter: Nathan Vander Wilt
Priority: Minor
While CouchDB's automatic ETag handling on Show/List functions is desirable 95%
of the time, I keep running into situations where I want to do something handy
in a documentless show function ("if all you have is a hammer...") but end up
getting into trouble with cached responses.
I think the most straightforward fix is to send along any ETag header in a
viewserver response instead of the default. Currently, instead of *overriding*
the ETag header, the two headers are combined. This does "bust the cache" in
some browsers if the only attempt to revalidate the first one (which happens to
be that of the show function), but Firefox at least sends both back and CouchDB
finds its match and responds with 304 "Not Modified". Letting a show/list
function return a single garbage ETag would let it avoid having its result
considered so strongly valid later.
Consider my stupid simple little public IP address reflector
(https://github.com/natevw/ipcalf/blob/master/shows/address.js) or the
following show:
function (doc, req) {
return "Now is " + Date() + " and here is a unique identifier " +
req.uuid + " which might have more entropy than " + Math.random();
}
There are a lot of interesting/fun things that are well within JavaScript's
reach in a (practically) side-effect free formatting function: different
stylesheet based on user agent, SVG chart of DB stats in req.info, random quote
generator... None of these are practical if the response will quickly end up
locked by a cache — potentially in proxies well upstream of the client — based
on an overly narrow definition (and IMO sometimes needless requirement) of
idempotence.
Letting the show function "bust the cache" by providing a response ETag which
CouchDB won't re-validate would be a simple way to avoid this. With my proposal
above, my IP address example would simply override the ETag and avoid
304-effects altogether:
function (doc, req) {
return {headers:{ETag:'"'+req.uuid+'"'}, body: "Your IP address is: " +
req.peer};
}
[If such a function wanted to allow for some caching benefit, it could provide
an appropriate Expires header 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
Re: [VOTE] Apache CouchDB 1.2.0 -- Windows Binaries
Hi!
Have installed setup-couchdb-1.2.0_otp_R15B.exe on Windows 2003 x86 SP2
Seems like everything works as before except tests (Chrome 16):
changes failure 3317ms
Assertion failed: expected '0', got '2'
Assertion failed: expected '0', got '2'
reduce failure 3658ms
Assertion failed: expected '6', got '7'
Assertion failed: expected '7', got '8'
Assertion failed: expected '8', got '9'
Assertion failed: expected '8', got '9'
Assertion failed: expected '7', got '8'
Assertion failed: expected '6', got '7'
Assertion failed: expected '1', got '2'
Assertion failed: expected '2', got '3'
replicator_db failure 66310ms
Assertion failed: copy === null
Assertion failed: copy === null
Assertion failed: expected 'null', got
'{"_id":"foo666","_rev":"1-8f008c4354eb07d5fbfc399a84bc88a1","value":666}'
Assertion failed: expected 'null', got
'{"_id":"foo666","_rev":"2-19d0c28ea169872441d6d33c2c5a6cce","value":666}'
stats failure 8126ms
Assertion 'We have the same number of open dbs.' failed: expected '2', got '0'
Assertion 'We have the same number of open files.' failed: expected
'4', got '0'
users_db_security failure 906ms
Assertion 'false, "anonymous can read _changes"' failed: anonymous
can read _changes
Assertion 'user can't read _changes' failed: expected
'"unauthorized"', got 'null'
view_errors failure 2047ms
Assertion failed: xhr.status == 500
Assertion failed: result.error == "reduce_overflow_error"
attachment_ranges had failed, but this is expected behavior for Chrome.
--
,,,^..^,,,
[jira] [Commented] (COUCHDB-1330) provides() does not supports returning a status code or headers
[
https://issues.apache.org/jira/browse/COUCHDB-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216133#comment-13216133
]
Alexander Shorin commented on COUCHDB-1330:
---
Oops, it looks like I'd break some things...My position was that provides
functions are operates with data level, providing specific handler for
requested content-type, while headers/status code is metadata that should be
determent early.
However, @Nathan right, there could be {"json": ...} body definition and also
{"base64": ...} that processed behind of scene at CouchDB side. Mixing them
better to count as unexpectable result due to it depends on key order in json
response from query server.
However, there is possible case for data collision:
function (doc, req) {
provides('html', function () {
return {
headers: { Location: 'http://www.iriscouch.com' },
code: 302,
json: {status: 'redirecting', message: 'We will take you with us to
IrisCouch!'}
};
});
return {
code: 404,
headers: {"X-Couch-Reponse": "Relax!"}
json: {error: 'not_a_chance', reason: "I'm tired, leave me alone!"}
}
}
What is expected output? 404 and error message or 302 and redirect? Should
headers be merged or provided_resp one only wins? IMHO, provided_resp should
override all resp data, except in case of chunked response when resp.body =
resp.chunks + resp.body + provided_resp.chunks + provided_resp.body.
If nobody stand against those terms I'll update patch to follow described
behavior.
> provides() does not supports returning a status code or headers
> ---
>
> Key: COUCHDB-1330
> URL: https://issues.apache.org/jira/browse/COUCHDB-1330
> Project: CouchDB
> Issue Type: Bug
> Components: JavaScript View Server
>Affects Versions: 1.1.1
> Environment: Iris Couch
>Reporter: Jason Smith
>Priority: Minor
> Attachments:
> A_0001-Support-provides-callbacks-indicating-status-code-an.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> An Iris Couch user lost the ability to redirect from a provides() callback in
> a show function:
> http://getsatisfaction.com/iriscouch/topics/_provides_method_not_returning_code_and_headers
> This show function no longer works:
> function (doc, req) {
> provides('html', function () {
> return {
> headers: { Location: 'http://www.iriscouch.com' },
> code: 302,
> body: 'Redirecting to IrisCouch website...'
> };
> });
> }
> This looks like a regression from 1.1.0; although there are no unit tests so
> perhaps strictly speaking it was unsupported functionality. Git bisect places
> the error at the patch to COUCHDB-1272.
--
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: [VOTE] Apache CouchDB 1.2.0 -- Windows Binaries
Using R14B04
Windows 7 Enterprise, SP 1, 64-bit
Firefox 10.0.2 (privacy mode, cache cleared)
signature OK
md5 & sha OK
No malware
End-user verification OK
Futon tests failed:
replication
1. *Assertion failed:* |expected '"tony"', got 'null'|
2. *Assertion 'Unauthorized to cancel replication' failed:* |expected
'401', got '200'|
3. *Assertion failed:* |expected '"unauthorized"', got 'null'|
4. *Assertion 'Authorized to cancel replication' failed:* |expected
'200', got '404'|
replicator_db
1. *Assertion failed:* |copy === null|
2. *Assertion failed:* |expected 'null', got
'{"_id":"foo666","_rev":"1-8f008c4354eb07d5fbfc399a84bc88a1","value":666}'|
Similar errors reported by Nick North. If these are known/acceptable
timing issues, then still
+1
On 2/24/2012 12:16 PM, Dave Cottlehuber wrote:
Hello,
I would like to call a vote on the following Windows binaries based on
the concurrent Apache CouchDB 1.2.0 release artefacts.
We encourage the whole community to download and test these
release artifacts so that any critical issues can be resolved before the
release is made. Everyone is free to vote on this release, so get stuck in!
We are voting on the following two binaries for R14B04 and R15B:
https://people.apache.org/~dch/dist/1.2.0/
These have been built using Microsoft SDK 7.1 from the following
tree-ish in git:
4cd60f3d1683a3445c3248f48ae064fb573db2a1
And include the following 3rd party code:
Erlang R14B04 or R15B
OpenSSL 0.9.8r
wxWidgets 2.8.12
Mozilla JavaScript 1.8.5
cURL 7.23.1
ICU 4.6.1
Inno setup 5.4.3
Please follow the test procedure before voting:
https://wiki.apache.org/couchdb/Windows_Binary_Releases
A+
Dave
Re: Web site in git
Randal, can you rewind your changes please? On Tue, Feb 21, 2012 at 4:45 PM, Paul Davis wrote: > Indeed. Infra is requiring website code to remain in SVN for the time > being and use the svnpubsub stuff they have configured. > > On Tue, Feb 21, 2012 at 2:49 AM, Randall Leeds > wrote: > > On Tue, Feb 21, 2012 at 00:00, Noah Slater wrote: > >> Hey, > >> > >> I appreciate the gesture. But I think we may need to leave the website > in > >> Subversion for now. The infrastructure side of things hooks in to it. We > >> may be able to move to Git, but we should clarify that with infra first. > > > > I had the same thought, but went ahead anyway knowing it would have no > > integration. > > Probably a silly gesture. > > > >> > >> On Tue, Feb 21, 2012 at 7:27 AM, Randall Leeds >wrote: > >> > >>> I just pulled the site/htdocs directory from svn and put it up into > >>> the htdocs branch on git. > >>> > >>> I goofed and didn't have site checked out, only htdocs, but rather > >>> than make more noise right now I won't correct that, since I don't > >>> know how much that code will change anyway. > >>> It's a small gesture to help push its development. > >>> >
Re: [VOTE] Apache CouchDB 1.2.0 -- Windows Binaries
Win8 with R15B much like Win7:
+1
Windows8 Developer Preview x64 (on VMWare)
Firefox 10.0.2
signature OK
md5 & sha OK
No malware
End-user verification OK
Futon tests failed
All passed except replicator_db, which fails in various ways both locally
and over the network, often with: Assertion failed: expected 'null', got
'{"_id":"foo666","_rev":"1-8f008c4354eb07d5fbfc399a84bc88a1","value":666}'. But
I believe this is a known timing issue so am still +1
Nick
On 24 February 2012 18:16, Dave Cottlehuber wrote:
> Hello,
>
> I would like to call a vote on the following Windows binaries based on
> the concurrent Apache CouchDB 1.2.0 release artefacts.
>
> We encourage the whole community to download and test these
> release artifacts so that any critical issues can be resolved before the
> release is made. Everyone is free to vote on this release, so get stuck in!
>
> We are voting on the following two binaries for R14B04 and R15B:
>
> https://people.apache.org/~dch/dist/1.2.0/
>
> These have been built using Microsoft SDK 7.1 from the following
> tree-ish in git:
>
> 4cd60f3d1683a3445c3248f48ae064fb573db2a1
>
> And include the following 3rd party code:
> Erlang R14B04 or R15B
> OpenSSL 0.9.8r
> wxWidgets 2.8.12
> Mozilla JavaScript 1.8.5
> cURL 7.23.1
> ICU 4.6.1
> Inno setup 5.4.3
>
> Please follow the test procedure before voting:
>
> https://wiki.apache.org/couchdb/Windows_Binary_Releases
>
> A+
> Dave
>
Re: [VOTE] Apache CouchDB 1.2.0 -- Windows Binaries
Using R15B:
+1
Windows7 x64
Firefox 10.0.2
signature OK
md5 & sha OK
No malware
End-user verification OK
Futon tests failed
All passed except replicator_db, which fails in various ways both locally
and over the network, often with: Assertion failed: expected 'null', got
'{"_id":"foo666","_rev":"1-8f008c4354eb07d5fbfc399a84bc88a1","value":666}'.
But I believe this is a known timing issue so am still +1.
I'll try to test on other Windows varieties tomorrow.
Nick
On 24 February 2012 18:16, Dave Cottlehuber wrote:
> Hello,
>
> I would like to call a vote on the following Windows binaries based on
> the concurrent Apache CouchDB 1.2.0 release artefacts.
>
> We encourage the whole community to download and test these
> release artifacts so that any critical issues can be resolved before the
> release is made. Everyone is free to vote on this release, so get stuck in!
>
> We are voting on the following two binaries for R14B04 and R15B:
>
> https://people.apache.org/~dch/dist/1.2.0/
>
> These have been built using Microsoft SDK 7.1 from the following
> tree-ish in git:
>
> 4cd60f3d1683a3445c3248f48ae064fb573db2a1
>
> And include the following 3rd party code:
> Erlang R14B04 or R15B
> OpenSSL 0.9.8r
> wxWidgets 2.8.12
> Mozilla JavaScript 1.8.5
> cURL 7.23.1
> ICU 4.6.1
> Inno setup 5.4.3
>
> Please follow the test procedure before voting:
>
> https://wiki.apache.org/couchdb/Windows_Binary_Releases
>
> A+
> Dave
>
Re: [VOTE] Apache CouchDB 1.2.0 -- Windows Binaries
Over to Dave. On Fri, Feb 24, 2012 at 9:17 PM, Andrew Hamilton wrote: > Yes, I was following the instructions on the wiki: > https://wiki.apache.org/couchdb/Windows_Binary_Releases > > -Andrew Hamilton > Project Engineer > www.facilityone.com > > > > > On Feb 24, 2012, at 4:12 PM, Noah Slater wrote: > > > Andrew, were you testing in Firefox in privacy mode with your caches > clear? > > > > On Fri, Feb 24, 2012 at 8:18 PM, Andrew Hamilton > > wrote: > > > >> Not sure if this the best way to show my error log, but I am attaching > the > >> test suite results from couch. > >> > >> -1 > >> Windows 7 x64 > >> Firefox 11.0 > >> signature OK > >> md5 & sha OK > >> No malware > >> End-user verification OK > >> Futon tests failed: > >> attachments > >> attachment_paths > >> config > >> cookie_auth > >> delayed_commits > >> design_docs > >> erlang views > >> invalid_docids > >> replicator_db > >> view_errors > >> > >> -Andrew Hamilton > >> Project Engineer > >> www.facilityone.com > >> > >> > >> > >> > >> > >> On Feb 24, 2012, at 1:16 PM, Dave Cottlehuber wrote: > >> > >>> Hello, > >>> > >>> I would like to call a vote on the following Windows binaries based on > >>> the concurrent Apache CouchDB 1.2.0 release artefacts. > >>> > >>> We encourage the whole community to download and test these > >>> release artifacts so that any critical issues can be resolved before > the > >>> release is made. Everyone is free to vote on this release, so get stuck > >> in! > >>> > >>> We are voting on the following two binaries for R14B04 and R15B: > >>> > >>> https://people.apache.org/~dch/dist/1.2.0/ > >>> > >>> These have been built using Microsoft SDK 7.1 from the following > >>> tree-ish in git: > >>> > >>> 4cd60f3d1683a3445c3248f48ae064fb573db2a1 > >>> > >>> And include the following 3rd party code: > >>> Erlang R14B04 or R15B > >>> OpenSSL 0.9.8r > >>> wxWidgets 2.8.12 > >>> Mozilla JavaScript 1.8.5 > >>> cURL 7.23.1 > >>> ICU 4.6.1 > >>> Inno setup 5.4.3 > >>> > >>> Please follow the test procedure before voting: > >>> > >>> https://wiki.apache.org/couchdb/Windows_Binary_Releases > >>> > >>> A+ > >>> Dave > >> > >> > >> > >
Re: [VOTE] Apache CouchDB 1.2.0 -- Windows Binaries
Yes, I was following the instructions on the wiki: https://wiki.apache.org/couchdb/Windows_Binary_Releases -Andrew Hamilton Project Engineer www.facilityone.com On Feb 24, 2012, at 4:12 PM, Noah Slater wrote: > Andrew, were you testing in Firefox in privacy mode with your caches clear? > > On Fri, Feb 24, 2012 at 8:18 PM, Andrew Hamilton > wrote: > >> Not sure if this the best way to show my error log, but I am attaching the >> test suite results from couch. >> >> -1 >> Windows 7 x64 >> Firefox 11.0 >> signature OK >> md5 & sha OK >> No malware >> End-user verification OK >> Futon tests failed: >> attachments >> attachment_paths >> config >> cookie_auth >> delayed_commits >> design_docs >> erlang views >> invalid_docids >> replicator_db >> view_errors >> >> -Andrew Hamilton >> Project Engineer >> www.facilityone.com >> >> >> >> >> >> On Feb 24, 2012, at 1:16 PM, Dave Cottlehuber wrote: >> >>> Hello, >>> >>> I would like to call a vote on the following Windows binaries based on >>> the concurrent Apache CouchDB 1.2.0 release artefacts. >>> >>> We encourage the whole community to download and test these >>> release artifacts so that any critical issues can be resolved before the >>> release is made. Everyone is free to vote on this release, so get stuck >> in! >>> >>> We are voting on the following two binaries for R14B04 and R15B: >>> >>> https://people.apache.org/~dch/dist/1.2.0/ >>> >>> These have been built using Microsoft SDK 7.1 from the following >>> tree-ish in git: >>> >>> 4cd60f3d1683a3445c3248f48ae064fb573db2a1 >>> >>> And include the following 3rd party code: >>> Erlang R14B04 or R15B >>> OpenSSL 0.9.8r >>> wxWidgets 2.8.12 >>> Mozilla JavaScript 1.8.5 >>> cURL 7.23.1 >>> ICU 4.6.1 >>> Inno setup 5.4.3 >>> >>> Please follow the test procedure before voting: >>> >>> https://wiki.apache.org/couchdb/Windows_Binary_Releases >>> >>> A+ >>> Dave >> >> >>
Re: [VOTE] Apache CouchDB 1.2.0 -- Windows Binaries
Andrew, were you testing in Firefox in privacy mode with your caches clear? On Fri, Feb 24, 2012 at 8:18 PM, Andrew Hamilton wrote: > Not sure if this the best way to show my error log, but I am attaching the > test suite results from couch. > > -1 > Windows 7 x64 > Firefox 11.0 > signature OK > md5 & sha OK > No malware > End-user verification OK > Futon tests failed: >attachments >attachment_paths >config >cookie_auth >delayed_commits >design_docs >erlang views >invalid_docids >replicator_db >view_errors > > -Andrew Hamilton > Project Engineer > www.facilityone.com > > > > > > On Feb 24, 2012, at 1:16 PM, Dave Cottlehuber wrote: > > > Hello, > > > > I would like to call a vote on the following Windows binaries based on > > the concurrent Apache CouchDB 1.2.0 release artefacts. > > > > We encourage the whole community to download and test these > > release artifacts so that any critical issues can be resolved before the > > release is made. Everyone is free to vote on this release, so get stuck > in! > > > > We are voting on the following two binaries for R14B04 and R15B: > > > > https://people.apache.org/~dch/dist/1.2.0/ > > > > These have been built using Microsoft SDK 7.1 from the following > > tree-ish in git: > > > > 4cd60f3d1683a3445c3248f48ae064fb573db2a1 > > > > And include the following 3rd party code: > > Erlang R14B04 or R15B > > OpenSSL 0.9.8r > > wxWidgets 2.8.12 > > Mozilla JavaScript 1.8.5 > > cURL 7.23.1 > > ICU 4.6.1 > > Inno setup 5.4.3 > > > > Please follow the test procedure before voting: > > > > https://wiki.apache.org/couchdb/Windows_Binary_Releases > > > > A+ > > Dave > > >
Re: [VOTE] Apache CouchDB 1.2.0 -- Windows Binaries
Not sure if this the best way to show my error log, but I am attaching the test suite results from couch. -1 Windows 7 x64 Firefox 11.0 signature OK md5 & sha OK No malware End-user verification OK Futon tests failed: attachments attachment_paths config cookie_auth delayed_commits design_docs erlang views invalid_docids replicator_db view_errors -Andrew Hamilton Project Engineer www.facilityone.com dev_test.json Description: application/json On Feb 24, 2012, at 1:16 PM, Dave Cottlehuber wrote: > Hello, > > I would like to call a vote on the following Windows binaries based on > the concurrent Apache CouchDB 1.2.0 release artefacts. > > We encourage the whole community to download and test these > release artifacts so that any critical issues can be resolved before the > release is made. Everyone is free to vote on this release, so get stuck in! > > We are voting on the following two binaries for R14B04 and R15B: > > https://people.apache.org/~dch/dist/1.2.0/ > > These have been built using Microsoft SDK 7.1 from the following > tree-ish in git: > > 4cd60f3d1683a3445c3248f48ae064fb573db2a1 > > And include the following 3rd party code: > Erlang R14B04 or R15B > OpenSSL 0.9.8r > wxWidgets 2.8.12 > Mozilla JavaScript 1.8.5 > cURL 7.23.1 > ICU 4.6.1 > Inno setup 5.4.3 > > Please follow the test procedure before voting: > > https://wiki.apache.org/couchdb/Windows_Binary_Releases > > A+ > Dave
Re: [VOTE] Apache CouchDB 1.2.0 -- Windows Binaries
On Fri, Feb 24, 2012 at 19:16, Dave Cottlehuber wrote: > We are voting on the following two binaries for R14B04 and R15B: > > https://people.apache.org/~dch/dist/1.2.0/ On Windows 7, 64-bit, I downloaded the R15B version of the installer and installed it. Located couchdb.bat in the bin folder, ran it, pointed the brower at localhost:5984 and ran the test suite. Everything seemed to work alright except that from users_db_security on, all tests started failing with "error": "unauthorized", "reason": "You are not a server admin". This subsequently even happened on rerunning tests that had previously passed. (I'm admittedly a stranger to CouchDB on Windows, although I've run it on Linux boxen for years.) Cheers, Dirkjan
[jira] [Commented] (COUCHDB-1330) provides() does not supports returning a status code or headers
[
https://issues.apache.org/jira/browse/COUCHDB-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215849#comment-13215849
]
Nathan Vander Wilt commented on COUCHDB-1330:
-
Just noticed one thing that might warrant further review by someone who
understands the stack a little better:
Jason's patch will always set "provided_resp.body", potentially to an empty
string. Could the presence of that (albeit empty) string conflict with
provided_resp.json field at the Erlang level?
> provides() does not supports returning a status code or headers
> ---
>
> Key: COUCHDB-1330
> URL: https://issues.apache.org/jira/browse/COUCHDB-1330
> Project: CouchDB
> Issue Type: Bug
> Components: JavaScript View Server
>Affects Versions: 1.1.1
> Environment: Iris Couch
>Reporter: Jason Smith
>Priority: Minor
> Attachments:
> A_0001-Support-provides-callbacks-indicating-status-code-an.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> An Iris Couch user lost the ability to redirect from a provides() callback in
> a show function:
> http://getsatisfaction.com/iriscouch/topics/_provides_method_not_returning_code_and_headers
> This show function no longer works:
> function (doc, req) {
> provides('html', function () {
> return {
> headers: { Location: 'http://www.iriscouch.com' },
> code: 302,
> body: 'Redirecting to IrisCouch website...'
> };
> });
> }
> This looks like a regression from 1.1.0; although there are no unit tests so
> perhaps strictly speaking it was unsupported functionality. Git bisect places
> the error at the patch to COUCHDB-1272.
--
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] [Commented] (COUCHDB-1330) provides() does not supports returning a status code or headers
[
https://issues.apache.org/jira/browse/COUCHDB-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215843#comment-13215843
]
Nathan Vander Wilt commented on COUCHDB-1330:
-
This regression was introduced by
https://github.com/apache/couchdb/commit/92f70219ce5ba487e4eb65dea7d16a9168a8547f#share/server/render.js
for [#COUCHDB-1272] and also breaks returning "json" instead of "body".
Jason's patch looks good to me for fixing it, and I'd love to see it applied
soon.
> provides() does not supports returning a status code or headers
> ---
>
> Key: COUCHDB-1330
> URL: https://issues.apache.org/jira/browse/COUCHDB-1330
> Project: CouchDB
> Issue Type: Bug
> Components: JavaScript View Server
>Affects Versions: 1.1.1
> Environment: Iris Couch
>Reporter: Jason Smith
>Priority: Minor
> Attachments:
> A_0001-Support-provides-callbacks-indicating-status-code-an.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> An Iris Couch user lost the ability to redirect from a provides() callback in
> a show function:
> http://getsatisfaction.com/iriscouch/topics/_provides_method_not_returning_code_and_headers
> This show function no longer works:
> function (doc, req) {
> provides('html', function () {
> return {
> headers: { Location: 'http://www.iriscouch.com' },
> code: 302,
> body: 'Redirecting to IrisCouch website...'
> };
> });
> }
> This looks like a regression from 1.1.0; although there are no unit tests so
> perhaps strictly speaking it was unsupported functionality. Git bisect places
> the error at the patch to COUCHDB-1272.
--
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
[VOTE] Apache CouchDB 1.2.0 -- Windows Binaries
Hello, I would like to call a vote on the following Windows binaries based on the concurrent Apache CouchDB 1.2.0 release artefacts. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release, so get stuck in! We are voting on the following two binaries for R14B04 and R15B: https://people.apache.org/~dch/dist/1.2.0/ These have been built using Microsoft SDK 7.1 from the following tree-ish in git: 4cd60f3d1683a3445c3248f48ae064fb573db2a1 And include the following 3rd party code: Erlang R14B04 or R15B OpenSSL 0.9.8r wxWidgets 2.8.12 Mozilla JavaScript 1.8.5 cURL 7.23.1 ICU 4.6.1 Inno setup 5.4.3 Please follow the test procedure before voting: https://wiki.apache.org/couchdb/Windows_Binary_Releases A+ Dave
Re: Rebuilding the couchdb rpm on CentOS6.2?
Hi, Just a heads up, the etap tests in couchdb 1.0.2 require to run on port 5984 (this was fixed in 1.0.3). I just rebuild the couchdb 1.0.2 rpm without any issues on a CentOS6.2 VM without couchdb running. Best regards, Jeroen Janssen On Fri, Feb 24, 2012 at 10:58 AM, Jeroen Janssen wrote: > Hi, > > I have a CentOS 6.2 machine currently running couchdb-1.0.2-8.el6.x86_64 > > In order to (eventually) build a couchdb 1.2 rpm I am trying to > rebuild couchdb 1.0.2 from the source rpm to verify my build > environment is setup correctly. > I installed the couchdb-1.0.2 source rpm and did yum-builddep couchdb > to install the build dependencies. > > However, rebuilding the rpm fails for me with failing tests and as a > result doesn't finish correctly. > > Test Summary Report > --- > /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/070-couch-db.t > (Wstat: 256 Tests: 0 Failed: 0) > Non-zero exit status: 1 > Parse errors: Bad plan. You planned 4 tests but ran 0. > /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/110-replication-httpc.t > (Wstat: 256 Tests: 0 Failed: 0) > Non-zero exit status: 1 > Parse errors: Bad plan. You planned 6 tests but ran 0. > /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/111-replication-changes-feed.t > (Wstat: 256 Tests: 0 Failed: 0) > Non-zero exit status: 1 > Parse errors: Bad plan. You planned 13 tests but ran 0. > /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/112-replication-missing-revs.t > (Wstat: 256 Tests: 0 Failed: 0) > Non-zero exit status: 1 > Parse errors: Bad plan. You planned 12 tests but ran 0. > /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/113-replication-attachment-comp.t > (Wstat: 256 Tests: 0 Failed: 0) > Non-zero exit status: 1 > Parse errors: Bad plan. You planned 45 tests but ran 0. > /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/130-attachments-md5.t > (Wstat: 256 Tests: 0 Failed: 0) > Non-zero exit status: 1 > Parse errors: Bad plan. You planned 16 tests but ran 0. > /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/140-attachment-comp.t > (Wstat: 256 Tests: 0 Failed: 0) > Non-zero exit status: 1 > Parse errors: Bad plan. You planned 86 tests but ran 0. > /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/150-invalid-view-seq.t > (Wstat: 256 Tests: 0 Failed: 0) > Non-zero exit status: 1 > Parse errors: Bad plan. You planned 10 tests but ran 0. > /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/160-vhosts.t > (Wstat: 256 Tests: 0 Failed: 0) > Non-zero exit status: 1 > Parse errors: Bad plan. You planned 4 tests but ran 0. > Files=34, Tests=332, 22 wallclock secs ( 0.16 usr 0.06 sys + 12.21 > cusr 5.77 csys = 18.20 CPU) > Result: FAIL > make: *** [check] Error 1 > + exit 1 > error: Bad exit status from /var/tmp/rpm-tmp.acze6o (%check) > > RPM build errors: > Bad exit status from /var/tmp/rpm-tmp.acze6o (%check) > > Has anyone else ever rebuild couchdb (1.0.2) from the source rpm > succesfully (or any tips/hints on how to proceed here)? > Is anyone else working on getting a couchdb 1.2 rpm working for RHEL6/CentOS6? > > Thanks in advance, > > Jeroen Janssen
Re: [VOTE] Apache CouchDB 1.2.0 release, second round
On Fri, Feb 24, 2012 at 4:39 PM, Benoit Chesneau wrote: > On Thu, Feb 23, 2012 at 12:28 AM, Noah Slater wrote: >> Hello, >> >> I would like call a vote for the Apache CouchDB 1.2.0 release, second round. >> >> We encourage the whole community to download and test these >> release artifacts so that any critical issues can be resolved before the >> release is made. Everyone is free to vote on this release, so get stuck in! >> >> We are voting on the following release artifacts: >> >> http://people.apache.org/~nslater/dist/1.2.0/ >> >> >> These artifacts have been built from the following tree-ish in Git: >> >> 4cd60f3d1683a3445c3248f48ae064fb573db2a1 >> >> >> Please follow the test procedure before voting: >> >> http://wiki.apache.org/couchdb/Test_procedure >> >> >> Thank you. >> >> Happy voting, >> >> N > > +1 make check &, js tests & signatures ok > > erlang R14B04 - osx lion & snow leopard, ubuntu 11.04, 11.10, debian 6, fbsd > 8.2 > > - benoît q note: i had to buy my openssl to have it working with it on osx lion. Also I used spidermonkey 1.8.5.
Re: [VOTE] Apache CouchDB 1.2.0 release, second round
On Thu, Feb 23, 2012 at 12:28 AM, Noah Slater wrote: > Hello, > > I would like call a vote for the Apache CouchDB 1.2.0 release, second round. > > We encourage the whole community to download and test these > release artifacts so that any critical issues can be resolved before the > release is made. Everyone is free to vote on this release, so get stuck in! > > We are voting on the following release artifacts: > > http://people.apache.org/~nslater/dist/1.2.0/ > > > These artifacts have been built from the following tree-ish in Git: > > 4cd60f3d1683a3445c3248f48ae064fb573db2a1 > > > Please follow the test procedure before voting: > > http://wiki.apache.org/couchdb/Test_procedure > > > Thank you. > > Happy voting, > > N +1 make check &, js tests & signatures ok erlang R14B04 - osx lion & snow leopard, ubuntu 11.04, 11.10, debian 6, fbsd 8.2 - benoît
Re: Couchbase trademark issues
That's an interesting approach Christian, thanks! I'll revisit this method once we get around to doing the new site. On Fri, Feb 24, 2012 at 2:55 AM, Bob Dionne wrote: > I like this look, crisper and easier to read. Nice work > > > On Feb 23, 2012, at 9:20 PM, Christian Swinehart wrote: > > > On Mon, Feb 20, 2012 at 7:12 AM, Robert Newson > wrote: > >> coinciding with the 1.2 release would be awesome > >> > >> On 20 February 2012 12:09, Robert Newson wrote: > >>> 1 for a revamped couchdb.apache.org. The most recent change, I > >>> think, was mine, which simply dropped the misleading diagram in the > >>> top-right. Long past time for an overhaul. Who has the time and skill > >>> to make this happen? > > > > as one potential drop in that bucket, i spent some time fiddling with > > the wiki's css to bring it more in line with the project's color > > scheme. i also took the liberty of tweaking the typography a bit. > > > > here's a demo (based on what i was able to wget of the site): > > http://samizdat.cc/couchdb/ > > > > all the modifications can be found in: > > http://samizdat.cc/moin_static188/modernized/css/screen.css > > except for the header image which lives at: > > > http://samizdat.cc/moin_static188/modernized/img/couchdb-wiki-logo-small.png > > > > -christian > >
Re: [VOTE] Apache CouchDB 1.2.0 release, second round
+1! Jonathan Porta On Fri, Feb 24, 2012 at 7:07 AM, Sebastian Cohnen wrote: > Jonathan, you forgot to cast your vote! (Which needs to be either +1 or -1) > > On 24.02.2012, at 14:50, Jonathan Porta wrote: > >> Fedora 15 64bit, Erlang 14B04, Spidermonkey 1.8.5 >> >> Everything checks out! >> >> Jonathan Porta >> >> >> >> On Fri, Feb 24, 2012 at 3:44 AM, Dirkjan Ochtman wrote: >>> On Thu, Feb 23, 2012 at 00:28, Noah Slater wrote: We are voting on the following release artifacts: http://people.apache.org/~nslater/dist/1.2.0/ >>> >>> Gentoo Linux 64-bits, Erlang 13B4, Spidermonkey 1.8.5. >>> >>> Signatures check out, make check passes. >>> >>> Browser tests pass in Firefox 12.0a2, although replicator_db_security >>> failed once before it succeeded. >>> >>> +1 on release. >>> >>> Cheers, >>> >>> Dirkjan >
Re: [VOTE] Apache CouchDB 1.2.0 release, second round
On Wed, Feb 22, 2012 at 11:28 PM, Noah Slater wrote: > Hello, > > I would like call a vote for the Apache CouchDB 1.2.0 release, second round. > > We encourage the whole community to download and test these > release artifacts so that any critical issues can be resolved before the > release is made. Everyone is free to vote on this release, so get stuck in! > > We are voting on the following release artifacts: > > http://people.apache.org/~nslater/dist/1.2.0/ > > > These artifacts have been built from the following tree-ish in Git: > > 4cd60f3d1683a3445c3248f48ae064fb573db2a1 > > > Please follow the test procedure before voting: > > http://wiki.apache.org/couchdb/Test_procedure +1 Good build, make check, browser tests pass: * Fedora 16, R15B * Ubuntu 11.10, R15B * Ubuntu 10.04 LTS, R15B * OS X Lion, R15B, no crashes or hangs either -- Iris Couch
Re: [VOTE] Apache CouchDB 1.2.0 release, second round
Jonathan, you forgot to cast your vote! (Which needs to be either +1 or −1) On 24.02.2012, at 14:50, Jonathan Porta wrote: > Fedora 15 64bit, Erlang 14B04, Spidermonkey 1.8.5 > > Everything checks out! > > Jonathan Porta > > > > On Fri, Feb 24, 2012 at 3:44 AM, Dirkjan Ochtman wrote: >> On Thu, Feb 23, 2012 at 00:28, Noah Slater wrote: >>> We are voting on the following release artifacts: >>> >>> http://people.apache.org/~nslater/dist/1.2.0/ >> >> Gentoo Linux 64-bits, Erlang 13B4, Spidermonkey 1.8.5. >> >> Signatures check out, make check passes. >> >> Browser tests pass in Firefox 12.0a2, although replicator_db_security >> failed once before it succeeded. >> >> +1 on release. >> >> Cheers, >> >> Dirkjan
Re: [VOTE] Apache CouchDB 1.2.0 release, second round
Fedora 15 64bit, Erlang 14B04, Spidermonkey 1.8.5 Everything checks out! Jonathan Porta On Fri, Feb 24, 2012 at 3:44 AM, Dirkjan Ochtman wrote: > On Thu, Feb 23, 2012 at 00:28, Noah Slater wrote: >> We are voting on the following release artifacts: >> >> http://people.apache.org/~nslater/dist/1.2.0/ > > Gentoo Linux 64-bits, Erlang 13B4, Spidermonkey 1.8.5. > > Signatures check out, make check passes. > > Browser tests pass in Firefox 12.0a2, although replicator_db_security > failed once before it succeeded. > > +1 on release. > > Cheers, > > Dirkjan
[jira] [Commented] (COUCHDB-523) View API POST keys to retrieve multiple docs by key could also allow for multiple 'range' queries, i.e. an array of { startkey: .., endkey: ... } params in the POST
[
https://issues.apache.org/jira/browse/COUCHDB-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215576#comment-13215576
]
Robert Newson commented on COUCHDB-523:
---
also +1 on the array/order preserving API and -1 on the object thing, just to
get things moving.
> View API POST keys to retrieve multiple docs by key could also allow for
> multiple 'range' queries, i.e. an array of { startkey: .., endkey: ... }
> params in the POST
>
>
> Key: COUCHDB-523
> URL: https://issues.apache.org/jira/browse/COUCHDB-523
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
>Reporter: Nathan Stott
>Assignee: Adam Kocoloski
>Priority: Minor
> Fix For: 1.3
>
> Attachments: couch_httpd_view.erl, multi_start_end_key.diff,
> ranged_key_post.diff
>
>
> It would be useful if I could do a single POST to a view to retrieve multiple
> ranges specified by startkey, endkey.
> The format could be as follows:
> { "ranges": [ { "startkey": "a", "endkey": "c" }, { "startkey":"g",
> "endkey":"z" } ] }
--
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-523) View API POST keys to retrieve multiple docs by key could also allow for multiple 'range' queries, i.e. an array of { startkey: .., endkey: ... } params in the POST
[
https://issues.apache.org/jira/browse/COUCHDB-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson updated COUCHDB-523:
--
Fix Version/s: 1.3
Let's reopen this and try to get it done for 1.3. I don't see any fundamental
objection just bikeshedding over the API.
> View API POST keys to retrieve multiple docs by key could also allow for
> multiple 'range' queries, i.e. an array of { startkey: .., endkey: ... }
> params in the POST
>
>
> Key: COUCHDB-523
> URL: https://issues.apache.org/jira/browse/COUCHDB-523
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
>Reporter: Nathan Stott
>Assignee: Adam Kocoloski
>Priority: Minor
> Fix For: 1.3
>
> Attachments: couch_httpd_view.erl, multi_start_end_key.diff,
> ranged_key_post.diff
>
>
> It would be useful if I could do a single POST to a view to retrieve multiple
> ranges specified by startkey, endkey.
> The format could be as follows:
> { "ranges": [ { "startkey": "a", "endkey": "c" }, { "startkey":"g",
> "endkey":"z" } ] }
--
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: [VOTE] Apache CouchDB 1.2.0 release, second round
On Thu, Feb 23, 2012 at 00:28, Noah Slater wrote: > We are voting on the following release artifacts: > > http://people.apache.org/~nslater/dist/1.2.0/ Gentoo Linux 64-bits, Erlang 13B4, Spidermonkey 1.8.5. Signatures check out, make check passes. Browser tests pass in Firefox 12.0a2, although replicator_db_security failed once before it succeeded. +1 on release. Cheers, Dirkjan
Re: [VOTE] Apache CouchDB 1.2.0 release, second round
thanks for the clarification, Bob. I wasn't ware of this issue. On 24.02.2012, at 10:28, Robert Newson wrote: > attachment_ranges is expected to fail on Chrome because Chrome is wrong. > > to prove this more clearly, change line 29 of the test to "Range": > "bytes=0-1000" and run it again, Chrome will tell you it > fetched 1001 bytes of the 28 byte attachment. A neat trick. > > B. > > On 24 February 2012 09:03, Sebastian Cohnen > wrote: >> OS X 10.7.3, Erlang R15B, Spidermonkey 1.8.5, tests run in Chrome >> 19.0.1049.3 dev >> >> * signatures okay >> * make check okay >> * test suite okay (the "attachment_ranges" test constantly fails [1] in >> Chrome, but works fine in FF 10.0) >> >> >> So I'm +1 >> >> >> [1]: >> expected '"bytes 0-28/29"', got '"bytes 0-29/29"' >> expected '"29"', got '"30"' >> >> On 23.02.2012, at 00:28, Noah Slater wrote: >> >>> Hello, >>> >>> I would like call a vote for the Apache CouchDB 1.2.0 release, second round. >>> >>> We encourage the whole community to download and test these >>> release artifacts so that any critical issues can be resolved before the >>> release is made. Everyone is free to vote on this release, so get stuck in! >>> >>> We are voting on the following release artifacts: >>> >>> http://people.apache.org/~nslater/dist/1.2.0/ >>> >>> >>> These artifacts have been built from the following tree-ish in Git: >>> >>> 4cd60f3d1683a3445c3248f48ae064fb573db2a1 >>> >>> >>> Please follow the test procedure before voting: >>> >>> http://wiki.apache.org/couchdb/Test_procedure >>> >>> >>> Thank you. >>> >>> Happy voting, >>> >>> N >>
Rebuilding the couchdb rpm on CentOS6.2?
Hi, I have a CentOS 6.2 machine currently running couchdb-1.0.2-8.el6.x86_64 In order to (eventually) build a couchdb 1.2 rpm I am trying to rebuild couchdb 1.0.2 from the source rpm to verify my build environment is setup correctly. I installed the couchdb-1.0.2 source rpm and did yum-builddep couchdb to install the build dependencies. However, rebuilding the rpm fails for me with failing tests and as a result doesn't finish correctly. Test Summary Report --- /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/070-couch-db.t (Wstat: 256 Tests: 0 Failed: 0) Non-zero exit status: 1 Parse errors: Bad plan. You planned 4 tests but ran 0. /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/110-replication-httpc.t (Wstat: 256 Tests: 0 Failed: 0) Non-zero exit status: 1 Parse errors: Bad plan. You planned 6 tests but ran 0. /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/111-replication-changes-feed.t (Wstat: 256 Tests: 0 Failed: 0) Non-zero exit status: 1 Parse errors: Bad plan. You planned 13 tests but ran 0. /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/112-replication-missing-revs.t (Wstat: 256 Tests: 0 Failed: 0) Non-zero exit status: 1 Parse errors: Bad plan. You planned 12 tests but ran 0. /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/113-replication-attachment-comp.t (Wstat: 256 Tests: 0 Failed: 0) Non-zero exit status: 1 Parse errors: Bad plan. You planned 45 tests but ran 0. /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/130-attachments-md5.t (Wstat: 256 Tests: 0 Failed: 0) Non-zero exit status: 1 Parse errors: Bad plan. You planned 16 tests but ran 0. /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/140-attachment-comp.t (Wstat: 256 Tests: 0 Failed: 0) Non-zero exit status: 1 Parse errors: Bad plan. You planned 86 tests but ran 0. /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/150-invalid-view-seq.t (Wstat: 256 Tests: 0 Failed: 0) Non-zero exit status: 1 Parse errors: Bad plan. You planned 10 tests but ran 0. /home/rpmbuild/rpmbuild/BUILD/apache-couchdb-1.0.2/test/etap/160-vhosts.t (Wstat: 256 Tests: 0 Failed: 0) Non-zero exit status: 1 Parse errors: Bad plan. You planned 4 tests but ran 0. Files=34, Tests=332, 22 wallclock secs ( 0.16 usr 0.06 sys + 12.21 cusr 5.77 csys = 18.20 CPU) Result: FAIL make: *** [check] Error 1 + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.acze6o (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.acze6o (%check) Has anyone else ever rebuild couchdb (1.0.2) from the source rpm succesfully (or any tips/hints on how to proceed here)? Is anyone else working on getting a couchdb 1.2 rpm working for RHEL6/CentOS6? Thanks in advance, Jeroen Janssen
Re: [VOTE] Apache CouchDB 1.2.0 release, second round
attachment_ranges is expected to fail on Chrome because Chrome is wrong. to prove this more clearly, change line 29 of the test to "Range": "bytes=0-1000" and run it again, Chrome will tell you it fetched 1001 bytes of the 28 byte attachment. A neat trick. B. On 24 February 2012 09:03, Sebastian Cohnen wrote: > OS X 10.7.3, Erlang R15B, Spidermonkey 1.8.5, tests run in Chrome 19.0.1049.3 > dev > > * signatures okay > * make check okay > * test suite okay (the "attachment_ranges" test constantly fails [1] in > Chrome, but works fine in FF 10.0) > > > So I'm +1 > > > [1]: > expected '"bytes 0-28/29"', got '"bytes 0-29/29"' > expected '"29"', got '"30"' > > On 23.02.2012, at 00:28, Noah Slater wrote: > >> Hello, >> >> I would like call a vote for the Apache CouchDB 1.2.0 release, second round. >> >> We encourage the whole community to download and test these >> release artifacts so that any critical issues can be resolved before the >> release is made. Everyone is free to vote on this release, so get stuck in! >> >> We are voting on the following release artifacts: >> >> http://people.apache.org/~nslater/dist/1.2.0/ >> >> >> These artifacts have been built from the following tree-ish in Git: >> >> 4cd60f3d1683a3445c3248f48ae064fb573db2a1 >> >> >> Please follow the test procedure before voting: >> >> http://wiki.apache.org/couchdb/Test_procedure >> >> >> Thank you. >> >> Happy voting, >> >> N >
Re: [VOTE] Apache CouchDB 1.2.0 release, second round
OS X 10.7.3, Erlang R15B, Spidermonkey 1.8.5, tests run in Chrome 19.0.1049.3 dev * signatures okay * make check okay * test suite okay (the "attachment_ranges" test constantly fails [1] in Chrome, but works fine in FF 10.0) So I'm +1 [1]: expected '"bytes 0-28/29"', got '"bytes 0-29/29"' expected '"29"', got '"30"' On 23.02.2012, at 00:28, Noah Slater wrote: > Hello, > > I would like call a vote for the Apache CouchDB 1.2.0 release, second round. > > We encourage the whole community to download and test these > release artifacts so that any critical issues can be resolved before the > release is made. Everyone is free to vote on this release, so get stuck in! > > We are voting on the following release artifacts: > > http://people.apache.org/~nslater/dist/1.2.0/ > > > These artifacts have been built from the following tree-ish in Git: > > 4cd60f3d1683a3445c3248f48ae064fb573db2a1 > > > Please follow the test procedure before voting: > > http://wiki.apache.org/couchdb/Test_procedure > > > Thank you. > > Happy voting, > > N
