-
Notifications
You must be signed in to change notification settings - Fork 51
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
publish_subscribe example panics on MacOS #80
Comments
@bschwind could you please try it in debug mode? |
Here it is in debug mode: Subscriber
Publisher
I'll try #82 and report back |
I tried the code in #82 The event example seems to work. Here is the output of the pub-sub example - they no longer panic but I'm not sure if the behavior/output is correct. They both start up, print out some data, then seem to hang: Subscriber
Publisher
|
@bschwind I think you hit one of the open issues of iceoryx2, meaning when a process crashes we do not yet have an instance that cleans up stale resources. Could you reboot your mac and try again, please? On linux you can do a simple |
I see, thanks for the info! Sorry to bail for now but I'm in the Japan timezone and about to sleep 😅 I'll report back tomorrow with what happens after a reboot. |
…-macos iox2-#80 Fix 'clock_nanosleep' on macOS
You know what, I think I made a stupid mistake on the last check - I'm running the subscriber twice, instead of a subscriber and a publisher. That explains why they're just sitting there waiting. I also passed a But in summary, I was able to run them again with the new code and it works! Thanks for the quick response :) |
Required information
Operating system:
Rust version:
rustc 1.75.0 (82e1608df 2023-12-21)
Cargo version:
cargo 1.75.0 (1d8b05cdd 2023-11-20)
iceoryx2 version:
main
(9e5113f)Observed result or behaviour:
Run
cargo run --release --example publish_subscribe_subscriber
in the root project directory, and I receive a panic:Expected result or behaviour:
Expected to see the subscriber start and receive a message (assuming I run the publisher example as well)
Conditions where it occurred / Performed steps:
Happens on every run of the publish_subscribe example.
The text was updated successfully, but these errors were encountered: