-
Notifications
You must be signed in to change notification settings - Fork 71
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
Inlet does not return info if it was queried once before the stream was open on Ubuntu 20.04 and 22.04 #179
Comments
I wouldn't have thought to use liblsl this way. I either construct an info for creating an outlet, or I get an info from a resolver for creating an inlet. I wouldn't have thought to use a manual stream_info to create an inlet. After all, how do you know a stream exists and you can connect to it if not for finding the streaminfo via a resolver? But I might be wrong; we seem to have a unit test implying this is a valid workflow: However, if I augment that unit test trying to do anything with the inlet ( I honestly don't know why the @tstenner , should someone be able to create a valid inlet from a hand-made stream_info? How about from an outlet.info()? |
The stream_inlet constructor docstring implies that this should work though it is discouraged.
|
I found this surprising behavior using the python binding, which hints to a bug in the C++ library as the methods invoked are one-line wrapper around the C++ functions.
If you open the stream and then query for the attached
StreamInfo
, it works.If you query for the attached
StreamInfo
an inlet that did not open the stream first, it fails withTimeoutError
as it should. But if you then open the stream and query again for the attachedStreamInfo
, instead of working it raises aTimeoutError
again.Note that this behavior was observed on CIs running
ubuntu-latest
and on my debian 22.04 LTS (POP_OS) machine and on codespace running Ubuntu 20.04 LTS, using the 1.16 version of the library for the 20.04 (focal) version.This behavior is not observed on macOS or on Windows. On those 2 OS, the last call does not timeout and returns the
StreamInfo
.The text was updated successfully, but these errors were encountered: