Re: API Docs (finally)
[New subthread] Jan, I see the Creative Commons license, but which one is it? Usually it is "-Attribution" plus zero or more of: * -NonCommercial * -ShareAlike I am guessing -Atribution only. Correct? Thanks. On Tue, Feb 21, 2012 at 8:36 PM, Jan Lehnardt wrote: > Hi all, > > I finally got my act together and prepared the CouchDB API docs that MC Brown > made for Couchbase for your consideration to be added to the project. > > I put it up on GitHub so you can check it out. > > The repo is: > > https://github.com/janl/couchdb-docs > > To build all docs, you run `make everything`. I put the results on GitHub > Pages. > > It includes multiple HTML builds with different granularities (single page, > break by section, break by chapter) as well as PDF and ePub versions: > > Single Page: > http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.html > By Chapter: > http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.html-dir/index.html > By Section: > http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.html-section/index.html > PDF: > http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.pdf > ePub > http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.epub > > There's also a CouchDB 1.1. release guide that explains all the new features > in depth: > > Single Page: > http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.html > By Chapter: > http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.html-dir/index.html > By Section: > http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.html-section/index.html > PDF: > http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.pdf > ePub > http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.epub > > The README.md files outlines the build dependencies. > > The license is CC 3.0 but we can adapt that to whatever is required. > > There's a few rough edges, no styling should be obvious and the few > screenshots are using our old Single Server branded Futon, but I don't > consider these things to block adoption. > > Let me know what you think. I hope you like it! :) > > (w finally!) > > Cheers > Jan > -- > -- Iris Couch
Re: API Docs (finally)
I think it works out fine so long as git commits don't hit upstream until after someone has 'git svn rebase'd them locally and then 'svn dcommit'd them. Otherwise you need to force push the git copy. In other words git commits that have not been pushed to svn are provisional and will have their hashed changed after they hit svn. Nothing prevents us from collaborating in git as long as we push first to svn before using the git-svn copy to push to the canonical git repo. On Feb 21, 2012 9:28 PM, "Paul Davis" wrote: > On Tue, Feb 21, 2012 at 7:07 PM, Jason Smith wrote: > > Jan, easy question: > > > > CouchDB is now in Git, and now there are two additional projects > > people are talking about: the web site and now the documentation. > > > > I wonder if the same repo could host all three projects, with > > dissimilar, independent history trees. (I know the web site has svn > > requirements but most would agree that git-svn is quite excellent > > dealing with this.) > > > > Someone feel free to correct me if I'm wrong, but I think this would > require that our Git repo mirror some form of an SVN url. Plus our > history has been disconnected so we'd have to do some fancy dancing to > get things back in sync. > > So basically, no. But I can't think of a reason that we can't host > both in the Git repo and then write a script that forcibly updates > some random SVN url. Me and Benoit have a very similar setup for > handling all the documentation for Gunicorn (though its based on > GitHub's Pages thing in a branch (but the basic idea is the same). > > > On Wed, Feb 22, 2012 at 3:36 AM, Jan Lehnardt wrote: > >> Hi all, > >> > >> I finally got my act together and prepared the CouchDB API docs that MC > Brown made for Couchbase for your consideration to be added to the project. > >> > >> I put it up on GitHub so you can check it out. > >> > >> The repo is: > >> > >> https://github.com/janl/couchdb-docs > >> > >> To build all docs, you run `make everything`. I put the results on > GitHub Pages. > >> > >> It includes multiple HTML builds with different granularities (single > page, break by section, break by chapter) as well as PDF and ePub versions: > >> > >> Single Page: > http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.html > >> By Chapter: > http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.html-dir/index.html > >> By Section: > http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.html-section/index.html > >> PDF: > http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.pdf > >> ePub > http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.epub > >> > >> There's also a CouchDB 1.1. release guide that explains all the new > features in depth: > >> > >> Single Page: > http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.html > >> By Chapter: > http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.html-dir/index.html > >> By Section: > http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.html-section/index.html > >> PDF: > http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.pdf > >> ePub > http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.epub > >> > >> The README.md files outlines the build dependencies. > >> > >> The license is CC 3.0 but we can adapt that to whatever is required. > >> > >> There's a few rough edges, no styling should be obvious and the few > screenshots are using our old Single Server branded Futon, but I don't > consider these things to block adoption. > >> > >> Let me know what you think. I hope you like it! :) > >> > >> (w finally!) > >> > >> Cheers > >> Jan > >> -- > >> > > > > > > > > -- > > Iris Couch >
Re: Issues blocking the 1.2.0 release
I think COUCHDB-1413 wouldn't hurt to have for 1.2.0, after all it's about correct query results. 1.2.1 is also aceptable. If no objections, I'll push the fix to 1.2.x as well. On Tue, Feb 21, 2012 at 6:32 PM, Jason Smith wrote: > My reading of the JIRA ticket (FWIW) is that Paul explained pretty > convincingly why this is only a minor bug if at all. For this release, > Paul had a simple fix; although I do not see it in 1.2.x nor JIRA and > don't recall offhand what it was exactly. > > On Tue, Feb 21, 2012 at 10:50 PM, Robert Newson wrote: >> heh, actually I don't think we did. >> >> On 21 February 2012 22:41, Paul Davis wrote: >>> Did we fix the original JSON thing that started this whole broughaha? >>> >>> On Tue, Feb 21, 2012 at 3:57 PM, Noah Slater wrote: Thanks. On Tue, Feb 21, 2012 at 9:46 PM, Jan Lehnardt wrote: > On 21.02.2012, at 22:38, Robert Newson wrote: > > > I resolved the ipv6 ticket as 'cannot reproduce' given that two > > committers have verified ipv6 replication with 1.2.x. Time for round > > 2? > > +1 > > > > > > On 21 February 2012 21:11, Noah Slater wrote: > >> Are we blocked on anything else? Are we good to go? > >> > >> On Tue, Feb 21, 2012 at 7:21 PM, Jan Lehnardt wrote: > >> > >>> Thanks guys, committed. > >>> > >>> Noah, 1.2.0 is unblocked on this one. > >>> > >>> On Feb 21, 2012, at 20:13 , Paul Davis wrote: > >>> > +1 on the patch to require admin for _changes. > > On Tue, Feb 21, 2012 at 3:36 AM, Jan Lehnardt > wrote: > > *nudge* > > > > I don't feel very confident with a single opinion (thanks Robert), > and > >>> would love your input on this one. > > > > Cheers > > Jan > > -- > > > > > > On Feb 16, 2012, at 16:12 , Jan Lehnardt wrote: > > > >> > >> On Feb 14, 2012, at 13:14 , Noah Slater wrote: > >> > >>> Devs, > >>> > >>> Please outline: > >>> > >>> - What remains to be fixed for regression purposes > >> > >> I want to bring up one more thing (sorry :). > >> > >> /_users/_changes is currently end-user readable. While > >>> /_users/_changes?include_docs=true will not fetch docs the requesting > user > >>> doesn't have access to, it still gets all doc ids in the /_users db > >>> and > >>> thus easily can generate a list of all users. > >> > >> I'd like to propose to make /_user/_changes also admin-only before > we > >>> ship 1.2.0. Again, I'm happy to revisit and make things configurable > down > >>> the road. > >> > >> Note that the information that a particular user is registered is > >>> leaked (a user can't sign up with a username that is already taken, > from > >>> that it can be deduced that that particular username is already > >>> registered). This is in line with most signup systems. Making > >>> /_users/_changes admin-only doesn't prevent all leakage of what users > have > >>> signed up, but it stops bulk-leakage of *all* users in one swoop. > >> > >> What do you think? > >> > >> Cheers > >> Jan > >> -- > >> > >> > > > >>> > >>> > > > > > -- > Iris Couch -- 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: JIRA Bots
On Wed, Feb 22, 2012 at 12:54 AM, Paul Davis wrote: > Can whoever designed the "Sam Bisbee" JIRA bot (what an odd name > choice) figure out if its possible to tag emails somehow to give me a > filter criteria to add a label for "closing old ass bugs" or > something? Resolved for a while. Closing. > (Awesome work on JIRA processing Sam!) For your kind words you now have the night to figure out gmail filters. Assuming apache/jira's mail servers are all caught up. :) Cheers, -- Sam Bisbee
[jira] [Closed] (COUCHDB-413) src/couchdb/priv/couchspawnkillable not included by "make dist"
[ https://issues.apache.org/jira/browse/COUCHDB-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-413. -- Resolved for a while. Closing. > src/couchdb/priv/couchspawnkillable not included by "make dist" > --- > > Key: COUCHDB-413 > URL: https://issues.apache.org/jira/browse/COUCHDB-413 > Project: CouchDB > Issue Type: Bug > Components: Build System >Affects Versions: 0.10 > Environment: Ubuntu 9.04 >Reporter: James Henstridge >Assignee: Noah Slater > Fix For: 0.10 > > > I was building a tarball from Subversion r793829, and ended up with the > following error: > ... > make[3]: *** No rule to make target `priv/couchspawnkillable', needed by > `all-am'. Stop. > make[3]: Leaving directory > `/build/buildd/couchdb-0.10.0~svn793829/src/couchdb' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/build/buildd/couchdb-0.10.0~svn793829' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/build/buildd/couchdb-0.10.0~svn793829' > It seems that the script is not included in the distribution tarball. This > could be fixed by adding $(couchpriv_SCRIPTS) to EXTRA_DIST in > src/couchdb/Makefile.am. -- 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-406) build on windows
[ https://issues.apache.org/jira/browse/COUCHDB-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-406. -- Resolved for a while. Closing. > build on windows > > > Key: COUCHDB-406 > URL: https://issues.apache.org/jira/browse/COUCHDB-406 > Project: CouchDB > Issue Type: Improvement > Components: Build System > Environment: windows, trunk >Reporter: Mark Hammond >Assignee: Paul Joseph Davis > Fix For: 0.10 > > Attachments: windows_build.patch, windows_build_2.patch, > windows_build_3.patch, windows_build_4.patch > > > Attaching a patch to get things building on Windows, including docs. As > noted in the docs, we reuse as much of the couch and erlang build processes > as possible. This patch leaves a functioning couch on Windows - with some > polish left to be done, but working and tests passing as well as expected - > and still works on linux. > Includes a couple of new files - couchspawnkillable_win.c from COUCHDB-374 > (while I will close), and a couchdb.bat.tpl file which generates a suitable > .bat file at 'make install' time. > Note this patch makes no attempt to create an installer - it just creates a > functioning tree suitable for zipping up, or for future consumption by an > installer. -- 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-69) Allow selective retaining of older revisions to a document
[ https://issues.apache.org/jira/browse/COUCHDB-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-69. - Resolved for a while. Closing. > Allow selective retaining of older revisions to a document > -- > > Key: COUCHDB-69 > URL: https://issues.apache.org/jira/browse/COUCHDB-69 > Project: CouchDB > Issue Type: Improvement > Components: Database Core > Environment: All >Reporter: Jan Lehnardt >Assignee: Paul Joseph Davis >Priority: Minor > Fix For: 0.10 > > Attachments: history_revs.2.patch, history_revs.3.patch, > history_revs.4.patch, history_revs.5.patch, history_revs.patch > > > At the moment, compaction gets rid of all old revisions of a document. Also, > replication also deals with the latest revision. It would be nice if it would > be possible to specify a list of revisions to keep around that do not get > compacted away and replicated. -- 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-471) make distcheck fails
[ https://issues.apache.org/jira/browse/COUCHDB-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-471. -- Resolved for a while. Closing. > make distcheck fails > > > Key: COUCHDB-471 > URL: https://issues.apache.org/jira/browse/COUCHDB-471 > Project: CouchDB > Issue Type: Bug > Components: Build System >Affects Versions: 0.10 > Environment: Mac OS X >Reporter: Jan Lehnardt >Assignee: Paul Joseph Davis >Priority: Critical > Fix For: 0.10 > > Attachments: couchdb-licence_skip.patch > > > make[2]: *** No rule to make target `local.ini', needed by `distdir'. Stop. > make[1]: *** [distdir] Error 1 > make: *** [distdir] Error 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] [Closed] (COUCHDB-468) POST with _id
[ https://issues.apache.org/jira/browse/COUCHDB-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-468. -- Resolved for a while. Closing. > POST with _id > - > > Key: COUCHDB-468 > URL: https://issues.apache.org/jira/browse/COUCHDB-468 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Reporter: Mark Hammond >Assignee: Paul Joseph Davis > Fix For: 0.10 > > > From -dev: > "Is there any reason why, if you POST a document to a database and that > document has an "_id" member, why this is ignored and a server-generated _id > is used instead?" > To which the general consensus was "no". Issue opened so jchris need not > worry about "this thread being lost to the sands of time." -- 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-237) Futon page for creating test cases.
[ https://issues.apache.org/jira/browse/COUCHDB-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-237. -- Resolved for a while. Closing. > Futon page for creating test cases. > --- > > Key: COUCHDB-237 > URL: https://issues.apache.org/jira/browse/COUCHDB-237 > Project: CouchDB > Issue Type: New Feature > Components: Futon, Test Suite >Reporter: Paul Joseph Davis >Assignee: Paul Joseph Davis > Fix For: 0.10 > > > It'd help to have a Futon page that allowed us to write test cases directly > in JavaScript. I'm not thinking of anything really fancy beyond a text box on > a page that has couch.js and couch_test_runner.js loaded. > Integration with a paste service for pasting links into IRC or email would > also be awesome. -- 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-416) Replicating shards into a single aggregation node may cause endless respawning
[
https://issues.apache.org/jira/browse/COUCHDB-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-416.
--
Resolved for a while. Closing.
> Replicating shards into a single aggregation node may cause endless respawning
> --
>
> Key: COUCHDB-416
> URL: https://issues.apache.org/jira/browse/COUCHDB-416
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
>Affects Versions: 0.9
> Environment: couchdb 0.9.0.r766883 CentOS x86_64
>Reporter: Enda Farrell
>Assignee: Adam Kocoloski
>Priority: Critical
> Fix For: 0.10
>
> Attachments: Picture 2.png
>
>
> I have a set of CouchDB instances, each one acting as a shard for a large set
> of data.
> Ocassionally, we replicate each instances' database into a different CouchDB
> instance. We always "pull" replicate (see image attached)
> When we do this, we often see errors like this on the target instance:
> * [Thu, 16 Jul 2009 13:52:32 GMT] [error] [emulator] Error in process
> <0.29787.102> with exit value:
> {function_clause,[{lists,map,[#Fun,undefined]},{couch_rep,enum_docs_since,4}]}
> *
> *
> *
> * [Thu, 16 Jul 2009 13:52:32 GMT] [error] [<0.7456.6>] replication enumerator
> exited with {function_clause,
> * [{lists,map,
> *
> [#Fun,undefined]},
> * {couch_rep,enum_docs_since,4}]} ..
> respawning
> Once this starts, it is fatal to the CouchDB instance. It logs these messages
> at over 1000 per second (log level = severe) and chews up HDD.
> No errors (other than a HTTP timeout) are seen.
> After a database had gone "respawning", the target node was shutdown, logs
> cleared, target node restarted. Log was tailed - all was quiet. Once a single
> replication was called again against this database it again immediatly went
> into respawning hell. There were no stacked replications in this case.
> From this it seems that - if a database ever goes into "respawning" it cannot
> recover (when your enviroment/setup requires replication to occur always).
--
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-422) PUT to _local/doc_id creates document '_local'
[
https://issues.apache.org/jira/browse/COUCHDB-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-422.
--
Resolved for a while. Closing.
> PUT to _local/doc_id creates document '_local'
> --
>
> Key: COUCHDB-422
> URL: https://issues.apache.org/jira/browse/COUCHDB-422
> Project: CouchDB
> Issue Type: Bug
>Affects Versions: 0.10
> Environment: Ubuntu 9.04
>Reporter: eric casteleijn
>Assignee: Paul Joseph Davis
>Priority: Minor
> Fix For: 0.10
>
>
> After davisp's revision r796246 doing a put to a document id like
> '_local/doc_id' results in a visible, and apparently non-local document with
> id '_local'. When escaping the slash as '%2F' everything works as before, and
> expected, i.e. a local document with the above id is created.
> To test:
> curl -X PUT -d '{"foo": "bar"}' http://127.0.0.1:5987/db1/_local/yokal
> result:
> {"ok":true,"id":"_local","rev":"1-770307fe8d4210bab8ec65c59983e03c"}
--
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-377) allow native view servers
[
https://issues.apache.org/jira/browse/COUCHDB-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-377.
--
Resolved for a while. Closing.
> allow native view servers
> -
>
> Key: COUCHDB-377
> URL: https://issues.apache.org/jira/browse/COUCHDB-377
> Project: CouchDB
> Issue Type: Improvement
>Reporter: Mark Hammond
> Attachments: couch_native_process.erl,
> erlang_test_include_docs.patch, native_query_servers.patch,
> native_query_servers.patch, native_query_servers2.patch,
> native_view_js_tests.patch, query_proc.patch
>
>
> There has been some discussion on IRC etc about how to support 'native' view
> servers, such as 'erlview' in a generic way. Currently using erlview
> requires you to modify couch.
> I'm attaching a patch as a first attempt at supporting this. In summary, the
> patch now looks up a new 'native_query_servers' config file section for a
> list of view_server names with a {Module, Func, Args} style string specifying
> the entry-point of the view server. The code now passes an additional atom
> around indicating if the PID is 'native' or 'external', and map_docs takes
> advantage of this to avoid the json step. This patch allows erlview to work
> for me, but in theory any erlang code could be used here.
> I'm very new at erlang - please let me know if I should make stylistic or
> other changes, or indeed if I should take a different approach completely.
--
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-429) Wrong rows shown when clicking "previous" in Futon for reduce views
[ https://issues.apache.org/jira/browse/COUCHDB-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-429. -- Resolved for a while. Closing. > Wrong rows shown when clicking "previous" in Futon for reduce views > --- > > Key: COUCHDB-429 > URL: https://issues.apache.org/jira/browse/COUCHDB-429 > Project: CouchDB > Issue Type: Bug > Components: Futon >Reporter: Jason Davies >Assignee: Paul Joseph Davis >Priority: Blocker > Fix For: 0.10 > > Attachments: futon.browse.js.2.patch, futon.browse.js.patch > > > Click "next" twice, and then click "previous" twice, and it only shows 9 rows > on the first page (less if you click "next" more times). This is due to the > "extra" row being put in the wrong place when clicking "previous". Patch to > follow. -- 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-461) attachments - handle correctly chunked encoding and Content-Length, send attachments unchunked
[ https://issues.apache.org/jira/browse/COUCHDB-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-461. -- Resolved for a while. Closing. > attachments - handle correctly chunked encoding and Content-Length, send > attachments unchunked > -- > > Key: COUCHDB-461 > URL: https://issues.apache.org/jira/browse/COUCHDB-461 > Project: CouchDB > Issue Type: Bug >Reporter: Benoit Chesneau > Fix For: 0.10 > > Attachments: attachments_get_length.diff, > attachments_put_length.diff, chunked.diff, chunked2.diff > > > This patch allow couchdb to send attachments unchunked, instead, > Content-Length is fixed and content is streamed. It also fix attachments PUT > by detecting first if encoding is chunked then test the length witch is the > standard way to do it. -- 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: JIRA Bots
+1 Jonathan Porta On Tue, Feb 21, 2012 at 10:54 PM, Paul Davis wrote: > Can whoever designed the "Sam Bisbee" JIRA bot (what an odd name > choice) figure out if its possible to tag emails somehow to give me a > filter criteria to add a label for "closing old ass bugs" or > something? > > (Awesome work on JIRA processing Sam!)
[jira] [Closed] (COUCHDB-4) Use HTTP Etags for cache support
[
https://issues.apache.org/jira/browse/COUCHDB-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-4.
Resolved for a while. Closing.
> Use HTTP Etags for cache support
>
>
> Key: COUCHDB-4
> URL: https://issues.apache.org/jira/browse/COUCHDB-4
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
>Reporter: Noah Slater
>Assignee: Chris Anderson
>Priority: Blocker
> Fix For: 0.11
>
>
> CouchDb currently puts a number of headers in HTTP responses that disable
> any caching. However, the docid and rev that are part of every document
> would make it extremely easy to instead generate solid Etag headers, and
> then return 204 Not Modified responses for GET and HEAD requests if the
> client sends along the most current Etag value.
> For example, instead of:
> HTTP/1.1 200 OK
> Server: inets/develop
> Date: Sat, 15 Sep 2007 11:21:41 GMT
> Cache-Control: no-cache
> Pragma: no-cache
> Expires: Sat, 15 Sep 2007 11:21:41 GMT
> CouchDB should return something like:
> HTTP/1.1 200 OK
> Server: inets/develop
> Date: Sat, 15 Sep 2007 11:21:41 GMT
> Cache-Control: must-revalidate
> Etag: ${docid}@${rev}
> Sufficiently sophisticated clients (such as Python httplib2) could then use
> If-None-Match to perform conditional GET requests.
> Thinking about it again, as the docid is already in the URL, only the rev
> is needed in the Etag headers.
> --
> Comment 1 by cml...@gmx.de, Oct 01, 2007
> See also
> http://intertwingly.net/blog/2007/09/24/Tests-Id-Like-CouchDB-to-Pass#etag
--
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-453) If "Accept: foo" header is sent, server returns a render_error
[
https://issues.apache.org/jira/browse/COUCHDB-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-453.
--
Resolved for a while. Closing.
> If "Accept: foo" header is sent, server returns a render_error
> --
>
> Key: COUCHDB-453
> URL: https://issues.apache.org/jira/browse/COUCHDB-453
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
>Reporter: Jason Davies
> Attachments: render.js.patch
>
>
> The full error is: {"error":"render_error","reason":"function raised error:
> [object Object]"}
> This occurs because there is no match for the "foo" mime type. Simple patch
> to follow that makes us fall back to sending the first mime type provided.
> "Be conservative in what you send, liberal in what you accept".
--
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-20) Output from update listener causes error messages/db server crash
[ https://issues.apache.org/jira/browse/COUCHDB-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-20. - Resolved for a while. Closing. > Output from update listener causes error messages/db server crash > - > > Key: COUCHDB-20 > URL: https://issues.apache.org/jira/browse/COUCHDB-20 > Project: CouchDB > Issue Type: Bug >Reporter: Noah Slater >Assignee: Paul Joseph Davis >Priority: Minor > Fix For: 0.10 > > > What steps will reproduce the problem? > 1. Write a program/script that continuously reads its stdin and writes > something to stdout as stdin line has arrived > 2. Register it as a db update listener in couch.ini > [Couch] > ... > DbUpdateNotificationProcess=/path/to/daemon > 3. Start couchdb. Each time db is updated, the listener program receives > input and writes back to stdout. > This causes long and obscure error messages in couchdb server concole > output (not showed here). According to [1], listener is not supposed to > send anything back. > It is therefore proposed that whatever is received from the listener is > merely logged in special log file e. g. notifier_log (which may be > redirected to /dev/null in couch.ini if not needed). > [1] > http://groups.google.com/group/couchdb/browse_thread/thread/a81fb0058ae2430 > b/7285fb233fa10368#7285fb233fa10368 -- 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-420) OAuth authentication support (2-legged initially) and cookie-based authentication
[
https://issues.apache.org/jira/browse/COUCHDB-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-420.
--
Resolved for a while. Closing.
> OAuth authentication support (2-legged initially) and cookie-based
> authentication
> -
>
> Key: COUCHDB-420
> URL: https://issues.apache.org/jira/browse/COUCHDB-420
> Project: CouchDB
> Issue Type: New Feature
> Components: HTTP Interface
>Reporter: Jason Davies
>Priority: Blocker
> Fix For: 0.10
>
> Attachments: oauth.1.diff, oauth.2.patch, oauth.3.patch
>
>
> This patch adds two-legged OAuth support to CouchDB.
> 1. In order to do this, a couple of changes have been made to the way auth
> handlers are used. Essentially, the patch allows multiple handlers to be
> specified in a comma-separated list in the following in the [httpd] section
> of your .ini config e.g.
> authentication_handlers = {couch_httpd_oauth,
> oauth_authentication_handler}, {couch_httpd_auth,
> default_authentication_handler}
> The handlers are tried in order until one of them successfully authenticates
> and sets user_ctx on the request. Then the request is passed to the main
> handler.
> 2. Now for the OAuth consumer keys and secrets: as Ubuntu need to be able to
> bootstrap this i.e. add tokens without a running CouchDB, I have advised
> creating a new config file in $PREFIX/etc/couchdb/default.d/ called oauth.ini
> or similar. This should get read by CouchDB's startup script when it loads
> its config files (e.g. default.ini and local.ini as well). There are three
> sections available:
> i. [oauth_consumer_secrets] =
> ii. [oauth_token_secrets] =
> iii. [oauth_token_users] =
> The format I've used above is [section name] followed by how the keys and
> values for that section will look on subsequent lines. The secrets are a way
> for the consumer to prove that it owns the corresponding consumer key or
> access token. The mapping of auth tokens to usernames is a way to specify
> which user/roles to give to a consumer with a given access token.
> In the future we will also store tokens in the user database (see below).
> 3. OAuth replication. I've extended the JSON sent via POST when initiating a
> replication as follows:
> {
> source: {
>url: ,
>auth: {
> oauth: {
>consumer_key: ,
>consumer_secret: ,
>token_secret: ,
>token:
> }
>}
> },
> target: /* same syntax as source, or string for a URL with no auth info, or
> string for local database name */
> }
> 4. This patch also includes cookie-authentication support to CouchDB. I've
> covered this here:
> http://www.jasondavies.com/blog/2009/05/27/secure-cookie-authentication-couchdb/
> The cookie-authentication branch is being used on a couple of live sites and
> the branch has also been worked on by jchris and benoitc. As well as cookie
> auth it includes the beginnings of support for a per-node user database, with
> APIs for creating/deleting users etc.
--
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-236) Test for a regression reported by jrutherford on IRC
[ https://issues.apache.org/jira/browse/COUCHDB-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-236. -- Resolved for a while. Closing. > Test for a regression reported by jrutherford on IRC > > > Key: COUCHDB-236 > URL: https://issues.apache.org/jira/browse/COUCHDB-236 > Project: CouchDB > Issue Type: Test > Components: Test Suite >Reporter: Paul Joseph Davis >Assignee: Paul Joseph Davis > Attachments: COUCHDB-236.patch > > > Jrutherford experienced a temporary regression in SVN revision 738148. The > error was related to _all_docs behaving oddly when using descending=true. > Upgrading to trunk fixed the issue. This is just a test for the specific > regression so we know about it in the future. -- 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-231) Make local_dev.ini generate from `make dev` and svn:ignore it
[ https://issues.apache.org/jira/browse/COUCHDB-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-231. -- Resolved for a while. Closing. > Make local_dev.ini generate from `make dev` and svn:ignore it > - > > Key: COUCHDB-231 > URL: https://issues.apache.org/jira/browse/COUCHDB-231 > Project: CouchDB > Issue Type: Improvement > Components: Build System >Reporter: Chris Anderson >Assignee: Paul Joseph Davis >Priority: Minor > Fix For: 0.10 > > > Make local_dev.ini generate from `make dev` and svn:ignore it. > This way I'll stop losing my admin passwords when I revert to apply patches. -- 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-442) Add a "view" or "format" function to process source doc on query
[ https://issues.apache.org/jira/browse/COUCHDB-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-442. -- Resolved for a while. Closing. > Add a "view" or "format" function to process source doc on query > > > Key: COUCHDB-442 > URL: https://issues.apache.org/jira/browse/COUCHDB-442 > Project: CouchDB > Issue Type: Improvement > Components: JavaScript View Server >Reporter: Curt Arnold > > It is common practice to do emit(key, null) in a map function and then query > with ?include_docs=true to retrieve the documents that were responsible for > the entries. However, the full document may include information that is > privileged or the full document may be substantially larger than the > information needed to be transferred to the client. > The proposed enhancement is to allow defining a "view" function in addition > to the existing "map" and "reduce" on a view. If specified, the view > function would take the id, key, value and doc and return a JSON value that > would be added as the "view" member to the row in the result set. > One of the use cases on > http://wiki.apache.org/couchdb/Authentication_and_Authorization is to be able > to specify that a user can retrieve the values from a view, but not add > include_docs since that may expose information that they are not authorized > to view. Without the "view" function, there would be pressure to start > pushing things into the emitted value. > Production of views would be likely controlled using a include_views=true in > the query string. -- 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-425) Hiding sidebar in Futon
[ https://issues.apache.org/jira/browse/COUCHDB-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-425. -- Resolved for a while. Closing. > Hiding sidebar in Futon > --- > > Key: COUCHDB-425 > URL: https://issues.apache.org/jira/browse/COUCHDB-425 > Project: CouchDB > Issue Type: Improvement > Components: Futon >Affects Versions: 0.10 >Reporter: Volker Mische >Assignee: Christopher Lenz >Priority: Minor > Fix For: 0.10 > > Attachments: bg.png, futon-hide-sidebar-2.patch, > futon-hide-sidebar-cmlenz1.patch, futon-hide-sidebar-cmlenz2.patch, > futon-hide-sidebar-vmx.patch, futon-hide-sidebar.patch, sidebar-toggle.png, > sidebar-toggle.png > > > Sometimes you'd like to have maximum space for browsing your views. Therefore > I'd like to see a way to hide the sidebar. -- 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-428) Extra row shown per page for pages greater than 1 in Futon
[ https://issues.apache.org/jira/browse/COUCHDB-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-428. -- Resolved for a while. Closing. > Extra row shown per page for pages greater than 1 in Futon > -- > > Key: COUCHDB-428 > URL: https://issues.apache.org/jira/browse/COUCHDB-428 > Project: CouchDB > Issue Type: Bug > Components: Futon >Reporter: Jason Davies >Assignee: Christopher Lenz >Priority: Minor > Fix For: 0.10 > > Attachments: futon.browse.js.patch > > > See patch for one-line fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-423) couch_file misses an edge case
[ https://issues.apache.org/jira/browse/COUCHDB-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-423. -- Resolved for a while. Closing. > couch_file misses an edge case > -- > > Key: COUCHDB-423 > URL: https://issues.apache.org/jira/browse/COUCHDB-423 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Reporter: Bob Dionne >Assignee: Paul Joseph Davis >Priority: Minor > Fix For: 0.10 > > Attachments: couch_file.diff > > > pread_binary reads the first 20 bytes. This causes a simple append_binary > followed by pread_binary to fail, as in 010-file-basics.t test case. This > case may never occur because of couchdb's file format -- 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-227) Large Number Support Bug
[ https://issues.apache.org/jira/browse/COUCHDB-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-227. -- Resolved for a while. Closing. > Large Number Support Bug > > > Key: COUCHDB-227 > URL: https://issues.apache.org/jira/browse/COUCHDB-227 > Project: CouchDB > Issue Type: Bug > Components: Futon, JavaScript View Server >Reporter: Adam Kocoloski > > It looks like SpiderMonkey rounds large integers. To reproduce, create a > document in Futon with a field value > > Futon will round this to 1. Or, create a document with that > field value by some other means and then emit the field in a view. The > document will have the correct value for the field, but the value in the view > will be wrong. -- 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-424) fixed minor issues in etap tests dues to code evolution
[ https://issues.apache.org/jira/browse/COUCHDB-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-424. -- Resolved for a while. Closing. > fixed minor issues in etap tests dues to code evolution > --- > > Key: COUCHDB-424 > URL: https://issues.apache.org/jira/browse/COUCHDB-424 > Project: CouchDB > Issue Type: Improvement > Components: Test Suite >Reporter: Bob Dionne >Assignee: Paul Joseph Davis > Fix For: 0.10 > > Attachments: etaps.diff, etaps.diff > > > fixed etap tests to accomodate changes in couch_config, couch_stream, etc.. -- 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-426) Sort view names alphabetically in Futon
[ https://issues.apache.org/jira/browse/COUCHDB-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-426. -- Resolved for a while. Closing. > Sort view names alphabetically in Futon > --- > > Key: COUCHDB-426 > URL: https://issues.apache.org/jira/browse/COUCHDB-426 > Project: CouchDB > Issue Type: Improvement > Components: Futon >Reporter: Jason Davies > Fix For: 0.10 > > Attachments: futon.browse.js.2.diff, futon.browse.js.diff > > > Simple patch to follow... -- 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-328) [patch] allow futon reduce textareas to contain accidental white spaces.
[ https://issues.apache.org/jira/browse/COUCHDB-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-328. -- Resolved for a while. Closing. > [patch] allow futon reduce textareas to contain accidental white spaces. > -- > > Key: COUCHDB-328 > URL: https://issues.apache.org/jira/browse/COUCHDB-328 > Project: CouchDB > Issue Type: Improvement > Components: Futon >Affects Versions: 0.9 > Environment: ubuntu 8.10 >Reporter: Kevin Ilchmann Jørgensen >Assignee: Christopher Lenz >Priority: Trivial > Fix For: 0.10 > > Attachments: check_reduceVal.patch, check_reduceVal2.patch > > > simple patch, so that an accidental white space character dont return a > cryptic 'Badmatch: ..' javascript alert. -- 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-142) Test case submissions from Futon
[ https://issues.apache.org/jira/browse/COUCHDB-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-142. -- Resolved for a while. Closing. > Test case submissions from Futon > > > Key: COUCHDB-142 > URL: https://issues.apache.org/jira/browse/COUCHDB-142 > Project: CouchDB > Issue Type: New Feature > Components: Futon, Infrastructure, Test Suite > Environment: Futon Interface >Reporter: Paul Joseph Davis >Assignee: Paul Joseph Davis >Priority: Minor > Fix For: 0.10 > > > Bit of insight while helping trogdoro submit a failing test case for couch. > it'd be fairly awesome if we had an interface within futon for writing > failing cases. Major bonus points for making a "Submit to JIRA" button. Major > extra super x10 multiplier bonus points if there were a build bot style thing > that would actually confirm the failing case on either the latest SVN > version, last release, or both versions of couch. -- 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-318) if the _attachments key's value, generated by uploading a file is overwritten. The admin interface fails with a object is null error on jquery.js?1.3.1 (line 666).
[ https://issues.apache.org/jira/browse/COUCHDB-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-318. -- Resolved for a while. Closing. > if the _attachments key's value, generated by uploading a file is > overwritten. The admin interface fails with a object is null error on > jquery.js?1.3.1 (line 666). > --- > > Key: COUCHDB-318 > URL: https://issues.apache.org/jira/browse/COUCHDB-318 > Project: CouchDB > Issue Type: Bug > Components: Futon >Affects Versions: 0.9 > Environment: Ubuntu 8.10 - using apache-couchdb-0.9.0.tar.gz >Reporter: Kevin Ilchmann Jørgensen >Assignee: Christopher Lenz > Fix For: 0.10 > > > if the _attachments key's value, generated by uploading a file is > overwritten. The admin interface fails with a object is null error on > jquery.js?1.3.1 (line 666). > reproduce by: creating new document - attach file - add new field named > "_attachments" - save document - observe javascript error. -- 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-408) Futon _view URLs should be similar to the HTTP interface
[ https://issues.apache.org/jira/browse/COUCHDB-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-408. -- Resolved for a while. Closing. > Futon _view URLs should be similar to the HTTP interface > > > Key: COUCHDB-408 > URL: https://issues.apache.org/jira/browse/COUCHDB-408 > Project: CouchDB > Issue Type: Improvement > Components: Futon >Affects Versions: 0.9.1 >Reporter: Volker Mische >Assignee: Christopher Lenz > Fix For: 0.10 > > Attachments: futon-view-url-2.patch, futon_design_name_slashes.diff > > > URLs of view in Futon normally look like: > http://localhost:5984/_utils/database.html?db/_design/designdocname/viewname > The HTTP interface is: > http://localhost:5984/db/_design/desigdocname/_view/viewname > The patch changes the URLs to: > http://localhost:5984/_utils/database.html?db/_design/designdocname/_view/viewname > It changes the dropdown menu on the top right to use this new URL, are there > any other places where you can get to a view? -- 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-301) Jumping to documents in Futon
[ https://issues.apache.org/jira/browse/COUCHDB-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-301. -- Resolved for a while. Closing. > Jumping to documents in Futon > - > > Key: COUCHDB-301 > URL: https://issues.apache.org/jira/browse/COUCHDB-301 > Project: CouchDB > Issue Type: New Feature > Components: Futon >Affects Versions: 0.9 >Reporter: Dirkjan Ochtman >Priority: Minor > Fix For: 0.10 > > Attachments: futon-jump-to.diff > > > I'd love to be able to make a quick jump to a document for which I know the > ID, from the database page in Futon. > When doing admin tasks on a larger database, browsing documents to find a > needed document becomes tedious. We can provide a simple text box that allows > us to quickly jump to a document. It can use auto-suggest to make it even > easier. > It could be expanded even more to also do views, but just documents would be > a good start, IMO. -- 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-409) $.couch.saveDoc() in jquery.couch.js sets doc._id and doc._rev to undefined on error, causing a new doc to be created if the same doc is modified and saved again
[ https://issues.apache.org/jira/browse/COUCHDB-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-409. -- Resolved for a while. Closing. > $.couch.saveDoc() in jquery.couch.js sets doc._id and doc._rev to undefined > on error, causing a new doc to be created if the same doc is modified and > saved again > - > > Key: COUCHDB-409 > URL: https://issues.apache.org/jira/browse/COUCHDB-409 > Project: CouchDB > Issue Type: Bug > Components: Futon >Affects Versions: 0.9.1, 0.10 >Reporter: Jason Davies >Assignee: Paul Joseph Davis > Fix For: 0.9.1 > > Attachments: jquery.couch.saveDoc.diff > > > Simple fix attached. Recommend that we include this in 0.9.1 as it's a > non-obvious annoyance that occurs when saving docs in Futon. > For example, if I try and save a doc and validation fails, and I fix the doc > and save again, it will be saved with a NEW document id, since doc._id is set > to undefined. -- 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-381) it would be nice to have an option in bin/couchdb to pass "-sname node_name" to erlang at startup
[ https://issues.apache.org/jira/browse/COUCHDB-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-381. -- Resolved for a while. Closing. > it would be nice to have an option in bin/couchdb to pass "-sname node_name" > to erlang at startup > - > > Key: COUCHDB-381 > URL: https://issues.apache.org/jira/browse/COUCHDB-381 > Project: CouchDB > Issue Type: Improvement > Components: Build System >Affects Versions: 0.10 >Reporter: Bob Dionne >Priority: Minor > Attachments: couchdb.tpl.in.patch > > > attached is a patch to bin/couchdb.tpl.in that accomplishes this -- 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-402) C code fails to build on Windows
[ https://issues.apache.org/jira/browse/COUCHDB-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-402. -- Resolved for a while. Closing. > C code fails to build on Windows > > > Key: COUCHDB-402 > URL: https://issues.apache.org/jira/browse/COUCHDB-402 > Project: CouchDB > Issue Type: Bug >Reporter: Mark Hammond >Assignee: Paul Joseph Davis > Fix For: 0.10 > > Attachments: move_c_decls.patch > > > Much of the C code in couch currently fails to compile on Windows, due to the > MS compiler being very slow keeping up with the C standards. Specifically, > the MS c compiler still doesn't like 'inline' variable declarations - they > must all be declared at the top of a block. Submitting a patch which does > exactly this. -- 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-389) [PATCH] Make offset calculation more available during btree folding
[ https://issues.apache.org/jira/browse/COUCHDB-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-389. -- Resolved for a while. Closing. > [PATCH] Make offset calculation more available during btree folding > --- > > Key: COUCHDB-389 > URL: https://issues.apache.org/jira/browse/COUCHDB-389 > Project: CouchDB > Issue Type: Improvement > Components: Database Core >Affects Versions: 0.9 >Reporter: Brad Anderson >Assignee: Paul Joseph Davis >Priority: Minor > Fix For: 0.10 > > Attachments: clustered_offset.patch, couchdb-389-2.svn.patch, > couchdb-389-3.git.patch, couchdb-389.svn.patch > > > When CouchDB returns no values for _all_docs (or potentially any fold over > the btree), then no offset is calculated, either. This is not a problem in > non-clustered CouchDB. However, when you are in a clustered environment and > treat each shard as its own CouchDB, then not returning an offset when no > values are found on the shard can be problematic. The specific case is if > there is a startkey or skip specified, and there were values before (or after > with descending=true) the startkey or skip values, but there are no current > values. > Moving the Offset calculation to be available for all clauses in the return > fun of couch_httpd_view:make_view_fold_fun/6 allows the user to store Offsets > in the RowFunAcc and client code using this function will work as expected. -- 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-374) couchspawnkillable doesn't work on windows
[ https://issues.apache.org/jira/browse/COUCHDB-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-374. -- Resolved for a while. Closing. > couchspawnkillable doesn't work on windows > -- > > Key: COUCHDB-374 > URL: https://issues.apache.org/jira/browse/COUCHDB-374 > Project: CouchDB > Issue Type: Bug > Environment: windows >Reporter: Mark Hammond > Attachments: couchspawnkillable_win.c > > > The shell script 'couchspawnkillable' doesn't work on windows, meaning lots > of things are broken in the trunk. It might be possible to bash cygwin/msys > etc to work, but I think a better solution for windows is a custom little C > app which does the same basic thing. > I've attached the source for such an app and it works for me. It creates a > suspended child process with the same handles as us, then echos the 'kill' > command, then spawns the real app and terminates. The 'kill command' is a > reference to the same couchspawnkillable.exe but with a '--kill' > command-line. I've not tried to integrate with a build system, but simple > instructions are at the top of the file. > Attaching it here so it doesn't get lost... -- 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-401) Remove trailing whitespaces from JavaScript files
[
https://issues.apache.org/jira/browse/COUCHDB-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-401.
--
Resolved for a while. Closing.
> Remove trailing whitespaces from JavaScript files
> -
>
> Key: COUCHDB-401
> URL: https://issues.apache.org/jira/browse/COUCHDB-401
> Project: CouchDB
> Issue Type: Improvement
> Components: JavaScript View Server, Test Suite
>Affects Versions: 0.10
>Reporter: Volker Mische
>Priority: Minor
>
> The JavaScript failes contain many trailing whitespaces, please remove them.
> I could submit a patch, but I think it's way easier if one of the committers
> runs the one-liner locally and committs the changes.
> I've used
> find . -name '*.js' -exec sed -i {} -e 's/[ \t]*$//' ';'
> which I've found at
> http://zebert.blogspot.com/2009/06/clean-up-trailing-whitespaces-in.html
--
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-61) Separate storage of attachments from the main database file
[ https://issues.apache.org/jira/browse/COUCHDB-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-61. - Paul doesn't plan on looking at this later. Closing. > Separate storage of attachments from the main database file > --- > > Key: COUCHDB-61 > URL: https://issues.apache.org/jira/browse/COUCHDB-61 > Project: CouchDB > Issue Type: New Feature > Components: Database Core > Environment: All >Reporter: Jan Lehnardt >Assignee: Paul Joseph Davis >Priority: Minor > > At the moment all document- and attachment-data go into the same database > file. It would be nice if the attachments could be saved in a different file. > This would enable the use of slower and cheaper hardware for attachment > storage and faster hardware for the document and index data storage. -- 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-66) Add read-only mode
[ https://issues.apache.org/jira/browse/COUCHDB-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213330#comment-13213330 ] Sam Bisbee commented on COUCHDB-66: --- Sorry, please ignore misplaced comment. > Add read-only mode > -- > > Key: COUCHDB-66 > URL: https://issues.apache.org/jira/browse/COUCHDB-66 > Project: CouchDB > Issue Type: Improvement > Components: Database Core, HTTP Interface > Environment: All >Reporter: Jan Lehnardt >Assignee: Paul Joseph Davis >Priority: Minor > > Allow CouchDB to run in read-only mode so that multiple instances can run on > a singe database file where only one instance has write access to the > database. -- 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-66) Add read-only mode
[ https://issues.apache.org/jira/browse/COUCHDB-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-66. - https://issues.apache.org/jira/browse/COUCHDB-61 > Add read-only mode > -- > > Key: COUCHDB-66 > URL: https://issues.apache.org/jira/browse/COUCHDB-66 > Project: CouchDB > Issue Type: Improvement > Components: Database Core, HTTP Interface > Environment: All >Reporter: Jan Lehnardt >Assignee: Paul Joseph Davis >Priority: Minor > > Allow CouchDB to run in read-only mode so that multiple instances can run on > a singe database file where only one instance has write access to the > database. -- 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: API Docs (finally)
On Tue, Feb 21, 2012 at 7:07 PM, Jason Smith wrote: > Jan, easy question: > > CouchDB is now in Git, and now there are two additional projects > people are talking about: the web site and now the documentation. > > I wonder if the same repo could host all three projects, with > dissimilar, independent history trees. (I know the web site has svn > requirements but most would agree that git-svn is quite excellent > dealing with this.) > Someone feel free to correct me if I'm wrong, but I think this would require that our Git repo mirror some form of an SVN url. Plus our history has been disconnected so we'd have to do some fancy dancing to get things back in sync. So basically, no. But I can't think of a reason that we can't host both in the Git repo and then write a script that forcibly updates some random SVN url. Me and Benoit have a very similar setup for handling all the documentation for Gunicorn (though its based on GitHub's Pages thing in a branch (but the basic idea is the same). > On Wed, Feb 22, 2012 at 3:36 AM, Jan Lehnardt wrote: >> Hi all, >> >> I finally got my act together and prepared the CouchDB API docs that MC >> Brown made for Couchbase for your consideration to be added to the project. >> >> I put it up on GitHub so you can check it out. >> >> The repo is: >> >> https://github.com/janl/couchdb-docs >> >> To build all docs, you run `make everything`. I put the results on GitHub >> Pages. >> >> It includes multiple HTML builds with different granularities (single page, >> break by section, break by chapter) as well as PDF and ePub versions: >> >> Single Page: >> http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.html >> By Chapter: >> http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.html-dir/index.html >> By Section: >> http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.html-section/index.html >> PDF: >> http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.pdf >> ePub >> http://janl.github.com/couchdb-docs/couchdb-manual-1.1/couchdb-manual.epub >> >> There's also a CouchDB 1.1. release guide that explains all the new features >> in depth: >> >> Single Page: >> http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.html >> By Chapter: >> http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.html-dir/index.html >> By Section: >> http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.html-section/index.html >> PDF: >> http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.pdf >> ePub >> http://janl.github.com/couchdb-docs/couchdb-release-1.1/couchdb-release-1.1.epub >> >> The README.md files outlines the build dependencies. >> >> The license is CC 3.0 but we can adapt that to whatever is required. >> >> There's a few rough edges, no styling should be obvious and the few >> screenshots are using our old Single Server branded Futon, but I don't >> consider these things to block adoption. >> >> Let me know what you think. I hope you like it! :) >> >> (w finally!) >> >> Cheers >> Jan >> -- >> > > > > -- > Iris Couch
[jira] [Closed] (COUCHDB-46) Time out after saving a design document in Futon
[
https://issues.apache.org/jira/browse/COUCHDB-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-46.
-
Resolved for a while. Closing.
> Time out after saving a design document in Futon
>
>
> Key: COUCHDB-46
> URL: https://issues.apache.org/jira/browse/COUCHDB-46
> Project: CouchDB
> Issue Type: Bug
> Components: Futon, JavaScript View Server
> Environment: Futon on Apache CouchDB 0.7.3a650295
> Linux nebula 2.6.22-14-server #1 SMP Tue Feb 12 03:10:53 UTC 2008 x86_64
> GNU/Linux
> Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.14) Gecko/20080404
> Firefox/2.0.0.14
>Reporter: Paul Joseph Davis
>Assignee: Paul Joseph Davis
>Priority: Minor
> Fix For: 0.10
>
>
> Occasionally, after saving a View in futon, I noticed that occasionally the
> first hit to the view results in a timeout. It appears that its generally
> required to change the number of documents in the view to cause a timeout.
> This only happens on the first request to the view and subsequent request are
> all fine.
> Captured headers and output from a time out:
> Response Headers
> Transfer-Encoding chunked
> ServerMochiWeb/1.0 (Any of you quaids got a smint?)
> Date Sun, 27 Apr 2008 18:38:44 GMT
> Content-Type text/plain;charset=utf-8
> Request Headers
> Host nebula:5984
> User-AgentMozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.14)
> Gecko/20080404 Firefox/2.0.0.14
> Accept
> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
> Accept-Language en-us,en;q=0.5
> Accept-Encoding gzip,deflate
> Accept-CharsetISO-8859-1,utf-8;q=0.7,*;q=0.7
> Keep-Alive300
> Connectionkeep-alive
> Response:
> {"error":"error","reason":"wait_timeout"}
> CouchDB log:
> [info] [<0.227.0>] HTTP Error (code 500): wait_timeout
> [info] [<0.227.0>] 172.18.130.165 - - "GET /test/_view/all/tree" 500
--
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-384) [PATCH] Improvements to couch_config for unit testing purposes
[ https://issues.apache.org/jira/browse/COUCHDB-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-384. -- Resolved for a while. Closing. > [PATCH] Improvements to couch_config for unit testing purposes > -- > > Key: COUCHDB-384 > URL: https://issues.apache.org/jira/browse/COUCHDB-384 > Project: CouchDB > Issue Type: Improvement > Components: Database Core >Affects Versions: 0.9 >Reporter: Brad Anderson >Assignee: Paul Joseph Davis >Priority: Minor > Fix For: 0.10 > > Attachments: couchdb-384.patch > > > To be able to run unit tests involving configuration (i.e. couch_config > module), two changes are proposed: > 1. The ability to start the couch_config gen_server with no .ini files in > start_link/1. This means that CouchDB doesn't even need to be running for > tests to be performed. The caller of set/4 needs to use 'false' as the > Persist argument, but this is probably desirable when running unit tests. > 2. The ability to shut down the couch_config gen_server is necessary for > proper cleanup after the tests are run. > The attached patch solves both issues. -- 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-383) HTTP get parameter strictness/looseness
[
https://issues.apache.org/jira/browse/COUCHDB-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-383.
--
Resolved for a while. Closing.
> HTTP get parameter strictness/looseness
> ---
>
> Key: COUCHDB-383
> URL: https://issues.apache.org/jira/browse/COUCHDB-383
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
>Affects Versions: 1.0
> Environment: Linux Debian 5.0 (VMware image)
>Reporter: Simon Thulbourn
>Assignee: Paul Joseph Davis
>Priority: Minor
> Fix For: 0.10
>
>
> The use of GET params in a URL is either too loose or too strict depending on
> your point of view.
> Adding extra GET params that are not needed to a query works on every request
> except for /dbname/_all_docs, in this event CouchDB returns an error.
> Test Case:
> /foobar/_all_docs?callback=jsonp1244562168058&_=1244562168079
> Returns: jsonp1244562168058({"error":"query_parse_error","reason":"Invalid
> URL parameter: \"_\""});
> NOTE: this is not just a JSONP error, this is just how I found it.
> Ideally, CouchDB either needs to accept this or to error on every request
> with that contains erroneous GET parameters.
--
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-327) Replication of document results in invalid_json error
[
https://issues.apache.org/jira/browse/COUCHDB-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-327.
--
Resolved for a while. Closing.
> Replication of document results in invalid_json error
> -
>
> Key: COUCHDB-327
> URL: https://issues.apache.org/jira/browse/COUCHDB-327
> Project: CouchDB
> Issue Type: Bug
>Affects Versions: 0.9
> Environment: Ubuntu 8.10
>Reporter: Matthew Gregg
>Assignee: Adam Kocoloski
>
> While replicating a document containing UTf8 characters replication fails
> with invalid_json errors in the receiving couch instance.
> The test below will cause the replication error.
> couchTests.utf8_replication = function(debug) {
> if (debug) debugger;
> var host = CouchDB.host;
> var texts = [];
> var dbPairs = [
> {source:"http://"+host+"/test_suite_db_a";,
> target:"http://"+host+"/test_suite_db_b"}
> ]
> var dbA = new CouchDB("test_suite_db_a");
> var dbB = new CouchDB("test_suite_db_b");
> var numDocs = 10;
> var xhr;
> for (var testPair = 0; testPair < dbPairs.length; testPair++) {
> var A = dbPairs[testPair].source
> var B = dbPairs[testPair].target
> dbA.deleteDb();
> dbA.createDb();
> dbB.deleteDb();
> dbB.createDb();
> text = " Fakain: Faktor produksi yang digunakan hanya tenaga kerja
> saja. Kualitas ba";
> dbA.save({_id:"1", text:text})
> var result = CouchDB.replicate(A, B);
> }
> };
--
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-372) update_notification broken with couchspawnkillable change
[
https://issues.apache.org/jira/browse/COUCHDB-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-372.
--
Resolved for a while. Closing.
> update_notification broken with couchspawnkillable change
> -
>
> Key: COUCHDB-372
> URL: https://issues.apache.org/jira/browse/COUCHDB-372
> Project: CouchDB
> Issue Type: Bug
>Reporter: Robert Newson
>Assignee: Paul Joseph Davis
>Priority: Critical
>
> as of at least r780544, my update_notification cannot be launched by couchdb.
> I get this;
> Apache CouchDB 0.10.0a780544 (LogLevel=info) is starting.
> [error] [<0.49.0>] {error_report,<0.22.0>,
> {<0.49.0>,crash_report,
> [[{pid,<0.49.0>},
>{registered_name,[]},
>{error_info,
>{exit,
>{bad_return_value,{os_process_error,{data,"kill -9 19883\n"}}},
>[{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},
>{initial_call,{couch_os_process,init,['Argument__1']}},
>{ancestors,
>[couch_db_update,couch_primary_services,couch_server_sup,<0.1.0>]},
>{messages,[]},
>{links,[<0.43.0>]},
>{dictionary,[]},
>{trap_exit,false},
>{status,running},
>{heap_size,610},
>{stack_size,23},
>{reductions,244}],
> []]}}
> {"init terminating in
> do_boot",{{badmatch,{error,shutdown}},[{couch_server_sup,start_server,1},{erl_eval,do_apply,5},{erl_eval,exprs,5},{init,start_it,1},{init,start_em,1}]}}
> If I comment out the first line in src/couchdb/priv/couchspawnkillable my
> process is launched correctly but is then killed shortly afterwards by couch;
> Apache CouchDB 0.10.0a780544 (LogLevel=info) is starting.
> [couchdb-lucene] INFO indexer started.
> [couchdb-lucene] INFO indexer stopped.
> [error] [<0.49.0>] {error_report,<0.22.0>,
> {<0.49.0>,crash_report,
> [[{pid,<0.49.0>},
>{registered_name,[]},
>{error_info,
>{exit,
>{bad_return_value,{os_process_error,"OS process timed out."}},
>[{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},
>{initial_call,{couch_os_process,init,['Argument__1']}},
>{ancestors,
>[couch_db_update,couch_primary_services,couch_server_sup,<0.1.0>]},
>{messages,[]},
>{links,[<0.43.0>]},
>{dictionary,[]},
>{trap_exit,false},
>{status,running},
>{heap_size,610},
>{stack_size,23},
>{reductions,244}],
> []]}}
> {"init terminating in
> do_boot",{{badmatch,{error,shutdown}},[{couch_server_sup,start_server,1},{erl_eval,do_apply,5},{erl_eval,exprs,5},{init,start_it,1},{init,start_em,1}]}}
> Crash dump was written to: erl_crash.dump
> init terminating in do_boot ()
> real 0m5.769s
> user 0m0.648s
> sys 0m0.520s
--
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-333) Json handling of UTF8 strings not in accordance with rfc4627
[
https://issues.apache.org/jira/browse/COUCHDB-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-333.
--
Resolved for a while. Closing.
> Json handling of UTF8 strings not in accordance with rfc4627
>
>
> Key: COUCHDB-333
> URL: https://issues.apache.org/jira/browse/COUCHDB-333
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
>Affects Versions: 0.9
> Environment: couchdb 0.9.0 spidermonkey 0.7.0 erlang R12B3
>Reporter: mark
> Attachments: utf16-surrogate-pairs.diff
>
>
> Handling of some unicode values escaped in json format \u fails with
> "invalid_json" error.
> curl -X PUT -d
> '{"revisions":[],"_id":"U_1d11e","codepoint":"3441","definition":"\uD834\uDD1E
> G clef character"}' http://localhost:5984/mydb/U_1d11e
> yields
> {"error":"invalid_json","reason":"{\"revisions\":[],\"_id\":\"U_1d11e\",\"codepoint\":\"3441\",\"definition\":\"\\uD834\\uDD1E
> G clef character\"}"}
> When the RFC states:
>To escape an extended character that is not in the Basic Multilingual
>Plane, the character is represented as a twelve-character sequence,
>encoding the UTF-16 surrogate pair. So, for example, a string
>containing only the G clef character (U+1D11E) may be represented as
>"\uD834\uDD1E".
> Furthermore, couchdb accepts encoded strings of the format \u which
> is not mentioned as acceptable in the json rfc
> curl -X PUT -d
> '{"revisions":[],"_id":"U_1d11e","codepoint":"3441","definition":"\u0001D11E
> G clef character"}' http://localhost:5984/mydb/U_1d11e
> Yields:
> {"ok":true,"id":"U_1d11e","rev":"1-1270273433"}
--
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-363) can't POST to an external
[
https://issues.apache.org/jira/browse/COUCHDB-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-363.
--
Resolved for a while. Closing.
> can't POST to an external
> -
>
> Key: COUCHDB-363
> URL: https://issues.apache.org/jira/browse/COUCHDB-363
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
>Affects Versions: 0.10
>Reporter: Benoit Chesneau
>Assignee: Paul Joseph Davis
>Priority: Critical
> Fix For: 0.9.1
>
> Attachments: couch_httpd_external.diff
>
>
> Trying to post to an external and get error 500 :
> Headers: [{'Accept',"application/json, text/javascript, */*"},
> {'Accept-Charset',"ISO-8859-1,utf-8;q=0.7,*;q=0.7"},
> {'Accept-Encoding',"gzip,deflate"},
> {'Accept-Language',"en-us,en;q=0.5"},
> {'Cache-Control',"no-cache"},
> {'Connection',"keep-alive"},
> {'Content-Length',"59"},
> {'Content-Type',"application/x-www-form-urlencoded; charset=UTF-8"},
> {'Host',"127.0.0.1:5984"},
> {'Keep-Alive',"300"},
> {'Pragma',"no-cache"},
>
> {'Referer',"http://127.0.0.1:5984/friendpaste/_design/fp/index.html"},
> {'User-Agent',"Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5;
> en-US; rv:1.9.0.10) Gecko/2009042315 Firefox/3.0.10"},
> {"X-Requested-With","XMLHttpRequest"}]
> [error] [<0.60.0>] Uncaught error in HTTP request: {error,function_clause}
> [info] [<0.60.0>] Stacktrace: [{mochiweb_util,parse_qs_key,[undefined,[]]},
> {mochiweb_util,parse_qs,2},
> {couch_httpd_external,json_req_obj,2},
> {couch_httpd_external,process_external_req,3},
> {couch_httpd_db,do_db_req,2},
> {couch_httpd,handle_request,5},
> {mochiweb_http,headers,5},
> {proc_lib,init_p_do_apply,3}]
> [debug] [<0.60.0>] httpd 500 error response:
> {"error":"unknown_error","reason":"function_clause"}
--
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-364) Badly formed bulk insert returns an invalid HTTP response
[
https://issues.apache.org/jira/browse/COUCHDB-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-364.
--
No follow up from reporter. Closing.
> Badly formed bulk insert returns an invalid HTTP response
> -
>
> Key: COUCHDB-364
> URL: https://issues.apache.org/jira/browse/COUCHDB-364
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
>Affects Versions: 0.9
> Environment: Linux 2.6.29.4-162.fc11.x86_64 (Fedora 11)
> Erlang (BEAM) emulator version 5.6.5 [source] [64-bit] [smp:4]
> [async-threads:0] [hipe] [kernel-poll:false] with OTP R12B
> CouchDB 0.9.0
>Reporter: Vilya Harvey
>Assignee: Paul Joseph Davis
>Priority: Minor
> Fix For: 0.10
>
>
> Trying to do a bulk update via /database/_bulk_docs and passing any
> unexpected JSON value as the body (i.e. anything other than a map with the
> key "docs" containing the list of documents) causes CouchDB to return an
> empty response. I guess it should be returning an error message describing
> the problem in this case?
> For example, this works correctly and returns the list of inserted documents:
> curl -X POST -d '{ "docs": [{"name": "Fred"}, {"name": "Bruce"}] }'
> http://localhost:5984/scans/_bulk_docs
> But this fails with the error message as below:
> curl -X POST -d '[{"name": "Fred"}, {"name": "Bruce"}]'
> http://localhost:5984/scans/_bulk_docs
> curl: (52) Empty reply from server
> (the difference being that the second is just passing through a list of
> documents, leaving out the { "docs": ... } wrapper).
--
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-353) [PATCH] add default_handler into configuration for overriding couch_httpd_db:handle_request/1 if needed
[ https://issues.apache.org/jira/browse/COUCHDB-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-353. -- Resolved for a while. Closing. > [PATCH] add default_handler into configuration for overriding > couch_httpd_db:handle_request/1 if needed > --- > > Key: COUCHDB-353 > URL: https://issues.apache.org/jira/browse/COUCHDB-353 > Project: CouchDB > Issue Type: Improvement > Components: HTTP Interface >Affects Versions: 0.9 >Reporter: Brad Anderson >Assignee: Paul Joseph Davis >Priority: Minor > Fix For: 0.10 > > Attachments: default_handler.console.txt, default_handler.patch > > > To execute code other than couch_httpd_db:handle_request/1 for the default > handler function, we need to add a configuration option to specify the new > module/fun and execute that function upon a request. This will allow devs to > execute alternate code for things like database creation and deletion, etc. -- 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-357) group_level fails for multi-key reduce view
[ https://issues.apache.org/jira/browse/COUCHDB-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-357. -- Resolved as not fixing a while ago with no push back. Closing. > group_level fails for multi-key reduce view > --- > > Key: COUCHDB-357 > URL: https://issues.apache.org/jira/browse/COUCHDB-357 > Project: CouchDB > Issue Type: Bug > Components: HTTP Interface >Reporter: Mark Hammond >Assignee: Paul Joseph Davis > Fix For: 0.9.1 > > Attachments: issue-357.patch > > > If you try and execute a multi-key reduce view with a group_level param, > could returns a query parser error with message '"Multi-key fetchs for reduce > view must include `group=true`". The error persists if you add that param. > The problem appears to be that couch_httpd_view.erl is only checking for > 'exact' grouping, not an integer level. Attaching a patch; thanks to Paul > Davis for the direction... -- 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-41) Differentiate between not existent database and not existant document in response on 404
[
https://issues.apache.org/jira/browse/COUCHDB-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-41.
-
Resolved for a while. Closing.
> Differentiate between not existent database and not existant document in
> response on 404
>
>
> Key: COUCHDB-41
> URL: https://issues.apache.org/jira/browse/COUCHDB-41
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
> Environment: CouchDB 0.7.2
>Reporter: Kore Nordmann
>Assignee: Paul Joseph Davis
>Priority: Blocker
> Fix For: 0.10
>
>
> Currently it is not possible to know from a request on a not existent
> document in the database, if the database does not exist, or if it is just
> the document which is missing.
> It would be nice to have this information in the response JSON structure, so
> that the application using the CouchDB could handle such errors more
> gracefully. An extract from a CouchDB interaction showing the problem:
> == Ensure database is absent
> DELETE /test HTTP/1.0
> Host: localhost
> HTTP/1.0 404 Object Not Found
> Server: inets/develop
> Date: Tue, 15 Apr 2008 20:54:20 GMT
> Cache-Control: no-cache
> Pragma: no-cache
> Expires: Tue, 15 Apr 2008 20:54:20 GMT
> Connection: close
> Content-Type: text/plain;charset=utf-8
> {"error":"not_found","reason":"missing"}
> == Try GET on absent database
> GET /test/not_existant HTTP/1.0
> Host: localhost
> HTTP/1.0 404 Object Not Found
> Server: inets/develop
> Date: Tue, 15 Apr 2008 20:54:20 GMT
> Cache-Control: no-cache
> Pragma: no-cache
> Expires: Tue, 15 Apr 2008 20:54:20 GMT
> Connection: close
> Content-Type: text/plain;charset=utf-8
> {"error":"not_found","reason":"missing"}
> == Create database, but not the document
> PUT /test HTTP/1.0
> Host: localhost
> HTTP/1.0 201 Created
> Server: inets/develop
> Date: Tue, 15 Apr 2008 20:54:20 GMT
> Cache-Control: no-cache
> Pragma: no-cache
> Expires: Tue, 15 Apr 2008 20:54:20 GMT
> Connection: close
> Content-Type: text/plain;charset=utf-8
> {"ok":true}
> == Try to fetch document again
> GET /test/not_existant HTTP/1.0
> Host: localhost
> HTTP/1.0 404 Object Not Found
> Server: inets/develop
> Date: Tue, 15 Apr 2008 20:54:20 GMT
> Cache-Control: no-cache
> Pragma: no-cache
> Expires: Tue, 15 Apr 2008 20:54:20 GMT
> Connection: close
> Content-Type: text/plain;charset=utf-8
> {"error":"not_found","reason":"missing"}
--
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-349) Removing a _view can cause the database browser interface to break
[ https://issues.apache.org/jira/browse/COUCHDB-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-349. -- > Removing a _view can cause the database browser interface to break > -- > > Key: COUCHDB-349 > URL: https://issues.apache.org/jira/browse/COUCHDB-349 > Project: CouchDB > Issue Type: Bug > Components: Futon >Affects Versions: 0.9 >Reporter: Sam Bisbee >Assignee: Paul Joseph Davis > Fix For: 0.9.1 > > > Futon may navigate you to a _view that no longer exists when returning to the > database's browser, causing the interface to break. > Steps to reproduce: > 1. View an existing _view in Futon (ex., > http://localhost:5984/_utils/database.html?foo/_design%2FuserInfo%2Fbar) > 2. Browse to the design document - I just clicked on the "_design/userInfo" > link on the right side of the "View code" box. > 3. Edit the design document, removing the _view we were just at (in this > case, "bar"). > 4. Save the design document. > 5. Return to the database's overview. I clicked on the "Overview > foo" link > in the top navigation bar. > Error message(s): > 1. Firebug reports the following... > viewCode is undefined > http://localhost:5984/_utils/script/futon.browse.js?0.9.0 > Line 298 > 2. Firebug reports the following... > document.body is null > http://localhost:5984/_utils/script/jquery.js?1.3.1 > Line 3085 > The cause: > When you return to the database's browser, whether from the Futon Overview > page or a direct link, Futon attempts to return to the previous view, which > we just removed from the design document. > Temporary fix: > You need to change the URL in the address bar to something valid (ex., > specify a _view that's valid). If you try to go back to the Futon Overview > page and then click on the database, it will simply redirect you to the > invalid view again. -- 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-343) [PATCH] JSONP support
[
https://issues.apache.org/jira/browse/COUCHDB-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-343.
--
Resolved for a while. Closing.
> [PATCH] JSONP support
> -
>
> Key: COUCHDB-343
> URL: https://issues.apache.org/jira/browse/COUCHDB-343
> Project: CouchDB
> Issue Type: New Feature
> Components: HTTP Interface
>Affects Versions: 0.9
>Reporter: Brad Anderson
>Assignee: Paul Joseph Davis
>Priority: Minor
> Fix For: 0.10
>
> Attachments: jsonp.js, jsonp.patch
>
>
> Adds support for JSONP, or JSON with Padding, which surrounds the response
> JSON object with a callback from the querystring ?callback=blah as
> blah({json_resp});
> http://bob.pythonmac.org/archives/2005/12/05/remote-json-jsonp/
--
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-334) With deferred commits and 100+ active dbs, CouchDB can lose uncommitted changes
[ https://issues.apache.org/jira/browse/COUCHDB-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-334. -- Resolved for a while. Closing. > With deferred commits and 100+ active dbs, CouchDB can lose uncommitted > changes > --- > > Key: COUCHDB-334 > URL: https://issues.apache.org/jira/browse/COUCHDB-334 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Affects Versions: 0.9 >Reporter: Damien Katz >Assignee: Damien Katz > Fix For: 0.9.1 > > > By default, CouchDB keeps a maximum of 100 databases open and active. This is > controlled by the ini setting max_dbs_open in [couchdb] . > This limit controls the number of Erlang server processes that are readily > available and hold resources, like file handles, and hold state for deferred > commits. Once CouchDB hits the open database limit, it will always close an > idle database and files before opening a new database file. The problem is > that CouchDB would consider instances to be idle even if they still had > deferred commits pending. It would then close the instance and drop it's > deferred commits. -- 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-332) Reject documents whose ids start with underscore
[
https://issues.apache.org/jira/browse/COUCHDB-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-332.
--
Resolved for a while. Closing.
> Reject documents whose ids start with underscore
>
>
> Key: COUCHDB-332
> URL: https://issues.apache.org/jira/browse/COUCHDB-332
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
> Environment: 0.10.0a767851
>Reporter: Brian Candler
>Assignee: Paul Joseph Davis
>Priority: Minor
> Fix For: 0.10
>
>
> docids which start with underscore are reserved for CouchDB. I believe they
> should be rejected to avoid confusion.
> Currently observed behaviour:
> (1) an attempt to PUT to /db/_docid succeeds, and creates a document whose ID
> starts with an underscore
> $ curl -X PUT -d "{}" http://127.0.0.1:5984/foo/_xxx
> {"ok":true,"id":"_xxx","rev":"1-1751372641"}
> (2) a POST to /db/_docid tries to do something and fails; possibly it could
> succeed given the right headers and body.
> $ curl -X POST -d "{}" http://127.0.0.1:5984/foo/_yyy
> {"error":"bad_content_type","reason":"Invalid Content-Type header for form
> upload"}
> -- status line show 415 Unsupported Media Type
> This means that typos can result in confusing error messages; for example, a
> POST to /db/_tmp_view instead of /db/_temp_view. IMO it would be cleaner
> first to test the docid and reject it on that basis.
> (Sorry, I am not including a test suite submission. It will be much easier
> for someone who already knows their way around the rather large set of
> private libraries which the test suite contains. I currently use Ruby to talk
> to CouchDB, not ECMAscript)
--
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-311) Wrong encoded _external error message
[ https://issues.apache.org/jira/browse/COUCHDB-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-311. -- Resolved for a while. Closing. > Wrong encoded _external error message > - > > Key: COUCHDB-311 > URL: https://issues.apache.org/jira/browse/COUCHDB-311 > Project: CouchDB > Issue Type: Bug > Components: HTTP Interface >Affects Versions: 0.9 >Reporter: Volker Mische >Assignee: Paul Joseph Davis >Priority: Minor > Fix For: 0.9.1 > > Attachments: no-server-error.patch > > > The error message when no external server configuration is found is encoded > as a list of bytes. > To reproduce this bug, enable _external and browse > http://localhost:5984/geodata/_external/ithrowanerror -- 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
dev@couchdb.apache.org
[ https://issues.apache.org/jira/browse/COUCHDB-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-331. -- Resolved for a while. Closing. > Allow reduce=true&include_docs=false > > > Key: COUCHDB-331 > URL: https://issues.apache.org/jira/browse/COUCHDB-331 > Project: CouchDB > Issue Type: Improvement > Components: HTTP Interface > Environment: 0.10.0a767851 >Reporter: Brian Candler >Assignee: Paul Joseph Davis >Priority: Trivial > Fix For: 0.10 > > Attachments: test-reduce.diff > > > If you query to a map/reduce view, then currently a request for > reduce=true&include_docs=false > is rejected as erroneous. > It would be useful to allow this, to simplify clients which remember default > options for a view (e.g. :reduce=>false,:include_docs=>true) and then > override them for particular queries. -- 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-310) Fix hardcoded redirect to "/_utils/"
[ https://issues.apache.org/jira/browse/COUCHDB-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-310. -- Resolved for a while. Closing. > Fix hardcoded redirect to "/_utils/" > > > Key: COUCHDB-310 > URL: https://issues.apache.org/jira/browse/COUCHDB-310 > Project: CouchDB > Issue Type: Improvement > Components: HTTP Interface >Affects Versions: 0.10 > Environment: * >Reporter: Benoit Chesneau >Assignee: Paul Joseph Davis > Fix For: 0.9.1, 0.10 > > Attachments: couch_httpd_misc_handlers.erl.diff > > > Find attached a patch that remove hard writing of "_utils" path in > handle_utils_dir_req. It allows to really change the util path or use the > handler to manage other path. -- 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-322) Specifying reduce=true on a view with no reduce does not cause an error.
[ https://issues.apache.org/jira/browse/COUCHDB-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-322. -- Resolved for a while. Closing. > Specifying reduce=true on a view with no reduce does not cause an error. > > > Key: COUCHDB-322 > URL: https://issues.apache.org/jira/browse/COUCHDB-322 > Project: CouchDB > Issue Type: Bug > Components: HTTP Interface >Affects Versions: 0.9.1 > Environment: trunk >Reporter: Paul Joseph Davis >Assignee: Paul Joseph Davis > Fix For: 0.9.1 > > > Specifying group=true when a view has no reduce function should probably > throw an error. Any objections? -- 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-305) Warnings from the /usr/bin/couchdb script
[ https://issues.apache.org/jira/browse/COUCHDB-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-305. -- Resolved for a while. Closing. > Warnings from the /usr/bin/couchdb script > - > > Key: COUCHDB-305 > URL: https://issues.apache.org/jira/browse/COUCHDB-305 > Project: CouchDB > Issue Type: Bug > Components: Build System >Affects Versions: 0.9 > Environment: Gentoo, bash 3.2.39. >Reporter: Dirkjan Ochtman >Priority: Minor > Fix For: 0.9 > > > When starting CouchDB, I get the following warnings: > /usr/bin/couchdb: line 143: 0: command not found > /usr/bin/couchdb: line 147: 0: command not found > /usr/bin/couchdb: line 151: 0: command not found -- 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-324) startkey and endkey don't work with ~ or %7E
[
https://issues.apache.org/jira/browse/COUCHDB-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-324.
--
Closing non-issue.
> startkey and endkey don't work with ~ or %7E
>
>
> Key: COUCHDB-324
> URL: https://issues.apache.org/jira/browse/COUCHDB-324
> Project: CouchDB
> Issue Type: Bug
> Environment: svn -r763553
>Reporter: Brian Candler
>
> The following range queries don't work as expected
> startkey="a"&endkey="a~"
> startkey="a"&endkey="a%7E"
> (Aside: I was hoping to use "foo" to "foo~" as a reasonably clean way of
> querying "any key beginning with foo")
> The following testcase shows this for "a~", since query doesn't encode it.
> However I wasn't sure how to test for "a%7E" cleanly.
> --- /home/brian/svn/couchdb/share/www/script/test/view_collation.js
> 2009-03-20 12:50:46.0 +
> +++ view_collation.js 2009-04-09 11:23:20.0 +0100
> @@ -109,4 +109,11 @@
> endkey : "b", endkey_docid: "b",
> inclusive_end:false}).rows;
>T(rows[rows.length-1].key == "aa")
> +
> + // startkey and endkey with ~ (currently query doesn't encode this,
> + // but really we should test both a~ and a%7E)
> + var rows = db.query(queryFun, null, {startkey: "a", endkey: "a~"}).rows;
> + T(rows.length == 3); // a, A, aa
> + var rows = db.query(queryFun, null, {startkey: "a~", endkey: "b"}).rows;
> + T(rows.length == 1 && rows[0].key == "b");
> };
> Here are the actual results obtained using curl:
> $ curl -X POST -d '{"map":"function(doc) { emit(doc.foo, null); }"}'
> 'http://127.0.0.1:5984/test_suite_db/_temp_view?startkey="a"&endkey="a~";'
> {"total_rows":26,"offset":7,"rows":[
> {"id":"7","key":"a","value":null},
> {"id":"8","key":"A","value":null}
> ]}
> $ curl -X POST -d '{"map":"function(doc) { emit(doc.foo, null); }"}'
> 'http://127.0.0.1:5984/test_suite_db/_temp_view?startkey="a"&endkey="a%7E";'
> {"total_rows":26,"offset":7,"rows":[
> {"id":"7","key":"a","value":null},
> {"id":"8","key":"A","value":null}
> ]}
> But what I was expecting was the same as range "a" to "az":
> $ curl -X POST -d '{"map":"function(doc) { emit(doc.foo, null); }"}'
> 'http://127.0.0.1:5984/test_suite_db/_temp_view?startkey="a"&endkey="az";'
> {"total_rows":26,"offset":7,"rows":[
> {"id":"7","key":"a","value":null},
> {"id":"8","key":"A","value":null},
> {"id":"9","key":"aa","value":null}
> ]}
--
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-319) javascript is default language for views. - not working for save and save-as
[ https://issues.apache.org/jira/browse/COUCHDB-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-319. -- Resolved for a while. Closing. > javascript is default language for views. - not working for save and save-as > -- > > Key: COUCHDB-319 > URL: https://issues.apache.org/jira/browse/COUCHDB-319 > Project: CouchDB > Issue Type: Bug > Components: Futon >Affects Versions: 0.9 > Environment: couchdb 0.9.0a762190 and 0.9.0 on ubuntu 8.10 >Reporter: Kevin Ilchmann Jørgensen >Priority: Minor > > javascript is default language for views. and works when run from the futon. > But save and save-as still requires a "language" : "javascript" key value in > the _design/document. > the checks are on share/couchdb/www/script/futon.browse.js:434 and 388 -- 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-300) Update Sequence broken
[ https://issues.apache.org/jira/browse/COUCHDB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-300. -- Resolved for a while. Closing. > Update Sequence broken > -- > > Key: COUCHDB-300 > URL: https://issues.apache.org/jira/browse/COUCHDB-300 > Project: CouchDB > Issue Type: Bug > Environment: ubuntu hardy >Reporter: Sven Helmberger > Fix For: 0.9 > > Attachments: all_docs_by_seq.js, update_seq_kaputt.js > > > Database gets into a state where there is one document but an empty update > sequence. -- 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-295) Upload attachment form in futon does not work
[ https://issues.apache.org/jira/browse/COUCHDB-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-295. -- No further info from reporter. Closing. > Upload attachment form in futon does not work > - > > Key: COUCHDB-295 > URL: https://issues.apache.org/jira/browse/COUCHDB-295 > Project: CouchDB > Issue Type: Bug > Components: Futon >Affects Versions: 0.9 > Environment: couchdb 0.9.0a754958 > firefox 3.0.7-1.fc10 >Reporter: Jamie Brandon >Assignee: Christopher Lenz >Priority: Minor > Fix For: 0.9 > > > Using 'upload attachment' form in futon. The server returns 405 and the > upload form hangs with full progress bar. -- 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-52) building with a --prefix that has an ending slash confuses serve_file()
[ https://issues.apache.org/jira/browse/COUCHDB-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-52. - Assignee: (was: Christopher Lenz) No further info or reopen. Closing. > building with a --prefix that has an ending slash confuses serve_file() > --- > > Key: COUCHDB-52 > URL: https://issues.apache.org/jira/browse/COUCHDB-52 > Project: CouchDB > Issue Type: Bug > Components: HTTP Interface >Affects Versions: 0.8 > Environment: osx >Reporter: Johan Sørensen >Priority: Minor > Fix For: 0.9 > > > configuring with: > $ ./configure --prefix=$HOME/couchdb/ > caused the futon interface to 404 because it couldn't handle a > "$HOME/couchdb//share/couchdb/www" path (I'm guessing), note the > double-slashes. > Configuring with an ending slash on the --prefix works. -- 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-221) Test that validation and authorization work properly with replicated edits.
[ https://issues.apache.org/jira/browse/COUCHDB-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-221. -- Resolved for a while. Closing. > Test that validation and authorization work properly with replicated edits. > --- > > Key: COUCHDB-221 > URL: https://issues.apache.org/jira/browse/COUCHDB-221 > Project: CouchDB > Issue Type: Test > Components: Test Suite >Reporter: Dean Landolt >Assignee: Damien Katz >Priority: Blocker > Fix For: 0.9 > > > Test that the validation and authorization stuff work properly with > replicated edits, the same as it does with live edits. This should already > work, but its not tested. Also there is a good chance > validation/authorization failures might not be handled gracefully by the > replicator. It should eat failures, keeping statistics about the failures and > maybe a record of the last failure, or last N failures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-34) Enable replicator to use HTTP authentication
[ https://issues.apache.org/jira/browse/COUCHDB-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-34. - Resolved for a while. Closing. > Enable replicator to use HTTP authentication > > > Key: COUCHDB-34 > URL: https://issues.apache.org/jira/browse/COUCHDB-34 > Project: CouchDB > Issue Type: New Feature > Components: Database Core >Reporter: Christopher Lenz >Assignee: Damien Katz >Priority: Blocker > Fix For: 0.9 > > > You can currently give the CouchDB replicator HTTP URIs to remote databases. > However, if one of those remote instances is behind HTTP authentication, the > replication will fail. It should be possible to specify authentication > credentials to the replicator, which it would then use in response to 401 > responses. -- 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-281) couch clobbers stdout file and stderr file
[ https://issues.apache.org/jira/browse/COUCHDB-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-281. -- Resolved for a while. Closing. > couch clobbers stdout file and stderr file > -- > > Key: COUCHDB-281 > URL: https://issues.apache.org/jira/browse/COUCHDB-281 > Project: CouchDB > Issue Type: Bug >Affects Versions: 0.9 > Environment: Linux melkjug.com 2.6.23-gentoo-r8 #1 SMP Wed Feb 13 > 14:28:49 EST 2008 x86_64 QEMU Virtual CPU version 0.9.1 GenuineIntel GNU/Linux >Reporter: Joshua Bronson > > If you start couch with -o or -e and give it a file that already exists, it > truncates the file rather than appending to it. -- 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-255) Update MochiWeb
[ https://issues.apache.org/jira/browse/COUCHDB-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-255. -- Resolved for a while. Closing. > Update MochiWeb > --- > > Key: COUCHDB-255 > URL: https://issues.apache.org/jira/browse/COUCHDB-255 > Project: CouchDB > Issue Type: Task > Components: HTTP Interface >Affects Versions: 0.8, 0.8.1, 0.9 >Reporter: Jan Lehnardt >Assignee: Christopher Lenz >Priority: Blocker > Fix For: 0.9 > > > http://code.google.com/p/mochiweb/source/detail?r=89 -- 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-274) Add a -C option to load configuration file without resetting system default
[ https://issues.apache.org/jira/browse/COUCHDB-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-274. -- Resolved for a while. Closing. > Add a -C option to load configuration file without resetting system default > --- > > Key: COUCHDB-274 > URL: https://issues.apache.org/jira/browse/COUCHDB-274 > Project: CouchDB > Issue Type: New Feature > Components: Infrastructure >Reporter: eric casteleijn >Priority: Minor > Attachments: couchdb.patch > > > I created a patch that adds a -C (as opposed to lowercase -c) option that > accepts one of more configuration files and overrides the system default with > the values specified therein. -- 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-153) Erlang should warn about log/data file permissions
[ https://issues.apache.org/jira/browse/COUCHDB-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-153. -- Resolved for a while. Closing. > Erlang should warn about log/data file permissions > -- > > Key: COUCHDB-153 > URL: https://issues.apache.org/jira/browse/COUCHDB-153 > Project: CouchDB > Issue Type: Bug > Components: Infrastructure >Reporter: Noah Slater >Assignee: Jan Lehnardt >Priority: Critical > Attachments: issue-153.patch, issue-153.patch > > > CouchDB is installed as root for most people, and hence without remembering > to change the permissions on the log/data directories, errors are very > common. The problems caused by incorrect permissions can be very confusing. > We should re-add the checks for these that used to be in the init script, but > place them in CouchDB core. We need to do this so that the multiple > configuration settings will be taken account for. -- 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-238) should throw error on creating docs with illegal private names
[ https://issues.apache.org/jira/browse/COUCHDB-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-238. -- Resolved for a while. Closing. > should throw error on creating docs with illegal private names > -- > > Key: COUCHDB-238 > URL: https://issues.apache.org/jira/browse/COUCHDB-238 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Reporter: Chris Anderson >Priority: Blocker > Fix For: 0.9 > > Attachments: COUCHDB-238.patch > > > currently the only legal _ prefixes are _local and _design. We should test > for this and return http errors. The applies to PUT and bulk-docs -- 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-190) _uuid should respond to GET, not POST
[ https://issues.apache.org/jira/browse/COUCHDB-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-190. -- Resolved for a while. Closing. > _uuid should respond to GET, not POST > - > > Key: COUCHDB-190 > URL: https://issues.apache.org/jira/browse/COUCHDB-190 > Project: CouchDB > Issue Type: Improvement > Components: Database Core >Affects Versions: 0.9 >Reporter: Matt Goodall >Priority: Blocker > Fix For: 0.9 > > Attachments: COUCH-190.diff > > > The /_uuid resource can happily return a response to a GET without being > unresty. In fact, supporting POST is probably incorrect as it implies it > would change server state. > Quick summary: > * _uuid never changes server state > * calling _uuid multiple times does not impact other clients > * that the resource returns something different each time it is requested > does not mean it cannot be a POST > * GET with proper cache control (i.e. don't cache it ever) will work equally > well > Full discussion can be found on the user m.l., > http://mail-archives.apache.org/mod_mbox/couchdb-user/200901.mbox/%3C21939021.1440421230910477169.JavaMail.servlet@perfora%3E. -- 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-266) PUTting json docs > 1MB causes Uncaught error in HTTP request: {exit,{body_too_large,content_length}}
[
https://issues.apache.org/jira/browse/COUCHDB-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-266.
--
Resolved for a while. Closing.
> PUTting json docs > 1MB causes Uncaught error in HTTP request:
> {exit,{body_too_large,content_length}}
> --
>
> Key: COUCHDB-266
> URL: https://issues.apache.org/jira/browse/COUCHDB-266
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
>Affects Versions: 0.9
> Environment: Apache CouchDB 0.9.0a747258
>Reporter: Jeff Hinrichs
>Assignee: Christopher Lenz
> Fix For: 0.9
>
>
> error displays itself when trying to PUT a json document that is > 1MB.
> First noticed in the python interface, confirmed with curl
> [Tue, 24 Feb 2009 13:30:00 GMT] [error] [<0.1113.0>] Uncaught error in HTTP
> request: {exit,{body_too_large,content_length}}
> 2
> 3 [Tue, 24 Feb 2009 13:30:00 GMT] [debug] [<0.1113.0>] Stacktrace:
> [{mochiweb_request,stream_body,5},
> 4 {mochiweb_request,recv_body,2},
> 5 {couch_httpd,json_body,1},
> 6 {couch_httpd_db,db_doc_req,3},
> 7 {couch_httpd_db,do_db_req,2},
> 8 {couch_httpd,handle_request,3},
> 9 {mochiweb_http,headers,4},
> 10{proc_lib,init_p,5}]
> modifying src/mochiweb/mochiweb_request.erl > -define(MAX_RECV_BODY,
> (1024*1024))
> to something bigger, say -define(MAX_RECV_BODY, (1024*1024*16))
> alleviates the problem temporarily.
> issue confirmed by cmlenz on irc, he believed it to be a regression
--
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-225) local-clean target removes things that shouldn't be removed
[ https://issues.apache.org/jira/browse/COUCHDB-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-225. -- Resolved for a while. Closing. > local-clean target removes things that shouldn't be removed > --- > > Key: COUCHDB-225 > URL: https://issues.apache.org/jira/browse/COUCHDB-225 > Project: CouchDB > Issue Type: Bug >Reporter: Noah Slater >Assignee: Noah Slater >Priority: Blocker > Fix For: 0.9 > > Attachments: COUCHDB-225.diff > > > `make local-clean` removes the m4/ folder and you have to do a `svn up` > before you can `./bootstrap` again -- 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] [Reopened] (COUCHDB-11) CouchDB should handle errors when opening port gracefully
[ https://issues.apache.org/jira/browse/COUCHDB-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee reopened COUCHDB-11: --- Yes, I do mean to reopen this ticket from so long ago. :) The same mochiweb error is getting printed, but so are a bunch of erlang dumps. A lot of the dumps aren't clearly linked to the port already being bound to. The cause of the issue becomes non-obvious for the uninitiated and it would be a lot nicer for the user to just have a "that port is in use" message with couch exiting immediately. Cheers. > CouchDB should handle errors when opening port gracefully > - > > Key: COUCHDB-11 > URL: https://issues.apache.org/jira/browse/COUCHDB-11 > Project: CouchDB > Issue Type: Bug >Reporter: Noah Slater >Priority: Minor > > ATM CouchDB crashes loud and hard when it tries to open a port that is not > available. There should be some error handling code in place that produces > a nice message like so: > "Could not open port %d: %s" % (port_number, message) > Obviously, the above is written in Python - but you get the idea. -- 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-211) Can't add attachments in Futon
[ https://issues.apache.org/jira/browse/COUCHDB-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-211. -- Resolved for a while. Closing. > Can't add attachments in Futon > -- > > Key: COUCHDB-211 > URL: https://issues.apache.org/jira/browse/COUCHDB-211 > Project: CouchDB > Issue Type: Bug > Components: Futon >Affects Versions: 0.9 > Environment: Windows Firefox 3.0.5 > CouchDB 0.9.0a734451-incubating >Reporter: Dean Landolt >Assignee: Christopher Lenz > Fix For: 0.9 > > > The attachments popover is failing to submit with the error > Error: Form elements must not be named "submit". -- 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-203) added total run time to the tests
[ https://issues.apache.org/jira/browse/COUCHDB-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-203. -- Resolved for a while. Closing. > added total run time to the tests > - > > Key: COUCHDB-203 > URL: https://issues.apache.org/jira/browse/COUCHDB-203 > Project: CouchDB > Issue Type: Improvement > Components: Futon >Reporter: Bob Dionne >Assignee: Christopher Lenz >Priority: Trivial > Fix For: 0.9 > > Attachments: couch_test_runner.diff > > > added running total to footer. It provides a quick indication whether the > test are faster overall or not -- 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-214) Futon doesn't handle slashes in doc store names
[ https://issues.apache.org/jira/browse/COUCHDB-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-214. -- Resolved for a while. Closing. > Futon doesn't handle slashes in doc store names > --- > > Key: COUCHDB-214 > URL: https://issues.apache.org/jira/browse/COUCHDB-214 > Project: CouchDB > Issue Type: Bug > Components: Futon > Environment: OS X, Safari, Firefox >Reporter: Bob Dionne >Assignee: Christopher Lenz >Priority: Minor > Fix For: 0.9 > > > create a doc store with names "foo/bar" and then save a custom query for it -- 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-202) [PATCH] Support other languages for views in Futon
[ https://issues.apache.org/jira/browse/COUCHDB-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-202. -- Resolved for a while. Closing. > [PATCH] Support other languages for views in Futon > -- > > Key: COUCHDB-202 > URL: https://issues.apache.org/jira/browse/COUCHDB-202 > Project: CouchDB > Issue Type: Improvement > Components: Futon >Reporter: Brian Palmer >Assignee: Christopher Lenz > Fix For: 0.9 > > Attachments: Futon_languages_support.patch > > > Attached is a small patch to generalize Futon to support any language defined > in the .ini file. If the language is recognized, Futon will use the correct > "stub" map function in the edit textarea. Currently I've added stub map > methods for javascript and ruby, more could be added. > Languages are checked on save and handled conservatively. So once a view has > been created, its language cannot be changed. And when first saving a view, > the target document's language is checked and an error is returned if the > languages don't match. -- 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-207) href not properly closed in document view
[ https://issues.apache.org/jira/browse/COUCHDB-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-207. -- Resolved for a while. Closing. > href not properly closed in document view > - > > Key: COUCHDB-207 > URL: https://issues.apache.org/jira/browse/COUCHDB-207 > Project: CouchDB > Issue Type: Bug > Components: Futon >Affects Versions: 0.9 >Reporter: Maciek Starzyk >Assignee: Christopher Lenz >Priority: Trivial > Fix For: 0.9 > > Attachments: href.patch > > > The href in the document id at the top of the page is missing the terminating > quote, so the HTML is broken. -- 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-171) Futon app not showing data in Firefox3.1b2
[ https://issues.apache.org/jira/browse/COUCHDB-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-171. -- Resolved for a while. Closing. > Futon app not showing data in Firefox3.1b2 > -- > > Key: COUCHDB-171 > URL: https://issues.apache.org/jira/browse/COUCHDB-171 > Project: CouchDB > Issue Type: Bug > Components: Test Suite >Affects Versions: 0.9 > Environment: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; > rv:1.9.1b2) Gecko/20081125 Firefox/3.1b2 >Reporter: Andrea Schiavini >Priority: Trivial > Attachments: futon_firefox3.1beta-updated.patch, > futon_firefox3.1beta_fix.patch > > > No data is displayed in the Futon application under Firefox3.1b2. Checked > against Camino and Safari and both work. -- 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-196) Bug in _all_docs: extra incorrect row returned when ?key= is specified
[ https://issues.apache.org/jira/browse/COUCHDB-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-196. -- Resolved for a while. Closing. > Bug in _all_docs: extra incorrect row returned when ?key= is specified > -- > > Key: COUCHDB-196 > URL: https://issues.apache.org/jira/browse/COUCHDB-196 > Project: CouchDB > Issue Type: Bug > Components: HTTP Interface >Reporter: Jason Davies > Attachments: collation_ids.diff, collation_test.2.diff, > collation_test.diff, couch_db_updater.diff, docid_collation.diff, view_coll.js > > > I first noticed this when attempting to reverse the order of docs displayed > in Futon, when listing the design docs. When the order is reversed, > non-design docs are displayed. > After digging deeper I discovered that querying _all_docs with key="Z" can > potentially return two rows, with keys "Z" and "a". > I will attach a test case to reproduce this. My locale is set to > en_GB.UTF-8, which could be related to this problem. -- 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-186) Bookmarkable URLs in Futon
[ https://issues.apache.org/jira/browse/COUCHDB-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-186. -- Resolved for a while. Closing. > Bookmarkable URLs in Futon > -- > > Key: COUCHDB-186 > URL: https://issues.apache.org/jira/browse/COUCHDB-186 > Project: CouchDB > Issue Type: Improvement > Components: Futon >Affects Versions: 0.9 >Reporter: Jason Davies >Assignee: Christopher Lenz >Priority: Minor > Fix For: 0.9 > > Attachments: bookmarkable_futon.2.diff, bookmarkable_futon.3.diff, > bookmarkable_futon.4.diff, bookmarkable_futon.diff > > > This is a nice-to-have: make Futon's URLs bookmarkable by putting various > data about the current page in the URL fragment (after the '#' character). -- 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-56) Allow refreshing of a list of documents or a single document in one click
[ https://issues.apache.org/jira/browse/COUCHDB-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-56. - Resolved for a while. Closing. > Allow refreshing of a list of documents or a single document in one click > - > > Key: COUCHDB-56 > URL: https://issues.apache.org/jira/browse/COUCHDB-56 > Project: CouchDB > Issue Type: Improvement > Components: Futon >Reporter: Harry Fuecks >Assignee: Christopher Lenz >Priority: Trivial > Fix For: 0.9 > > Attachments: couchdb-56_20080624.patch > > > Doesn't seem to be a way to refresh the view of single document or a list of > documents (e.g. the database view or some custom view) with a single click - > currently requires switching to some other part of the UI then back again, > which gets annoying if you're updating the data elsewhere in the background. > Perhaps the name of the database / view / document at the top in the > breadcrumb trail could be an active link which allows the currently displayed > data to be refreshed. -- 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-90) A custom query should not run until the user clicks the "Run" button
[ https://issues.apache.org/jira/browse/COUCHDB-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-90. - Resolved for a while. Closing. > A custom query should not run until the user clicks the "Run" button > > > Key: COUCHDB-90 > URL: https://issues.apache.org/jira/browse/COUCHDB-90 > Project: CouchDB > Issue Type: Improvement > Components: Futon >Affects Versions: 0.9 >Reporter: Matt Goodall > > The view build time for new/custom queries against a large database is long > and processor intensive. In addition the default custom view functions (emit > all docs with a null key) are only useful as a guide/template. > I suggest that the custom query tool only requests the view once the user > explicitly clicks on the "Run" button. It would also make more sense if the > "View Code" panel is always visible. -- 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-32) map function timeout
[
https://issues.apache.org/jira/browse/COUCHDB-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-32.
-
Resolved for a while. Closing.
> map function timeout
>
>
> Key: COUCHDB-32
> URL: https://issues.apache.org/jira/browse/COUCHDB-32
> Project: CouchDB
> Issue Type: Bug
> Components: JavaScript View Server
> Environment: ubuntu/ openbsd . dualcore amd64 440+ with 2go of ram,
> couchdb version 0.7.2
>Reporter: Benoit Chesneau
>Priority: Critical
>
> I can't have any results with views on 229 items in database. Each execution
> give this result :
> {"error":"map_process_error","reason":"map function timed out"} . _adhoc
> views_ work.
> debug log :
> [Tue, 01 Apr 2008 01:36:17 GMT] [info] [<0.68.0>] HTTP Request: GET
> /test/_view/paste/all HTTP/1.1
> [Tue, 01 Apr 2008 01:36:17 GMT] [debug] [<0.68.0>] Headers:
> [{"connection","keep-alive"},
> {"keep-alive","300"},
> {"accept-charset","ISO-8859-1,utf-8;q=0.7,*;q=0.7"},
>{"accept-encoding","gzip,deflate"},
> {"accept-language","en-us,en;q=0.5"},
> {"accept",
>
> "text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5"},
> {"user-agent",
>"Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.13)
> Gecko/20080325 Ubuntu/7.10 (gutsy) Firefox/2.0.0.13"},
> {"host","localhost:5984"}]
> [Tue, 01 Apr 2008 01:36:17 GMT] [debug] [<0.68.0>] Body: []
> [Tue, 01 Apr 2008 01:36:18 GMT] [info] [<0.77.0>] Spawning new
> text/javascript instance.
> [Tue, 01 Apr 2008 01:36:30 GMT] [error] [emulator] Error in process <0.77.0>
> with exit value: {{nocatch,{map_process_error,"map function timed
> out"}},[{couch_query_servers,readline,2},{couch_query_servers,read_json,1},{couch_query_servers,'-map_docs/2-fun-0-',2},{lists,map,2},{couch_query_servers,map_docs,2...
>
> [Tue, 01 Apr 2008 01:36:30 GMT] [info] [<0.68.0>] HTTP Error (code 500):
> {obj,[{error,"map_process_error"},
> {reason,"map function timed out"}]}
> [Tue, 01 Apr 2008 01:36:30 GMT] [debug] [<0.68.0>] HTTP Response Headers
> (code 500): [{"cache-control","no-cache"},
>{"pragma","no-cache"},
>{"expires","Tue, 01 Apr 2008 01:36:30
> GMT"},
>{"transfer-encoding","chunked"},
>{"content-type",
> "text/plain;charset=utf-8"}]
> [Tue, 01 Apr 2008 01:36:30 GMT] [info] [<0.68.0>] HTTP Response Code:500
> View tested :
> function(doc) {
>if (doc.type == 'snippet') map(doc._id, doc);
> }
--
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-166) Request with include_docs=true&reduce=false fails
[
https://issues.apache.org/jira/browse/COUCHDB-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-166.
--
Resolved for a while. Closing.
> Request with include_docs=true&reduce=false fails
> -
>
> Key: COUCHDB-166
> URL: https://issues.apache.org/jira/browse/COUCHDB-166
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
>Affects Versions: 0.9
> Environment: Tested on Linux with CouchDB 0.9.0a720489
>Reporter: Michael Fellinger
> Attachments: patch
>
>
> There seems to be an issue related to parameter order, which I think is a
> bug, given that they are named.
> This request will work:
> /testdb/_view/user/all?reduce=false&include_docs=true
> This request will fail:
> /testdb/_view/user/all?include_docs=true&reduce=false
> producing following error with status 500:
> {"error":"query_parse_error","reason":"Bad URL query key for reduce
> operation: include_docs"}
--
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-138) reduce=false & include_docs=true cannot be combined in a query
[
https://issues.apache.org/jira/browse/COUCHDB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-138.
--
Resolved for a while. Closing.
> reduce=false & include_docs=true cannot be combined in a query
> --
>
> Key: COUCHDB-138
> URL: https://issues.apache.org/jira/browse/COUCHDB-138
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
>Affects Versions: 0.9
>Reporter: Paul Carey
>Priority: Minor
> Attachments: couch_tests.js.view_include_docs.diff
>
>
> Passing ?reduce=false&include_docs=true to a query results in the following
> error message
> {"error":"query_parse_error","reason":"Bad URL query key for reduce
> operation: include_docs"}
> I believe that the presence of a reduce function should not prevent
> include_docs from working.
--
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-102) External Server Support
[ https://issues.apache.org/jira/browse/COUCHDB-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-102. -- No longer seems relevant given the iterations on externals over the last few years. Closing. > External Server Support > --- > > Key: COUCHDB-102 > URL: https://issues.apache.org/jira/browse/COUCHDB-102 > Project: CouchDB > Issue Type: New Feature > Components: Full-Text Search, HTTP Interface >Affects Versions: 0.9 >Reporter: Paul Joseph Davis > Attachments: 0001-External-Server-Support.patch > > > External Server Support > > Based on jchris's Action Server code. Exposes an "_external" interface akin > to the view server, but using a json line protocol communicates to an > external process. There's a section in couch.ini that allows for custom > external processes to be setup. Ie: > > [Couch External Servers] > fti = /path/to/couchdb-xapian-query > > Would result in the url "http://localhost:5984/db/_external/fti"; being > available. Notice the correspondence in the url to the fti specified in the > config. -- 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: replicator
On Feb 21, 2012, at 11:00 PM, Filipe David Manana wrote: > On Tue, Feb 21, 2012 at 7:30 PM, Bob Dionne > wrote: >> Hi Filipe, >> >> I'm seeing an issue in the replicator. This anonymous function [1] is >> throwing function_clause errors as it doesn't handle codes 400-500 that >> might occur in [2,3]. > > Right, like in some other places we don't deal with all possible http > status codes, only a subset that are expected (success or otherwise). I can see that, except in this case the funs that use the callback do so in clauses that explicitly test for >= 400 and <= 500 I'm seeing the 400 in long running pull replications from BigCouch. I'm not sure of the underlying cause yet but I'll run it down and let you know Thanks, Bob > Which http status code are you receiving? How to reproduce that? > > I have a rough idea how to fix it but I'm not sure whether I should > handle it in replicator_httpc or up in the callback. Does this ring a > bell? Opinions? >> >> Cheers, >> >> Bob >> >> [1] >> https://github.com/bdionne/couchdb/blob/master/src/couch_replicator/src/couch_replicator_api_wrap.erl#L335 >> [2] >> https://github.com/bdionne/couchdb/blob/master/src/couch_replicator/src/couch_replicator_httpc.erl#L90 >> [3] >> https://github.com/bdionne/couchdb/blob/master/src/couch_replicator/src/couch_replicator_httpc.erl#L111 > > > > -- > 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."
[jira] [Closed] (COUCHDB-160) replication performance improvements
[ https://issues.apache.org/jira/browse/COUCHDB-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-160. -- Resolved for a while. Closing. > replication performance improvements > > > Key: COUCHDB-160 > URL: https://issues.apache.org/jira/browse/COUCHDB-160 > Project: CouchDB > Issue Type: Improvement > Components: Database Core >Affects Versions: 0.9 >Reporter: Adam Kocoloski >Priority: Minor > Attachments: couch_rep.erl.diff > > > I wrote some code to speed up CouchDB's replication process by parallelizing > document requests and using _bulk_docs to write changes to the target. I > tested the speedup as follows: > * 1000 document DB, 1022 update_seq, ~450 KB after compaction > * local and remote machines have ~45 ms latency > * timed requests using timer:tc(couch_rep, replicate, [<<"source">>, > <<"target">>] > * all replications are "from scratch" > trunk: > local-local 115 > local-remote145 > remote-remote 173 > remote-local146 > db size after replication: 1.8 MB > patch: > local-local 1.83 > local-remote38 > remote-remote 64 > remote-local35 > db size after replication: 453 KB > I'll attach the patch as an update to this issue. It might be worth exposing > the "batch size" (currently 100 docs) as a configurable parameter. Comments > welcome. Best, > Adam -- 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-177) Malformed JSON returned by keys based query
[
https://issues.apache.org/jira/browse/COUCHDB-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-177.
--
Resolved for a while. Closing.
> Malformed JSON returned by keys based query
> ---
>
> Key: COUCHDB-177
> URL: https://issues.apache.org/jira/browse/COUCHDB-177
> Project: CouchDB
> Issue Type: Bug
> Components: JavaScript View Server
>Affects Versions: 0.9
>Reporter: Paul Carey
> Attachments: COUCHDB-177.patch, keys_based_query.sh
>
>
> If not all keys exist for a keys based query on a reduce view, malformed JSON
> may be returned.
> The attached test case queries a view that returns an array commencing with a
> comma character.
> {"rows":[,{"key":"1","value":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] [Closed] (COUCHDB-174) Docs with lots of revisions break replication
[ https://issues.apache.org/jira/browse/COUCHDB-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Bisbee closed COUCHDB-174. -- Resolved for a while. Closing. > Docs with lots of revisions break replication > - > > Key: COUCHDB-174 > URL: https://issues.apache.org/jira/browse/COUCHDB-174 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Reporter: Adam Kocoloski > Attachments: couch_rep.diff > > > When replicating from a remote source CouchDB uses the open_revs query string > parameter in a document request and supplies a list of revisions that are > present on the source but not on the target. If this list is very large the > resulting URL might exceed 8 KB, in which case MochiWeb/gen_tcp will not > serve the request. > I'm sure there are a number of ways to work around this limitation. I'm > attaching a patch that checks if the URL formed from the list of revs to open > will be larger than 8 KB, and if so chunks the list and makes multiple > smaller requests. Best, > Adam -- 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-45) Error when concurrently hitting HTTP. Seems that it doesn't honor Connection: Close
[
https://issues.apache.org/jira/browse/COUCHDB-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-45.
-
No re-open in several years. Closing.
> Error when concurrently hitting HTTP. Seems that it doesn't honor Connection:
> Close
> ---
>
> Key: COUCHDB-45
> URL: https://issues.apache.org/jira/browse/COUCHDB-45
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Environment: linux
>Reporter: Jeff Davey
>Assignee: Damien Katz
> Fix For: 0.9
>
>
> While doing some load testing against couch, i've noticed that it throws
> errors when sending concurrently with more than 40 threads.
> I'm guessing that it's trying to send something back to the client after the
> socket has already been closed. I'm using Connection: Close in the headers on
> the http client.
> {mochiweb_socket_server,221,
> {child_error,{{case_clause,{error,enotconn}},
> [{mochiweb_request,get,2},
>{couch_httpd,handle_request,2},
>{mochiweb_http,headers,4},
>{proc_lib,init_p,5}]}}}
> [error] [<0.4889.0>] {error_report,
> <0.22.0>,
> {<0.4889.0>,
> crash_report,
> [[{pid,<0.4889.0>},
>{registered_name,[]},
>{error_info,
>{{case_clause,{error,enotconn}},
> [{mochiweb_request,get,2},
> {couch_httpd,handle_request,2},
> {mochiweb_http,headers,4},
> {proc_lib,init_p,5}]}},
>{initial_call,
>{mochiweb_socket_server,
>acceptor_loop,
>[{<0.53.0>,#Port<0.125>,#Fun}]}},
>{ancestors,[couch_httpd,couch_server_sup,<0.1.0>]},
>{messages,[]},
>{links,[<0.53.0>,#Port<0.3453>]},
>{dictionary,
>[{mochiweb_request_body,
> <<"{ \"sender\" : \"bob\", \"recipient\" : \"test1\",
> \"flagNew\" : true }">>}]},
>{trap_exit,false},
>{status,running},
>{heap_size,6765},
>{stack_size,21},
>{reductions,5351}],
> []]}}
> [error] [<0.53.0>] {error_report,
> <0.22.0>,
> {<0.53.0>,
> std_error,
> {mochiweb_socket_server,
> 221,
> {child_error,
> {{case_clause,{error,enotconn}},
> [{mochiweb_request,get,2},
>{couch_httpd,handle_request,2},
>{mochiweb_http,headers,4},
>{proc_lib,init_p,5}]}
--
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-123) Error (54 'Connection reset by peer') when try to fetch item from db
[
https://issues.apache.org/jira/browse/COUCHDB-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee closed COUCHDB-123.
--
No follow up from reporter for several years. Closing.
> Error (54 'Connection reset by peer') when try to fetch item from db
>
>
> Key: COUCHDB-123
> URL: https://issues.apache.org/jira/browse/COUCHDB-123
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
>Affects Versions: 0.8.1
> Environment: Mac OS 10.5
> Python 2.5.2
> couchdb-python 0.4
> Django 1.0
>Reporter: Senmiao Liu
>Assignee: Damien Katz
> Attachments: error at
> _blog_detail_76157aebf566c3ab5dfa126f7c68f5d6_.html, error at _blog_new_.html
>
>
> I recently play with django+couchdb using couchdb-python.
> Sometimes I met a error like this:
> =
> Environment:
> Request
> Method: GET
> Request URL:
> http://127.0.0.1:8000/blog/detail/76157aebf566c3ab5dfa126f7c68f5d6/
> Django Version: 1.0-final-SVN-unknown
> Python Version: 2.5.2
> Installed Applications:
> ['django.contrib.auth', 'django.contrib.contenttypes',
> 'django.contrib.sessions', 'django.contrib.sites', 'djcouch.blog']
> Installed Middleware:
> ('django.middleware.common.CommonMiddleware',
> 'django.contrib.sessions.middleware.SessionMiddleware',
> 'django.contrib.auth.middleware.AuthenticationMiddleware')
> Traceback:
> File
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/core/handlers/base.py"
> in get_response 86. response = callback(request, *callback_args,
> **callback_kwargs)
> File
> "/Users/zai/workspace/python/djcode/djcouch/../djcouch/blog/views.py"
> in detail 18. post = db.get(id)
> File
> "/opt/local/lib/python2.5/site-packages/CouchDB-0.4-py2.5.egg/couchdb/client.py"
> in get 295. return Document(self.resource.get(id, **options))
> File
> "/opt/local/lib/python2.5/site-packages/CouchDB-0.4-py2.5.egg/couchdb/client.py"
> in get 646. return self._request('GET', path, headers=headers,
> **params)
> File
> "/opt/local/lib/python2.5/site-packages/CouchDB-0.4-py2.5.egg/couchdb/client.py"
> in _request 674. body=body, headers=headers)
> File
> "/opt/local/lib/python2.5/site-packages/httplib2-0.4.0-py2.5.egg/httplib2/__init__.py"
> in request 1050. (response, content) = self._request(conn, authority,
> uri, request_uri, method, body, headers, redirections, cachekey)
> File
> "/opt/local/lib/python2.5/site-packages/httplib2-0.4.0-py2.5.egg/httplib2/__init__.py"
> in _request 854. (response, content) = self._conn_request(conn,
> request_uri, method, body, headers)
> File
> "/opt/local/lib/python2.5/site-packages/httplib2-0.4.0-py2.5.egg/httplib2/__init__.py"
> in _conn_request 824. response = conn.getresponse()
> File
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/httplib.py"
> in getresponse 928. response.begin()
> File
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/httplib.py"
> in begin 385. version, status, reason = self._read_status()
> File
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/httplib.py"
> in _read_status 343. line = self.fp.readline()
> File
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/socket.py"
> in readline 331. data = recv(1)
> Exception Type: error at /blog/detail/76157aebf566c3ab5dfa126f7c68f5d6/
> Exception Value: (54, 'Connection reset by peer')
> =
> I'm new to python and couchdb, so I'm not sure it's a bug of django, couchdb
> or the python client.
> Any ideas?
> Thank you,
--
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
