Paul Fitzpatrick

I definitely like the idea of offering UI to deal with this. Your suggestion is pretty good. If there were a suggestion that was equally tidy while also easier to...

@dsagal how inefficient would it be to replace `kd.scope(widgetObs, (widget: NewAbstractWidget) => { ...` with `kd.scope(() => [widgetObs(), row._isAddRow()], ([widget, addRow]: [NewAbstractWidget, boolean]) => {` do you think? (the first-field...

Overall, the logic here feels similar to a container health check. It seems fairly reasonable to expect that a Grist installation with multiple workers is containerized, and probably has health...

@fflorent any thoughts on the `LanguageSettings` test failure?

Ah, we use lifecycle rules on the bucket to handle that, rather than doing it in code. Is that an option for you? Sorry for not having this gotcha in...

Hmm, that's too bad. There is code for pruning snapshots at: https://github.com/gristlabs/grist-core/blob/7a0e0a9707f63e0807dfeb156b7fd54939d7fc7d/app/server/lib/DocSnapshots.ts#L20-L23 This is needed since there the logic about which snapshots to retain is very custom. It could be...

Not silly @fflorent, keeping just the latest version of `meta.json` is fine, there's no reason for it to be versioned. It can be rebuilt, it is a cache. The only...

(we used a retention policy since at the time this feature was built, we were focused on our own SaaS, and retention policies were available and easy)

It does seems a good idea. For UI, I could imagine an editable region in the Code Viewer. The data engine would need a bit of tweaking to make it...

Thanks @rouja! The overall change makes sense, I'm just trying to think about how to handle the impact on existing users, specifically if files in /persist become unwritable. I think...