Eric Cornelius
Eric Cornelius
@dusan-dragon - what is your this.restartConsumer() logic doing here? The heartbeats being reacted to in the 'consumer.heartbeat' instrumentation events are being triggered when the kafkajs consumer client is sending heartbeats...
There's something very funny going on with the build in virtual filesystem. Here's a basic reproduction script: ``` #!/bin/bash echo "const find = require('shelljs').find; console.log(process.cwd()); console.log(find('build').slice(0));" > test.js npm install...
Actually, looking at my build scripts, I may have just been silently seeding the nexe cache directory with files of the proper name, not sure that file:// protocol was supported...
Looks like it originates from this PR to me: https://github.com/nodejs/node/commit/80c0b89bbbed26eca955f4f70922fa288b664c68 I don't understand the structure of how nexe is initialized quite well enough to understand why the cjs loader is...
@calebboyd - looks like that's not the only thing which is non-functional to me - just patched it to insert `internalBinding("module_wrap").callbackMap = new SafeWeakMap();` before `initializePolicy()` and to replace the...
Ah gotcha - I'd been using `clean: true` in the nexe wrapper around make, and that's been triggering a full rebuild, instead of just codegen and a relink. Much faster...
This is new as well: https://github.com/nodejs/node/blob/master/lib/internal/modules/run_main.js And the CLI starting appears to be because `first_arg` here: https://github.com/nodejs/node/blob/master/src/node.cc#L476 is an empty string now when running the nexe build I'm guessing this...
After manually setting `std::string first_arg = "entrypoint.js";` here: https://github.com/nodejs/node/blob/master/src/node.cc#L475 The nexe build works as expected. So, I'm not sure exactly where to go from here, but hopefully at least it'll...
At the very least, I think we need to be able to configure the selected wrapper element type, This change breaks even straightforward table row lazy loading...
Does this also mean that require and import dependencies are both going to be cached as modules when using the `node:module` `register` hook? Trying to track down a very baffling...