Skip to content
#

sandbox

Here are 1,319 public repositories matching this topic...

fitzgen
fitzgen commented Dec 11, 2020

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

good first issue fuzzing
thomasballinger
thomasballinger commented Aug 1, 2021

Related to metering wasm3/wasm3#127 and being able to run a set number of instructions, I'd like to be able to serialize a paused interpreter's state and deserialize it to a new interpreter instance; very roughly,

const interp = new wasm3.Interpreter(module);
interp.interpretNInstructions(100);
const interpState = interp.serializeState();
const interp2 = wasm3.In
feature help wanted good first issue
Terasology
jdrueckert
jdrueckert commented Jan 22, 2022

Motivation

Working with our game logs, for instance when investigating a crash or other kind of issue, is annoying because there's a lot of (unnecessary) noise in them, that we learn to accept / ignore instead of reducing it.
One part of the log noise is complaints regarding unknown components or component fields.

Proposal

  1. Investigate the common complaints regarding unknown co
Status: Needs Investigation Good First Issue Topic: Stabilization Type: Chore
sandpack
danilowoz
danilowoz commented Feb 18, 2022

Currently, a lot of operations are being done in the componentDidUpdate, and as Dan mentioned on #377 this is a pattern that must be avoided, in order to prevent nested updates. So, we need to find out how to improve this method and address other performances issues that this might be causing.

I haven't gone any further and haven't collected evidence of any performance issues, but as the curr

good first issue feature:request triage
nanos
wjhun
wjhun commented Mar 24, 2021

The virtio_scsi driver enqueues buffers to the eventq but does not actually handle them on completion. The following events could be reported to the driver which require some action to be taken:

  • transport reset: This may occur as a result of hotplug events or a device being reset. Sense codes cannot be relied on when new devices or busses appear, so this event needs to be handled.
  • asynchro
Thrive
judge-server

Improve this page

Add a description, image, and links to the sandbox topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the sandbox topic, visit your repo's landing page and select "manage topics."

Learn more