Github release checksums mismatch

Users
1

Hello,

I’m a bit puzzled. Tried to download the release files from github, v24.0.0, latest, namely:

  • badger-checksum-linux-amd64.sha256
  • badger-linux-amd64.tar.gz
  • dgraph-checksum-linux-amd64.sha256
  • dgraph-linux-amd64.tar.gz

And tried to actually verify the checksums by sha256sum. They don’t match:

$ cat *sha256
928b06638a9cb332372f98df1ebb4c73a05a7de02bd828e1b849d67a7ec5c5af
5c8d5ee8fd0c092cbaf80f5fbbd4cddb1db478d2eb4ee9e244e638abaef5a233

$ sha256sum *gz
a50101d04f47153139ea5e2a09e7c4c243c37d9137dead20034dd77f8c74b88c  badger-linux-amd64.tar.gz
a784dcc9ff7aea9c78e13baf3b6ca50fea967175322783cba28651c09becd49d  dgraph-linux-amd64.tar.gz

Am I the only one trying to check it, or it’s made with a different method than anyone else do? What am I doing wrong?

Thanks!

2

Hi Peter,

The checksums are for the binaries (dgraph/Badger) inside the compressed tar bundles.
You should first extract the tar.gz bundles and then run sha256sum on the resulting Badger and Dgraph binaries as following:

% sha256sum dgraph ( AMD Binary)
5c8d5ee8fd0c092cbaf80f5fbbd4cddb1db478d2eb4ee9e244e638abaef5a233 dgraph

% % sha256sum badger-linux-amd64 ( AMD Binary)
928b06638a9cb332372f98df1ebb4c73a05a7de02bd828e1b849d67a7ec5c5af badger-linux-amd64

As you can see, the checksums are matching from my execution.
Hope that helps
Thanks
-Megha

1 Like
3

This pipeline is really solid dgraph/.github/workflows/cd-dgraph.yml at main · dgraph-io/dgraph · GitHub … I do have a small quirk here. I think your team should automate the release markdown information from the changelog right here.

It’s nice to see dgraph handles both Binaries. So my next question as a followup to this:

  • ARM is the future, so is dgraph running arm binary on cloud? or is it dgraph amd?
  • I would love to understand if ARM binary is experimental or at a similar performance to AMD?

The pipeline seems to publish both, hence I am curious. As I can only use arm on my machine today, and this is a pretty nice addition.

4

@honeybadger Yeah I tried the ARM binary on an AWS machine. It was really slow compared to x86. And not just Dgraph, but golang in general was slow. I tried a prime number generator. My test could have been wrong and with flaws, so if you have some evidence to the contrary, I am willing to do some bench marking.

5

Dgraph Cloud is running AMD.

6

Thanks for the clarifictaion … it may actually be more profitable for you folks to run Dgraph on ARM (if it is performant). The unit economics is like +25% savings easily.

@harshil_goel, I do have some questions. But I will reserve those after I have done some work on my end. I may raise a few PRs and nudge you guys after a week.

1 Like