-
Notifications
You must be signed in to change notification settings - Fork 167
BM-1859: Clean Bento Inputs #1298
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
base: main
Are you sure you want to change the base?
Conversation
|
bento section looks fine to me |
|
realizing there is a flaw with this in that currently we cache inputs to try to deduplicate, so deleting one may interfere with another if in-between preflight and prove. Will explore alternatives to see if a clean way to get around |
|
Experimented with uploading duplicate input for each order variant, can work but is pretty messy and very unideal to put more memory pressure on the REST API and unnecessary IO. Intuition is that perhaps checking the other variant is skipped/failed/completed before deleting might be a better way around this, with the tradeoff that on the race condition both check at the same time, storage is leaked. Will explore that when I work on this next |
Deletes the inputs which can be quite large (e.g. Signal) when the Order is completed or failed.
It will also delete when it fails preflights in the OrderPicker and when the OrderMonitor decides to skip.
Still testing on personal machine to see how effective this is.