osrf-migration
commented
7 years ago Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).
This seems related to issue #45. This is the sequence of events:
-
The browser makes a request to the portal to launch the arbiter machine.
-
The portal launches the machine and sends information back to the browser.
-
The browser relays that information to the widgets server.
-
When the page is reloaded, the browser requests for information coming from the widgets server.
If there was a problem doing step 3, the browser sees the arbiter machine the moment it was launched, but the information is lost on refresh.
Looking at the database, this seems to be the case here... Maybe the user saw a red message at the bottom when launching the arbiter? It's also possible that we're not handling well whatever error comes and there was no red message...
I'm not sure how to make this more robust without making some big changes in architecture. It feels too error prone that the browser must be responsible for relaying information from one server to the other.
Original report (archived issue) by Tully Foote (Bitbucket: Tully Foote, GitHub: tfoote).
After launching a round the web interface is losing the information about the Arbiter.
This has effected the specific user 3 times in a row.
Here's a video showing the information not-presisting.
https://youtu.be/0VK1goBkcto