fix(w3c trace context): do not pass down unknown flags.

[basti1302]

The W3C trace context specification mandates that a participant must only send known flags downstream. See
https://www.w3.org/TR/trace-context/#other-flags: "The behavior of other flags, such as (00000100) is not defined and is reserved for future use. Vendors MUST set those to zero."

[github-actions]

❌ @basti1302 the signed-off-by was not found in the following 1 commits:

• 65678d6: fix(w3c trace context): do not pass down unknown flags.

📝 What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

❔ Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'

[github-actions]

❌ @basti1302 the signed-off-by was not found in the following 1 commits:

• 43c7dd0: fix(w3c trace context): do not pass down unknown flags.

📝 What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

❔ Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'

[Ferenc-]

@basti1302 Rebasing onto the current master branch should unblock you.

[pvital]

Looks good. Great job.

[pvital]

@basti1302 this PR needs to rebase before merging it.

[basti1302]

@basti1302 this PR needs to rebase before merging it.

@pvital I just rebased again, should be good now.

[Ferenc-]

@basti1302 this PR needs to rebase before merging it.

@pvital I just rebased again, should be good now.

My apologies, #421 went in the meantime.

[pvital]

@basti1302 this PR needs to rebase before merging it.

@pvital I just rebased again, should be good now.

My apologies, #421 went in the meantime.

@basti1302 if the PR is OK, we can rebase before merging it. Just say, and we can do it.

[basti1302]

My apologies, #421 went in the meantime.

@basti1302 if the PR is OK, we can rebase before merging it. Just say, and we can do it.

Lolol, no merges since weeks and today you are merging all the PRs 🎉 No worries, I rebased again. But if you plan to merge more PRs before this one, you can also feel free to rebase this on your own.