runtime

Version

v16.10.0

Platform

Linux solus 5.14.7-198.current #1 SMP PREEMPT Wed Sep 22 16:02:46 UTC 2021 x86_64 GNU/Linux

Subsystem

stream

What steps will reproduce the bug?

const {Writable} = require('stream');

class X extends Writable {
    async _destroy(error, callback) {
        (async () => {
            await new Promise(resolve => setTimeout(

We can build much smaller Mono runtime for .NET Core purposes by simply removing code we don't need in this configuration. We did a few easy initial steps but we can go much further.

This list is not comprehensive but parts like

• Culture Data
• Any PAL related code
• Unused icalls

• Source

JsPointerToString(NULL, 0, &str);

• Expected
  str = empty string

• Actual
  failed and returns JsErrorNullArgument

I think this should be possible

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

Current, if we try to run a more recent Java class in an old JVM, we get the following error message:

Error: LinkageError occurred while loading main class some.Class
	java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=some/Class, offset=6

However, it is not so easily to detect that the class was compiled with a version above the supported by the JVM.Hotspot

Tons of good improvements that can be made to the codebase:
https://deepsource.io/gh/elsaland/elsa/issues/?category=recommended

If a new Environment is created, processes inside of it will not have access to any command line arguments or environment variables by default. They need to be added to the ConfigEnv struct from which the Environment is created. Currently this is only possible from the host, but is not exposed as a [host function

With #235 I've noticed that InstanceOf is undocumented in the readme.

Add a dark/light mode switch in the menu.
The semantic-ui framework already handles that.
The thing is to also change the plot background color when in dark mode.