Currently validating checksums requires lots of knowledge on the part of the caller. We should expose optional checksum validation in our existing validation functions e.g. IPv4.IsValid.

header.UDP and header.TCP don't currently have these functions; we should add them.

In bytecodealliance/wasmtime#2497 (comment) we added support for generating nested modules, and we generate these modules by concatenating strings of WAT and then passing it to Module::new which internally checks for WAT strings and assembles them into Wasm bytes if necessary.

We can make this more efficient, improving the number of test cases we fuzz in a

Use Case

As a developer, I want to join a multiplayer server as a new user, as if I were joining it for the first time. Even though I had previously logged in to it with this client.

I tried changing my "Player Name" in the player settings. That changed the way my name displays, but still connects me to my previous character.

Discussion

This can be done by removing the `security.

Need to add the text to MainMenu.CallMiscTranslations and that should be it

Regressed in DMOJ/judge-server#673, since now the cache is per-worker-process, and gets destroyed on exit. Will require a rewrite of the caching system.

I created a new issue to separate the last we've discuss in issue nestybox/sysbox#118.

#400

There are numerous areas in the kernel where a heap allocation failure is being silently ignored, merely asserted against or otherwise mishandled. Assertions may suffice for allocations on initialization (where system bringup would otherwise be impossible), but allocation failures which may reasonably happen during runtime must be addressed.

See, for example, #1199; all the various calls to the