Paul Fitzpatrick

> We propose another strategy: run the VACUUM when a document is being closed for inactivity and if no shutdown is in progress. This way, we hope that's much less...

> Errors seems to be related to our work: > > ``` > 1) ActiveDocShutdown > "after each" hook for "should not close ActiveDoc while loading": > Error: Timeout of...

Hi @fflorent, there is some existing auto-pruning logic: https://github.com/gristlabs/grist-core/blob/7bae7a86bf45ac66085cddd27e7562961e038688/app/server/lib/ActionHistoryImpl.ts#L16-L23 Making it configurable would be easy and desirable. Pruning to 0 would currently leave the document unusable, since in there is...

External storage of history is attractive since documents could retain hashes of history items - these already exist - and only consult their actual content when needed, such as for...

Thanks @hellpe. This reminds me of this possibly related issue https://github.com/gristlabs/grist-widget/pull/176 - @dsagal what do you think?

> Hi, I begin to check how to implement that on Grist. I see multiple commented code about "remove" trigger event types. I want to know why is commented ?...

Thanks for reporting. In principle this should have been done for grist-core, I guess the behavior has rusted? https://github.com/gristlabs/grist-core/pull/745

> I am not sure how the bundling would help there unless the npm packaging of grist-widgets gets rid of those. Yes, that's exactly what it does - crawls them,...

Thanks for reporting, we have neither gotten around to implementing update checking, or removing it from the menu.

> Gristlabs people do you have an opinion on the wanted behavior in grist ? (@paulfitz @dsagal @anaisconce) Yohan's arguments about the sanest behavior are persuasive to me. In general...