You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before releasing version 1.0.0, I thought it would be better to let users choose their own sleeper implementations, so I didn't enable them by default. However, many users encountered runtime panics. I apologize for not finding a solution that meets all requirements simultaneously: no API breaks, allowing sleeper passing at runtime, and no extra cost.
So in version 1.1.0, I have added tokio-sleeper and gloo-timers-sleep to the default feature. This change will make BackON behave like version 0.4.4, allowing users to upgrade without adding new features. Additionally, I have moved the panic to occur earlier during the poll feature instead of during the sleep call. This makes it easier to catch issues during development rather than at runtime. Furthermore, we will only panic during the debug profile and do nothing in the release profile. This should protect users from panics even in the worst-case scenarios.
Please let me know if you have better solutions! Thanks in advance!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
A Letter to BackON Users
Hello everyone,
Thank you very much for using BackON!
Before releasing version
1.0.0
, I thought it would be better to let users choose their own sleeper implementations, so I didn't enable them by default. However, many users encountered runtime panics. I apologize for not finding a solution that meets all requirements simultaneously: no API breaks, allowing sleeper passing at runtime, and no extra cost.So in version
1.1.0
, I have addedtokio-sleeper
andgloo-timers-sleep
to thedefault
feature. This change will make BackON behave like version0.4.4
, allowing users to upgrade without adding new features. Additionally, I have moved the panic to occur earlier during thepoll
feature instead of during thesleep
call. This makes it easier to catch issues during development rather than at runtime. Furthermore, we will only panic during thedebug
profile and do nothing in therelease
profile. This should protect users from panics even in the worst-case scenarios.Please let me know if you have better solutions! Thanks in advance!
Xuanwo
What's Changed
Full Changelog: v1.0.2...v1.1.0
This discussion was created from the release v1.1.0.
Beta Was this translation helpful? Give feedback.
All reactions