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

Can't Ctrl-C decoder out of waiting for LSL stream #50

Open
charlesbmi opened this issue Oct 12, 2023 · 2 comments
Open

Can't Ctrl-C decoder out of waiting for LSL stream #50

charlesbmi opened this issue Oct 12, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@charlesbmi
Copy link
Contributor

Describe the bug

If a script like decoder is run without the appropriate LSL stream, the script gets stuck. That part is expected behavior, but Ctrl-C doesn't exit out of the script, so it is necessary to close the terminal or kill the Python process.

Steps to reproduce

Replace this text with a code snippet or minimal working example to replicate your problem.

❯ decoder
INFO [nds-decoder]: Using settings from '/Users/charles/.nds/settings_decoder.yaml'
^C

(Does not exit script).

Include a description of your setup including:

  • Python version: 3.11.5
  • OS version and name: {'system': 'Darwin', 'node': 'charles-macbook.lan', 'release': '22.6.0', 'version': 'Darwin Kernel Version 22.6.0: Wed Jul 5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000', 'machine': 'arm64', 'processor': 'arm'}

Expected results

Script exits on Ctrl-C.

Actual results

Script does not exit:

image
@charlesbmi charlesbmi added the bug Something isn't working label Oct 12, 2023
@charlesbmi charlesbmi changed the title Running decoder gets stuck waiting for LSL stream, can't Ctrl-C Can't Ctrl-C decoder out of waiting for LSL stream Oct 13, 2023
@charlesbmi
Copy link
Contributor Author

Looks like this is a direct result of: labstreaminglayer/pylsl#35

@charlesbmi
Copy link
Contributor Author

If I understand labstreaminglayer/pylsl#35 (comment) correctly:

resolve_stream is a legacy function and is hence just in place to prevent older projects from breaking

we should move away from the resolve_stream legacy function.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant