You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Libsweep on commit 8539c1c, compiled with -DCMAKE_BUILD_TYPE=Release
Also (with some effort) reproducable with the scanse tool on Windows.
Affected bindings: probably all, I'm currently using my own Haskell binding.
operating system
Linux (NixOS), Windows (with scanse tool)
Platform/Hardware Setup
Tested with Scanse sweep V1.0
How to reproduce
Disconnect Scanse device from USB
Run a program that tries to open /dev/ttyUSB0 every 100ms or so. Ignore the opening serial port failed error and just keep trying.
Connect the Scanse device while this program is running.
Find that the program is blocking on the sweep_device_construct C call indefinitely.
Motivation
This negatively affects the stability of the device. I've written a program that will try to reconnect to the device after it disconnects. With this bug the program freezes and I have to resort to timeouts. A device not ready exception or an internal retry mechanism would be appreciated.
The text was updated successfully, but these errors were encountered:
sweep firmware version
1.4
libsweep version + affected bindings
Libsweep on commit 8539c1c, compiled with
-DCMAKE_BUILD_TYPE=Release
Also (with some effort) reproducable with the scanse tool on Windows.
Affected bindings: probably all, I'm currently using my own Haskell binding.
operating system
Linux (NixOS), Windows (with scanse tool)
Platform/Hardware Setup
Tested with Scanse sweep V1.0
How to reproduce
/dev/ttyUSB0
every 100ms or so. Ignore theopening serial port failed
error and just keep trying.sweep_device_construct
C call indefinitely.Motivation
This negatively affects the stability of the device. I've written a program that will try to reconnect to the device after it disconnects. With this bug the program freezes and I have to resort to timeouts. A
device not ready
exception or an internal retry mechanism would be appreciated.The text was updated successfully, but these errors were encountered: