glue.js | Implements Object.watch for javascript objects | Runtime Evironment library

For anyone who comes across this, the problem was that karma-typescript automatically enables code-coverage so I just had to add a setting to disable it and enable source maps

In my karma config

The data being written had some fields that were "optional". The Item being written was like:

So i was able to sort this issue, the underlying issue is with axios library being used by google auth library (v1.3.2)

here is the issue : https://github.com/axios/axios/issues/662

The workaround for me was to replace axios with request promise in google auth library and then publish it in our private npm registry, this solved the issue for now.

Is there a reason why you're not using https://github.com/pact-foundation/pact-js?

Pact Node is a lower level library probably not ideally suited to what you're doing. Pact JS is the higher level DSL for tests as you've created.

There is a TypeScript example in there.

update: you might need to increase the timeout, it seems your system is taking longer than 2s to start the mock server and is bailing.

The second error described looks unrelated to pact.

Short answer: Your Module already uses WebAssembly.instantiateStreaming() behind the scenes.

Long answer: Emscripten (emcc) is not only a compiler, but also a whole toolchain infrastructure. When you use the emcc command, emcc calls clang compiler to compile your C code to WASM, links necessary JS code to use in the WASM using imports, and generates a boilerplate JS code (it's called preamble.js) to instantiate the WASM code for Module so that devs don't need to write your own code to write bootstrapping code.

Look at your glue.js code. You can find a line that uses WebAssembly.instantiateStreaming(). Unless you use emcc without -s SIDE_MODULE=1 option, it always generates preamble.js code for you. So normally you don't need to use WebAssembly on your own.

Some advanced users don't want this big boilerplate and use WASM in harder way, like using clang without emcc. Then they need to use WebAssembly including instantiateStreaming() themselves.

A long time later I learned that my docker container hadn't successfully finished all of it's operations before I was saving the image. When I fixed that, this problem went away. X11 runs fine in a Docker container / AWS Fargate.

So my question basically is how to do the above example in Audioworklet,

For your first example, there is already an AudioWorklet version for it: https://github.com/GoogleChromeLabs/web-audio-samples/blob/gh-pages/audio-worklet/basic/js/noise-generator.js

I do not recommend the second example (aka buffer stitching), because it creates lots of source nodes and buffers thus it can cause GC which will interfere with the other tasks in the main thread. Also discontinuity can happen at the boundary of two consecutive buffers if the scheduled start time does not fall on the sample. With that said, you won't be able to hear glitch in this specific example because the source material is noise.

when the data is generated continuously in the main thread in some array and the playback of that data is happening in the Webaudio thread.

The first thing you should do is to separate the audio generator from the main thread. The audio generator must run on AudioWorkletGlobalScope. That's the whole purpose of AudioWorklet system - the lower latency and the better audio rendering performance.

In your code, VGMPlay_WebAudio.generateBuffer() should be called in AudioWorkletProcessor.process() callback to fill the output buffer of the processor. That roughly matches what your onaudioprocess callback does.

I've been reading about the messageport thing, but I'm not sure that's the way to go either. The examples don't point me into that direction I'd say. What I might need is the proper way to provide the process function in the AudioWorkletProcesser derived class with my own data.

I don't think your use case requires MessagePort. I've seen other methods in the code but they really don't do much other than starting and stopping the node. That can be done by connecting/disconnecting AudioWorkletNode in the main thread. No cross-thread messaging necessary.

The code example at the end can be the setup for AudioWorklet. I am well aware that the separation between the setup and the actual audio generation can be tricky, but it will be worth it.

Few questions to you:

1. How does the game graphics engine send messages to the VGM generator?
2. Can the VGMPlay class live on the worker thread without any interaction with the main thread? I don't see any interaction in the code except for starting and stopping.
3. Is XMLHttpRequest essential to the VGMPlay class? Or can that be done somewhere else?

You are running python on Windows, where the default encoding is cp1252. The json is encoded as utf-8, hence the error.

When you require an NPM package, depending on your module system¹, the default export will not automatically be imported when you do this: