Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: App can only find robots if "Try again" is clicked after the interface comes up #5343

Closed
SyntaxColoring opened this issue Apr 1, 2020 · 1 comment · Fixed by #5933
Closed
Labels
app Affects the `app` project bug robot-svcs Falls under the purview of the Robot Services squad (formerly CPX, Core Platform Experience). workaround available This issue has a workaround available, though it isn't necessarily totally fixed.
Milestone

Comments

@SyntaxColoring
Copy link
Contributor

Overview

Clicking the "Try again" / "Refresh list" button doesn't do anything useful if the network interface wasn't already up when you clicked the button.

It takes ~20–25 seconds for the link-local network interface to come up after plugging in an OT-2, so if you plug in an OT-2 and immediately click the button, the 30 second discovery period will be wasted. This is one reason why people might have to click "Try again" more than once to see the robot that they just plugged in.

Current behavior

Quoth the @mcous:

...the mDNS browser only checks the computer's interface list for binding at the beginning of any given discovery period, and won't refresh that list until a new fast discovery period is started (for example, by clicking the button).

Expected behavior

  • If an interface comes up in the middle of a "Try again" / "Refresh list" fast discovery period, discovery requests should go out on that interface, just like the interfaces that were up before the discovery period started.
  • If an interface comes up during slow discovery (when I haven't clicked the button and the app is just sitting idle), discovery requests should automatically start going out on that interface.
@SyntaxColoring SyntaxColoring added bug robot-svcs Falls under the purview of the Robot Services squad (formerly CPX, Core Platform Experience). labels Apr 1, 2020
@SyntaxColoring SyntaxColoring added the app Affects the `app` project label Apr 1, 2020
@mcous mcous added this to the CPX Sprint 10 milestone May 27, 2020
@mcous mcous modified the milestones: CPX Sprint 10, CPX Sprint 11 Jun 9, 2020
@SyntaxColoring SyntaxColoring added the workaround available This issue has a workaround available, though it isn't necessarily totally fixed. label Aug 3, 2020
@SyntaxColoring
Copy link
Contributor Author

Workaround

(Simple, but documenting this here for posterity.)

  1. Turn on and plug in your OT-2.
  2. Wait 2 minutes.
  3. Then click Try again or Refresh list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app Affects the `app` project bug robot-svcs Falls under the purview of the Robot Services squad (formerly CPX, Core Platform Experience). workaround available This issue has a workaround available, though it isn't necessarily totally fixed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants