Re: [jira] [Resolved] (COUCHDB-1228) Key range error apparently ignores view collation
On Thu, Aug 11, 2011 at 1:45 PM, Paul Joseph Davis (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/COUCHDB-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Paul Joseph Davis resolved COUCHDB-1228. > > > Resolution: Fixed > Fix Version/s: (was: 1.1.1) > 1.2 Thanks! Would it be possible to backport this to 1.1.x so it can make the 1.1.1 release? (I actually developed it against 1.1.x unintentionally). -- Iris Couch
[jira] [Updated] (COUCHDB-1227) Deleted validators are still run
[ https://issues.apache.org/jira/browse/COUCHDB-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filipe Manana updated COUCHDB-1227: --- Attachment: couchdb-1227.patch > Deleted validators are still run > > > Key: COUCHDB-1227 > URL: https://issues.apache.org/jira/browse/COUCHDB-1227 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Affects Versions: 1.1 > Environment: Windows XP >Reporter: James Howe >Assignee: Filipe Manana > Labels: delete, validation > Attachments: couchdb-1227.patch > > > If design documents are deleted using an update to add _deleted while still > retaining the validate_doc_update function, it is still run on updates. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (COUCHDB-1227) Deleted validators are still run
[ https://issues.apache.org/jira/browse/COUCHDB-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filipe Manana reassigned COUCHDB-1227: -- Assignee: Filipe Manana > Deleted validators are still run > > > Key: COUCHDB-1227 > URL: https://issues.apache.org/jira/browse/COUCHDB-1227 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Affects Versions: 1.1 > Environment: Windows XP >Reporter: James Howe >Assignee: Filipe Manana > Labels: delete, validation > > If design documents are deleted using an update to add _deleted while still > retaining the validate_doc_update function, it is still run on updates. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1248) 500 http error when replicating with doc_ids=null
500 http error when replicating with doc_ids=null
-
Key: COUCHDB-1248
URL: https://issues.apache.org/jira/browse/COUCHDB-1248
Project: CouchDB
Issue Type: Bug
Components: Replication
Affects Versions: 1.1
Environment: Apple OS X 10.6, CouchDB 1.1.0, Erlang R14B03
Reporter: Erick Tryzelaar
Fix For: 1.0.2
Couchdb 1.1.0 throws an exception when passing a null doc_ids. This error does
not happen in 1.0.2. Here's an example:
$ curl -H "content-type: application/json" -XPUT
"http://127.0.0.1:5984/couchrest-test";
$ curl -H "content-type: application/json" -XPUT
"http://127.0.0.1:5984/couchrest-test-replication";
$ curl -H "content-type: application/json" -XPOST -d
"{\"doc_ids\":null,\"target\":\"couchrest-test-replication\",\"create_target\":false,\"continuous\":false,\"source\":\"http://127.0.0.1:5984/couchrest-test\"}";
"http://127.0.0.1:5984/_replicate";
{"error":"case_clause","reason":"{error,\n{{{badmatch,\n {error,\n
{{case_clause,null},\n
[{couch_rep_changes_feed,init,1},\n{gen_server,init_it,6},\n
{proc_lib,init_p_do_apply,3}]}}},\n [{couch_rep,do_init,1},\n
{couch_rep,init,1},\n {gen_server,init_it,6},\n
{proc_lib,init_p_do_apply,3}]},\n
{child,undefined,\"f88508b53ee0a5ccd49aa64197f385ae\",\n
{gen_server,start_link,\n [couch_rep,\n
[\"f88508b53ee0a5ccd49aa64197f385ae\",\n
{[{<<\"doc_ids\">>,null},\n
{<<\"target\">>,<<\"couchrest-test-replication\">>},\n
{<<\"create_target\">>,false},\n {<<\"continuous\">>,false},\n
{<<\"source\">>,<<\"http://127.0.0.1:5984/couchrest-test\";>>}]},\n
{user_ctx,null,\n [<<\"_admin\">>],\n
<<\"{couch_httpd_auth, default_authentication_handler}\">>}],\n
[]]},\n temporary,1,worker,\n [couch_rep]}}}"}
The couchdb log file reports:
[Fri, 12 Aug 2011 23:30:24 GMT] [info] [<0.6901.0>] 127.0.0.1 - - 'HEAD'
/couchrest-test/ 200
[Fri, 12 Aug 2011 23:30:24 GMT] [info] [<0.6902.0>] 127.0.0.1 - - 'GET'
/couchrest-test/ 200
[Fri, 12 Aug 2011 23:30:24 GMT] [info] [<0.6904.0>] 127.0.0.1 - - 'GET'
/couchrest-test/_local/f88508b53ee0a5ccd49aa64197f385ae 404
[Fri, 12 Aug 2011 23:30:24 GMT] [info] [<0.6905.0>] 127.0.0.1 - - 'GET'
/couchrest-test/_local/95173aa20da0c34f68b0ae173cf37d1e 404
[Fri, 12 Aug 2011 23:30:24 GMT] [error] [<0.6928.0>] {error_report,<0.328.0>,
{<0.6928.0>,crash_report,
[[{initial_call,
{couch_rep_changes_feed,init,['Argument__1']}},
{pid,<0.6928.0>},
{registered_name,[]},
{error_info,
{exit,
{{case_clause,null},
[{couch_rep_changes_feed,init,1},
{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]},
[{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]}},
{ancestors,
[<0.6919.0>,couch_rep_sup,
couch_primary_services,couch_server_sup,
<0.329.0>]},
{messages,[]},
{links,[<0.6919.0>]},
{dictionary,[]},
{trap_exit,true},
{status,running},
{heap_size,610},
{stack_size,24},
{reductions,134}],
[]]}}
[Fri, 12 Aug 2011 23:30:24 GMT] [error] [<0.6919.0>] {error_report,<0.328.0>,
{<0.6919.0>,crash_report,
[[{initial_call,{couch_rep,init,['Argument__1']}},
{pid,<0.6919.0>},
{registered_name,[]},
{error_info,
{exit,
{{badmatch,
{error,
{{case_clause,null},
[{couch_rep_changes_feed,init,1},
{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]}}},
[{couch_rep,do_init,1},
{couch_rep,init,1},
{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]},
[{gen_server,init_it,6},
[jira] [Resolved] (COUCHDB-1241) function_clause error when making HTTP request to external process
[
https://issues.apache.org/jira/browse/COUCHDB-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana resolved COUCHDB-1241.
Resolution: Fixed
Fix applied to trunk
> function_clause error when making HTTP request to external process
> --
>
> Key: COUCHDB-1241
> URL: https://issues.apache.org/jira/browse/COUCHDB-1241
> Project: CouchDB
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: Couchbase Single Server 2.0.0-dev4 on OS X 10.7
>Reporter: Nathan Vander Wilt
>Assignee: Filipe Manana
>
> A Python external helper based on the old/original protocol
> (http://wiki.apache.org/couchdb/ExternalProcesses) that worked fine under
> earlier versions of CouchDB but is exploding on Couchbase Server v2.0.0-dev4
> (1.2.0a-b11df55-git):
> [error] [<0.16764.1>] function_clause error in HTTP request
> [info] [<0.16764.1>] Stacktrace: [{couch_httpd_external,
>parse_external_response,
>[{json,
> <<"{\"json\": {\"allows_originals\":
> false, \"ok\": true}}">>}]},
> {couch_httpd_external,
>send_external_response,2},
> {couch_db_frontend,do_db_req,2},
> {couch_httpd,handle_request_int,6},
> {mochiweb_http,headers,5},
> {proc_lib,init_p_do_apply,3}]
> [info] [<0.16764.1>] 127.0.0.1 - - POST
> /photos/_local_shutterstem/folder/imgsrc-abc123/update?utility=%2FVolumes%2FEOS_DIGITAL%2FDCIM%2FShutterStem%20-%20Import%20EOS%20350D.html&token=ABC123
> 500
> My external process seems to be getting called successfully but CouchDB gets
> unhappy when trying to forward the result to the client.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Trouble replicating
On Fri, Aug 12, 2011 at 1:52 PM, Zachary Zolton wrote: > So, my replication task has again stalled, with my logs filling up > with thousands of that aforementioned error message, again today at > around 1:25 CDT. I'll also note that this error state seems to > adversely affect couch's responsiveness... > > I'm still unsure how to troubleshoot this. Is there any more > information about my setup that would help? I never experienced that SSL issue with R14B03 yet. Maybe you can try with R14B01 for example? > > FYI, I deleted the _replicator doc and have gone back to maintaining > this continuous replication with a cron script. You shouldn't need that anymore in the next minor release (1.1.1). With 1.1.0, if it ends in the "error" state you have to manually start it again (delete the doc and add it again or just remove its _replication_state field) > > On Thu, Aug 11, 2011 at 11:40 PM, Dustin Sallings wrote: >> >> On Aug 11, 2011, at 11:59 AM, Zachary Zolton wrote: >> >>> By the way, after the _replicator doc went into the error state, I >>> removed all the _replication* fields and save it. The replication task >>> resumed and it seems to be keeping up-to-date for the past few hours. >>> >>> Guess I'll keep my fingers crossed for now... (^_^ >> >> >> You only need to remove the _replicator_state. >> >> There are a few bugs that prevent it from automatically restarting as >> you might expect. I'm sure I've hit all of them. :) >> >> -- >> dustin sallings >> >> >> >> > -- Filipe David Manana, fdman...@gmail.com, fdman...@apache.org "Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men."
Re: Trouble replicating
So, my replication task has again stalled, with my logs filling up with thousands of that aforementioned error message, again today at around 1:25 CDT. I'll also note that this error state seems to adversely affect couch's responsiveness... I'm still unsure how to troubleshoot this. Is there any more information about my setup that would help? FYI, I deleted the _replicator doc and have gone back to maintaining this continuous replication with a cron script. On Thu, Aug 11, 2011 at 11:40 PM, Dustin Sallings wrote: > > On Aug 11, 2011, at 11:59 AM, Zachary Zolton wrote: > >> By the way, after the _replicator doc went into the error state, I >> removed all the _replication* fields and save it. The replication task >> resumed and it seems to be keeping up-to-date for the past few hours. >> >> Guess I'll keep my fingers crossed for now... (^_^ > > > You only need to remove the _replicator_state. > > There are a few bugs that prevent it from automatically restarting as > you might expect. I'm sure I've hit all of them. :) > > -- > dustin sallings > > > >
[jira] [Created] (COUCHDB-1247) _replicate throws 500 when POSTing {} or an undefined source/target
_replicate throws 500 when POSTing {} or an undefined source/target
---
Key: COUCHDB-1247
URL: https://issues.apache.org/jira/browse/COUCHDB-1247
Project: CouchDB
Issue Type: Bug
Components: Replication
Affects Versions: 1.1, 1.0.2
Reporter: Derek Perez
Priority: Minor
rnewson and I discussed this, steps to reproduce:
1. POST /_replicate -d "{}"
this emits a 500, when it likely should emit a 400.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Futon Test Suite
Here's a bit of a brain dump on the sort of environment I'd like to see our CLI JS tests have. If anyone has any thoughts I'd like to hear them. Otherwise I'll start hacking on this at some point over the weekend. https://gist.github.com/1142306
