Project

General

Profile

Actions
Copy link

Bug #4706

open

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

Added by Peter Amstutz about 10 years ago. Updated over 3 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 1 (0 open — 1 closed)

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

Actions
Actions
Copy link
 #1

Updated by Tom Clegg about 10 years ago

  • Story points set to 1.0
Actions
Copy link
 #2

Updated by Tom Clegg about 10 years ago

  • Target version changed from Bug Triage to Arvados Future Sprints
Actions
Copy link
 #3

Updated by Brett Smith over 9 years ago

  • Target version changed from Arvados Future Sprints to 2015-06-10 sprint
Actions
Copy link
 #4

Updated by Brett Smith over 9 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.

Actions
Copy link
 #5

Updated by Peter Amstutz over 9 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.

Actions
Copy link
 #6

Updated by Brett Smith over 9 years ago

  • Target version changed from 2015-06-10 sprint to Arvados Future Sprints
Actions
Copy link
 #7

Updated by Peter Amstutz over 3 years ago

  • Target version deleted (Arvados Future Sprints)
Actions
Copy link

Also available in: Atom PDF