The TLDR:
> We tackled critical container image bloat on our Sealos platform, fixing a severe disk space exhaustion issue by shrinking an 800GB, 272-layer image to just 2.05GB.
They say they made a 800GB container image, so your issue is about singular vs plural?
Regardless, I don't really get why anyone would self report like this. Is next article going to be about how they don't encrypt passwords and when they accidentally dropped prod DB they could restore account from logs because it had the passwords in clear text?
When I've used i2s it has required setting spi clocks that made my spi devices not function. While it does have all of these IO buses, using more than one at a time is a bit of tetris. I wouldn't be surprised if there is some hardware constraint making i2s impossible.
I've found this to be particularly true with William Gibson, tried to listen to some but a split second lapses in attention forcing me to go back often and I gave up. And just pick up a text.
I built a tool to create "average llm" probability of code for checking how aligned code is with what an LLM would output. Working on adding context from a project to check how the style of a section aligns with the style, content and domain of a project.
Idea is to use it to identify code that sticks out, because that usually what's interesting or bad.