-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
Surface task scheduling results(success/failure) from SchedulerClient #326
Comments
Agreed |
TBH, I feel the safe thing to do here is to throw an exception. This should be quite unusual. And introduce another method |
Won't it be a breaking change for people that rely on it being silently ignored? Alternatively, we can keep the existing behavior in the method, and add new ones as you suggested. |
Picking this up. Yeah, on second thought, I will just add new methods and mark the other as deprecated. |
🎉 This issue has been resolved in |
Currently SchedulerClient#schedule() function hides the failure if a task is created as duplicates.
It would be nice if the failure (or the boolean result) could be handed back to the user and let the user decide what action to take upon duplicates. Sometimes, duplicates are caused by programming bugs that are hard to detect if the failure is not surfaced.
The text was updated successfully, but these errors were encountered: