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.

Sign up for GitHub

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

Jump to bottom

Cleanup of alias table after an alias conflict #738

Open
balazsracz opened this issue Sep 8, 2023 · 0 comments
Open

Cleanup of alias table after an alias conflict #738

balazsracz opened this issue Sep 8, 2023 · 0 comments
Labels
bug

Comments

@balazsracz
Copy link
Collaborator

It seems we are leaving a spurious entry in the local alias map after an alias conflict.

Steps to reproduce:

  • let openmrn allocate an alias for it self upon startup (say 0x345)
  • send a message to the bus that conflicts with this alias (e.g. :X195b4345N8877665544332211;)
  • watch openmrn allocate a second alias (say 0x789).
  • send a global AME frame to the bus (CS-105 startup does this), e.g. :X10702600N;

Expected result:

  • openmrn replies with AMD for 0x789

Actual result:

  • openmrn replies with AMD for 0x789 and another AMD for 0x345
@balazsracz balazsracz added the bug label Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@balazsracz