Michaël Zasso
Michaël Zasso
I reopened because the error was wrong, but I still think the failure was expected (Jenkins CI had a failure).
But why did ncu say "Last Jenkins CI successful" when https://ci.nodejs.org/job/node-test-pull-request/48124/ is clearly red?
I had a look and it's because of this part of the code: https://github.com/nodejs/node-core-utils/blob/4ef0fe2607f3986f702bcd1ada244965cfcd4457/lib/pr_checker.js#L393-L410 It's actually the Jenkins CI check that is red. I wonder if we should remove this...
We do not maintain this project anymore. I recommend to use piscina if you want this kind of functionality in Node.js: https://github.com/piscinajs/piscina
> The build email alias has been sent this from IBM. Are you sure about that? I can't find this in my emails.
I don't have an IBM Cloud account yet. Last time I tried to create one it didn't work.
> I don't have an IBM Cloud account yet. Last time I tried to create one it didn't work. Still not working...
I like that idea! I made a quick PoC here: https://github.com/targos/node/commit/c4f5e91ca4d4219e13f6f18f14b6101a26f96be5 ``` $ ./node --no-warnings --loader "data:text/javascript," poc.mjs initialize loader { entryPoint: '/Users/mzasso/git/nodejs/node/poc.mjs' } loader initialized ```
How should we start the discussion? Depending on what we are talking about, this might interest the `@nodejs/fs` team, and people working on the permissions model. Maybe we should try...
What about this idea: add a CLI flag to make the process abort (so it cannot be caught by the caller) whenever permission is denied?