Skip to content

[638][io] use UUIDv4 in ROOT files#22063

Merged
dpiparo merged 6 commits into
root-project:v6-38-00-patchesfrom
dpiparo:bp_22035_638
Apr 25, 2026
Merged

[638][io] use UUIDv4 in ROOT files#22063
dpiparo merged 6 commits into
root-project:v6-38-00-patchesfrom
dpiparo:bp_22035_638

Conversation

@dpiparo
Copy link
Copy Markdown
Member

@dpiparo dpiparo commented Apr 25, 2026

BP of #22035 (by hand, some conflicts needed resolution). To be automatically backported to 6.36.

jblomer added 6 commits April 25, 2026 18:02
(cherry picked from commit 7865c27)
(cherry picked from commit e9292b8)
Use UUIDv4 in TDirectory (hence in TDirectoryFile and TFile) and in the
RMiniFile. Note that TDirectory is used without gSystem (needed for
GetCryptoRandom()) in the context of rootcling.  In principle,
GetCryptoRandom() should work without a TSystem object.  That may be for
a later commit.

The UUIDv4, unlike the current UUIDv1, is (with high enough probability)
globally unique.

(cherry picked from commit b387638)
Factor out calling the OS crypto random number generator into a free
function in the Base package. In turn, TSystem::GetCryptoRandom() can be
static and does not rely in gSystem being initialized.

(cherry picked from commit f20d779)
@dpiparo dpiparo self-assigned this Apr 25, 2026
@github-actions
Copy link
Copy Markdown

Test Results

    19 files      19 suites   3d 2h 55m 1s ⏱️
 3 730 tests  3 730 ✅ 0 💤 0 ❌
69 125 runs  69 125 ✅ 0 💤 0 ❌

Results for commit 14894f7.

Copy link
Copy Markdown
Contributor

@jblomer jblomer left a comment

Choose a reason for hiding this comment

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

Thanks! So once resolved for 6.38, the bot can use that to apply the correct changes to 6.36? That's nice!

@dpiparo dpiparo merged commit 8c4b972 into root-project:v6-38-00-patches Apr 25, 2026
28 of 29 checks passed
@dpiparo
Copy link
Copy Markdown
Member Author

dpiparo commented Apr 25, 2026

I hope so...

@dpiparo
Copy link
Copy Markdown
Member Author

dpiparo commented Apr 25, 2026

/backport to 6.36

@root-project-bot
Copy link
Copy Markdown

Preparing to backport PR #22063 to branch 6.36 requested by dpiparo

@root-project-bot
Copy link
Copy Markdown

Something went wrong with the creation of the PR to backport to 6.36: @dpiparo please see the logs

@root-project-bot
Copy link
Copy Markdown

This PR has been backported to

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants