Andrey Novoseltsev

It was not that easy. It seems that behaviour is a bit random with shorter notebooks, while with the one including relatively long code and mix of plots and dataframes...

One option is to make what is displayed depend on existence of any automatic payment method on file (including sufficient balance to cover the next charge). Another is to add...

Not some random user, but **I** got pretty scared seeing this message for a large scale subscription:  There is a message about update to automatic payments required on the...

My understanding is that the label is determined by https://github.com/sagemathinc/cocalc/blob/master/src/packages/frontend/purchases/subscriptions.tsx#L60 If "unpaid" status is essential for inner workings and subscription renewal, which certainly may be the case, I would at...

I don't recall exactly, but I have tried it as well as clicking "Default layout". Either nothing or maybe the screen got cleared, but there were still no reaction to...

A closely related silly issue:  Not only there is an extra zero where there should be none, but the hover over is less precise and they also disagree in...

Still the case. For minimum balance there is no need for hover over precision, it is likely to be a nice round number always.

"CoCalc credit voucher ..." or just "Voucher ..." without any mention of cash or money ;-) It think that would be fine solution - the checkout dialog can be kept...

I actually don't know - what should I be doing when there is a "Not saved" message? And, perhaps equally important - what I should NOT be doing? Should I...

I am very much against configuring a separate limit for every single bloody model! Having separate limits for LLMs/network/compute servers in theory makes sense, but I think won't really matter...