Michaël Zasso

> I think we'll need to change it to the GitHub changelog. Example: https://github.com/nodejs/node/releases/tag/v18.9.0 There's another limitation on this. I had to truncate https://github.com/nodejs/node/releases/tag/v16.17.0 because the number of characters is...

No. There's at least a client-side check that just prevents from entering more characters: 

Is it different to the logistic regression (which we have)?

This seems like a useful feature. Pull request welcome (please add test cases and update `matrix.d.ts`)! We suggest the following signature: ```ts class Matrix { applyAlongAxis( callback: (vector: number[], index:...

In the V8 repo: https://github.com/v8/v8/blob/50504b168d2c364d49e3332cbd934dc60a4bfad8/src/base/platform/memory.h#L117-L118 Introduced by https://chromium-review.googlesource.com/c/v8/v8/+/3858226 In this repo (canary is updated every day so the commit is ephemeral): https://github.com/nodejs/node-v8/blob/4e97ad7ae1c6d4639f227094f3270de44214c4f1/deps/v8/src/base/platform/memory.h#L117-L118

> The fix looks straight-forward (add V8_OS_SOLARIS to the exclusion list for V8_HAS_MALLOC_USABLE_SIZE on line 26, similar to AIX) but I assume I'll need to get this through the v8...

Du coup j'ai déplacé cette issue dans CoC.

@nodejs/build-infra there seems to be an issue with `test-nearform_intel-ubuntu1604-x64-1`: ``` 11:15:39 [0:00:42] fatal: unable to access 'https://chromium.googlesource.com/chromium/src/third_party/jinja2.git/': Could not resolve host: chromium.googlesource.com ```

So, `node-test-commit-v8-linux` isn't broken. Now I don't know how to try it with `ENABLE_CONVERT_V8_JSON_TO_XML`.

@richardlau do you have a suggestion about what we should do now?