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

[2SP, 2SP] Implement DNS support in GnuRadioWorker service #159

Closed
frankosterfeld opened this issue Feb 23, 2024 · 3 comments · Fixed by #168
Closed

[2SP, 2SP] Implement DNS support in GnuRadioWorker service #159

frankosterfeld opened this issue Feb 23, 2024 · 3 comments · Fixed by #168
Assignees

Comments

@frankosterfeld
Copy link
Contributor

Ensure that the signal name properties are read from the signal_name properties configured at the source (like PicoScope) and registered at the DNS. The DNS entries should be dynamically update as the signal_name properties in the flow graph's data sinks change.

@frankosterfeld frankosterfeld self-assigned this Feb 26, 2024
@frankosterfeld frankosterfeld linked a pull request Feb 29, 2024 that will close this issue
@frankosterfeld
Copy link
Contributor Author

frankosterfeld commented Feb 29, 2024

This builds on top of #160 , which needs to be merged first.

In addition, this depends on

fair-acc/gnuradio4#281 : the service needs to learn about any signal_name/signal_unit etc. change inside the graph, while the graph is executed.

@frankosterfeld
Copy link
Contributor Author

Work unblocked (as Ivan's settings message patch is in)

@frankosterfeld
Copy link
Contributor Author

frankosterfeld commented Mar 5, 2024

Ready for review. Dependencies to #160 still persist.

@frankosterfeld frankosterfeld changed the title [2SP] Implement DNS support in GnuRadioWorker service [2SP, 2SP] Implement DNS support in GnuRadioWorker service Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: QA-Accepted/Merged (∞)
Development

Successfully merging a pull request may close this issue.

1 participant