-
Notifications
You must be signed in to change notification settings - Fork 99
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
fix: Don't delete existing flags on decide errors #621
Conversation
This seems to be off: the whole point of this library being stateful is to not bork when decide sporadically errors out. This means flags can go stale if decide is down for a long time, _but_ you wouldn't lose all flags - which can be a much bigger hindrance.
Size Change: +4.82 kB (0%) Total Size: 2.31 MB
ℹ️ View Unchanged
|
Adding Marius & Ben as reviewers too - if you have any context why this should stick around |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah you're right. Not sure why that's there... only think I wish is that there was a test for this....
Yep yep, will add, alongside some rate limit specific handling 👀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤷
This seems to be off: the whole point of this library being stateful is to not bork when decide sporadically errors out.
This means flags can go stale if decide is down for a long time, but you wouldn't lose all flags - which can be a much bigger hindrance.
Changes
...
Checklist