-
Updated
Feb 8, 2021 - Rust
sandbox
Here are 1,102 public repositories matching this topic...
fuzzing: Use `wasm-encoder` rather than generating WAT text and then assembling it in dummy imports
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
-
Updated
Feb 6, 2021 - Swift
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.
-
Updated
Feb 1, 2021 - C++
-
Updated
Feb 5, 2021 - JavaScript
-
Updated
Feb 19, 2019 - C
-
Updated
Dec 2, 2020 - JavaScript
-
Updated
Feb 4, 2021 - C++
-
Updated
Jan 10, 2021 - Shell
-
Updated
Aug 24, 2018 - JavaScript
At least if the user hasn't taken a screenshot the open screenshots button just silently fails.
Instead it should show a warning popup that the folder doesn't exist and suggest taking a screenshot and then trying again.
The same probably also applies to the browse saves folder button so that should also have a warning popup, and suggesting the player to make a save first.
I think it's fine to
-
Updated
Oct 6, 2020 - Python
-
Updated
Oct 5, 2020 - Python
-
Updated
Feb 6, 2021 - C#
-
Updated
Jan 19, 2019 - C
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.
-
Updated
Jan 6, 2020 - C++
-
Updated
Feb 2, 2021 - Ruby
#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
I created a new issue to separate the last we've discuss in issue nestybox/sysbox#118.
-
Updated
Jan 20, 2021 - Python
-
Updated
Feb 4, 2021 - C#
-
Updated
Feb 6, 2021 - Go
-
Updated
Jan 26, 2021 - Go
-
Updated
Jan 30, 2021 - JavaScript
Improve this page
Add a description, image, and links to the sandbox topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the sandbox topic, visit your repo's landing page and select "manage topics."


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.