-
-
Notifications
You must be signed in to change notification settings - Fork 369
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
July 2021 monthly release (1.3.0) with limited ghc 9.0 support (needs hackage release) #1990
Comments
I think we could send to lsp clients, when called for ghc 9, some "warning" that noting GHC 9.0.1 support is in the beta stage with partial functionalities and pointing to GHC 9 tracking issue #297. |
Good idea, a warning popup would be great |
Oh, does it no longer pass the test suite? What broke? |
Dont worry enabled tests are passing but afaics ghc-9.0 is not tested at all in windows and macOS After a deeper look, the hls test suite is being executed and some plugins still are included in it (all the enabled ones for ghc-9.0.1) |
In fact we are not testing macOS at all 😟 |
I have run all the tests manually on MacOS on my machine and they worked fine there last I checked. I don't know about windows. But yes, we could enable the tests for ghc9 on windows and macos at the cost of more CI time. |
(I believe both windows and macos are significantly more expensive than ubuntu for github's ci time calculations, but I don't know how that matters for this project) |
I've activated test for windows and macOs in my repo, lets see how they are going: https://github.com/jneira/haskell-language-server/actions/runs/986014293 |
Not bad at all for Windows (the macOS job was cancelled):
The failing test:
|
Would we want to see some pending pr in the next release? In the vscode extension side we have to add the alert when downloading 9.0 |
I am afraid i have not much free time as i would like to lately, if someone want to drive the release the work would be very welcomed 😟 |
I can take it over. Probably I have at least that amount of time span... |
BTW; I think it will be great if #1955 can be merged within the timeframe of this release (and I guess it's feasible?). So I will wait that if no one objects. |
@Ailrun It has the basic function now, and I'll push it today asap, release the current version is OK. But it doesn't support |
@July541 I think a few days of delay is OK (though it may become August release than July release :) ), and releasing more fully-featured one is worth the delay. |
I'd like to land #1873 as well |
@isovector, do you want to include #2038 into this release? Otherwise I will prepare the release once #2040 is merged C.C. @pepeiborra |
@hasufell hi! we should synchronize our release with the ghcup update. Only want to note that, until we include the binary for windows and ghc-8.8.4, as standalone zip and inside the ghcup tar and the sha list, the release is not complete (we will not unmark the prerelease check until that happens) |
@jneira, could you upload GHC 8.8.4 if you have time for that? I think SHA256SUMS should also be fixed with that though |
the release has got me away from my laptop, will start the build asap |
i've uploaded the bin for windows and ghc-8.8.4 and udpated the windows .tar.gz and sha256sum, makint the release definitive, so it is available 🎉 |
|
Thank you for the note! I added the branch and created the backport PR |
We have a terrible list of allow-newer and a source repository package over ghc-api-compat which has to be removed to get the hackage release: haskell-language-server/cabal.project Lines 32 to 86 in b8b9620
Also we should check and fix the |
And ideally we should make packages not buildables for ghc >= 9.0.1 via base upper bound (as we need lot of dependencies hackage releases) |
Ok, i am giving a try, removing all things from cabal.project that might block the hackage release:
Due to removing
So we would need a ghc-api-compat release |
tbh, given the amount of upstream packages we need up to date in hackage, i dont know if a hackage release will be possible before the next github one |
I am gonna to start the compilation of packages and correlated prs/issues in the description of the issue 😓 |
It may not be a popular position, but if we're serious about releasing to Hackage regularly we need to try really hard to avoid pulling things in via |
same for allow-newer's, for them and source repo packages I would ask to include a comment linking the relevant issue/pr which resolution will allow remove it |
I vaguely remember ghc-api-compat cannot be uploaded to Hackage anymore, at least from HEAD. Maybe we need to backport the 8.10.5 fix and ask for a minor release /cc @hsyl20 Are there any other blockers for 8.10.x? |
yeah, I commented in the ghc-api-compat issue I linked in the description: https://gitlab.haskell.org/haskell/ghc-api-compat/-/issues/1#note_371055 |
Ok, finally we got to remove all the blocking |
As the needed fixes in cabal/hackage for being able to upload ghc-api-compat will not be done in a short period of time and @fendor has raised good points against its use (maybe we could include here for completeness?) we are gonna take the alternative of drop ghc-api-compat itself. |
@fendor have you got the chance to start the work to remove ghc-api-compat form hls? thanks! |
Yes and I made good progress!
I hope to have a PR for at least |
We are exercising the automatic hacka relese here: https://github.com/jneira/haskell-language-server/runs/3545669772 The first error has been with ghcide:
//cc @pepeiborra |
Retrie dropped support for 8.6.5 a while ago. |
uhmm and how is working master? |
ghcide doesn't specify any lower bounds on retrie, so I suppose cabal is just using an older version of retrie which builds with ghc 8.6. |
it worked!!! We have to publish them definitely:
|
Well it did what we want but the logic to skip existing packages with the same version and no changes (or throw error if there is changes) did not work well: hls-graph has not changed but is has been built |
So this is done, if the release has any issue it will be in a new one. Thanks to all helped in this release, specially @Ailrun, who drove the release |
The release also would include, among other things:
allow-newer
: Clean cabal project #2097The text was updated successfully, but these errors were encountered: