[HELP WANTED] Fix bugs in named interceptor test.#781
[HELP WANTED] Fix bugs in named interceptor test.#781mkrufky wants to merge 4 commits intonodejs:masterfrom
Conversation
Copied, more or less, from commit 946377f Returning a string in the enumerator was never allowed but wasn't enforced until recently. In Node.js 10, it hits a CHECK in V8.
|
Seems like this was not the right fix, the array elements must be strings (or symbols) https://github.com/nodejs/node/blob/master/deps/v8/include/v8.h#L5134 |
|
Well, it wasn't as simple as 946377f :-P I tried, but I'm closing this. |
|
I suppose it must be some recent Node.js change because it wasn't failing for me two weeks ago when I fixed the other test. I'll have a look. |
|
#782. Note it didn't hit a CHECK for me but the |
Yes, I remember everything passing after the indexed interceptor test fix, which confused me now. Semver, schmemver... I am happy it is sorted out now. |
|
I'm reasonably sure it's caused by nodejs/node#20350, which I would say is a legitimate bug fix (but I signed off on it so of course I would say that :-)) |
|
I don't think it was caused by a new regression - the named interceptor test was failing the moment we added node 10 to the matrix: ...but it's passing now. Thanks :-) |
Copied, more or less, from commit 946377f
Returning a string in the enumerator was never allowed but wasn't
enforced until recently. In Node.js 10, it hits a CHECK in V8.
This builds, but the tests fail:
I'm not sure what else is needed but this is at least a starting point for fixing the Node 10 CI failure.