[jira] [Commented] (COUCHDB-2237) Add a 'live' sugar for 'continuous'
[ https://issues.apache.org/jira/browse/COUCHDB-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14395739#comment-14395739 ] Dale Harvey commented on COUCHDB-2237: -- Also forgot to say thanks loads for implement @ Robert, I hope it does get picked up Add a 'live' sugar for 'continuous' --- Key: COUCHDB-2237 URL: https://issues.apache.org/jira/browse/COUCHDB-2237 Project: CouchDB Issue Type: Improvement Security Level: public(Regular issues) Components: HTTP Interface Reporter: Dale Harvey With PouchDB we generally try to stick to the same param names as Couch, we are even changing some we implemented first to be compatible (https://github.com/pouchdb/pouchdb/issues/2193) However 'continuous' sucks to type, its confusing to type and spell and everyone gets it wrong, we still support it but switched to documenting it as 'live' and life is awesome again -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2237) Add a 'live' sugar for 'continuous'
[ https://issues.apache.org/jira/browse/COUCHDB-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14395738#comment-14395738 ] Dale Harvey commented on COUCHDB-2237: -- I wouldnt suggest any breaking changes, we support both and its mostly a one line change (https://github.com/pouchdb/pouchdb/blob/master/lib/changes.js#L132) I dont thing stream is a good name since it is easily confused with the efforts to turn replication into an actual stream. However I think Couch could use live, watch or follow easily based on these patches, and if Couch went for an option that wasnt 'live' we would implement it in PouchDB as well. However I am not day to day involved enough in CouchDB to be trying to push for a change if people are against it. We have had this for a long time in PouchDB, its been very nice to not have to deal with the hard to spell continuous and it doesnt look like anyone is confused by the term 'live' and I dont hold much of a preference between live / watch / follow, I think semantically they are equally clear (or unclear). Its just a nice touch of usability in the API Add a 'live' sugar for 'continuous' --- Key: COUCHDB-2237 URL: https://issues.apache.org/jira/browse/COUCHDB-2237 Project: CouchDB Issue Type: Improvement Security Level: public(Regular issues) Components: HTTP Interface Reporter: Dale Harvey With PouchDB we generally try to stick to the same param names as Couch, we are even changing some we implemented first to be compatible (https://github.com/pouchdb/pouchdb/issues/2193) However 'continuous' sucks to type, its confusing to type and spell and everyone gets it wrong, we still support it but switched to documenting it as 'live' and life is awesome again -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2444) Mirror CORS domains
[ https://issues.apache.org/jira/browse/COUCHDB-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14201822#comment-14201822 ] Dale Harvey commented on COUCHDB-2444: -- Authentication from wildcard origins does not validate the spec, the spec doesnt specify the possible functionality of the servers ability to authenticate requests from wherever it chooses, it just specifies the valid server responses Mirror CORS domains --- Key: COUCHDB-2444 URL: https://issues.apache.org/jira/browse/COUCHDB-2444 Project: CouchDB Issue Type: Improvement Security Level: public(Regular issues) Components: HTTP Interface Reporter: Zachary Lym Most APIs that support CORS specify acceptable domains not with a wildcard but by mirroring the caller. I believe that this is an XSS mitigation technique but it would also allow cookie-based authentication on domains (which are blocked when a wildcard is used to specify the domains). If this capability exists, then it should be documented it in interface highlighted in the CORS documentation. [PouchDB cross-pollination|https://github.com/pouchdb/pouchdb/issues/896]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2442) Ability to ensure a cluster has been started successfully
Dale Harvey created COUCHDB-2442: Summary: Ability to ensure a cluster has been started successfully Key: COUCHDB-2442 URL: https://issues.apache.org/jira/browse/COUCHDB-2442 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: BigCouch Reporter: Dale Harvey We are currently using python dev/run to boot up a cluster and run our pouchdb tests against https://github.com/pouchdb/pouchdb/blob/master/bin/run-couch-master-on-travis.sh#L29 Ideally I would like something like python dev/run -d to start the cluster as a daemon, but only return once the cluster has all joined together and is ready to be written to, currently we are just 'sleep 10'ing and even 10 seconds is proving unreliable -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2205) 400 bad_request on DELETE /db/
[ https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-2205: - Description: During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow was: During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow 400 bad_request on DELETE /db/ -- Key: COUCHDB-2205 URL: https://issues.apache.org/jira/browse/COUCHDB-2205 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: HTTP Interface Reporter: Dale Harvey During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (COUCHDB-2205) 400 bad_request on DELETE /db/
[ https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey closed COUCHDB-2205. Resolution: Cannot Reproduce Havent seen this in a while, didnt mean to edit the title, closing out for now 400 bad_request on DELETE /db/ -- Key: COUCHDB-2205 URL: https://issues.apache.org/jira/browse/COUCHDB-2205 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: HTTP Interface Reporter: Dale Harvey During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2386) Cant undelete documents in master
Dale Harvey created COUCHDB-2386: Summary: Cant undelete documents in master Key: COUCHDB-2386 URL: https://issues.apache.org/jira/browse/COUCHDB-2386 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Database Core Reporter: Dale Harvey Basic commands to reproduce https://gist.github.com/daleharvey/cd5f058b20e92b52d80c There was a bug tracking this fix in previous versions of Couch, was reintroduced with the cluster merge https://issues.apache.org/jira/browse/COUCHDB-292 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2386) Cant undelete documents in master while passing _rev
[ https://issues.apache.org/jira/browse/COUCHDB-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170871#comment-14170871 ] Dale Harvey commented on COUCHDB-2386: -- Apparently there was a bug in the CouchDB test suite that verified this behaviour, it failed when we ran the couchdb test suite against pouchdb, however https://github.com/apache/couchdb/blob/master/share/www/script/test/recreate_doc.js#L36 is the only test I have found so far and it verifies different behaviour (that undeleting documents with a rev when there is a live one is a conflict) Cant undelete documents in master while passing _rev Key: COUCHDB-2386 URL: https://issues.apache.org/jira/browse/COUCHDB-2386 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Database Core Reporter: Dale Harvey Basic commands to reproduce https://gist.github.com/daleharvey/cd5f058b20e92b52d80c There was a bug tracking this fix in previous versions of Couch, was reintroduced with the cluster merge https://issues.apache.org/jira/browse/COUCHDB-292 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2383) Installation instructions are wrong
Dale Harvey created COUCHDB-2383: Summary: Installation instructions are wrong Key: COUCHDB-2383 URL: https://issues.apache.org/jira/browse/COUCHDB-2383 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Documentation Reporter: Dale Harvey As someone who doesnt build couchdb a lot, when I do it is fustrating I visited http://couchdb.apache.org/, clicked contribute, there was a huge wall of text, I think the calls to action should be clearer. I found Git workflow but it links to an empty wiki page, I then decided to go back and through the documentation, I found http://docs.couchdb.org/en/1.6.1/install/mac.html, the dependencies are wrong, there is little information on installing from source. I then took a look at https://github.com/apache/couchdb/blob/master/INSTALL.Unix, it also had the wrong dependencies and no mention of how to start a dev cluster (./configure make python2 dev/run) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2237) Add a 'live' sugar for 'continuous'
Dale Harvey created COUCHDB-2237: Summary: Add a 'live' sugar for 'continuous' Key: COUCHDB-2237 URL: https://issues.apache.org/jira/browse/COUCHDB-2237 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: HTTP Interface Reporter: Dale Harvey With PouchDB we generally try to stick to the same param names as Couch, we are even changing some we implemented first to be compatible (https://github.com/pouchdb/pouchdb/issues/2193) However 'continuous' sucks to type, its confusing to type and spell and everyone gets it wrong, we still support it but switched to documenting it as 'live' and life is awesome again -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2205) 400 bad_request on DELETE /db/
[ https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944096#comment-13944096 ] Dale Harvey commented on COUCHDB-2205: -- I didnt see any 400 response at all in the log, I dont understand what log you are referring to that indicates its POST /db/bulk_docs, from the PouchDB side its fairly certain its from DELETE /db/ (the stack refers to utils.js which cleans up databases pre and post run, also https://github.com/daleharvey/pouchdb/pull/1706/files#diff-74a635be9be46d0f8b20784f5117bb0cL74 will have this error not show up) 400 bad_request on DELETE /db/ -- Key: COUCHDB-2205 URL: https://issues.apache.org/jira/browse/COUCHDB-2205 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: HTTP Interface Reporter: Dale Harvey During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2205) 400 bad_request on DELETE /db/
[ https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944097#comment-13944097 ] Dale Harvey commented on COUCHDB-2205: -- The link from the gist never fired a 400, that was a full successful run, the error stacktrace looks to be expected 400 bad_request on DELETE /db/ -- Key: COUCHDB-2205 URL: https://issues.apache.org/jira/browse/COUCHDB-2205 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: HTTP Interface Reporter: Dale Harvey During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2205) 400 bad_request on DELETE /db/
[ https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944135#comment-13944135 ] Dale Harvey commented on COUCHDB-2205: -- Worth mentioning I hadnt ever previously seen this locally, installed 1.3.1 last night and seen it this morning at some point, it seems like it may have been fixed 400 bad_request on DELETE /db/ -- Key: COUCHDB-2205 URL: https://issues.apache.org/jira/browse/COUCHDB-2205 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: HTTP Interface Reporter: Dale Harvey During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2205) 400 bad_request on DELETE /db/
Dale Harvey created COUCHDB-2205: Summary: 400 bad_request on DELETE /db/ Key: COUCHDB-2205 URL: https://issues.apache.org/jira/browse/COUCHDB-2205 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: HTTP Interface Reporter: Dale Harvey During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2205) 400 bad_request on DELETE /db/
[ https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943890#comment-13943890 ] Dale Harvey commented on COUCHDB-2205: -- Here is a failing test with the CouchDB log in debug mode, I dont see it actually spitting out a 400 at any point https://travis-ci.org/daleharvey/pouchdb/jobs/21293717 (raw is @ https://s3.amazonaws.com/archive.travis-ci.org/jobs/21293717/log.txt) for comparison sake, here is a log of a passing local run against 1.3.1 https://gist.github.com/daleharvey/9700938 400 bad_request on DELETE /db/ -- Key: COUCHDB-2205 URL: https://issues.apache.org/jira/browse/COUCHDB-2205 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: HTTP Interface Reporter: Dale Harvey During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2205) 400 bad_request on DELETE /db/
[ https://issues.apache.org/jira/browse/COUCHDB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943892#comment-13943892 ] Dale Harvey commented on COUCHDB-2205: -- For some extra information about what is happening during the logs, https://github.com/daleharvey/pouchdb/blob/master/tests/test.bulk_docs.js is the client code 400 bad_request on DELETE /db/ -- Key: COUCHDB-2205 URL: https://issues.apache.org/jira/browse/COUCHDB-2205 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: HTTP Interface Reporter: Dale Harvey During the PouchDB test suite run I am seeing an intermittent 400 bad_request when trying to delete a database (it may or may not exist) CouchDB 1.3.1 (default on travis), I am unable to reproduce this anywhere else, logs to follow -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-1950) ddoc-based conflict resolution
[ https://issues.apache.org/jira/browse/COUCHDB-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13843162#comment-13843162 ] Dale Harvey commented on COUCHDB-1950: -- The notion that conflicts should not be fixed at all is confusing to me, the distinction between 'we' isnt clear, this is talking about a simpler way for users to resolve their conflicts how they choose. Are you saying conflicts should just grow infinitely until they are purged? ddoc-based conflict resolution -- Key: COUCHDB-1950 URL: https://issues.apache.org/jira/browse/COUCHDB-1950 Project: CouchDB Issue Type: Improvement Reporter: Nathan Vander Wilt This was discussed at CouchConf in Vancouver last month, but didn't see a hook here I could refer to in another conversation, so… It'd be great if a design document could include a conflict resolver function, in the vein of other app logic handler hooks like validate_doc_write. I imagine it would look something like either function (currentWinner, nextWinningestLoser, parent) (simply called multiple times if more than 2 leafs) or simply function (arrayOfDocs, revisionHistor) — if it returns a document, that's the winner, if not the next design document in line gets a pass at it. (Bonus: if it throws, the conflict stays no matter what other resolvers say?) -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (COUCHDB-1950) ddoc-based conflict resolution
[ https://issues.apache.org/jira/browse/COUCHDB-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13843170#comment-13843170 ] Dale Harvey commented on COUCHDB-1950: -- Sorry I meant 'prune' A design document based conflict resolution function wouldnt discard users writes, its a mechanism to allow users to more easily do what we already suggest they do to resolve conflicts, write a new document and/or delete conflicting leafs, a read resolver is similiar however the conflicts would still exist, which isnt a particularly a bad thing however it makes the semantics of all_docs / views and changes more complicated ddoc-based conflict resolution -- Key: COUCHDB-1950 URL: https://issues.apache.org/jira/browse/COUCHDB-1950 Project: CouchDB Issue Type: Improvement Reporter: Nathan Vander Wilt This was discussed at CouchConf in Vancouver last month, but didn't see a hook here I could refer to in another conversation, so… It'd be great if a design document could include a conflict resolver function, in the vein of other app logic handler hooks like validate_doc_write. I imagine it would look something like either function (currentWinner, nextWinningestLoser, parent) (simply called multiple times if more than 2 leafs) or simply function (arrayOfDocs, revisionHistor) — if it returns a document, that's the winner, if not the next design document in line gets a pass at it. (Bonus: if it throws, the conflict stays no matter what other resolvers say?) -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (COUCHDB-1950) ddoc-based conflict resolution
[ https://issues.apache.org/jira/browse/COUCHDB-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13843730#comment-13843730 ] Dale Harvey commented on COUCHDB-1950: -- So the problem being that in a system where we manage to get conflicts to happen simultaneously on seperate nodes, instead of having a 3 way merge with the original documents, this will result in a 2 way merge of the result of the 'resolved' documents (potentially lost information). That is entirely true of how we currently document how conflict resolution should be done now. There isnt a problem with this suggestion per se, more that its just exposing what is already a 'flaw' in the current documented implementation. A read resolver would be a much easier / safer thing to implement, however it comes with its own problems, to make a read resolver any way API consistent between all_docs / views / changes etc will mean a huge increase in the number of disk fetches each api call has to make, as it now needs to fetch each conflicting document and run them through a view engine Currently we hide all these complexities behind the winning revision mechanism, this is hiding what most people to consider CouchDB's killer feature so I do think its worth figuring out how to get it right ddoc-based conflict resolution -- Key: COUCHDB-1950 URL: https://issues.apache.org/jira/browse/COUCHDB-1950 Project: CouchDB Issue Type: Improvement Reporter: Nathan Vander Wilt This was discussed at CouchConf in Vancouver last month, but didn't see a hook here I could refer to in another conversation, so… It'd be great if a design document could include a conflict resolver function, in the vein of other app logic handler hooks like validate_doc_write. I imagine it would look something like either function (currentWinner, nextWinningestLoser, parent) (simply called multiple times if more than 2 leafs) or simply function (arrayOfDocs, revisionHistor) — if it returns a document, that's the winner, if not the next design document in line gets a pass at it. (Bonus: if it throws, the conflict stays no matter what other resolvers say?) -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (COUCHDB-1950) ddoc-based conflict resolution
[ https://issues.apache.org/jira/browse/COUCHDB-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837480#comment-13837480 ] Dale Harvey commented on COUCHDB-1950: -- This is something that can happen regardless of options to have conflicts true by default, its something I was planning to work on for PouchDB and make a patch for CouchDB if it worked nicely ddoc-based conflict resolution -- Key: COUCHDB-1950 URL: https://issues.apache.org/jira/browse/COUCHDB-1950 Project: CouchDB Issue Type: Improvement Reporter: Nathan Vander Wilt This was discussed at CouchConf in Vancouver last month, but didn't see a hook here I could refer to in another conversation, so… It'd be great if a design document could include a conflict resolver function, in the vein of other app logic handler hooks like validate_doc_write. I imagine it would look something like either function (currentWinner, nextWinningestLoser, parent) (simply called multiple times if more than 2 leafs) or simply function (arrayOfDocs, revisionHistor) — if it returns a document, that's the winner, if not the next design document in line gets a pass at it. (Bonus: if it throws, the conflict stays no matter what other resolvers say?) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (COUCHDB-1934) jquery.couch status
[ https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13834713#comment-13834713 ] Dale Harvey commented on COUCHDB-1934: -- Having jquery.couch.js's canonical location inside CouchDB never made sense, its a client library, a completely seperate project (and one that is extremely dated one at that), People fixing a client library shouldnt have to deal with the same intricacies that a db core developer has to worry about Project organisation aside, there have been problems with jquery.couch forcing limitations on the jquery version, plus issues with having them assumed to be available, couch instances that disable futon shouldnt suddenly break applications based on couch because of a broken dependancy The proposal to deprecate it then remove along with a major version bump was a good one, we shouldnt be scared to make positive changes to CouchDB just because its effort to make them. jquery.couch status --- Key: COUCHDB-1934 URL: https://issues.apache.org/jira/browse/COUCHDB-1934 Project: CouchDB Issue Type: Question Reporter: Alexander Shorin When [~nslater] had proposed to include [jquery.couch.js docs|http://daleharvey.github.io/jquery.couch.js-docs/symbols/] into official CouchDB one I recall old good time when we had discussed Futon.Next project. Suddenly, it was out of official mailing lists, so no references are available, but [~garren], [~dch], [~bigbluehat] and [~ryanramage] were there and our discussion was around jquery vs backbone vs pouchdb. Backbone won. Nowdays, we have Fauxton which doesn't used jquery.couch and based on Backbone. So it seems if we'll replace Futon with him this client library would be left orphan. So that's the question: what is the status of jquery.couch.js? Is it still actual and supported or going to be deprecated? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (COUCHDB-1934) jquery.couch status
[ https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13834741#comment-13834741 ] Dale Harvey commented on COUCHDB-1934: -- Yeh a console.warn in the file as suggested will be very visible to anyone thats using it jquery.couch status --- Key: COUCHDB-1934 URL: https://issues.apache.org/jira/browse/COUCHDB-1934 Project: CouchDB Issue Type: Question Reporter: Alexander Shorin When [~nslater] had proposed to include [jquery.couch.js docs|http://daleharvey.github.io/jquery.couch.js-docs/symbols/] into official CouchDB one I recall old good time when we had discussed Futon.Next project. Suddenly, it was out of official mailing lists, so no references are available, but [~garren], [~dch], [~bigbluehat] and [~ryanramage] were there and our discussion was around jquery vs backbone vs pouchdb. Backbone won. Nowdays, we have Fauxton which doesn't used jquery.couch and based on Backbone. So it seems if we'll replace Futon with him this client library would be left orphan. So that's the question: what is the status of jquery.couch.js? Is it still actual and supported or going to be deprecated? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (COUCHDB-1934) jquery.couch status
[ https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13834845#comment-13834845 ] Dale Harvey commented on COUCHDB-1934: -- Although I dont love it, I do think its still the best client library for CouchDB and the one poeple should be pointed at, I most definitely aim to make PouchDB the best client side HTTP library for Couch, but it isnt there yet, similiarly with nano its still more aimed with node in mind. I just dont believe its canonical development location lives inside CouchDB core, similiarly with fauxton itself and many other things inside CouchDB they can be used, developed and tested independently, the Reductio ad absurdum of keeping anything couch related inside the same repository gets silly quickly and I think this is one of the fairly obvious and uncontroversial things that can be moved. Its worth mentioning when I maintained a forked version of jquery.couch due to difficulties getting my patches into apache, I started receiving numerous pull requests to that repo, I suggested they be sent to apache but I know that many didnt make it. jquery.couch status --- Key: COUCHDB-1934 URL: https://issues.apache.org/jira/browse/COUCHDB-1934 Project: CouchDB Issue Type: Question Reporter: Alexander Shorin When [~nslater] had proposed to include [jquery.couch.js docs|http://daleharvey.github.io/jquery.couch.js-docs/symbols/] into official CouchDB one I recall old good time when we had discussed Futon.Next project. Suddenly, it was out of official mailing lists, so no references are available, but [~garren], [~dch], [~bigbluehat] and [~ryanramage] were there and our discussion was around jquery vs backbone vs pouchdb. Backbone won. Nowdays, we have Fauxton which doesn't used jquery.couch and based on Backbone. So it seems if we'll replace Futon with him this client library would be left orphan. So that's the question: what is the status of jquery.couch.js? Is it still actual and supported or going to be deprecated? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (COUCHDB-1862) Configuring CORS sucks
Dale Harvey created COUCHDB-1862: Summary: Configuring CORS sucks Key: COUCHDB-1862 URL: https://issues.apache.org/jira/browse/COUCHDB-1862 Project: CouchDB Issue Type: Bug Components: HTTP Interface Reporter: Dale Harvey In general cors configuration is confusing, the original implementation of the couch config is sufficient but I think we should introduce more sensible defaults. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1863) Documentation link should be on top links of front page
Dale Harvey created COUCHDB-1863: Summary: Documentation link should be on top links of front page Key: COUCHDB-1863 URL: https://issues.apache.org/jira/browse/COUCHDB-1863 Project: CouchDB Issue Type: Bug Reporter: Dale Harvey Its about the most important link there and nobody (including me) can find it. Can send in a patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1863) Documentation link should be on top links of front page
[ https://issues.apache.org/jira/browse/COUCHDB-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1863: - Component/s: Website Documentation link should be on top links of front page --- Key: COUCHDB-1863 URL: https://issues.apache.org/jira/browse/COUCHDB-1863 Project: CouchDB Issue Type: Bug Components: Website Reporter: Dale Harvey Its about the most important link there and nobody (including me) can find it. Can send in a patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1863) Documentation link should be on top links of front page
[ https://issues.apache.org/jira/browse/COUCHDB-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720724#comment-13720724 ] Dale Harvey commented on COUCHDB-1863: -- So something needs to go to make space for documentation, my vote would be mailing list. Documentation link should be on top links of front page --- Key: COUCHDB-1863 URL: https://issues.apache.org/jira/browse/COUCHDB-1863 Project: CouchDB Issue Type: Bug Components: Website Reporter: Dale Harvey Its about the most important link there and nobody (including me) can find it. Can send in a patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1863) Documentation link should be on top links of front page
[ https://issues.apache.org/jira/browse/COUCHDB-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720726#comment-13720726 ] Dale Harvey commented on COUCHDB-1863: -- Or somewhat more appropriate, the link to mailing list becomes part of a new section that highlights all the places to go to get help using couchdb, including the documentation, the guide, irc, mailing list etc Documentation link should be on top links of front page --- Key: COUCHDB-1863 URL: https://issues.apache.org/jira/browse/COUCHDB-1863 Project: CouchDB Issue Type: Bug Components: Website Reporter: Dale Harvey Its about the most important link there and nobody (including me) can find it. Can send in a patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1678) Seach in the documentation 404's
Dale Harvey created COUCHDB-1678: Summary: Seach in the documentation 404's Key: COUCHDB-1678 URL: https://issues.apache.org/jira/browse/COUCHDB-1678 Project: CouchDB Issue Type: Bug Components: Documentation Reporter: Dale Harvey Go to docs.couchdb.org (or .com) and do a search, it 404's http://docs.couchdb.com/en/latest/search.html?q=testcheck_keywords=yesarea=default -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1607) cookie_authentication_handler does not properly handle AuthSession signatures starting with : character(s)
[
https://issues.apache.org/jira/browse/COUCHDB-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499581#comment-13499581
]
Dale Harvey commented on COUCHDB-1607:
--
Good debugging, you can use re:split(a:b:c, :, [{return, list}]). although
I would be worried about 1. why its using lists at all, 2. why is it generating
an empty value in the first place?
cookie_authentication_handler does not properly handle AuthSession signatures
starting with : character(s)
Key: COUCHDB-1607
URL: https://issues.apache.org/jira/browse/COUCHDB-1607
Project: CouchDB
Issue Type: Bug
Affects Versions: 1.2
Reporter: Nathan Vander Wilt
Priority: Critical
AuthSession cookies will intermittently break — a user will have a
perfectly valid session, but suddenly after their cookie gets refreshed they
can randomly get logged out for practical purposes.
The cause is that Erlang's `string:tokens` behaviour does act as this code
expects:
https://github.com/apache/couchdb/blob/7d4181346626c0cdb50b44f7e5e33435a8ccae0f/src/couchdb/couch_httpd_auth.erl#L163
https://github.com/apache/couchdb/blob/7d4181346626c0cdb50b44f7e5e33435a8ccae0f/src/couchdb/couch_httpd_auth.erl#L183
After evaluating `[A,B | C] = string:tokens(a:b::c:d).` the value of C is
not `[,c,d]` but rather `[c,d]`. So when rejoined, the signature
becomes c:d instead of the original :c:d!
It appears that using re.split/2 would avoid this problem, but yields a
list/array result containing instead of types, which string:join
does not like. Should be pretty quick fix though for someone who knows just a
bit more of the Erlang way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1487) If-None-Match isnt invalidated by Accept type
Dale Harvey created COUCHDB-1487:
Summary: If-None-Match isnt invalidated by Accept type
Key: COUCHDB-1487
URL: https://issues.apache.org/jira/browse/COUCHDB-1487
Project: CouchDB
Issue Type: Bug
Components: HTTP Interface
Reporter: Dale Harvey
If-None-Match is not invalidated by the Accept header which may vary the
contents of the returned data (making the data cached by the client invalid)
// If-None-Match returns empty body regardless of Accept
$ curl -X GET http://localhost:1234/test_suite_db1/bin_doc2?attachments=true;
-H 'Accept: application/json' -H 'If-None-Match:
2-14688d4a246bd2a4cc390d998a9c5230'
~/src/pouchdb (master)
$ curl -X GET http://localhost:1234/test_suite_db1/bin_doc2?attachments=true;
-H 'If-None-Match: 2-14688d4a246bd2a4cc390d998a9c5230'~/src/pouchdb (master)
// Content differs base on Accept
$ curl -X GET http://localhost:1234/test_suite_db1/bin_doc2?attachments=true;
-H 'Accept:
application/json'{_id:bin_doc2,_rev:2-14688d4a246bd2a4cc390d998a9c5230,_attachments:{foo2.txt:{content_type:text/plain;
charset=UTF-8,revpos:2,digest:md5-oWU+DkMWYcPGKs/F0Lic5A==,data:VGhpcyBpcyBubyBiYXNlNjQgZW5jb2RlZCB0ZXh0},foo.txt:{content_type:text/plain,revpos:1,digest:md5-cCkGbCesb17xjWYNV0GXmg==,data:}}}
~/src/pouchdb (master)
$ curl -X GET http://localhost:1234/test_suite_db1/bin_doc2?attachments=true;
--8b098c9b630fa64a56ba8341b89186e0
content-type: application/json
{_id:bin_doc2,_rev:2-14688d4a246bd2a4cc390d998a9c5230,_attachments:{foo2.txt:{content_type:text/plain;
charset=UTF-8,revpos:2,digest:md5-oWU+DkMWYcPGKs/F0Lic5A==,length:30,follows:true,encoding:gzip,encoded_length:48},foo.txt:{content_type:text/plain,revpos:1,digest:md5-cCkGbCesb17xjWYNV0GXmg==,length:0,follows:true,encoding:gzip,encoded_length:20}}}
--8b098c9b630fa64a56ba8341b89186e0
?
??,V??|T3?Լ?Ԋ??=
--8b098c9b630fa64a56ba8341b89186e0
?
--8b098c9b630fa64a56ba8341b89186e0--
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1286) Cannot replicate with nginx as reverse proxy
Cannot replicate with nginx as reverse proxy Key: COUCHDB-1286 URL: https://issues.apache.org/jira/browse/COUCHDB-1286 Project: CouchDB Issue Type: Bug Components: Replication Affects Versions: 1.2 Reporter: Dale Harvey Replicating between 2 CouchDB instances on 1.2.x branch, one sites behind nginx, a push replication to the one behind nginx fails with the attached log -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1286) Cannot replicate with nginx as reverse proxy
[ https://issues.apache.org/jira/browse/COUCHDB-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1286: - Attachment: repl.log Cannot replicate with nginx as reverse proxy Key: COUCHDB-1286 URL: https://issues.apache.org/jira/browse/COUCHDB-1286 Project: CouchDB Issue Type: Bug Components: Replication Affects Versions: 1.2 Reporter: Dale Harvey Attachments: repl.log Replicating between 2 CouchDB instances on 1.2.x branch, one sites behind nginx, a push replication to the one behind nginx fails with the attached log -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1286) Cannot replicate with nginx as reverse proxy
[ https://issues.apache.org/jira/browse/COUCHDB-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1286: - Attachment: nginx.conf Cannot replicate with nginx as reverse proxy Key: COUCHDB-1286 URL: https://issues.apache.org/jira/browse/COUCHDB-1286 Project: CouchDB Issue Type: Bug Components: Replication Affects Versions: 1.2 Reporter: Dale Harvey Attachments: nginx.conf, repl.log Replicating between 2 CouchDB instances on 1.2.x branch, one sites behind nginx, a push replication to the one behind nginx fails with the attached log -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1286) Cannot replicate with nginx as reverse proxy
[ https://issues.apache.org/jira/browse/COUCHDB-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107547#comment-13107547 ] Dale Harvey commented on COUCHDB-1286: -- Thats quick work, I attached my nginx.conf and can confirm that I dont get it on 1.1.x branch Cannot replicate with nginx as reverse proxy Key: COUCHDB-1286 URL: https://issues.apache.org/jira/browse/COUCHDB-1286 Project: CouchDB Issue Type: Bug Components: Replication Affects Versions: 1.2 Reporter: Dale Harvey Assignee: Filipe Manana Attachments: nginx.conf, repl.log Replicating between 2 CouchDB instances on 1.2.x branch, one sites behind nginx, a push replication to the one behind nginx fails with the attached log -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1286) Cannot replicate with nginx as reverse proxy
[ https://issues.apache.org/jira/browse/COUCHDB-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107550#comment-13107550 ] Dale Harvey commented on COUCHDB-1286: -- I tested the patch against 1.2.x on the local couch, worked perfectly Thanks Filipe Cannot replicate with nginx as reverse proxy Key: COUCHDB-1286 URL: https://issues.apache.org/jira/browse/COUCHDB-1286 Project: CouchDB Issue Type: Bug Components: Replication Affects Versions: 1.2 Reporter: Dale Harvey Assignee: Filipe Manana Attachments: couchdb-1286_bulk_docs.patch, nginx.conf, repl.log Replicating between 2 CouchDB instances on 1.2.x branch, one sites behind nginx, a push replication to the one behind nginx fails with the attached log -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1180) Add deferred support to jquery.couch.js
Add deferred support to jquery.couch.js --- Key: COUCHDB-1180 URL: https://issues.apache.org/jira/browse/COUCHDB-1180 Project: CouchDB Issue Type: Improvement Components: Infrastructure Reporter: Dale Harvey Priority: Minor the recent releases of jquery have included deferreds which are an improved api for handling asynchronous callbacks, it is backwards compatible with the current use and just requires access to to the currently unused returned values from $.ajax this patch adds access to the returned jqxhr objects in the places that make sense, it should not affect anything else -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1180) Add deferred support to jquery.couch.js
[ https://issues.apache.org/jira/browse/COUCHDB-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1180: - Attachment: deferreds.patch Add deferred support to jquery.couch.js --- Key: COUCHDB-1180 URL: https://issues.apache.org/jira/browse/COUCHDB-1180 Project: CouchDB Issue Type: Improvement Components: Infrastructure Reporter: Dale Harvey Priority: Minor Attachments: deferreds.patch the recent releases of jquery have included deferreds which are an improved api for handling asynchronous callbacks, it is backwards compatible with the current use and just requires access to to the currently unused returned values from $.ajax this patch adds access to the returned jqxhr objects in the places that make sense, it should not affect anything else -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1158) Log server crashes when view contains unicode and log level is set to debug
[ https://issues.apache.org/jira/browse/COUCHDB-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13031662#comment-13031662 ] Dale Harvey commented on COUCHDB-1158: -- Awesome Filipe, confirmed that fixes it for me Log server crashes when view contains unicode and log level is set to debug --- Key: COUCHDB-1158 URL: https://issues.apache.org/jira/browse/COUCHDB-1158 Project: CouchDB Issue Type: Bug Components: Database Core Environment: OSX, Built from Git - 1.2.0a8a37632-git Reporter: Dale Harvey Attachments: couch_log_unicode.patch When a document contains a simple unicode escaped character and the log level is set to debug, running any view over the document crashes the log server http://pastebin.me/883abdacdb3feca6b4ed965413091458 will investigate further -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1156) Futon shows apache license when performing unauthorised operations
Futon shows apache license when performing unauthorised operations -- Key: COUCHDB-1156 URL: https://issues.apache.org/jira/browse/COUCHDB-1156 Project: CouchDB Issue Type: Bug Components: Futon Reporter: Dale Harvey Priority: Minor Attachments: accept-json.patch If you create / delete a database you are not allowed to, futon will make an extra request and show the code to the index page in a dialog as the request is forwarded to a login page, this is because jquery.couch.js doesnt specify the accept headers so couchdb assumed the request is being made from a using in the browser and not a http client -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1156) Futon shows apache license when performing unauthorised operations
[ https://issues.apache.org/jira/browse/COUCHDB-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1156: - Attachment: accept-json.patch Futon shows apache license when performing unauthorised operations -- Key: COUCHDB-1156 URL: https://issues.apache.org/jira/browse/COUCHDB-1156 Project: CouchDB Issue Type: Bug Components: Futon Reporter: Dale Harvey Priority: Minor Attachments: accept-json.patch If you create / delete a database you are not allowed to, futon will make an extra request and show the code to the index page in a dialog as the request is forwarded to a login page, this is because jquery.couch.js doesnt specify the accept headers so couchdb assumed the request is being made from a using in the browser and not a http client -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1156) Futon shows apache license when performing unauthorised operations
[ https://issues.apache.org/jira/browse/COUCHDB-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13031480#comment-13031480 ] Dale Harvey commented on COUCHDB-1156: -- A screenshot of the issue http://dropup.net/4hwjez-71c54c.png.html Futon shows apache license when performing unauthorised operations -- Key: COUCHDB-1156 URL: https://issues.apache.org/jira/browse/COUCHDB-1156 Project: CouchDB Issue Type: Bug Components: Futon Reporter: Dale Harvey Priority: Minor Attachments: accept-json.patch If you create / delete a database you are not allowed to, futon will make an extra request and show the code to the index page in a dialog as the request is forwarded to a login page, this is because jquery.couch.js doesnt specify the accept headers so couchdb assumed the request is being made from a using in the browser and not a http client -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1158) Log server crashes when view contains unicode and log level is set to debug
Log server crashes when view contains unicode and log level is set to debug --- Key: COUCHDB-1158 URL: https://issues.apache.org/jira/browse/COUCHDB-1158 Project: CouchDB Issue Type: Bug Components: Database Core Environment: OSX, Built from Git - 1.2.0a8a37632-git Reporter: Dale Harvey When a document contains a simple unicode escaped character and the log level is set to debug, running any view over the document crashes the log server http://pastebin.me/883abdacdb3feca6b4ed965413091458 will investigate further -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1131) Port Futon2 local replication target work to Futon
[ https://issues.apache.org/jira/browse/COUCHDB-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022367#comment-13022367 ] Dale Harvey commented on COUCHDB-1131: -- +1 on this, currently its a nightmare to replicate to databases that dont exist Port Futon2 local replication target work to Futon -- Key: COUCHDB-1131 URL: https://issues.apache.org/jira/browse/COUCHDB-1131 Project: CouchDB Issue Type: New Feature Components: Futon Reporter: Sam Bisbee Priority: Minor Attachments: 0001-Adding-jQuery-UI-1.8.11-JS-and-CSS-for-just-the-auto.patch, 0002-Replacing-replication-s-local-target-dropdown-with-a.patch, 0003-NOTICE-and-LICENSE-updates-for-inclusion-of-jQuery-U.patch Futon2 currently has a patch that makes the replication target into a text input, using jQuery UI's autocomplete widget to still provide the all databases functionality. If the database doesn't exist, then the user is prompted to see if they want it created with a JS confirm() prompt. If they do, then the create_target replication option is set to true. This will be a port of this Futon2 pull request: https://github.com/BigBlueHat/couchdb/pull/1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1133) Fix opacity on favicon
Fix opacity on favicon -- Key: COUCHDB-1133 URL: https://issues.apache.org/jira/browse/COUCHDB-1133 Project: CouchDB Issue Type: Improvement Components: Futon Reporter: Dale Harvey Priority: Trivial Fix the opacity on the favicon so it doesnt look awkward on non white browser chrome -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1090) jquery.couch.js enforces cache option
[
https://issues.apache.org/jira/browse/COUCHDB-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13020719#comment-13020719
]
Dale Harvey commented on COUCHDB-1090:
--
the reason I took it out completely is that it already is an option
$.ajaxSetup({
cache: false
});
and it can be passed through the options as long as it isnt set explicity, I
would say its up to jquery to specify sensible defaults and if futon wants no
cache in ie it can add it itself, I am happy either way though as long as the
developer can specify
jquery.couch.js enforces cache option
-
Key: COUCHDB-1090
URL: https://issues.apache.org/jira/browse/COUCHDB-1090
Project: CouchDB
Issue Type: Bug
Components: Infrastructure
Reporter: Dale Harvey
Priority: Trivial
Attachments: cache.patch
jquery.couch.js explicitly sets a cache, preventing the programmer from being
able to set it
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1116) Documentation for jquery.couch.js
[ https://issues.apache.org/jira/browse/COUCHDB-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015741#comment-13015741 ] Dale Harvey commented on COUCHDB-1116: -- Not a whole lot I put my stuff up at https://github.com/daleharvey/jquery.couch.js-docs the library used is http://code.google.com/p/jsdoc-toolkit/ which is MIT it means a java dependancy, and a few extra source files but not much impact, not sure where would be sensible in the tree to keep this stuff, but give me a directory and ill do the autofoo for it Documentation for jquery.couch.js - Key: COUCHDB-1116 URL: https://issues.apache.org/jira/browse/COUCHDB-1116 Project: CouchDB Issue Type: Improvement Components: Documentation Reporter: Dale Harvey Priority: Minor Attachments: jquery.couch.js-docs.patch, jquery.couch.js-docs.patch Creating documentation for jquery.couch.js -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1116) Documentation for jquery.couch.js
[ https://issues.apache.org/jira/browse/COUCHDB-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1116: - Attachment: jquery.couch.js-docs.patch Documentation for jquery.couch.js - Key: COUCHDB-1116 URL: https://issues.apache.org/jira/browse/COUCHDB-1116 Project: CouchDB Issue Type: Improvement Components: Documentation Reporter: Dale Harvey Priority: Minor Attachments: jquery.couch.js-docs.patch, jquery.couch.js-docs.patch Creating documentation for jquery.couch.js -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1116) Documentation for jquery.couch.js
[ https://issues.apache.org/jira/browse/COUCHDB-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1116: - Attachment: jquery.couch.js-docs.patch Documentation for jquery.couch.js - Key: COUCHDB-1116 URL: https://issues.apache.org/jira/browse/COUCHDB-1116 Project: CouchDB Issue Type: Improvement Components: Documentation Reporter: Dale Harvey Priority: Minor Attachments: jquery.couch.js-docs.patch Creating documentation for jquery.couch.js -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1116) Documentation for jquery.couch.js
Documentation for jquery.couch.js - Key: COUCHDB-1116 URL: https://issues.apache.org/jira/browse/COUCHDB-1116 Project: CouchDB Issue Type: Improvement Components: Documentation Reporter: Dale Harvey Priority: Minor Attachments: jquery.couch.js-docs.patch Creating documentation for jquery.couch.js -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1112) Allow running individual javascript tests
Allow running individual javascript tests - Key: COUCHDB-1112 URL: https://issues.apache.org/jira/browse/COUCHDB-1112 Project: CouchDB Issue Type: New Feature Components: Test Suite Reporter: Dale Harvey Priority: Minor Attachments: run.patch Allow people invoking the javascript test suite to add the path of a specific test to run -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1112) Allow running individual javascript tests
[ https://issues.apache.org/jira/browse/COUCHDB-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1112: - Attachment: run.patch Allow running individual javascript tests - Key: COUCHDB-1112 URL: https://issues.apache.org/jira/browse/COUCHDB-1112 Project: CouchDB Issue Type: New Feature Components: Test Suite Reporter: Dale Harvey Priority: Minor Attachments: run.patch Allow people invoking the javascript test suite to add the path of a specific test to run -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1112) Allow running individual javascript tests
[ https://issues.apache.org/jira/browse/COUCHDB-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1112: - Attachment: run.patch Allow running individual javascript tests - Key: COUCHDB-1112 URL: https://issues.apache.org/jira/browse/COUCHDB-1112 Project: CouchDB Issue Type: New Feature Components: Test Suite Reporter: Dale Harvey Priority: Minor Attachments: run.patch, run.patch, run.patch Allow people invoking the javascript test suite to add the path of a specific test to run -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1112) Allow running individual javascript tests
[ https://issues.apache.org/jira/browse/COUCHDB-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1112: - Attachment: run.patch Allow running individual javascript tests - Key: COUCHDB-1112 URL: https://issues.apache.org/jira/browse/COUCHDB-1112 Project: CouchDB Issue Type: New Feature Components: Test Suite Reporter: Dale Harvey Priority: Minor Attachments: run.patch, run.patch, run.patch Allow people invoking the javascript test suite to add the path of a specific test to run -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (COUCHDB-1089) Let anonymous users access _active_tasks for view generation estimates
[ https://issues.apache.org/jira/browse/COUCHDB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006106#comment-13006106 ] Dale Harvey commented on COUCHDB-1089: -- Caolan, do you mean expose the filter options on the (remote) target db that you are replicating too? I can see where that can be handy but I do think it sounds dangerous. Kowsik, if require_valid_user does what I think it does then it wont be affected, a private install will stay private. Filipe, the futon replication page is ok enough as a db admins tool, we are talking about providing a ui to replication for end users of applications built with couch (more specifically in my case, couchapps), right now its impossible for me to have continuous replication for my mobile apps because the user the app runs as is not an admin, I can start continous replication tasks but cant inspect whether they are running or not. Let anonymous users access _active_tasks for view generation estimates -- Key: COUCHDB-1089 URL: https://issues.apache.org/jira/browse/COUCHDB-1089 Project: CouchDB Issue Type: Improvement Components: HTTP Interface, JavaScript View Server Reporter: max ogden Priority: Minor Labels: http, view Original Estimate: 3h Remaining Estimate: 3h Currently you have to be a database administrator to access _active_tasks. For UX purposes I would like to allow anyone to see view generation statuses, preferably on a per database level. This solves the problem of the first user to generate a view that then receives no time estimate as to when their process will be completed. I can't think of an application use case for making replication data public. I spoke with Volker Mische about the implementation details on this issue and he asserted after a code dive that it appears achievable, though the innards of the view status code were not familiar to him. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (COUCHDB-1089) Let anonymous users access _active_tasks for view generation estimates
[ https://issues.apache.org/jira/browse/COUCHDB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13005985#comment-13005985 ] Dale Harvey commented on COUCHDB-1089: -- I have also really wanted this I found it extremely strange that instantiating a replication was possible without admin credentials but its never possible to see its status, im happy to provide a patch if the feature is agreeable Let anonymous users access _active_tasks for view generation estimates -- Key: COUCHDB-1089 URL: https://issues.apache.org/jira/browse/COUCHDB-1089 Project: CouchDB Issue Type: Improvement Components: HTTP Interface, JavaScript View Server Reporter: max ogden Priority: Minor Labels: http, view Original Estimate: 3h Remaining Estimate: 3h Currently you have to be a database administrator to access _active_tasks. For UX purposes I would like to allow anyone to see view generation statuses, preferably on a per database level. This solves the problem of the first user to generate a view that then receives no time estimate as to when their process will be completed. I can't think of an application use case for making replication data public. I spoke with Volker Mische about the implementation details on this issue and he asserted after a code dive that it appears achievable, though the innards of the view status code were not familiar to him. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (COUCHDB-1090) jquery.couch.js enforces cache option
jquery.couch.js enforces cache option - Key: COUCHDB-1090 URL: https://issues.apache.org/jira/browse/COUCHDB-1090 Project: CouchDB Issue Type: Bug Components: Infrastructure Reporter: Dale Harvey Priority: Trivial jquery.couch.js explicitly sets a cache, preventing the programmer from being able to set it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (COUCHDB-1090) jquery.couch.js enforces cache option
[ https://issues.apache.org/jira/browse/COUCHDB-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1090: - Attachment: cache.patch jquery.couch.js enforces cache option - Key: COUCHDB-1090 URL: https://issues.apache.org/jira/browse/COUCHDB-1090 Project: CouchDB Issue Type: Bug Components: Infrastructure Reporter: Dale Harvey Priority: Trivial Attachments: cache.patch jquery.couch.js explicitly sets a cache, preventing the programmer from being able to set it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (COUCHDB-943) Reformat comments with type specs and @doc directives
[ https://issues.apache.org/jira/browse/COUCHDB-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey closed COUCHDB-943. --- Resolution: Not A Problem Too old too apply, better done while developing anyway Reformat comments with type specs and @doc directives - Key: COUCHDB-943 URL: https://issues.apache.org/jira/browse/COUCHDB-943 Project: CouchDB Issue Type: Bug Components: Documentation Reporter: Dale Harvey Priority: Minor Attachments: format_comments.patch Start introducing consistent use of @doc directives and type specifications, makes it easier to use dialyzer and ensures the comments show up in generated documentation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932476#action_12932476 ] Dale Harvey commented on COUCHDB-912: - It only allows attachments to design docs, but yeh its not a solution I particularly like a flag on the design doc I would much prefer, Its what I mentioned http://comments.gmane.org/gmane.comp.db.couchdb.user/10681, forgot who pointed me towards implementing it as a config option but I figured I would do it quickly just so I could understand the implications.Hinnerk Haardts point out that with a flag on the design doc you can have seperate login / business logic design docs which would work fine. is reading the database on every request to a design document ok / anyway to cache it nicely? I dont want this particular patch to go in, I just wanted to post it to mark it as a priority because without it private couchapps are very very crippled. Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932075#action_12932075 ] Dale Harvey commented on COUCHDB-912: - Thanks for the advice Filipe, very helpful made those changes (the javascript is 2 space indented, just was a bug in one of the declarations which is fixed) I can merge the test into another suite if anyone would prefer that, just cleaner in a seperate one for now as it does a run_on_modified_server (that could be taken out as I would propose for this to be the default, I wasnt sure about the best practice for that though) Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-912: Attachment: anon.patch Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-912: Attachment: (was: anon.patch) Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COUCHDB-943) Reformat comments with type specs and @doc directives
Reformat comments with type specs and @doc directives - Key: COUCHDB-943 URL: https://issues.apache.org/jira/browse/COUCHDB-943 Project: CouchDB Issue Type: Bug Components: Documentation Reporter: Dale Harvey Priority: Minor Attachments: format_comments.patch Start introducing consistent use of @doc directives and type specifications, makes it easier to use dialyzer and ensures the comments show up in generated documentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-943) Reformat comments with type specs and @doc directives
[ https://issues.apache.org/jira/browse/COUCHDB-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-943: Attachment: format_comments.patch Reformat comments with type specs and @doc directives - Key: COUCHDB-943 URL: https://issues.apache.org/jira/browse/COUCHDB-943 Project: CouchDB Issue Type: Bug Components: Documentation Reporter: Dale Harvey Priority: Minor Attachments: format_comments.patch Start introducing consistent use of @doc directives and type specifications, makes it easier to use dialyzer and ensures the comments show up in generated documentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-912: Attachment: attachment_permissions.js anon.patch Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch, anon.patch, attachment_permissions.js Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-912: Attachment: (was: anon.patch) Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch, anon.patch, attachment_permissions.js Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-912: Attachment: (was: anon.patch) Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch, attachment_permissions.js Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12929918#action_12929918 ] Dale Harvey commented on COUCHDB-912: - I have redone the patch thanks to Filipes feedback, its much cleaner now, thanks. I have is_ddoc_attachment() which reproduces some routing logic that is spread throughout the entire couch_httpd_db.erl, I would prefer that the logic only done once, and it would be possible to workaround by reopening the database in various places. However that patch is far more intrusive. The right 'fix' is to decouple the routing from the actual logic, and paul mentioned experimenting with a webmachine / other routing layer so I think its ok to make changes like these and defer workarounds until a nicer routing layer is in place. (but if you want the open db patch, then just say) Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch, attachment_permissions.js Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12928971#action_12928971 ] Dale Harvey commented on COUCHDB-912: - Thats awesome feedback, cheers, yeh was in the middle of writing the tests, just put the patch up before so I could get comments like this :) Will repatch and send in the tests later today, thanks. Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch, anon.patch Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-912: Attachment: anon.patch Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12928630#action_12928630 ] Dale Harvey commented on COUCHDB-912: - This patch adds a configuration option that allows users to make attachments to design documents available to anonymous users on private database. Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-912: Attachment: anon.patch Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch, anon.patch Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
[ https://issues.apache.org/jira/browse/COUCHDB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12928903#action_12928903 ] Dale Harvey commented on COUCHDB-912: - Added a new patch that caches it. Personally I think httpd.erl and forward is a tad messy and would be best leave it uncached for now and if needed do a seperate refactor to make that caching more convenient / tidier. (Used an opaque dict so the next thing that needs cached doesnt add another parameter) Will write the tests for it now Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Attachments: anon.patch, anon.patch Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COUCHDB-933) Remove Dependancy on Inets
Remove Dependancy on Inets -- Key: COUCHDB-933 URL: https://issues.apache.org/jira/browse/COUCHDB-933 Project: CouchDB Issue Type: Improvement Components: Infrastructure Reporter: Dale Harvey Priority: Minor Inets is not used internally, but is started by the application and is also used in the etap tests, switch out all uses of inets to ibrowse -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-933) Remove Dependancy on Inets
[ https://issues.apache.org/jira/browse/COUCHDB-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-933: Attachment: inets.patch Remove Dependancy on Inets -- Key: COUCHDB-933 URL: https://issues.apache.org/jira/browse/COUCHDB-933 Project: CouchDB Issue Type: Improvement Components: Infrastructure Reporter: Dale Harvey Priority: Minor Attachments: inets.patch Inets is not used internally, but is started by the application and is also used in the etap tests, switch out all uses of inets to ibrowse -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-933) Remove Dependancy on Inets
[ https://issues.apache.org/jira/browse/COUCHDB-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-933: Attachment: inets.patch Remove Dependancy on Inets -- Key: COUCHDB-933 URL: https://issues.apache.org/jira/browse/COUCHDB-933 Project: CouchDB Issue Type: Improvement Components: Infrastructure Reporter: Dale Harvey Priority: Minor Attachments: inets.patch, inets.patch Inets is not used internally, but is started by the application and is also used in the etap tests, switch out all uses of inets to ibrowse -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-933) Remove Dependancy on Inets
[ https://issues.apache.org/jira/browse/COUCHDB-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-933: Attachment: (was: inets.patch) Remove Dependancy on Inets -- Key: COUCHDB-933 URL: https://issues.apache.org/jira/browse/COUCHDB-933 Project: CouchDB Issue Type: Improvement Components: Infrastructure Reporter: Dale Harvey Priority: Minor Attachments: anon.patch Inets is not used internally, but is started by the application and is also used in the etap tests, switch out all uses of inets to ibrowse -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-933) Remove Dependancy on Inets
[ https://issues.apache.org/jira/browse/COUCHDB-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-933: Attachment: anon.patch Remove Dependancy on Inets -- Key: COUCHDB-933 URL: https://issues.apache.org/jira/browse/COUCHDB-933 Project: CouchDB Issue Type: Improvement Components: Infrastructure Reporter: Dale Harvey Priority: Minor Attachments: anon.patch Inets is not used internally, but is started by the application and is also used in the etap tests, switch out all uses of inets to ibrowse -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-933) Remove Dependancy on Inets
[ https://issues.apache.org/jira/browse/COUCHDB-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-933: Attachment: (was: inets.patch) Remove Dependancy on Inets -- Key: COUCHDB-933 URL: https://issues.apache.org/jira/browse/COUCHDB-933 Project: CouchDB Issue Type: Improvement Components: Infrastructure Reporter: Dale Harvey Priority: Minor Attachments: anon.patch Inets is not used internally, but is started by the application and is also used in the etap tests, switch out all uses of inets to ibrowse -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-933) Remove Dependancy on Inets
[ https://issues.apache.org/jira/browse/COUCHDB-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12928116#action_12928116 ] Dale Harvey commented on COUCHDB-933: - Yeh you are right, I amended the patch so it only stops couch manually starting inets on boot, plus switched all the tests from inets to ibrowse, which lets us include inets as a library but not require it to be started to run couch or the tests. Remove Dependancy on Inets -- Key: COUCHDB-933 URL: https://issues.apache.org/jira/browse/COUCHDB-933 Project: CouchDB Issue Type: Improvement Components: Infrastructure Reporter: Dale Harvey Priority: Minor Attachments: anon.patch Inets is not used internally, but is started by the application and is also used in the etap tests, switch out all uses of inets to ibrowse -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COUCHDB-932) create_target CreateDB PUT request fails
create_target CreateDB PUT request fails Key: COUCHDB-932 URL: https://issues.apache.org/jira/browse/COUCHDB-932 Project: CouchDB Issue Type: Bug Components: Replication Environment: On a Mobile Broadband Connection Reporter: Dale Harvey Some proxies (for mobile broadband providers) require Content-Length to set for all PUT requests -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-932) create_target CreateDB PUT request fails
[ https://issues.apache.org/jira/browse/COUCHDB-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-932: Attachment: anon.patch create_target CreateDB PUT request fails Key: COUCHDB-932 URL: https://issues.apache.org/jira/browse/COUCHDB-932 Project: CouchDB Issue Type: Bug Components: Replication Environment: On a Mobile Broadband Connection Reporter: Dale Harvey Attachments: anon.patch Some proxies (for mobile broadband providers) require Content-Length to set for all PUT requests -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COUCHDB-912) Anonymous Access to Design Docs on private DB's
Anonymous Access to Design Docs on private DB's --- Key: COUCHDB-912 URL: https://issues.apache.org/jira/browse/COUCHDB-912 Project: CouchDB Issue Type: New Feature Components: HTTP Interface Reporter: Dale Harvey Right now people need to go through futon in order to login to couchapps running on private databases, this is a pretty big limitation on the type of couchapps that can be built Propose adding the ability for users to flag the design docs as readable for anonymous users, could be implemented though an attribute on the design doc? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COUCHDB-896) window.name set stalls futon
window.name set stalls futon Key: COUCHDB-896 URL: https://issues.apache.org/jira/browse/COUCHDB-896 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.2 Environment: Firefox 3.6 on OSX Leapord Reporter: Dale Harvey Priority: Minor Occasionally firefox will set window.name to true which causes futon to stall and not function in any way. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-896) window.name set stalls futon
[ https://issues.apache.org/jira/browse/COUCHDB-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-896: Attachment: couchdb-896.patch Fix for reported issue, its pretty trivial window.name set stalls futon Key: COUCHDB-896 URL: https://issues.apache.org/jira/browse/COUCHDB-896 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.2 Environment: Firefox 3.6 on OSX Leapord Reporter: Dale Harvey Priority: Minor Attachments: couchdb-896.patch Original Estimate: 0.03h Remaining Estimate: 0.03h Occasionally firefox will set window.name to true which causes futon to stall and not function in any way. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-896) window.name set stalls futon
[ https://issues.apache.org/jira/browse/COUCHDB-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-896: Attachment: (was: couchdb-896.patch) window.name set stalls futon Key: COUCHDB-896 URL: https://issues.apache.org/jira/browse/COUCHDB-896 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.2 Environment: Firefox 3.6 on OSX Leapord Reporter: Dale Harvey Priority: Minor Original Estimate: 0.03h Remaining Estimate: 0.03h Occasionally firefox will set window.name to true which causes futon to stall and not function in any way. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-896) window.name set stalls futon
[ https://issues.apache.org/jira/browse/COUCHDB-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-896: Attachment: couchdb-896.patch Updated patch, fixed for all access to window.name object window.name set stalls futon Key: COUCHDB-896 URL: https://issues.apache.org/jira/browse/COUCHDB-896 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.2 Environment: Firefox 3.6 on OSX Leapord Reporter: Dale Harvey Priority: Minor Attachments: couchdb-896.patch Original Estimate: 0.03h Remaining Estimate: 0.03h Occasionally firefox will set window.name to true which causes futon to stall and not function in any way. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
