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

Add hls-1.6.0.0 #19

Merged
merged 2 commits into from
Jan 28, 2022
Merged

Add hls-1.6.0.0 #19

merged 2 commits into from
Jan 28, 2022

Conversation

jneira
Copy link
Member

@jneira jneira commented Jan 28, 2022

No description provided.

@jneira
Copy link
Member Author

jneira commented Jan 28, 2022

@hasufell ci is happy 😄

@hasufell
Copy link
Member

[ Info  ] verifying digest of: haskell-language-server-Linux-alpine-x86_64-1.6.0.0.tar.xz
ghcup-gen: Codec.Compression.Lzma.decompressWith: decoding error LzmaRetFormatError

@jneira
Copy link
Member Author

jneira commented Jan 28, 2022

is that a local check? i cant find that in the ci logs, it seems ci only checks own ghcup tarballs

@hasufell
Copy link
Member

hasufell commented Jan 28, 2022

See https://github.com/haskell/ghcup-metadata#adding-a-new-ghc-version step 7

cabal run ghcup-gen -- check-tarballs -f ghcup-0.0.6.yaml -u 'hls-1\.6\.0\.0'

@jneira
Copy link
Member Author

jneira commented Jan 28, 2022

thanks! i inferred it from the ci invocation and it is running now

does it take too much time to check it in ci?

@hasufell
Copy link
Member

does it take too much time to check it in ci?

How would you run it?

@jneira
Copy link
Member Author

jneira commented Jan 28, 2022

hmm adding a step running cabal run ghcup-gen -- check-tarballs -f ghcup-0.0.6.yaml -u 'hls-1\.6\.0\.0'?

@hasufell
Copy link
Member

hmm adding a step running cabal run ghcup-gen -- check-tarballs -f ghcup-0.0.6.yaml -u 'hls-1\.6\.0\.0'?

How will that work for the next PR adding a new HLS version or a different GHC version?

@jneira
Copy link
Member Author

jneira commented Jan 28, 2022

ok reproduced the check error locally but i still am not sure what is going on, i can extract the files succesfully. The unique thing i did locally was rename the file, so ci produced the tarball

@hasufell
Copy link
Member

ok reproduced the check error locally but i still am not sure what is going on, i can extract the files succesfully. The unique thing i did locally was rename the file, so ci produced the tarball

We use lzma to decompress:

https://gitlab.haskell.org/haskell/ghcup-hs/-/blob/655ee432f8330d426199ad6ece190fc194f860eb/lib/GHCup/Utils.hs#L716-719

https://hackage.haskell.org/package/lzma-static

It appears to have problem with some feature of the archive, I guess.

@jneira
Copy link
Member Author

jneira commented Jan 28, 2022

The encoding for haskell-language-server-macOS-aarch64-1.6.0.0.tar.xz for example is LZMA2:23 CRC64, for alpine is LZMA:23
So each tarball is generated in the system where hls is being built and the version of the tool can affect the final result 😟

@jneira
Copy link
Member Author

jneira commented Jan 28, 2022

I am thinking in removing the alpine tarballs, like 1.5.1. At the end those binaries will suffer the same template haskell bug we hit in hls , no?

@jneira
Copy link
Member Author

jneira commented Jan 28, 2022

In fact all tarballs are LZMA2:23 CRC64 but the alpine one

dlUri: https://github.com/haskell/haskell-language-server/releases/download/1.6.0.0/haskell-language-server-Windows-1.6.0.0.tar.gz
dlHash: 9f1b4ea31602a775a8f5bfedcc6290d3e45dd695f389fd705c9fff96c63c8570
Linux_Alpine:
unknown_versioning: *hls-1600-64
Copy link
Member

Choose a reason for hiding this comment

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

If the current linux binaries are dynamic, this will not work.

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

Successfully merging this pull request may close these issues.

2 participants