-
Notifications
You must be signed in to change notification settings - Fork 0
Ric/sig 90152 resync fork2 #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
updSocketOptions are set when protocol is `udp` not `uds`. Simple fix!
* Add gaugeDelta implementation * Update type definitions * Add gaugeDelta to statsFunctions * Address double negative * Update README * Add gaugeDelta-specific tests
Bumps [word-wrap](https://github.com/jonschlinkert/word-wrap) from 1.2.3 to 1.2.4. - [Release notes](https://github.com/jonschlinkert/word-wrap/releases) - [Commits](jonschlinkert/word-wrap@1.2.3...1.2.4) --- updated-dependencies: - dependency-name: word-wrap dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3. - [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md) - [Commits](micromatch/braces@3.0.2...3.0.3) --- updated-dependencies: - dependency-name: braces dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [@babel/traverse](https://github.com/babel/babel/tree/HEAD/packages/babel-traverse) from 7.20.13 to 7.25.6. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md) - [Commits](https://github.com/babel/babel/commits/v7.25.6/packages/babel-traverse) --- updated-dependencies: - dependency-name: "@babel/traverse" dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Handle synchronous socket.send error in sendUsingDnsCache We are using UDP with DNS caching in production and noticed the occasional unhandled exception in our application when the datadog agent is unavailable. We tracked it down to the lookup branch of `sendUsingDnsCache` which calls `socket.send` within a callback. `socket.send` can throw a sync exception and not invoke `callback` as described here: https://nodejs.org/api/dgram.html#socketsendmsg-offset-length-port-address-callback. * PR feedback
* Upgrade mocha and package lock for security warning and a few misc README updates * Use older lockfile version * Update changelog * Fix changelog, noticed a very small nan update in lockfile
* Fixes for bdeitte#273 and bdeitte#244 * Fix up the fix and add CLAUDE file * Code review updates * More test fixups * Change Node versions tested and try to help with unix-dgram issue * Attempt to fix Ubuntu test issue
* Add some more tests for uncovered areas * Actually add files * Update changelog * Try to fix up Windows lint issues and remove unneeded tests * Ensure eslint really runs everywhere and fix up tests * Try to fix Windows again
* Add some more tests for uncovered areas * Actually add files * Update changelog * Try to fix up Windows lint issues and remove unneeded tests * Ensure eslint really runs everywhere and fix up tests * Try to fix Windows again * Fix bdeitte#196, bdeitte#260, bdeitte#214
* Add in debug logging * Code review fixups * Apply suggestion from @Copilot Co-authored-by: Copilot <[email protected]> --------- Co-authored-by: Copilot <[email protected]>
* Fix a number of small, old issues * Code review updates and try to fix flakiness in unix builds
* Add in Datadog telemetry * Small fixups * Update lib/statsd.js Co-authored-by: Copilot <[email protected]> * Update lib/telemetry.js Co-authored-by: Copilot <[email protected]> * Fix lint issue * Code review updates * Code review fixups --------- Co-authored-by: Copilot <[email protected]> Co-authored-by: Brian Deitte <[email protected]>
…c-fork2 # Conflicts: # .github/workflows/node-test.js.yml # lib/helpers.js # lib/statsd.js # package-lock.json
…deTagsUnoptimized
|
I verified the fix helps with the congestion issue by running a custom build against the wes test Before you can see the congestion issue causes an error to be propogated to sentry and after you can see that there are no longer errors propogated to sentry, while we still see the socket datagram "internal error" meaning it's successfully retrying. |
|
After enabling client side telemetry, I see that we are sending datadog about 10,000 metrics/second during the load test which was leading to the original congestion issue. @wesmoncrief Do you have a gut sense of what is the order of magnitude expected? I'm not too sure what the load tests are doing and if this is correct, or maybe we collect too many metrics. |
|
@wesmoncrief gentle bump when u get a chance ^ |
|
@donhcd Added you from Jonathon's suggestion - let me know if a screensharing session to catch you up and review would be helpful. |
@donhcd gentle bump on this review - I've been getting pressured to merge it because it's performance impacting due to the reduction of dns lookup overhead from crossover |
donhcd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems reasonable, just a couple questions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why rename the file? I'd think that the less drift we have from hot-shots, the better future rebases etc will be
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only because that's what it's currently named in our fork, I'm not sure why we renamed it originally. I may be suffering from cultural training
.github/workflows/node.js.yml
Outdated
| runs-on: ${{ matrix.os }} | ||
| steps: | ||
| - uses: actions/checkout@v6 | ||
| - uses: actions/checkout@v3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was there a problem with v6?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, like above for the ci stuff i opted to keep our setup. let me use upstream and see if it works
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not a comment on this PR directly, but for ease of future rebases it seems like we might as well just keep the existing overrideTags name and just call overrideTags2 in the specific spots where we want to use it...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why delete this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There were too many merge conflicts so I regenerated the file. It's not deleted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's remove this -- seems like we're not using this right now anyways?
as I mentioned in the other comment, though, I'd be on board in the future with just renaming overrideTagsUnoptimized back to overrideTags everywhere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
donhcd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, my comments are non-blocking (but it would be nice to clean this up later). I'm expecting/hoping the tests in this repo, the tests in mono-node, your manual tests, and staging baking should all help catch any bugs we discover 🙃
Re-sync fork. Move upstream overrideTags to overrideTagsUnoptimized, keep our overrideTags2.