-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Update and load styledstrings #51869
Update and load styledstrings #51869
Conversation
8f7b078
to
2de89d9
Compare
CI fails because of JuliaLang/StyledStrings.jl#8 |
Triage is happy with letting REPL depend StyledStrings.jl |
2de89d9
to
887c3ee
Compare
887c3ee
to
db6dc64
Compare
Ok, the problem seems to be this:
I only find this confusing though, if someone could weigh in that would be much appreciated 🙏. |
I think Pkg has some special internal list of stdlibs, as otherwise it needs to go find them in General, and I don't think it seems to be registered there |
Hm, Pkg looks these up at runtime by looking in the stdlib folder so it should find them. I'll try figure out what is going on.. |
Thanks Kristoffer :) |
Okay, the tests that error is within the "historical stdlib" stuff that I do not really know much about. Maybe @staticfloat knows what needs to be done here. It is possible it needs to be added to https://github.com/JuliaPackaging/HistoricalStdlibVersions.jl/blob/3eccb253cd154d56c0efd75d2315b459725addf9/src/version_map.jl#L1515 (which might be what Jameson meant) . |
I pushed a new commit to that repo; it's supposed to have a bot that auto-opens new PRs I think, but it doesn't seem to be working. |
To get this moving, @staticfloat might it be worth manually opening a PR? |
db6dc64
to
8d848dd
Compare
I've tried updating the branch in the hope that the "historical stdlib" issue has been fixed in the background. I guess I'll find out if this is the case or not from CI. |
Still seems like the same issue is occurring
|
I can't see how I can solve this myself, so if @KristofferC or @staticfloat could spare this some more attention, that would be much appreciated. |
JuliaPackaging/HistoricalStdlibVersions.jl#17 pushed a new commit but a new version for this was never registered. I will try bump the version and register it and we can rerun CI here and see what happens. |
Thanks, Kristoffer. I just took a look at the CI for the commit you pushed and I see the same error ( |
If I could give this a gentle bump once more, with the PRs blocked by this in particular it would be very good if this could be worked out. |
@KristofferC might you be able to spare the time to give this another look? |
f6aa299
to
e57e3b4
Compare
So the version with StyledStrings was registered JuliaRegistries/General#97838 Is Pkg using the right version of HistoricalStdlibVersions? |
It should install it here https://github.com/JuliaLang/Pkg.jl/blob/b13bd2ddf6049865ddd8f7984bc9aa2790c14d21/test/runtests.jl#L42-L47. But I don't see anything about it getting installed in the log. |
I confirm this is an issue even with the latest HistoricalStdlibVersions. However, I think this is a bug with the implementation in Pkg of the whole I would suggest disabling this Pkg test for now since it is unfortunate to block this on a Pkg bug. Edit: JuliaLang/Pkg.jl#3773 for the test disabling |
e57e3b4
to
07e1629
Compare
Now that #53138 is merged, this should be mergeable without any CI issues 🙂 |
CI hasn't quite finished yet, but so far I'm seeing:
The
|
This gets us two particular commits of interest: - Replace within-module eval with hygienic eval: which makes it possible to include StyledStrings in the sysimage without running into precompile errors. - Load the JULIA_*_COLOR env vars for compat: which mirrors the current behaviour to the relevant faces.
By loading the StyledStrings stdlib in REPL, we load the privateered print/show methods for the Annotated{String,Char} types defined there. This is nice to have, because it means that styled annotated strings can be constructed in Base and elsewhere without loading the StyledStrings stdlib, but they will be displayed as intended in the REPL.
07e1629
to
30ccace
Compare
Ok, at this point it seems like all the CI has run other than the Adress Sanitised/gnuassert builds. I'm not seeing any non-spurious errors other than a |
Alrighty, all the tests have finished now, and it looks all clear to me! The only non-allowed fail is the Address Sanitised build timing out. |
I'm so glad to see this merged, thanks to those who helped work out what was going on here and fix it! |
This has some value by itself, but mainly serves as a prerequisite for #51811, #51816, and #51829, along with two other PRs that have yet to be made.