Upgrade to rusty_v8 0.10.0 / V8 8.7.75

[piscisaureus]

No description provided.

[piscisaureus]

This is red because 'ts_decorators' failed, but that test is unsound (it has for example never passed for me locally).

Proposal is to land this PR and if you care enough we can delete the ts_decorators test.

[ry]

I'm fine with disabling the test and landing this - but it's confusing why would upgrading rusty_v8 effect this one random test...

[bartlomieju]

What's even more strange is that I get proper output on Mac and test passes. It seems class name is not printed on Linux 🙄 I guess we can disable this test for know, but this situation looks like V8 bug.

[piscisaureus]

My suspicion is that something gets compiled, then written to cache, then restored from cache, and there's a race condition in all this.

A V8 bug is certainly not out of the question but the fact that it happens on some systems only (and older versions of V8 too, just not on CI) makes me think that's an unlikely explanation.

[bartlomieju]

My suspicion is that something gets compiled, then written to cache, then restored from cache, and there's a race condition in all this.

I think that's unlikely, ts_decorators.ts is used only in this single test.

Should we land this PR before 1.4.0?

[bartlomieju]

@piscisaureus https://v8.dev/blog/v8-release-86#small-normative-changes <--- this might be the reason ts_decorators broke during the update