uuid frozen string warnings with ruby 3.4

[mscoutermarsh]

We're running:

• 2.29.1 and Ruby 3.4.1

And our logs are filled with:

uuidtools.rb:700: warning: literal string will be frozen in the future (run with --debug-frozen-string-literal for more information)

I realize this isn't technically an issue with the Datadog client. But, since uuidtools has not been updated in 5 years. It seems most likely the fix would be using something from Ruby's standard library to replace the functionality.

[github-actions[bot]]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[issyl0]

We're also seeing this. We patched it upstream. That change is merged but not in a real release yet, so we tried to vendor uuidtools latest in our app (2.2.0.GIT_SHA) and were blocked on the fact that this DataDog gem depends on < 2.2.0.

[github-actions[bot]]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[asilano]

Also seeing this. uuidtools now has a v3 which claims to fix the frozen literals, so it should be a simple case of upgrading the gem dependency

[asilano]

#2320 would fix this... be good to get it through if possible

[github-actions[bot]]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[asilano]

Fixed by #2320

Just noting for anyone searching later.

[github-actions[bot]]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.