[GitHub] couchdb-fauxton pull request: (Another) fix for flaky nightwatch t...
Github user asfgit closed the pull request at: https://github.com/apache/couchdb-fauxton/pull/282 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Returns if promise is undefined
Github user robertkowalski commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/284#issuecomment-75353452 When can a promise be undefined and why is it caused? What error does it fix? Can you also write that down in the commit message? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Returns if promise is undefined
GitHub user michellephung opened a pull request: https://github.com/apache/couchdb-fauxton/pull/284 Returns if promise is undefined You can merge this pull request into a Git repository by running: $ git pull https://github.com/michellephung/couchdb-fauxton return-undefined-promises Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/284.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #284 commit 2867e5b577748ba2ad69567999c5654b525c7cd9 Author: michelleph...@gmail.com Date: 2015-02-21T03:08:55Z Returns if promise is undefined --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Change new View Editor URLs to use F...
GitHub user michellephung opened a pull request: https://github.com/apache/couchdb-fauxton/pull/283 Change new View Editor URLs to use FauxtonAPI.urls() You can merge this pull request into a Git repository by running: $ git pull https://github.com/michellephung/couchdb-fauxton center-urls-copy Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/283.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #283 commit 753f4b9bd340a8770acff6d776f360a6cc4e8d1a Author: michelleph...@gmail.com Date: 2015-02-21T03:00:14Z Change new View Editor URLs to use FauxtonAPI.urls() --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-2191) Please consider including couchperuser in core
[
https://issues.apache.org/jira/browse/COUCHDB-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329444#comment-14329444
]
Bob Ippolito commented on COUCHDB-2191:
---
I'm happy to contribute the code (and sign away copyright, contributor
agreement, etc.), but I would not like to be responsible for maintenance of it.
The good news is that I did end up writing end-to-end integration tests, so it
shouldn't be a huge burden for whoever takes it on.
https://github.com/etrepum/couchperuser/blob/master/end-to-end-test.sh
> Please consider including couchperuser in core
> --
>
> Key: COUCHDB-2191
> URL: https://issues.apache.org/jira/browse/COUCHDB-2191
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
>Reporter: Nolan Lawson
>
> I would love to be able to use CouchDB as the exclusive backend for all my
> webapps. The {{_users}} database with the automatic password salting/hashing
> and session cookies is brilliant, and saves a lot of developer effort while
> still ensuring I don't shoot myself in the foot trying to implement password
> security.
> However, without creating a database per user, it's impossible to silo user
> data in any way other than through {{validate_doc_update}} - i.e. every user
> can see everybody else's data, but they can only write to theirs. This use
> case does exist (e.g. Twitter), but it's much less common than the case where
> users can only read/write their own data.
> The plugin ecosystem is great and all, and I totally understand not wanting
> to include the kitchen sink in Couch core, but I strongly feel
> [couchperuser|https://github.com/etrepum/couchperuser] (or something like it)
> should be a checkbox I can tick in the Couch config, rather than a plugin I
> have to install manually. It's just too common of a use case in typical
> webapps.
> Some background: this was prompted by a [discussion in
> PouchDB|https://github.com/daleharvey/pouchdb/issues/1575]; Dale has written
> a fine solution in
> [couch-persona|https://github.com/daleharvey/couch-persona], but I really
> think the "why Pouch/Couch?" story would be more compelling if you could do
> it in pure Couch without an extra server process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (COUCHDB-2602) delayed deletion as safety net
[ https://issues.apache.org/jira/browse/COUCHDB-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2602: - Fix Version/s: (was: 2.0.0) 2.1 > delayed deletion as safety net > -- > > Key: COUCHDB-2602 > URL: https://issues.apache.org/jira/browse/COUCHDB-2602 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Database Core >Affects Versions: 2.1 >Reporter: Robert Kowalski > Fix For: 2.1 > > > Delay deletion as a safety net for users. > Make the delay configurable -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2601) Config section - remove handler from chttpd
[ https://issues.apache.org/jira/browse/COUCHDB-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2601: - Fix Version/s: 2.0.0 > Config section - remove handler from chttpd > --- > > Key: COUCHDB-2601 > URL: https://issues.apache.org/jira/browse/COUCHDB-2601 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Database Core, Fauxton >Reporter: Robert Kowalski >Assignee: Robert Kowalski >Priority: Blocker > Fix For: 2.0.0 > > > if Fauxton gets a 404 we are not using the backdoor port which still > supports `/_config` - this also solves the problem if user are using curl and > try to change configuration on a clustered CouchDB behind a LB -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2603) set q/n parameters on creation of a database
[ https://issues.apache.org/jira/browse/COUCHDB-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2603: - Fix Version/s: (was: 2.0.0) 2.1 > set q/n parameters on creation of a database > > > Key: COUCHDB-2603 > URL: https://issues.apache.org/jira/browse/COUCHDB-2603 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Fauxton >Affects Versions: 2.1 >Reporter: Robert Kowalski > Fix For: 2.1 > > > set q/n parameters on creation of a database. Inform the user if the values > do not make sense (q < 1000 and warn if n == 1 because of possible data > loss). > Make it possible to select nodes which have space left (/_stats - disk usage > percentage) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2597) Release: make targets
[ https://issues.apache.org/jira/browse/COUCHDB-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2597: - Fix Version/s: 2.0.0 > Release: make targets > - > > Key: COUCHDB-2597 > URL: https://issues.apache.org/jira/browse/COUCHDB-2597 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Build System >Reporter: Robert Kowalski >Assignee: Jan Lehnardt >Priority: Blocker > Fix For: 2.0.0 > > > make dist and make docs are still missing for 2.0. Additionaly the Thanks.in > file that was generated by autotools when preparing a release must be readded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2596) Debian Package
[ https://issues.apache.org/jira/browse/COUCHDB-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2596: - Fix Version/s: 2.0.0 > Debian Package > -- > > Key: COUCHDB-2596 > URL: https://issues.apache.org/jira/browse/COUCHDB-2596 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Build System >Reporter: Robert Kowalski >Priority: Blocker > Fix For: 2.0.0 > > > Provide an unofficial debian package for 2.0 which will raise adoption -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2595) Packaging/Release: tarball
[ https://issues.apache.org/jira/browse/COUCHDB-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2595: - Fix Version/s: 2.0.0 > Packaging/Release: tarball > -- > > Key: COUCHDB-2595 > URL: https://issues.apache.org/jira/browse/COUCHDB-2595 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Build System >Reporter: Robert Kowalski >Assignee: Jan Lehnardt >Priority: Blocker > Fix For: 2.0.0 > > > We have to create a tarball for the release of 2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2603) set q/n parameters on creation of a database
[ https://issues.apache.org/jira/browse/COUCHDB-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2603: - Fix Version/s: 2.0.0 > set q/n parameters on creation of a database > > > Key: COUCHDB-2603 > URL: https://issues.apache.org/jira/browse/COUCHDB-2603 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Fauxton >Affects Versions: 2.1 >Reporter: Robert Kowalski > Fix For: 2.0.0 > > > set q/n parameters on creation of a database. Inform the user if the values > do not make sense (q < 1000 and warn if n == 1 because of possible data > loss). > Make it possible to select nodes which have space left (/_stats - disk usage > percentage) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2602) delayed deletion as safety net
[ https://issues.apache.org/jira/browse/COUCHDB-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2602: - Fix Version/s: 2.0.0 > delayed deletion as safety net > -- > > Key: COUCHDB-2602 > URL: https://issues.apache.org/jira/browse/COUCHDB-2602 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Database Core >Affects Versions: 2.1 >Reporter: Robert Kowalski > Fix For: 2.0.0 > > > Delay deletion as a safety net for users. > Make the delay configurable -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2600) Notify user that compaction just works on the backdoor ports
[ https://issues.apache.org/jira/browse/COUCHDB-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2600: - Fix Version/s: 2.0.0 > Notify user that compaction just works on the backdoor ports > > > Key: COUCHDB-2600 > URL: https://issues.apache.org/jira/browse/COUCHDB-2600 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Robert Kowalski >Assignee: Robert Kowalski >Priority: Blocker > Fix For: 2.0.0 > > > display message if user is accessing over chttpd on 5984 that points the user > in the right direction (5986, backdoor port) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2598) Finish setup wizard
[ https://issues.apache.org/jira/browse/COUCHDB-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2598: - Fix Version/s: 2.0.0 > Finish setup wizard > --- > > Key: COUCHDB-2598 > URL: https://issues.apache.org/jira/browse/COUCHDB-2598 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Database Core, Fauxton >Reporter: Robert Kowalski >Assignee: Robert Kowalski >Priority: Blocker > Fix For: 2.0.0 > > > The wizard to make setup easy has to get finished. It should warn users if > they have an old local db and want to create a cluster. We want to have a > button to replicated the local db to the cluster. The button will be at the > 5986 backdoor ports. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2599) Just display admin section on backdoor port
[ https://issues.apache.org/jira/browse/COUCHDB-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2599: - Fix Version/s: 2.0.0 > Just display admin section on backdoor port > --- > > Key: COUCHDB-2599 > URL: https://issues.apache.org/jira/browse/COUCHDB-2599 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Robert Kowalski >Assignee: Robert Kowalski >Priority: Blocker > Fix For: 2.0.0 > > > remove section to create admins & to change their password if Fauxton is > accessed through an LB - just display that one on the backdoor ports -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2594) Single node mode: remove warning
[ https://issues.apache.org/jira/browse/COUCHDB-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2594: - Fix Version/s: 2.0.0 > Single node mode: remove warning > > > Key: COUCHDB-2594 > URL: https://issues.apache.org/jira/browse/COUCHDB-2594 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Database Core >Reporter: Robert Kowalski >Priority: Blocker > Fix For: 2.0.0 > > > we have to remove a warning that is sent as response if the node is not > joined into a multi-node cluster and has no membership -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2593) Double check that we do not delete 1.x databases when starting to use 2.0
[ https://issues.apache.org/jira/browse/COUCHDB-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2593: - Fix Version/s: 2.0.0 > Double check that we do not delete 1.x databases when starting to use 2.0 > -- > > Key: COUCHDB-2593 > URL: https://issues.apache.org/jira/browse/COUCHDB-2593 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Robert Kowalski >Priority: Blocker > Fix For: 2.0.0 > > > Double check that we do not delete 1.x databases when starting to use 2.0 - > the 1.6 DB should be at 5986 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2592) Migration guides from 1.6 to 2.0
[ https://issues.apache.org/jira/browse/COUCHDB-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2592: - Fix Version/s: 2.0.0 > Migration guides from 1.6 to 2.0 > > > Key: COUCHDB-2592 > URL: https://issues.apache.org/jira/browse/COUCHDB-2592 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: BigCouch, Documentation >Reporter: Robert Kowalski >Priority: Blocker > Fix For: 2.0.0 > > > - How to start with 2.0 using the console if you used 1.6 before > - Mention the Fauxton wizard which hopefully needs no manual -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2591) Documentation
[ https://issues.apache.org/jira/browse/COUCHDB-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2591: - Fix Version/s: 2.0.0 > Documentation > - > > Key: COUCHDB-2591 > URL: https://issues.apache.org/jira/browse/COUCHDB-2591 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: BigCouch, Documentation >Reporter: Robert Kowalski >Priority: Blocker > Fix For: 2.0.0 > > > people would like to use 2.0 but they don’t know how to maintain it (e.g. > adding and rebalancing nodes, general setup) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-fauxton pull request: try to fix flaky test
Github user benkeen commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/278#issuecomment-75272681 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: (Another) fix for flaky nightwatch t...
Github user robertkowalski commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/282#issuecomment-75272638 merge if travis is green :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Fix for flaky nightwatch test
GitHub user benkeen opened a pull request: https://github.com/apache/couchdb-fauxton/pull/282 Fix for flaky nightwatch test This fixes the editDocumentsFromView.js test that would occasionally fail if the element was present but not visible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/benkeen/couchdb-fauxton nightwatch-test-fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/282.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #282 commit c2cb64fbf15437b15397a061e09f17272b010e2a Author: Ben Keen Date: 2015-02-20T16:52:00Z Fix for flaky nightwatch test This fixes the editDocumentsFromView.js test that would occasionally fail if the element was present but not visible. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Nw test fix
GitHub user benkeen opened a pull request: https://github.com/apache/couchdb-fauxton/pull/281 Nw test fix Fix for nightwatch test failing occasionally (e.g. on last build for https://github.com/apache/couchdb-fauxton/pull/265). You can merge this pull request into a Git repository by running: $ git pull https://github.com/benkeen/couchdb-fauxton nw-test-fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/281.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #281 commit ac15d181203e5512ea60524e88a4975b8ebcb26e Author: Ben Keen Date: 2015-02-11T01:04:23Z Changes page Filters tab moved to React This updates the Filter tab and content on the Changes page to use React. It also ports over Components.FilterView and Components.FilterViewItem found in fauxton/components commit ca66ff8dda603912f511ec7cfaeb160f0a9022ba Author: Ben Keen Date: 2015-02-16T16:25:28Z replaced manual DOM reference commit bf51490fb16f40bcdfc6c4d8e5b91c7819e7af8b Author: Ben Keen Date: 2015-02-16T19:51:38Z Incorporating feedback from @garrensmith commit 6f67f097aa9fdc65bfaba53ad32453e1b8ae3319 Author: Ben Keen Date: 2015-02-16T22:06:21Z Experimental refactoring commit 5e25c8ff7a8f888fd8d76ed7d4041d7e57b3da32 Author: Ben Keen Date: 2015-02-17T19:44:43Z Incorporating feedback from @garrensmith commit 31268faa7a63fa339ad3c1c9f9c6bf067fbbf1d0 Author: Ben Keen Date: 2015-02-18T16:36:26Z Fixes & feedback from @garrensmith commit c84966d2a851d2554f497f3fd3de72445d4e01da Author: Ben Keen Date: 2015-02-18T18:00:09Z Error handling for same filter added twice commit 26778f874526b4f8c5ec70a8d68d01fe8ad771c4 Author: Ben Keen Date: 2015-02-20T16:47:00Z Fix for unit test This test would fail every once in a while. This ensures the element is visible rather than present, prior to clicking it. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Nw test fix
Github user benkeen closed the pull request at: https://github.com/apache/couchdb-fauxton/pull/281 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Remove raf
Github user michellephung commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/279#issuecomment-75270466 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Selenium ports
Github user michellephung commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/280#issuecomment-75268129 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Selenium ports
Github user benkeen commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/280#issuecomment-75268466 nice +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Remove raf
Github user benkeen commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/279#issuecomment-75267475 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Selenium ports
GitHub user robertkowalski opened a pull request: https://github.com/apache/couchdb-fauxton/pull/280 Selenium ports You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertkowalski/couchdb-fauxton selenium-ports Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/280.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #280 commit afc3ed6032b96b00312f5488ad5488c469ba0d5c Author: Robert Kowalski Date: 2015-02-20T13:12:35Z backbone.layoutmanager@0.9.5 src: https://raw.githubusercontent.com/tbranyen/backbone.layoutmanager/0.9.5/backbone.layoutmanager.js commit f7dec4064bfafe45faa19b4dfee1b3dd64d24dbe Author: Robert Kowalski Date: 2015-02-20T13:14:56Z cleanup: remove useRAF leftovers Garren and me tried to use the latest layoutmanager in summer 2014 - the experiment lead to performance improvements regarding the rendering of our application, but we had to disable it as we as it lead to timing issues. As we are moving to React it does not make sense to me to invest further time into the issues we had in summer. This commit removes the leftovers of the experiment that are not needed any more and cleans up. See https://github.com/apache/couchdb-fauxton/pull/29 commit 87d73b3f733959e3deb0d9c9dd060bd7673abc30 Author: Robert Kowalski Date: 2015-02-20T16:22:09Z allow multiple selenium ports Make selenium port configurable, e.g. to spin up several selenium servers on one CI system --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Port View Indexes work from PR #33
Github user robertkowalski closed the pull request at: https://github.com/apache/couchdb-fauxton/pull/106 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-2601) Config section - remove handler from chttpd
[ https://issues.apache.org/jira/browse/COUCHDB-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329007#comment-14329007 ] ASF GitHub Bot commented on COUCHDB-2601: - Github user asfgit closed the pull request at: https://github.com/apache/couchdb-chttpd/pull/25 > Config section - remove handler from chttpd > --- > > Key: COUCHDB-2601 > URL: https://issues.apache.org/jira/browse/COUCHDB-2601 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Database Core, Fauxton >Reporter: Robert Kowalski >Assignee: Robert Kowalski >Priority: Blocker > > if Fauxton gets a 404 we are not using the backdoor port which still > supports `/_config` - this also solves the problem if user are using curl and > try to change configuration on a clustered CouchDB behind a LB -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2601) Config section - remove handler from chttpd
[ https://issues.apache.org/jira/browse/COUCHDB-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329002#comment-14329002 ] ASF subversion and git services commented on COUCHDB-2601: -- Commit 2a583cb0dfcd446ae259b272acd58068079c9b52 in couchdb-chttpd's branch refs/heads/master from [~robertkowalski] [ https://git-wip-us.apache.org/repos/asf?p=couchdb-chttpd.git;h=2a583cb ] Remove _config route on cluster In order to avoid users shooting themselves in the foot by using `/_config/` on a clustered CouchDB with a loadbalancer in front, we remove it on `15984` - it will be available for single-node- mode on the backdoor port (`15986`) or for users that are feeling lucky which want to fire curl requests to every node. It also allows Fauxton to detect if it is running on a the backdoor port. Fauxton will - if it gets a 200 instead of a 404 - show the config-section to the user. COUCHDB-2601 COUCHDB-2390 COUCHDB-2343 > Config section - remove handler from chttpd > --- > > Key: COUCHDB-2601 > URL: https://issues.apache.org/jira/browse/COUCHDB-2601 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Database Core, Fauxton >Reporter: Robert Kowalski >Assignee: Robert Kowalski >Priority: Blocker > > if Fauxton gets a 404 we are not using the backdoor port which still > supports `/_config` - this also solves the problem if user are using curl and > try to change configuration on a clustered CouchDB behind a LB -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2390) Fauxton config, admin sections considered dangerous in 2.0
[ https://issues.apache.org/jira/browse/COUCHDB-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329003#comment-14329003 ] ASF subversion and git services commented on COUCHDB-2390: -- Commit 2a583cb0dfcd446ae259b272acd58068079c9b52 in couchdb-chttpd's branch refs/heads/master from [~robertkowalski] [ https://git-wip-us.apache.org/repos/asf?p=couchdb-chttpd.git;h=2a583cb ] Remove _config route on cluster In order to avoid users shooting themselves in the foot by using `/_config/` on a clustered CouchDB with a loadbalancer in front, we remove it on `15984` - it will be available for single-node- mode on the backdoor port (`15986`) or for users that are feeling lucky which want to fire curl requests to every node. It also allows Fauxton to detect if it is running on a the backdoor port. Fauxton will - if it gets a 200 instead of a 404 - show the config-section to the user. COUCHDB-2601 COUCHDB-2390 COUCHDB-2343 > Fauxton config, admin sections considered dangerous in 2.0 > -- > > Key: COUCHDB-2390 > URL: https://issues.apache.org/jira/browse/COUCHDB-2390 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: BigCouch, Fauxton >Reporter: Joan Touzet >Assignee: Ben Keen >Priority: Blocker > Fix For: 2.0.0 > > > In Fauxton today, there is are 2 sections to edit config-file settings and to > create new admins. Neither of these sections will work as intended in a > clustered setup. > Any Fauxton session will necessarily be speaking to a single machine. The > config APIs and admin user info as exposed will only add that information to > a single node's .ini file. > We should hide these features in Fauxton for now (short-term fix) and correct > the config /admin creation APIs to work correctly in a clustered setup > (medium-term fix). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2343) /_config/admins/username fails on master
[ https://issues.apache.org/jira/browse/COUCHDB-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329004#comment-14329004 ] ASF subversion and git services commented on COUCHDB-2343: -- Commit 2a583cb0dfcd446ae259b272acd58068079c9b52 in couchdb-chttpd's branch refs/heads/master from [~robertkowalski] [ https://git-wip-us.apache.org/repos/asf?p=couchdb-chttpd.git;h=2a583cb ] Remove _config route on cluster In order to avoid users shooting themselves in the foot by using `/_config/` on a clustered CouchDB with a loadbalancer in front, we remove it on `15984` - it will be available for single-node- mode on the backdoor port (`15986`) or for users that are feeling lucky which want to fire curl requests to every node. It also allows Fauxton to detect if it is running on a the backdoor port. Fauxton will - if it gets a 200 instead of a 404 - show the config-section to the user. COUCHDB-2601 COUCHDB-2390 COUCHDB-2343 > /_config/admins/username fails on master > > > Key: COUCHDB-2343 > URL: https://issues.apache.org/jira/browse/COUCHDB-2343 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: HTTP Interface >Affects Versions: 2.0.0 >Reporter: Joan Touzet >Priority: Blocker > Labels: auth > Fix For: 2.0.0 > > > In a multi-node setup, calling _config/admins/username to create an admin > user fails to correctly configure a cluster with a new administrator. This > fails for two reasons: > 1) The call is only processed on a single node, and the admin entry is not > replicated > 2) Even if the call is repeated on all nodes manually, the hashes will be > different on each node, which will cause cookie failure when attempting to > authenticate via other machines. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-chttpd pull request: Remove _config route on cluster
Github user asfgit closed the pull request at: https://github.com/apache/couchdb-chttpd/pull/25 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Remove raf
GitHub user robertkowalski opened a pull request: https://github.com/apache/couchdb-fauxton/pull/279 Remove raf Garren and me tried to use the latest layoutmanager in summer 2014 - the experiment lead to performance improvements regarding the rendering of our application, but we had to disable it as we as it lead to timing issues. As we are moving to React it does not make sense to me to invest further time into the issues we had in summer. This commit removes the leftovers of the experiment that are not needed any more and cleans up. See apache#29 You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertkowalski/couchdb-fauxton remove-raf Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/279.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #279 commit afc3ed6032b96b00312f5488ad5488c469ba0d5c Author: Robert Kowalski Date: 2015-02-20T13:12:35Z backbone.layoutmanager@0.9.5 src: https://raw.githubusercontent.com/tbranyen/backbone.layoutmanager/0.9.5/backbone.layoutmanager.js commit f7dec4064bfafe45faa19b4dfee1b3dd64d24dbe Author: Robert Kowalski Date: 2015-02-20T13:14:56Z cleanup: remove useRAF leftovers Garren and me tried to use the latest layoutmanager in summer 2014 - the experiment lead to performance improvements regarding the rendering of our application, but we had to disable it as we as it lead to timing issues. As we are moving to React it does not make sense to me to invest further time into the issues we had in summer. This commit removes the leftovers of the experiment that are not needed any more and cleans up. See https://github.com/apache/couchdb-fauxton/pull/29 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-2191) Please consider including couchperuser in core
[
https://issues.apache.org/jira/browse/COUCHDB-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328981#comment-14328981
]
Jan Lehnardt commented on COUCHDB-2191:
---
I’d be in favour of this.
> Please consider including couchperuser in core
> --
>
> Key: COUCHDB-2191
> URL: https://issues.apache.org/jira/browse/COUCHDB-2191
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
>Reporter: Nolan Lawson
>
> I would love to be able to use CouchDB as the exclusive backend for all my
> webapps. The {{_users}} database with the automatic password salting/hashing
> and session cookies is brilliant, and saves a lot of developer effort while
> still ensuring I don't shoot myself in the foot trying to implement password
> security.
> However, without creating a database per user, it's impossible to silo user
> data in any way other than through {{validate_doc_update}} - i.e. every user
> can see everybody else's data, but they can only write to theirs. This use
> case does exist (e.g. Twitter), but it's much less common than the case where
> users can only read/write their own data.
> The plugin ecosystem is great and all, and I totally understand not wanting
> to include the kitchen sink in Couch core, but I strongly feel
> [couchperuser|https://github.com/etrepum/couchperuser] (or something like it)
> should be a checkbox I can tick in the Couch config, rather than a plugin I
> have to install manually. It's just too common of a use case in typical
> webapps.
> Some background: this was prompted by a [discussion in
> PouchDB|https://github.com/daleharvey/pouchdb/issues/1575]; Dale has written
> a fine solution in
> [couch-persona|https://github.com/daleharvey/couch-persona], but I really
> think the "why Pouch/Couch?" story would be more compelling if you could do
> it in pure Couch without an extra server process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (COUCHDB-2191) Please consider including couchperuser in core
[
https://issues.apache.org/jira/browse/COUCHDB-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328969#comment-14328969
]
Alexander Shorin commented on COUCHDB-2191:
---
If [~etrepum] would like to contribute his couchperuser project, so why not? (:
It could be included into core or as plugin that available out of the box. I
think that would be great too since the implemented pattern is too much common.
> Please consider including couchperuser in core
> --
>
> Key: COUCHDB-2191
> URL: https://issues.apache.org/jira/browse/COUCHDB-2191
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
>Reporter: Nolan Lawson
>
> I would love to be able to use CouchDB as the exclusive backend for all my
> webapps. The {{_users}} database with the automatic password salting/hashing
> and session cookies is brilliant, and saves a lot of developer effort while
> still ensuring I don't shoot myself in the foot trying to implement password
> security.
> However, without creating a database per user, it's impossible to silo user
> data in any way other than through {{validate_doc_update}} - i.e. every user
> can see everybody else's data, but they can only write to theirs. This use
> case does exist (e.g. Twitter), but it's much less common than the case where
> users can only read/write their own data.
> The plugin ecosystem is great and all, and I totally understand not wanting
> to include the kitchen sink in Couch core, but I strongly feel
> [couchperuser|https://github.com/etrepum/couchperuser] (or something like it)
> should be a checkbox I can tick in the Couch config, rather than a plugin I
> have to install manually. It's just too common of a use case in typical
> webapps.
> Some background: this was prompted by a [discussion in
> PouchDB|https://github.com/daleharvey/pouchdb/issues/1575]; Dale has written
> a fine solution in
> [couch-persona|https://github.com/daleharvey/couch-persona], but I really
> think the "why Pouch/Couch?" story would be more compelling if you could do
> it in pure Couch without an extra server process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] couchdb-fauxton pull request: add the cassim database to the list ...
Github user Poltergeist commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/277#issuecomment-75231689 @robertkowalski fixed the commit message it should now look good. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: try to fix flaky test
GitHub user robertkowalski opened a pull request: https://github.com/apache/couchdb-fauxton/pull/278 try to fix flaky test it sometimes fails on the ci You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertkowalski/couchdb-fauxton flaky-test Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/278.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #278 commit 48910707502034d4132866ac9fc9baaebc169cf8 Author: Robert Kowalski Date: 2015-02-20T12:01:17Z try to fix flaky test it sometimes fails on the ci --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [ANNOUNCE] Eric Avdey elected as CouchDB committer
Welcome Eric. This is great. > On 20 Feb 2015, at 12:04 PM, Andy Wenk wrote: > > Hi Eric and welcome on board ;-) > > On 20 February 2015 at 10:42, Klaus Trainer wrote: > >> Welcome Eric! >> >> >> On 19.02.2015 19:48, Robert Kowalski wrote: >>> Dear community, >>> >>> I am pleased to announce that the CouchDB Project Management Committee >>> has elected Eric Avdey as a CouchDB committer. >>> >>>Apache ID: eiri >>> >>>IRC nick: eiri >>> >>> Committers are given a binding vote in certain project decisions, as >>> well as write access to public project infrastructure. >>> >>> This election was made in recognition of Eric's commitment to the >>> project. We mean this in the sense of being loyal to the project and >>> its interests. >>> >>> Please join me in extending a warm welcome to Eric! >>> >>> On behalf of the CouchDB PMC, >>> Robert >>> >> >> > > > -- > Andy Wenk > Hamburg - Germany > RockIt! > > http://www.couchdb-buch.de > http://www.pg-praxisbuch.de > > GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 > > https://people.apache.org/keys/committer/andywenk.asc
Re: [ANNOUNCE] Tony Sun elected as CouchDB committer
Welcome Tony. > On 20 Feb 2015, at 11:55 AM, Andy Wenk wrote: > > Tony, welcome ;-) > > On 20 February 2015 at 10:43, Klaus Trainer wrote: > >> Welcome Tony! >> >> >> On 19.02.2015 20:18, Robert Kowalski wrote: >>> Dear community, >>> >>> I am pleased to announce that the CouchDB Project Management Committee >>> has elected Tony Sun as a CouchDB committer. >>> >>>Apache ID: tonysun83 >>> >>>IRC nick: tonysun83 >>> >>>Twitter: TonyS0427 >>> >>> Committers are given a binding vote in certain project decisions, as >>> well as write access to public project infrastructure. >>> >>> This election was made in recognition of Tony's commitment to the >>> project. We mean this in the sense of being loyal to the project and >>> its interests. >>> >>> Please join me in extending a warm welcome to Tony! >>> >>> On behalf of the CouchDB PMC, >>> Robert >>> >> >> > > > -- > Andy Wenk > Hamburg - Germany > RockIt! > > GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 > > https://people.apache.org/keys/committer/andywenk.asc
Re: [ANNOUNCE] Eric Avdey elected as CouchDB committer
Hi Eric and welcome on board ;-) On 20 February 2015 at 10:42, Klaus Trainer wrote: > Welcome Eric! > > > On 19.02.2015 19:48, Robert Kowalski wrote: > > Dear community, > > > > I am pleased to announce that the CouchDB Project Management Committee > > has elected Eric Avdey as a CouchDB committer. > > > > Apache ID: eiri > > > > IRC nick: eiri > > > > Committers are given a binding vote in certain project decisions, as > > well as write access to public project infrastructure. > > > > This election was made in recognition of Eric's commitment to the > > project. We mean this in the sense of being loyal to the project and > > its interests. > > > > Please join me in extending a warm welcome to Eric! > > > > On behalf of the CouchDB PMC, > > Robert > > > > -- Andy Wenk Hamburg - Germany RockIt! http://www.couchdb-buch.de http://www.pg-praxisbuch.de GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc
Re: [ANNOUNCE] Tony Sun elected as CouchDB committer
Tony, welcome ;-) On 20 February 2015 at 10:43, Klaus Trainer wrote: > Welcome Tony! > > > On 19.02.2015 20:18, Robert Kowalski wrote: > > Dear community, > > > > I am pleased to announce that the CouchDB Project Management Committee > > has elected Tony Sun as a CouchDB committer. > > > > Apache ID: tonysun83 > > > > IRC nick: tonysun83 > > > > Twitter: TonyS0427 > > > > Committers are given a binding vote in certain project decisions, as > > well as write access to public project infrastructure. > > > > This election was made in recognition of Tony's commitment to the > > project. We mean this in the sense of being loyal to the project and > > its interests. > > > > Please join me in extending a warm welcome to Tony! > > > > On behalf of the CouchDB PMC, > > Robert > > > > -- Andy Wenk Hamburg - Germany RockIt! GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc
Re: [ANNOUNCE] Tony Sun elected as CouchDB committer
Welcome Tony! On 19.02.2015 20:18, Robert Kowalski wrote: > Dear community, > > I am pleased to announce that the CouchDB Project Management Committee > has elected Tony Sun as a CouchDB committer. > > Apache ID: tonysun83 > > IRC nick: tonysun83 > > Twitter: TonyS0427 > > Committers are given a binding vote in certain project decisions, as > well as write access to public project infrastructure. > > This election was made in recognition of Tony's commitment to the > project. We mean this in the sense of being loyal to the project and > its interests. > > Please join me in extending a warm welcome to Tony! > > On behalf of the CouchDB PMC, > Robert > signature.asc Description: OpenPGP digital signature
Re: [ANNOUNCE] Eric Avdey elected as CouchDB committer
Welcome Eric! On 19.02.2015 19:48, Robert Kowalski wrote: > Dear community, > > I am pleased to announce that the CouchDB Project Management Committee > has elected Eric Avdey as a CouchDB committer. > > Apache ID: eiri > > IRC nick: eiri > > Committers are given a binding vote in certain project decisions, as > well as write access to public project infrastructure. > > This election was made in recognition of Eric's commitment to the > project. We mean this in the sense of being loyal to the project and > its interests. > > Please join me in extending a warm welcome to Eric! > > On behalf of the CouchDB PMC, > Robert > signature.asc Description: OpenPGP digital signature
