The Julia developers are pleased to annouce the release of Julia v1.4.0, the fourth minor release in the 1.x series. Binaries are available for all of your favorite platforms (Linux, macOS, Windows, and FreeBSD) at Download Julia. As a minor release, v1.4.0 contains no breaking changes, only new features, performance improvements, and marginal, undisruptive changes in behavior. The best reference for the changes in 1.4 is the NEWS file for 1.4.0. Note that 1.4, like 1.3, 1.2, and 1.1 before it, does not have long term support. As of this release, 1.3 has been effectively superseded by 1.4, which means there will not likely be any further 1.3.x releases. Julia 1.0 is still currently the only long term support version. We encourage everyone to give it a try. Packages can test with 1.4.0 on CI by specifying 1.4 on Travis, AppVeyor (with Appveyor.jl), and Cirrus (with CirrusCI.jl). As always, let us know in the issue tracker if you run into any issues. Enjoy!

[image] Albert_Zevelev: Is there some kind of testing that can be done before a new version of Julia is released to check that, say, the top 20 Julia packages (by github stars) work? And the maintainers can be notified pre-release if there is an issue? [image] Albert_Zevelev: That said, it could be nice to test the most frequently used Julia packages before a release… We already do exactly that. We test all registered Julia packages (registered in the General registry) prior to making a Julia release. We also do this every day on the latest Julia master. See: ANN: Nanosoldier package evaluation -- with badges! GitHub - JuliaCI/NanosoldierReports: A repository for human-readable reports generated by the Nanosoldier.jl CI system. GitHub - JuliaCI/Nanosoldier.jl: A package for running JuliaCI services on MIT's Nanosoldier cluster GitHub - JuliaCI/PkgEval.jl: Keeping tabs on the julia ecosystem

The problem you were experiencing was due to some issue with your local environment, as evidenced by the fact that it was fixed by rm -rf ~/.julia. In general, when people experience an issue with packages, my first advice is always to rm -rf ~/.julia. I know that it seems extreme, but it really does fix the vast majority of problems.

[image] dilumaluthge: my first advice is always to rm -rf ~/.julia . I know that it seems extreme Note that this could lead to work lost in packages checked out for development. May not be an issue for new users though. I think that the manual should contain advice about this, cf advice for recovering from corrupted depot in the manual opened 09:33AM - 18 Feb 20 UTC (UTC) [tpapp] tpapp Occasionally parts of the depot become corrupted (because of interrupted downloa…ds/processes, bugs in Pkg, etc). While this is not part of the normal workflow, it would be great if the manual could have a section on how to recover from these situations, that could be linked eg on Discourse. Eg 1. establish the depot path (examples below assume the default) 2. remove `~/.julia/packages` 3. remove the global manifest, 4. restart julia and do a `pkg> resolve`?

[image] Tamas_Papp: Note that this could lead to work lost in packages checked out for development. That’s a good point. I suppose my advice should actually be: Commit all changes in any packages that you have checked out for development Push all changes to a remote (GitHub, GitLab, etc.) rm -rf ~/.julia And of course, if you don’t have any packages checked out for development, then you simply do: rm -rf ~/.julia

It seems overly drastic to start by removing lots of files and REPL history and what not. My advice if you suspect problem with your depot would be to create an empty directory somewhere and point JULIA_DEPOT_PATH to it. If that works you can start to think about removing stuff in ~/.julia. If it doesn’t the problem is likely elsewhere and no amount of destruction in your normal depot will help you.

Rather than removing ~/.julia, I would suggest looking at the [compat] section of Project.toml of the two MJL versions alan-turing-institute/MLJ.jl/blob/v0.2.3/Project.toml name = "MLJ" uuid = "add582a8-e3ab-11e8-2d5e-e98b27df1bc7" authors = ["Anthony D. Blaom "] version = "0.2.3" [deps] CSV = "336ed68f-0bac-5ca0-87d4-7b16caf5d00b" CategoricalArrays = "324d7699-5711-5eae-9e2f-1d82baa6b597" Dates = "ade2ca70-3891-5945-98fb-dc099432e06a" Distributed = "8ba89e20-285c-5b6f-9357-94700520ee1b" Distributions = "31c24e10-a181-5473-b8eb-7969acd0382f" LinearAlgebra = "37e2e46d-f89d-539d-b4ee-838fcccc9c8e" MLJBase = "a7f614a8-145f-11e9-1d2a-a57a1082229d" MLJModels = "d491faf4-2d78-11e9-2867-c94bc002c0b7" Pkg = "44cfe95a-1eb2-52ea-b672-e2afdf69b78f" ProgressMeter = "92933f4c-e287-5a05-a399-4b506db050ca" Random = "9a3f8284-a2c9-5f02-9a11-845980a1fd5c" RecipesBase = "3cdcf5f2-1ef4-517c-9805-6587b60abb01" RemoteFiles = "cbe49d4c-5af1-5b60-bb70-0a60aa018e1b" Statistics = "10745b16-79ce-11e8-11f9-7d13ad32a3b2" This file has been truncated. show original alan-turing-institute/MLJ.jl/blob/v0.10.1/Project.toml name = "MLJ" uuid = "add582a8-e3ab-11e8-2d5e-e98b27df1bc7" authors = ["Anthony D. Blaom "] version = "0.10.1" [deps] CategoricalArrays = "324d7699-5711-5eae-9e2f-1d82baa6b597" ComputationalResources = "ed09eef8-17a6-5b46-8889-db040fac31e3" Distributed = "8ba89e20-285c-5b6f-9357-94700520ee1b" Distributions = "31c24e10-a181-5473-b8eb-7969acd0382f" LinearAlgebra = "37e2e46d-f89d-539d-b4ee-838fcccc9c8e" MLJBase = "a7f614a8-145f-11e9-1d2a-a57a1082229d" MLJModels = "d491faf4-2d78-11e9-2867-c94bc002c0b7" MLJScientificTypes = "2e2323e0-db8b-457b-ae0d-bdfb3bc63afd" MLJTuning = "03970b2e-30c4-11ea-3135-d1576263f10f" Pkg = "44cfe95a-1eb2-52ea-b672-e2afdf69b78f" ProgressMeter = "92933f4c-e287-5a05-a399-4b506db050ca" Random = "9a3f8284-a2c9-5f02-9a11-845980a1fd5c" Statistics = "10745b16-79ce-11e8-11f9-7d13ad32a3b2" StatsBase = "2913bbd2-ae8a-5f71-8c99-4fb6c76f3a91" This file has been truncated. show original If I interpret correctly, if you had installed Distributions v0.23 a few days ago, then you would not fulfill Distributions = "^0.21,^0.22", and the installer would fall back to MLJ v0.2.3. MLJ v0.2.4 would not install since it depends on MLJBase = "0.2.3", which maybe was hold back by CSV = "0.5" in MLJBase.jl/Project.toml at v0.2.3 · JuliaAI/MLJBase.jl · GitHub

This might be a case for the developers applying monotonic bounds in RetroCap. Going from 0.10 back to 0.2 is quite a difference, it would probably be more helpful to receive a Pkg incompatibility error.

Sorry to report a glitch on Linux 64 bits with (old) AMD processor (Turion II M640) Invalid instruction at 0x7ff8b4a3f1d0: 0x66, 0x0f, 0x3a, 0x0f, 0xc0, 0x08, 0x0f, 0x83, 0xae, 0x04, 0x00, 0x00, 0x48, 0xc1, 0xe0 signal (4): Illegal instruction in expression starting at none:0 _ZN4llvm13LexicalScopes23assignInstructionRangesERNS_15SmallVectorImplISt4pairIPKNS_12MachineInstrES5_EEERNS_8DenseMapIS ... jl_module_run_initializer at /buildworker/worker/package_linux64/build/src/toplevel.c:74 _julia_init at /buildworker/worker/package_linux64/build/src/init.c:788 unknown function (ip: 0x401527) __libc_start_main at /lib64/libc.so.6 (unknown line) unknown function (ip: 0x4015d4) Allocations: 2502 (Pool: 2493; Big: 9); GC: 0 Illegal instruction (core dumped) More info on https://github.com/JuliaLang/julia/issues/35215, where alea54 was the first to report issue on AMD Phenom

Just want to confirm, what LLVM binaries were being used when building those released Julia binaries? It looks like there’re compatibility issues on Windows and Linux: Travis CI https://github.com/JuliaBinaryWrappers/LLVM_jll.jl/issues/3 Edit: I noticed the Julia version on Travis CI is still Julia-1.4rc2, this might cause the above issue. (fixed now)

What can I do to fix issues while keeping most of the useful stuff, like my repl history? For example, should I just back up my repl_history.jl file, and copy it back over after rm -rf ~/.julia? What else should I try to keep? Any suggestions? How do I automatically reinstall all packages after deleting them?

Julia v1.4.0 has been released

Announcements

kdyrhage April 3, 2020, 2:35pm 26

For the record it works just fine for me on Catalina.

Issue with Upgrading to 1.4 on MacOS Catalina

Topic		Replies	Views
Julia v1.0-rc1 is now available Announcements release	60	7428	August 16, 2018
Julia v1.5.0 has been released Announcements release	38	9175	August 15, 2020
Julia v1.6.0-beta1 is now available Announcements release	41	8225	January 27, 2021
List of working packages on v. 1.0 New to Julia	71	8647	September 1, 2018
Julia 1.0.3 testing period Announcements release	37	4041	February 19, 2019

Julia v1.4.0 has been released

Related topics