-
Notifications
You must be signed in to change notification settings - Fork 1
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
Using an earliest { ... wait 0 { ... } } causes #4302
Comments
From @hoelzroThe attached script reproduces the issue. When I use earliest with a wait 0 block, I get the following error message: No exception handler located for last_label Interestingly enough, if I increase 0 to some arbitrary timeout, this affects the bug; I've found if I keep it below 220ms, it triggers the bug. Going higher fixes the problem. |
From @AlexDanielwhat is `earliest`, `more` and `wait`? On 2015-06-06 16:40:28, rob@hoelz.ro wrote:
|
The RT System itself - Status changed from 'new' to 'open' |
From @lizmatThose are predecessors of the “react / whenever” syntax. I think that therefore this ticket can be closed now.
|
From @AlexDanielAlright. On 2017-12-03 00:53:04, elizabeth wrote:
|
@AlexDaniel - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#125343 (status was 'rejected')
Searchable as RT125343$
The text was updated successfully, but these errors were encountered: