The hex function does not format the trace and span id correctly. In as much as the spec says the span-id and trace-id are fixed with hex numbers. 16 chars for the span-id and 32 for the trace-id.
Pull Request Check List
[x] Do not open pull requests from your main branch – Thanks for the warning. I know how to fix this in the future.
[x] Added tests for changed code.
The CI fails with less than 100% coverage.
[x] New APIs are added to our typing tests in api.py.
[x] Updated documentation for changed code.
[x] New functions/classes have to be added to docs/api.rst by hand.
[x] Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecateddirectives.
The next version is the second number in the current release + 1. The first number represents the current year. So if the current version on PyPI is 23.1.0, the next version is gonna be 23.2.0. If the next version is the first in the new year, it'll be 24.1.0.
[x] Documentation in .rst and .md files is written using semantic newlines.
[x] Changes (and possible deprecations) are documented in the changelog.
Summary
The
hexfunction does not format the trace and span id correctly. In as much as the spec says the span-id and trace-id are fixed with hex numbers. 16 chars for the span-id and 32 for the trace-id.Pull Request Check List
mainbranch – Thanks for the warning. I know how to fix this in the future.api.py.docs/api.rstby hand.versionadded,versionchanged, ordeprecateddirectives..rstand.mdfiles is written using semantic newlines.