[Workbench] Re-connect to websockets when the connection drops; use "last_log_id" so nothing is missed.
- Target version changed from Bug Triage to Arvados Future Sprints
- Target version changed from Arvados Future Sprints to 2015-06-10 sprint
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.
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.
- Target version changed from 2015-06-10 sprint to Arvados Future Sprints
- Target version deleted (
Arvados Future Sprints)
Also available in: Atom