Skip to content
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

Added <cstdint> for uint64_t support #56732

Closed
wants to merge 1 commit into from

Conversation

tjuhaszrh
Copy link
Contributor

@tjuhaszrh tjuhaszrh commented Jan 23, 2025

src: Adding #include <cstdint> to worker_inspector. h for gcc v15

Added cstdint to worker_inspector as on more recent version of gcc
the build was failing due to changes to libstdc++ and the removal
of transitive includes

Fixes: #56731

@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. needs-ci PRs that need a full CI run. v20.x v20.x Issues that can be reproduced on v20.x or PRs targeting the v20.x-staging branch. labels Jan 23, 2025
legendecas
legendecas previously approved these changes Jan 23, 2025
@legendecas
Copy link
Member

Would you mind updating the commit message according to the contributing guide? thanks!

@legendecas legendecas self-requested a review January 23, 2025 17:26
@legendecas
Copy link
Member

I think this should target the main branch instead of the v20.x-staging.

@legendecas legendecas dismissed their stale review January 23, 2025 17:27

Should be on main branch

Copy link
Member

@richardlau richardlau left a comment

Choose a reason for hiding this comment

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

@tjuhaszrh thanks for your first contribution. This PR should probably be targeted at the main branch -- our general policy is to land things on main first (unless the change doesn't apply there and is specific to release lines) and then our release team will handle landing the change into release lines (or indicate if a manual backport is required).

Also https://github.com/nodejs/node/actions/runs/12934388101/job/36076121164 failed -- as indicated in the output, this checks against https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines.

@@ -9,6 +9,7 @@
#include <string>
#include <unordered_map>
#include <unordered_set>
#include <cstdint>
Copy link
Member

Choose a reason for hiding this comment

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

Unless there's a reason not to, this should be above the #include <memory> line to keep the includes in alphabetical order.

@voxik
Copy link
Contributor

voxik commented Jan 23, 2025

@tjuhaszrh do you mind explaining reasons for the commit in the commit message? E.g. it would not be mistake to include the specific failure this is going to fix.

@tjuhaszrh tjuhaszrh changed the base branch from v20.x-staging to main January 24, 2025 08:23
@tjuhaszrh tjuhaszrh requested a review from a team as a code owner January 24, 2025 08:23
@tjuhaszrh tjuhaszrh changed the base branch from main to v20.x-staging January 24, 2025 08:24
@tjuhaszrh tjuhaszrh closed this Jan 24, 2025
@tjuhaszrh tjuhaszrh deleted the v20.x-staging branch January 24, 2025 09:17
@aduh95
Copy link
Contributor

aduh95 commented Jan 24, 2025

Superseded by #56740

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c++ Issues and PRs that require attention from people who are familiar with C++. needs-ci PRs that need a full CI run. v20.x v20.x Issues that can be reproduced on v20.x or PRs targeting the v20.x-staging branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants