# Julia v1.2.0-rc1 is now available

**URL:** <https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788>\
**Category:** Announcements\
**Created:** [May 31, 2019, 2:48am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788 "2019-05-31T02:48:20Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeff.bezanson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jeff.bezanson/32/48_2.png) [@jeff.bezanson](https://discourse.julialang.org/u/jeff.bezanson)\
**Post date:** [May 31, 2019, 2:48am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/1 "2019-05-31T02:48:20Z")

</div>

Hello Julians,

The first release candidate for Julia v1.2.0 is now available. Binaries can be found at the usual download page [Download Julia](https://julialang.org/downloads/). There are source tarballs available as github releases, or of course you can check out and build the release-1.2 branch.

Please test if you can, and file any issues you encounter at [Issues · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/issues). If you maintain any packages, this is a good time to add CI for 1.2, check compatibility, and tag new versions as needed.

Thank you and happy coding!

---

<div class="post-metadata">

**Author:** ![ImreSamu](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/imresamu/32/20677_2.png) [@ImreSamu](https://discourse.julialang.org/u/ImreSamu)\
**Post date:** [May 31, 2019, 3:39am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/2 "2019-05-31T03:39:41Z")

</div>

- Julia v1.2-rc1 Release Notes: [julia/NEWS.md at v1.2.0-rc1 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/blob/v1.2.0-rc1/NEWS.md)

---

<div class="post-metadata">

**Author:** ![Wikunia](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wikunia/32/2180_2.png) [@Wikunia](https://discourse.julialang.org/u/Wikunia)\
**Post date:** [May 31, 2019, 10:04am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/3 "2019-05-31T10:04:26Z")

</div>

Is there an option to run the tests on Travis already? Thought adding `1.2` in the julia versions is sufficient but as it not really released yet it seems not to be the case.

**Edit:** It somehow works on Mac?

> **[Travis CI - Test and Deploy with Confidence](https://app.travis-ci.com/lanl-ansi/Juniper.jl/builds/539622490)**
>
> Travis CI enables your team to test and ship your apps with confidence. Easily sync your projects with Travis CI and you'll be testing your code in minutes.

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [May 31, 2019, 11:31am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/4 "2019-05-31T11:31:47Z")

</div>

I can download [https://julialang-s3.julialang.org/bin/linux/x64/1.2/julia-1.2-latest-linux-x86\_64.tar.gz](https://julialang-s3.julialang.org/bin/linux/x64/1.2/julia-1.2-latest-linux-x86_64.tar.gz), but for some reason Travis can’t

---

<div class="post-metadata">

**Author:** ![oschulz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oschulz/32/2998_2.png) [@oschulz](https://discourse.julialang.org/u/oschulz)\
**Post date:** [May 31, 2019, 12:56pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/5 "2019-05-31T12:56:44Z")

</div>

I have trouble with Travis and v1.2 on Linux, too:

```julia
Installing Julia
0.01s$ CURL_USER_AGENT="Travis-CI $(curl --version | head -n 1)"
0.00s$ mkdir -p ~/julia
0.17s$ curl -A "$CURL_USER_AGENT" -s -L --retry 7 'https://julialang-s3.julialang.org/bin/linux/x64/1.2/julia-1.2-latest-linux-x86_64.tar.gz' | tar -C ~/julia -x -z --strip-components=1 -f -
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
The command "curl -A "$CURL_USER_AGENT" -s -L --retry 7 'https://julialang-s3.julialang.org/bin/linux/x64/1.2/julia-1.2-latest-linux-x86_64.tar.gz' | tar -C ~/julia -x -z --strip-components=1 -f -" failed and exited with 2 during .

```

OS-X runs fine.

---

<div class="post-metadata">

**Author:** ![pazzo83](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pazzo83/32/232_2.png) [@pazzo83](https://discourse.julialang.org/u/pazzo83)\
**Post date:** [May 31, 2019, 8:02pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/6 "2019-05-31T20:02:23Z")

</div>

Is there any reason the REPL simply wouldn’t start (this is on a Mac running 10.14.4)? When I start Julia it just aborts with no error.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [June 1, 2019, 4:14am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/7 "2019-06-01T04:14:21Z")

</div>

One thing that would be cool: whenever a first release candidate for a new minor version is released, some bot automatically opens PRs against all registered packages. Those PRs add the new version to the travis and appveyor scripts.

---

<div class="post-metadata">

**Author:** ![asinghvi17](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/asinghvi17/32/8272_2.png) [@asinghvi17](https://discourse.julialang.org/u/asinghvi17)\
**Post date:** [June 3, 2019, 2:09am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/8 "2019-06-03T02:09:57Z")

</div>

The main problems with that kind of mass-PR approach are:

1. If we use a GitHub bot, then it has to be installed on the package for it to be able to open a PR. This could be solved if, for example, we have Registrator (or TagBot) itself make a PR.
2. If we automate some solution ourselves for mass-PRs, then we run into (a) Github rate limits and (b) a lot of downloads of Git repos (even if they are shallow clones, that’s still a lot of data.

From my experience making mass PRs to the JuliaDiffEq and JuliaDynamics organizations, the abuse detection on Github is pretty easy to trigger, so you might have to wait an hour - or more - before the timeout expires. This is pretty annoying.

The Registrator/TagBot approach, however, might work. I just don’t want yet another bot to install for a normal Julia package repo.

Just my 2¢.

---

<div class="post-metadata">

**Author:** ![c42f](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/c42f/32/52842_2.png) [@c42f](https://discourse.julialang.org/u/c42f)\
**Post date:** [June 3, 2019, 3:23am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/9 "2019-06-03T03:23:18Z")

</div>

I’ve had a successful CI run on linux now, so I guess Travis has recovered from whatever weird caching issue (or otherwise) it was having.

---

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [June 3, 2019, 11:34pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/10 "2019-06-03T23:34:14Z")

</div>

Fails for me with 1.2.0 (tried also 1.2). Runs fine with 1.1.0

> **[Travis CI - Test and Deploy with Confidence](https://app.travis-ci.com/GenericMappingTools/GMT.jl/builds/540994588?utm_source=github_status&utm_medium=notification)**
>
> Travis CI enables your team to test and ship your apps with confidence. Easily sync your projects with Travis CI and you'll be testing your code in minutes.

---

<div class="post-metadata">

**Author:** ![c42f](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/c42f/32/52842_2.png) [@c42f](https://discourse.julialang.org/u/c42f)\
**Post date:** [June 4, 2019, 12:08am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/11 "2019-06-04T00:08:06Z")

</div>

> [@joa-quim](#):
>
> [Travis CI - Test and Deploy with Confidence](https://travis-ci.org/GenericMappingTools/GMT.jl/builds/540994588?utm_source=github_status&utm_medium=notification)

This is exactly the same error that I was getting previously.

---

<div class="post-metadata">

**Author:** ![pazzo83](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pazzo83/32/232_2.png) [@pazzo83](https://discourse.julialang.org/u/pazzo83)\
**Post date:** [June 4, 2019, 5:51pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/12 "2019-06-04T17:51:34Z")

</div>

I figured out my issue with the REPL not starting → for some reason I needed to start it with `sudo`. Is there any local configuration that would force that?

---

<div class="post-metadata">

**Author:** ![pazzo83](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pazzo83/32/232_2.png) [@pazzo83](https://discourse.julialang.org/u/pazzo83)\
**Post date:** [June 4, 2019, 6:49pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/13 "2019-06-04T18:49:40Z")

</div>

sorry for the spam, but I’ve corrected my issue. I had the env var `JULIA_BINDIR` set to point to the 1.1 `bin` directory. I removed that and the 1.2 REPL now opens without issue.

---

<div class="post-metadata">

**Author:** ![Gnimuc](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gnimuc/32/2194_2.png) [@Gnimuc](https://discourse.julialang.org/u/Gnimuc)\
**Post date:** [June 6, 2019, 7:20am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/14 "2019-06-06T07:20:04Z")

</div>

I’m wondering whether those Windows binaries were built using [the latest LLVMBuilder](https://github.com/staticfloat/LLVMBuilder/releases/tag/v6.0.1-5%2Bnowasm) nor not.

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [June 24, 2019, 12:45pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/15 "2019-06-24T12:45:28Z")

</div>

It would be nice if someone from the core team could give a brief update about the state of 1.2. I see [two outstanding issues](https://github.com/JuliaLang/julia/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.2) that have been around for a while, so I assume they are not very easy to fix.

Note that I understand that things take time and I respect the work people have put in to fix difficult issues. I am just asking for information, not urging anything.

---

<div class="post-metadata">

**Author:** ![ImreSamu](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/imresamu/32/20677_2.png) [@ImreSamu](https://discourse.julialang.org/u/ImreSamu)\
**Post date:** [June 24, 2019, 1:05pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/16 "2019-06-24T13:05:04Z")

</div>

> [@Tamas\_Papp](#):
>
> the state of 1.2.

WIP: `1.2.0 rc2`

> <https://github.com/JuliaLang/julia/pull/32270>
>
> Backported PRs:
> \- \[x\] #31933 - Unconditionally append lib/julia to rpath, fixes… #31903.
> \- \[x\] #31946 - Fix for optind in getopt on musl libc.
> \- \[x\] #32072 - Two fixes to win32 cross compilation
> \- \[x\] #32139 - fix #32121, macro hygiene bug in named tuples
> \- \[x\] #32144 - Fully qualify at-everywhere, fixes #28966.
> \- \[x\] #32161 - Fix unsigned wrap around in lpad/rpad/string allocation
> \- \[x\] #32192 - Bump OpenBLAS BB tarballs to \`v0.3.5-2\`, to fix FreeBSD
> \- \[x\] #32219 - fix LibGit2 test: unknown repo now returns error instead of EAUTH
> \- \[x\] #32260 - Remove internal sort from \`getipaddrs\`
> \- \[x\] #32041 - RFC: use \`AbstractMatrix\` as the eltype of \`Symmetric\` for array of arrays
> \- \[x\] #32255 - readdlm(bytearray) shouldn't modify bytearray
> \- \[x\] #32266 - Remove copy(::SubArray) definition from SparseArrays, fixes #32213.
> \- \[x\] #32169 - fix build with JULIA\_ENABLE\_THREADING==0
> \- \[x\] #32281 - Bump Pkg to v1.2.0-rc2.
> \- \[x\] #31499 - fixes for getindex tab-completion
> \- \[x\] #32326 - fix #32325, struct plus outer ctor inside \`let\`
> \- \[x\] #32351 - Fix tryparse for invalid Chars
> \- \[x\] #32383 - Add missing test dependency on Random to Statistics
> \- \[x\] #32375 - Fix -Symmetric for Bool or JuMP.VariableRef
> \- \[x\] #32356 - codegen,tbaa: fix array isassigned tbaa information
> \- \[x\] #32431 - Fix Distributed.head\_and\_tail
> \- \[x\] #32425 - fix #32386, type intersection bug in var bounds
> \- \[x\] #32428 - fix #30653, call \`malloc\_trim\` sometimes
> \- \[x\] #32412 - Prevent download on windows picking up rogue curl executable
> \- \[x\] #32464 - fix the fix for #32121, more named tuple macro hygiene
> \- \[x\] #32457 - bug fixed in read\_to\_buffer 
> \- \[x\] #32494 - fix #32465, inference of splatting unionall NamedTuple types
> \- \[x\] #32512 - fix #32499, regression in struct expr in assignment rhs #32512
> 
> 
> Non-merged PRs with backport label:
> \- \[\] #32512 - fix #32499, regression in struct expr in assignment rhs
> \- \[\] #32327 - bug fixes in matrix log
> \- \[\] #32271 - \[Statistics\] fix type determination in corm
> \- \[\] #32145 - fix bug in block renaming for dead code elimination

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [June 24, 2019, 1:48pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc1-is-now-available/24788/17 "2019-06-24T13:48:01Z")

</div>

Both of them should be fixed in the rc 2 backport branch.