[jira] [Reopened] (COUCHDB-665) Replication not possible via IPv6
[ https://issues.apache.org/jira/browse/COUCHDB-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds reopened COUCHDB-665: --- Re-opening in light of the last comment. Blocking 1.2 in my opinion. Replication not possible via IPv6 -- Key: COUCHDB-665 URL: https://issues.apache.org/jira/browse/COUCHDB-665 Project: CouchDB Issue Type: Bug Components: Replication Affects Versions: 0.10.1 Environment: Linux x200 2.6.32-2 #2 SMP Wed Feb 17 01:00:03 CET 2010 x86_64 GNU/Linux Reporter: Michael Stapelberg Assignee: Filipe Manana Priority: Blocker Labels: ipv6 Fix For: 1.1, 1.0.3, 1.2 Attachments: COUCHDB-665-replication-ipv6.patch, couchdb-ipv6.patch, patch Original Estimate: 0.25h Remaining Estimate: 0.25h I have a host which is only reachable via IPv6. While I can connect to a CouchDB running on this host just fine, I cannot replicate my database to it. This is due to the inet6-option missing from the gen_tcp.connect() call. I will attach a patch which fixes the issue. To test it, you can use a host which only has an record in the DNS. CouchDB will immediately return 404 if you want to replicate to it unless you add the inet6 option. -- 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-1367) When settings revs_limit on db - the db increases its update_seq counter when viewing stats - but not when getting changes
[ https://issues.apache.org/jira/browse/COUCHDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds reopened COUCHDB-1367: Re-opening in light of recent dev@ discussion. It appears action will be taken here. Thanks, Henrik. When settings revs_limit on db - the db increases its update_seq counter when viewing stats - but not when getting changes -- Key: COUCHDB-1367 URL: https://issues.apache.org/jira/browse/COUCHDB-1367 Project: CouchDB Issue Type: Bug Components: HTTP Interface Affects Versions: 1.1.1 Environment: Any Reporter: Henrik Hofmeister Priority: Minor Labels: revs_limit If you put a number to _revs_limit on a db (to update it) - the http://host/dbname/ info document gets an increase in update_seq number - however the changes feed does not contain this change (while its not a change). This causes the update_seq in the dbinfo doc and the last seq in the changes feed to differ - which breaks any application depending on the update_seq number as the expected sequence size of the db (in my case - couchdb-lucene that will only respond to stale requests because it thinks its not up to date) I know this is an edge case - but still its something fairly fundamental - that clearly is not working as intended. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (COUCHDB-1042) make libcurl a soft (optional) dependency
[ https://issues.apache.org/jira/browse/COUCHDB-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds reopened COUCHDB-1042: Skill Level: New Contributors Level (Easy) Assignee: Randall Leeds I think now that the js tests run with make check something is needed here. We should issue a warning that these tests won't be run when the dependency isn't satisfied, and then not run them. make libcurl a soft (optional) dependency - Key: COUCHDB-1042 URL: https://issues.apache.org/jira/browse/COUCHDB-1042 Project: CouchDB Issue Type: Improvement Components: Build System Affects Versions: 1.0.1 Reporter: Randall Leeds Assignee: Randall Leeds Priority: Minor Fix For: 1.2, 2.0 Attachments: 0001-make-cURL-an-optional-dependency.patch, 0001-no-lcurl-if-no-curl-support.patch, curl_as_soft_dep.patch, curl_as_soft_dep_v2.patch CouchDB currently uses libcurl only in couchjs to expose HTTP client functions to the JavaScript environment. This functionality is used by the JavaScript unit tests. For idempotent views it is discouraged to perform I/O in a view function. Therefore, I propose that libcurl be made an optional dependency, automatically detected at build time, and a flag added to couchjs so it can be explicitly enabled in the unit tests (but disabled, by default, for the query server). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (COUCHDB-860) Futon appends wrong version number to files
[ https://issues.apache.org/jira/browse/COUCHDB-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Leeds reopened COUCHDB-860: --- Thanks. I couldn't find where this happened. I tried grepping around for 0.11.0 but didn't find that somehow. Futon appends wrong version number to files --- Key: COUCHDB-860 URL: https://issues.apache.org/jira/browse/COUCHDB-860 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.0.1 Reporter: Volker Mische Priority: Minor Futon appends the CouchDB version number to the JavaScript files it loads. In 1.0.1 it still appends 0.11 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
