| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM but I would suggest adding a test to ensure the warning message you added is displayed under and only under the conditions in which it should be displayed.
Sorry, something went wrong.
|
Just a note, we should not land this yet since the method for getting stable object ID will change. Once the functionality is committed to V8, I will provide an update. |
Sorry, something went wrong.
|
This fix should work once this is landed on v10/v11: nodejs/node#23886 |
Sorry, something went wrong.
|
@DominicKramer Not yet, see my previous comment. The PR has to get merged first, then backported to v10/v11, and then released. |
Sorry, something went wrong.
Sorry, something went wrong.
|
This is blocked on release of Node 10.15.2 10.15.3, followed by Kokoro image updates for Node 10/11 |
Sorry, something went wrong.
Codecov Report
@@ Coverage Diff @@
## master #524 +/- ##
==========================================
- Coverage 92.91% 92.88% -0.03%
==========================================
Files 38 38
Lines 3556 3570 +14
Branches 106 108 +2
==========================================
+ Hits 3304 3316 +12
- Misses 229 230 +1
- Partials 23 24 +1
Continue to review full report at Codecov.
|
Sorry, something went wrong.
|
@googleapis/node-team This is finally ready to re-review and land, now that 10.15.3 is out. PTAL. |
Sorry, something went wrong.
|
Is this really still blocked? |
Sorry, something went wrong.
|
@JustinBeckwith I guess it is not now. When I set the blocked label I didn't see Kelvin's last comment. |
Sorry, something went wrong.
|
There will be a slight code coverage decrease because we can't pin old versions of Node to test that a warning message appears on those versions. I think this is fine as we know quite clearly which change introduced the fix we needed: 10.x, 11.x. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This allows us to properly represent objects with circular references in Node 10+, unless capture.maxDataSize=0, which will only be fixed once stableObjectId is introduced in Node 10. See #516