-
-
Notifications
You must be signed in to change notification settings - Fork 269
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
1.6.1 backports #2425
1.6.1 backports #2425
Conversation
…Foo")` instead (JuliaLang#2099) (cherry picked from commit 46eb2b2)
* Avoid invalidations related to * string concat * use same JULIA_PKG_SERVER setting for processcoverage to ensure registry is functional (cherry picked from commit 42fc1bf)
* make downloads respect IO (cherry picked from commit 2496426)
…aLang#2373) (cherry picked from commit 8cbd117)
29d24f4
to
e5d10cf
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
(cherry picked from commit 8ca403b)
@fredrikekre Is this good to go? |
I think probably these will all have to wait until 1.6.1, right? |
Yeah, I thought that was the case anyway
|
Want to rename this to "1.6.1 backports" and add #2377? |
Would you mind taking over? I don't have bandwidth currently |
I actually have no idea how to backport a PR... maybe @fredrikekre or @KristofferC can take over this PR. |
* hide progress bar after precomp finishes * indent precomp report (cherry picked from commit 7cec904)
Co-authored-by: David Varela <[email protected]> (cherry picked from commit 8ad4425)
(cherry picked from commit 8139716)
(cherry picked from commit 8b0045d)
@KristofferC would standard practice to be to switch CI on this branch to 1.6 rather than nightly? |
e09d23f
to
cdf685a
Compare
@KristofferC now that I know about your backport script, I'm wondering if we should merge this (once tests pass) and start a new tidier one with your script? Also, if we want to backport #2484 that will need JuliaLang/julia#40345 to be on the 1.6 base branch before tests pass. |
(cherry picked from commit 91b6754)
(cherry picked from commit 6e8b621)
(cherry picked from commit fd1820e)
…liaLang#2462) * add tip to auto-precomp for getting error details * switch tip to Pkg. API * call -> run (cherry picked from commit 0fa812e)
Drive by fix for the following issue in the output of the precompile ``` ┌ Error: Error in the keymap │ exception = │ TOML Parser error: │ C:\users\keno\Temp\jl_qpEfxR\registries\Registry\T/TestPkg\Package.toml:3:12 error: invalid uncidode scalar │ repo = "C:\users\keno\Temp\jl_qpEfxR/TestPkg.jl" │ ^ │ Stacktrace: │ [1] parse │ @ .\toml_parser.jl:441 [inlined] │ [2] Base.CachedTOMLDict(p::Base.TOML.Parser, path::String) │ @ Base .\loading.jl:180 │ [3] (::Base.var"JuliaLang#810#811"{String, Base.TOMLCache})() │ @ Base .\loading.jl:226 └ @ REPL.LineEdit Z:\home\keno\julia-win64\usr\share\julia\stdlib\v1.7\REPL\src\LineEdit.jl:2579 ``` (cherry picked from commit 749541a)
3dec9c3
to
0d33deb
Compare
@KristofferC Did #2377 make it into this? I don't see it in the diff. |
Sorry, I made a comment about it but I seem to have not submitted it. What I wrote was basically that I removed it from backport because:
|
PRs with backport label
Pkg.add("Foo.jl")
, instruct them to doPkg.add("Foo")
instead #2099Manual cherry-picks
JULIA_PKG_SERVER
environment variable is not set, use Git for cloning registries #2377Required a change of approach. See https://github.com/IanButterworth/Pkg.jl/blob/cdf685a6a1f40607df185cbacec8a1db5cec4a7b/src/Types.jl#L1003-L1004
status
output for pin/free #2446Individual commit backports