Bug #4706

[Workbench] Re-connect to websockets when the connection drops; use "last_log_id" so nothing is missed.

Added by Peter Amstutz over 4 years ago. Updated about 4 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
1.0

Related issues

Has duplicate Arvados - Bug #6048: Pipeline Instance does not automatically refreshDuplicate05/15/2015

History

#1 Updated by Tom Clegg over 4 years ago

  • Story points set to 1.0

#2 Updated by Tom Clegg over 4 years ago

  • Target version changed from Bug Triage to Arvados Future Sprints

#3 Updated by Brett Smith about 4 years ago

  • Target version changed from Arvados Future Sprints to 2015-06-10 sprint

#4 Updated by Brett Smith about 4 years ago

This is still an issue, but it may be lower priority: we just realized that #6048 was happening because websockets simply weren't running on the clusters in question.

#5 Updated by Peter Amstutz about 4 years ago

In addition, we could provide a fallback method that uses log table polling to get events. The Python SDK uses this to great success when websockets isn't available.

#6 Updated by Brett Smith about 4 years ago

  • Target version changed from 2015-06-10 sprint to Arvados Future Sprints

Also available in: Atom PDF