Github user garrensmith commented on the issue:

    https://github.com/apache/couchdb-fauxton/pull/864
  
    @justin-mcdavid-ibm I've made some of the changes. Others of them I have 
some comments:
    
    > 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.
    
    I'm a little confused on this. Do you still want a tab for the new 
replications? Can you do a quick mockup of how the `new replication page` now 
looks?
    
    > Hovering over the state should result in the state time displaying.
    
    We don't always get the state time returned. So its only displayed on hover 
if we get it. It seems that completed don't get the time.
    
    > The “Retrying” state should only be for for jobs that are actually 
being retried. Auth errors aren’t retried, are they? I’m seeing Retry for 
an error with message of “unauthorized: unauthorized to access or create 
database https://garrensmith.cloudant.com/tickle_production/” which I believe 
is a “failed” job, right?
    
    I agree. I followed the mock up comments of `"Retrying" shown for both 
"Error" state and "Crashing" state.`. The auth state is an Error state.
    
    > 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.
    
    The start time isn't always returned.


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to