[
https://issues.apache.org/jira/browse/COUCHDB-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944454#comment-14944454
]
ASF GitHub Bot commented on COUCHDB-2243:
-----------------------------------------
GitHub user benkeen opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/549
Fixing db page loading
Improve db page error handling
This PR fixes an old bug with the databases page where if one
database query fails, the remaining responses that haven't been
returned don't get populated and the database table has a lot
of incomplete rows.
Now the individual failed database rows don't affect the others and
show a "This database failed to load" message to make it clear to
the user.
Closes COUCHDB-2243
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/benkeen/couchdb-fauxton db-page-error-handling
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-fauxton/pull/549.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 #549
----
commit 9f9a549fb615ecae3903893a4a83410b6d5ba060
Author: Ben Keen <[email protected]>
Date: 2015-09-29T17:14:50Z
Improve db page error handling
This PR fixes an old bug with the databases page where if one
database query fails, the remaining responses that haven't been
returned don't get populated and the database table has a lot
of incomplete rows.
Now the individual failed database rows don't affect the others and
show a "This database failed to load" message to make it clear to
the user.
Closes COUCHDB-2243
----
> Fauxton shows no database info in list on first 401 failure
> -----------------------------------------------------------
>
> Key: COUCHDB-2243
> URL: https://issues.apache.org/jira/browse/COUCHDB-2243
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Fauxton
> Reporter: Alexander Shorin
> Assignee: Ben Keen
> Attachments: Screen Shot 2015-09-29 at 9.44.15 AM.png
>
>
> 1. Fix the Admin Party
> 2. Create few more dbs (let's say 10)
> 3. Setup for the security for the any to forbid access by anonymous users
> (add any user to members). To not fall on edge case, better pick database
> from top of the database list
> 4. Logout
> 5. If database lists didn't refresh, refresh it manually
> You'll see that almost all databases has no size, no docs and no update seq.
> Including those which you can't access being unauthorized and those which you
> can. However, if you'll move between pages, Fauxton will be able to show all
> the data correctly.
> Fauxton @ 2abdb2c
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
