-
-
Notifications
You must be signed in to change notification settings - Fork 42
synchronize() not work as expected #275
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
Comments
Well, it is kind of expected. This trajectory is equivalent to the one above: p = trajectory() %>%
clone(
n = 2,
trajectory() %>%
renege_in(
t = 1, out = trajectory() %>%
synchronize(wait = FALSE) %>%
log_('leave')) %>%
timeout(5),
trajectory() %>%
timeout(3) %>%
synchronize(wait = FALSE) %>%
log_('leave')
) Note what I did: I just replaced the p = trajectory() %>%
clone(
n = 2,
trajectory() %>%
timeout(1) %>%
synchronize(wait = FALSE) %>%
log_('leave'),
trajectory() %>%
timeout(3) %>%
synchronize(wait = FALSE) %>%
log_('leave')
) In essence, there are two distinct |
Oh I see. Thank you! |
Let me explore the possibility of setting a global storage for sync activities. Otherwise, I see no way of reneging and synchronizing. |
Created on 2022-03-04 by the reprex package (v2.0.1)
I expect that with wait=FALSE, only the first arrival can reach log_("leave").
Anyway, thank you guys for an amazing pacakges!
The text was updated successfully, but these errors were encountered: