Closed samuela closed 2 years ago
Sure!
Thanks @GuillaumeLeclerc !
Huh for some reason the download is not working for me. Opening https://github.com/libffcv/ffcv/archive/v0.0.3.tar.gz gives me
the given path has multiple possibilities: #<Git::Ref:0x00007f5296528a88>, #<Git::Ref:0x00007f529652f748>
I've never seen this before...
Perhaps the git tag was created with a SHA prefix that is not unique within this repo?
Whoa that would be extremely unlikely. No idea how to fix it :(
Unfortunately I'm working with existing automation that hits the https://github.com/libffcv/ffcv/archive/v0.0.3.tar.gz endpoint whether I like it or not.
I have a workaround for the time being, but it's an interesting failure I'd never seen before.
The weird thing is that if you refresh the page you get a different hash. Maybe worth reporting to github ?
Oh that is very odd! I hadn't noticed that the hashes change!
Btw I'm working on getting FFCV packaged in nixpkgs: https://github.com/NixOS/nixpkgs/pull/160441 which is how I ended up on this...
Looks cool! Thanks for integrating FFCV
(I hope you are not spending too much time on v0.0.3 as I hope to release v1.0.0-rc1 before the end of the week.)
ooh, exciting! shouldn't be a problem unless there are significant changes to the dependencies or build system
No just adding new features
I see that there's a release tagged for v0.0.3rc1, but no tag for release v0.0.3 which is currently that latest release on pypi. Would it be possible to get a git tag for v0.0.3?
Having git tags for releases makes it a lot easier for others to package ffcv, eg in Nixpkgs.