Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vesion is too long #111

Open
bistack opened this issue Dec 24, 2024 · 3 comments
Open

Vesion is too long #111

bistack opened this issue Dec 24, 2024 · 3 comments

Comments

@bistack
Copy link

bistack commented Dec 24, 2024

v0.6.0+5.3.0-1-ge13ca993e8ccb9ba9847cc330696e02839f328f7

What is the last part?
Is the jemalloc gid? It's not match 5.3.0's gid.

Just v0.6.0+5.3.0 is fine.

@bistack bistack changed the title Vesion is too long. Vesion is too long Dec 24, 2024
@BusyJay
Copy link
Member

BusyJay commented Dec 24, 2024

It's the ref (version and commit hash) of bundled jemalloc. What problem did you meet exactly?

@klensy
Copy link

klensy commented Dec 27, 2024

I guess that it's typo in git commit hash, i.e. jemalloc/jemalloc@ge13ca993e8ccb9ba9847cc330696e02839f328f7 not exist, while jemalloc/jemalloc@e13ca99 exist and points to correct commit.

@BusyJay
Copy link
Member

BusyJay commented Dec 27, 2024

The hash points to tikv/jemalloc@e13ca99 , it's generated by git describe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants