User scrolling is currently not emitted as an onScroll event. What's the reason for this? Is this really intended?
I'd like to monitor the scroll state of the terminal in order to notice when it's scrolled al

there are frequently issues like #5646 with people wondering why their files are classified as M)odified and read/chunked again.

we could all some logging that precisely tells:

• a files cache miss (filename key not in files cache)
• a timestamp mismatch (also telling which filestamp it is ctime or mtime)
• an inode number mismatch
• a size mismatch

there should be no output for cache hi

What would you like to be added

Add support for a DynamoDB storage backend. Although MySQL is available, it would require to run a RDS Instance for it. Extra costs, backup considerations, etc. Even with Aurora Serverless.

DynamoDB is just there, scales as needed with OnDemand pricing and has fine backup capabilities.

Why this is needed

We plan to run step-ca in AWS ECS on Farga