You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@couchdb.apache.org by justin-mcdavid-ibm <gi...@git.apache.org> on 2017/03/02 21:47:45 UTC

[GitHub] couchdb-fauxton issue #864: Update replication to work with scheduler api

Github user justin-mcdavid-ibm commented on the issue:

https://github.com/apache/couchdb-fauxton/pull/864

1. I'm sorry for the confusion in the mockups, but I think we should keep the "New Replication" button in place for Replicator DB Activity, and add it to the _replicate Activity tab as well, even though both buttons will only be capable of triggering a replicator db job. My mistake here; I think we want to try and maintain the cohesive pattern of "new" buttons above the table across the dashboard, and when it comes time to add "Advanced Replication" to the mix, we can do so still maintaining that pattern. Updated mockups below.

2. Hover help on the trashcan icon in the _replicate Activity section should not reference a document being deleted, but instead the job. \u201cDelete job id 1342345234534534563456.\u201d

3. Hovering over the state should result in the state time displaying.

4. _replicate Activity doesn\u2019t seem to be picking up the type correctly. My continuous jobs are showing up as \u201cone time.\u201d

5. The \u201cRetrying\u201d state should only be for for jobs that are actually being retried. Auth errors aren\u2019t retried, are they? I\u2019m seeing Retry for an error with message of \u201cunauthorized: unauthorized to access or create database https://garrensmith.cloudant.com/tickle_production/\u201d which I believe is a \u201cfailed\u201d job, right?

6. Not all Replicator DB jobs are displaying Start Times in the activity table, though the columns are still sorting on the start times in the replication docs.

7. I'd like to shorten our caveat, so that it remains a one-liner when we eventually constrain line-lengths for block text across the dashboard. Please change the caveat to:
"Active _replicate jobs are displayed. Completed and failed jobs are not."

8. Are we going to be able to surface erroring/crashing states for _replicate Activity? I see that in my earlier mockup, that I left the "State" column out, mostly because I figured that the "Start Time" one would suffice if state would only be showing running jobs. But perhaps I misunderstood. If we can pick up _troubled jobs' replication states, then we definitely should have the state column.

Here is the list of tweaks that I had in [FogBugz](https://cloudant.fogbugz.com/f/cases/81384/), if you'd like all comments consolidated here:

1. On the Replication form, make the URL-entry fields a consistent length. Default document IDs are longer than the current "Replication Document" field, as well, so let's make the field longer, consistent with the lenght of the URL fields. It looks like the remote URL fields are currenly longer (~346px) to match the length of the text string below. I'd be fine if all URL fields and the Rep Doc field were 400px.

2. On the Verify Deletion dialogue box, change the button text so that it accounts for singular and plural doc-deletions. Probably easiest would be to change the text to "Delete Document(s)", otherwise, you could have "Delete Document" for single deletions, and "Delete Documents" for multiple deletions.

3. Change embedded help pop-up text from center-justification to default (left) justification.

4. In the Replication-activity-section header, change "Replication" to "Replication Activity."

5. Breadcrumbs are unnecessary on the new/edit-replication pages, as clicking the main nav takes the user to the exact same place as clicking on "Replication" in the header. So, I think we should remove the "Replication" crumb.

6. Clicking on the edit-replication icon takes the user to the replication form page, where the header nav states "New Replication." "New" is a smidge confusing in the context of editing, but users are able to trigger entirely new replications from the page. So for both entirely "new" replications and replications being edited, lets change that header text to "Replication-Job Details".

7. Increase the margin between the two buttons on the "Fix Document Conflict" dialogue box to 20px.

Thanks much for all your work on this.

---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---