In 48dac81500ca4a588b6cf1d1b609a2326f6cf7d2, I discovered that the key-value expiration loader task was interfering with reliably persisting keys. There's a TODO in the expiration_after_close test referencing the need for a way to shut down the database and wait for tasks to finish.
There are some questions to answer:
How might this work in conjunction with #33?
Should this completely close Nebari as well? If so, can a Storage/Database reference point to a shut-down instance?
In 48dac81500ca4a588b6cf1d1b609a2326f6cf7d2, I discovered that the key-value expiration loader task was interfering with reliably persisting keys. There's a TODO in the
expiration_after_closetest referencing the need for a way to shut down the database and wait for tasks to finish.There are some questions to answer: