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.

Sign up for GitHub

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

Jump to bottom

ReschedulingOperation signalToRunImmediately() may not work as expected if task is currently running #228

Open
jentfoo opened this issue Mar 26, 2018 · 0 comments
Open

ReschedulingOperation signalToRunImmediately() may not work as expected if task is currently running #228

jentfoo opened this issue Mar 26, 2018 · 0 comments
Labels
bug

Comments

@jentfoo
Copy link
Member

jentfoo commented Mar 26, 2018

if signalToRunImmediately(Boolean) is invoked while the task is currently running, then when the task finishes it will schedule itself out the configured delay, rather than invoking itself again immediately.

This defect is not currently causing any cascading flaws within threadly (nothing currently depends on that behavior), but it would be good to clean up for (advanced) external users of the library.
@jentfoo jentfoo added the bug label Mar 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jentfoo