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

Remove opentrons- prefix from mDNS advertisements and /health name #2054

Closed
umbhau opened this issue Aug 13, 2018 · 6 comments
Closed

Remove opentrons- prefix from mDNS advertisements and /health name #2054

umbhau opened this issue Aug 13, 2018 · 6 comments
Labels
api Affects the `api` project BREAKING CHANGE Introduces a breaking change feature Ticket is a feature request / PR introduces a feature

Comments

@umbhau
Copy link

umbhau commented Aug 13, 2018

Expected Behavior

  • API should be returning robot ID from config (so that the App can display it)

Observed Behavior

  • API is returning longer string name

Steps to recreate

  • Connect to any robot
  • Observe 'Robot Name' in 'Information' card is reported as:
    "opentrons-OT2P20180314A02", or "Opentrons on Brians-MacBook-Pro-2" (@mcous edit: this is a a spoofed name from a dev tool and not relevant)
    rather than as the serial number/id:
    "OT2P20180314A02"
@umbhau
Copy link
Author

umbhau commented Aug 13, 2018

Not very familiar with how id/name (?) are configured as data / returned via API; filing this bug on behalf of @andySigler who reports the following:

"the #1 issue the SZ team kept reminding me of is that the App doesn't show the robot name as an ID anymore. Now it shows the random English words resin first assigns it like Opentrons-still-paper, but no longer shows the ID they then rename it to like OT2P20180812A01. They say this is super duper annoying because they don't know which robot is which"

With the following clarification from @mcous:

"At some point the API appears to have stopped being able to pick up the ID from configuration and so it’s reporting its name as the words name to the app, which is what gets displayed"

@btmorr @Laura-Danielle I can do further investigation, but suspect you might already be aware of this, if not the issue it's causing in Shenzhen.

@umbhau umbhau added bug api Affects the `api` project labels Aug 13, 2018
@umbhau umbhau added this to the Bugs milestone Aug 13, 2018
@mcous mcous added feature Ticket is a feature request / PR introduces a feature api Affects the `api` project and removed api Affects the `api` project bug labels Aug 17, 2018
@mcous mcous changed the title Robot Returning Incorrect Name Remove opentrons- prefix from mDNS advertisements and /health name Aug 17, 2018
@mcous
Copy link
Contributor

mcous commented Aug 17, 2018

@umbhau @andySigler in terms of the factory issue:

...Now it shows the random English words resin first assigns it like Opentrons-still-paper, but no longer shows the ID they then rename it to like OT2P20180812A01...

I've just done some testing and this appears to be a factory process issue, not a problem with the API. Removed bug tag accordingly and re-scoped this ticket to be a feature request to remove the opentrons- name prefix that the API has been adding to the name for no-longer-relevant technical reasons.

@andySigler and I will be following up on the factory process stuff outside of GH.

@mcous mcous added the BREAKING CHANGE Introduces a breaking change label Aug 17, 2018
@mcous
Copy link
Contributor

mcous commented Aug 17, 2018

Removing the opentrons- name prefix is a breaking change that will prevent older versions of the app from finding newer versions of the robot (that don't have the prefix) on the network

@btmorr
Copy link
Contributor

btmorr commented Mar 25, 2019

@mcous Should we close this in light of #2357? Seems like this is probably something we're not going to change

@mcous
Copy link
Contributor

mcous commented Mar 25, 2019

@btmorr I would prefer we don't add opentrons- automatically to the advertised name unless we have a good reason to do so.

@sfoster1 in this comment you mentioned something about advertising our capabilities more specifically than tcp; do you think that's something likely to ship with the new system?

@mcous
Copy link
Contributor

mcous commented Jul 26, 2019

This behavior has been changed in the new buildroot-based system; closing

@mcous mcous closed this as completed Jul 26, 2019
@mcous mcous removed this from the Bugs milestone Jul 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Affects the `api` project BREAKING CHANGE Introduces a breaking change feature Ticket is a feature request / PR introduces a feature
Projects
None yet
Development

No branches or pull requests

3 participants