Use math.MaxUint64 instead of 0xffffffffffffffff

[majorteach]

Which problem is this PR solving?

• Use the variables included in the go standard library to make the code clearer

Description of the changes

• Math MaxUint64 is a constant currently defined in the go standard library and can be used directly without having to define it repeatedly

How was this change tested?

• no need

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: yarn lint and yarn test

[james-ryans]

Hmm.. is there any explanation why is this PR needed? Maybe adding the "Which problem is this PR solving?" will clarify things, because I can't see what is this PR trying to solve. 🤔

[majorteach]

Hmm.. is there any explanation why is this PR needed? Maybe adding the "Which problem is this PR solving?" will clarify things, because I can't see what is this PR trying to solve. 🤔

Thanks. Modified

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.08%. Comparing base (53592b3) to head (2415c24).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5294   +/-   ##
=======================================
  Coverage   95.08%   95.08%           
=======================================
  Files         340      340           
  Lines       16626    16626           
=======================================
  Hits        15809    15809           
- Misses        628      629    +1     
+ Partials      189      188    -1     

Flag	Coverage Δ
badger	13.26% <ø> (ø)
cassandra-3.x	26.44% <ø> (ø)
cassandra-4.x	26.44% <ø> (ø)
elasticsearch-5.x	21.68% <ø> (ø)
elasticsearch-6.x	21.70% <ø> (+0.01%)	⬆️
elasticsearch-7.x	21.78% <ø> (+0.01%)	⬆️
elasticsearch-8.x	21.87% <ø> (ø)
grpc	10.96% <ø> (-0.02%)	⬇️
kafka	14.73% <ø> (ø)
opensearch-1.x	21.78% <ø> (+0.01%)	⬆️
opensearch-2.x	21.77% <ø> (-0.02%)	⬇️
unittests	92.25% <ø> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[james-ryans]

@majorteach there is a Github CI check failing, it is because your PR is opened from the main branch of your fork. As we're not allowed to directly push commits to main branch, please create another branch and open a new PR.

[majorteach]

there is a Github CI check failing, it is because your PR is opened from the main branch of your fork. As we're not allowed to directly push commits to main branch, please create another branch and open a new PR.

Thanks!

[majorteach]

@majorteach there is a Github CI check failing, it is because your PR is opened from the main branch of your fork. As we're not allowed to directly push commits to main branch, please create another branch and open a new PR.

The new PR #5295

I checkout from main and use another branch name.

Thanks