Actions
Bug #5481
closed
[Workbench] Pipeline instance page does not automatically refresh when pipeline does not need to be re-run
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
-
Start date:
03/17/2015
Due date:
% Done:
0%
Estimated time:
Story points:
-
Files
Updated by Bryan Cosca about 10 years ago
- File pipelineinstancerefresh.gif pipelineinstancerefresh.gif added
- Description updated (diff)
Updated by Brett Smith about 10 years ago
- Subject changed from Pipeline instance page does not automatically refresh when pipeline does not need to be re-run to [Workbench] Pipeline instance page does not automatically refresh when pipeline does not need to be re-run
- Category set to Workbench
- Target version set to Bug Triage
Bryan,
Is there some trick to reproducing this bug? I just tried a basic pipeline run, and it worked out all right for me.
One case where we do know this can happen is if the browser loses its connection to the websockets server. That's #4706. Is there any chance that's what happened here?
Updated by Bryan Cosca about 10 years ago
I honestly don't think I could reproduce this. I have tried before and it only happens sometimes. I'm not too familiar with websockets, I can't say for sure if that is the issue, there's definitely a chance.
Updated by Tom Clegg about 10 years ago
I'm guessing this is what it looks like when we haven't done #5767 yet:
- Workbench renders page with current pipeline state ("queued")
- Workbench sends page to browser
- Pipeline changes state to "finished"
- Browser renders page, runs scripts, and connects to websocket
- Websocket starts waiting for updates to the pipeline
- There are no updates because the pipeline is already finished
Updated by
Actions