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

TODOs #26

Open
sequoiap opened this issue Feb 14, 2022 · 0 comments
Open

TODOs #26

sequoiap opened this issue Feb 14, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@sequoiap
Copy link
Collaborator

An always-open issue just listing possible features to evaluate and implement. As we decide on each, we'll make a new issue for it.

  1. Implement for the daemon an active connection count and listing, and the ability to close out other connections, for load management. Perhaps a connection was not closed and is just hogging resources or something.
  2. Can PyroLab only restart changes in the config file from the CLI?
  3. Add the option to also log to console.
  4. DaemonConfiguration probably doesn't need the ns_host item.
  5. Implement autoconnect for scopes?
  6. PyroLab should check on autoconnect/connect if it's already connected. If it is, don't raise an error; just reuse the same connection.
  7. Double check that remote tracebacks are working properly.
  8. Add a "pip install pyrolab[all]" option.
@sequoiap sequoiap added the enhancement New feature or request label Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant