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

Listener command wrongly showing "never published" #12955

Closed
AmeliaEScott opened this issue Sep 13, 2019 · 2 comments · Fixed by #13006
Closed

Listener command wrongly showing "never published" #12955

AmeliaEScott opened this issue Sep 13, 2019 · 2 comments · Fixed by #13006
Assignees
Labels

Comments

@AmeliaEScott
Copy link
Contributor

Describe the bug
When running the "listener" command on the PX4 shell, it sometimes shows "never published" for topics that have absolutely been published. This happens when using the -n or -r arguments and NOT -i. Below are some examples (with the topic data removed, for brevity):

nsh> listener vehicle_attitude
  [correct topic data]
nsh> listener vehicle_attitude -i 0
  [correct topic data]
nsh> listener vehicle_attitude -i 0 -n 2
  [correct topic data twice]
nsh> listener vehicle_attitude -n 2
never published
nsh> listener vehicle_attitude -n 2 -r 2
never published

This behavior is the same in SITL.

To Reproduce
Steps to reproduce the behavior:

  1. Choose a topic that has been published (Run uorb top to find some such topics)
  2. Run the command listener <topic> and listener <topic> -i 0 -n 10 and observe correct behavior
  3. Run the command listener <topic> -n 10 and observe never published.

Drone (please complete the following information):

  • FMU V5 Test bench running the latest master branch as of the time of submitting this issue
  • Same issue in SITL
@AmeliaEScott AmeliaEScott changed the title Listener wrongly showing "never published" Listener command wrongly showing "never published" Sep 13, 2019
@AmeliaEScott
Copy link
Contributor Author

Perhaps related to #12799

@dagar
Copy link
Member

dagar commented Sep 13, 2019

Yes I was aware this slipped in with #12799 and was planning to go back and fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants