Skip to content
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.

fix: warn if maxDataSize=0 #744

Merged
merged 1 commit into from
Aug 19, 2019
Merged

fix: warn if maxDataSize=0 #744

merged 1 commit into from
Aug 19, 2019

Conversation

kjin
Copy link
Contributor

@kjin kjin commented Aug 18, 2019

Stable object ID was removed in Node 12, so maxDataSize=0 is once again dangerous to use. We warn if the user sets it to this value in Node 12.

This also disables the circular reference test for Node 12+.

Fixes #742

  • Tests and linter pass
  • Code coverage does not decrease (if any source code was changed)

@kjin kjin requested a review from a team August 18, 2019 21:49
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Aug 18, 2019
@kjin
Copy link
Contributor Author

kjin commented Aug 18, 2019

@DominicKramer FYI: You disabled a test that doesn't have to do with circular references (but it still is because of changes in the Inspector API in Node 12). I've re-enabled it conditionally running on Node 11 only.

@codecov
Copy link

codecov bot commented Aug 18, 2019

Codecov Report

Merging #744 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #744   +/-   ##
=======================================
  Coverage   85.45%   85.45%           
=======================================
  Files          13       13           
  Lines         949      949           
  Branches      193      193           
=======================================
  Hits          811      811           
  Misses         76       76           
  Partials       62       62
Impacted Files Coverage Δ
src/agent/debuglet.ts 80.16% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 444e321...2158449. Read the comment docs.

Copy link
Contributor

@DominicKramer DominicKramer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM once the tests pass.

@kjin kjin force-pushed the no-more-circ branch 2 times, most recently from 1eb7746 to 9af7c88 Compare August 19, 2019 16:47
Also, this is not reported in breakpoints in Node 12+, so modify
a test to reflect this.
@kjin
Copy link
Contributor Author

kjin commented Aug 19, 2019

@DominicKramer Why is it trying to run system tests on Node 8?

@DominicKramer
Copy link
Contributor

@kjin I think running system tests on Node 8 is an oversight. They should be run on the newest Node. We can address that issue in a followup PR.

@kjin kjin merged commit e322b6c into googleapis:master Aug 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Circular object tests are failing on master for Node 12+
3 participants