# \[ANN\] Juno 0.8

**URL:** <https://discourse.julialang.org/t/ann-juno-0-8/22157>\
**Category:** Juno\
**Tags:** announcement, juno\
**Created:** [March 21, 2019, 5:46pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157 "2019-03-21T17:46:59Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![sairus7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sairus7/32/10816_2.png) [@sairus7](https://discourse.julialang.org/u/sairus7)\
**Post date:** [March 25, 2019, 3:13am UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/21 "2019-03-25T03:13:10Z")

</div>

I have the same problem after periodical Atom updates (Windows), reinstalling `uber-juno` helps.

---

<div class="post-metadata">

**Author:** ![xiaodai](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xiaodai/32/15937_2.png) [@xiaodai](https://discourse.julialang.org/u/xiaodai)\
**Post date:** [March 25, 2019, 3:52am UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/22 "2019-03-25T03:52:14Z")

</div>

I have the same issue. I found this one trick that works. Go to the uber-juno setting page and you should see a “Disable” checkbox, can’t remember the full name.

Uncheck it and then press the button to disable the whole module (note this is not the same as the checkbox), now enable it right away without restarting Julia. Basically, click on the disable/enable button twice in a row while “Disable…” checkbox is unchecked. It should rebuild Juno for Atom.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [March 25, 2019, 8:28am UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/23 "2019-03-25T08:28:24Z")

</div>

> [@joa-quim](#):
>
> Don’t get it but my Atom seems to be always (half)broken. I have `Uber-Juno` installed and .jl files are rcognised as Julia files but there is no “Packages-\>Julia”, nor `Ctrl-j, Ctrl-o` open any console.

Yeah, this is an unfortunate bug that I didn’t quite solve yet. Following the instructions in the first post should work fine though:

> [@pfitzseb](#):
>
> ## Installation
> 
> **Important** : Restart Atom before updating `julia-client` or `ink` and do _not_ start a Julia session.  
> If that does not work, close all Atom instances and type
> 
> ```julia
> apm uninstall ink
> apm install ink
> apm uninstall julia-client
> apm install julia-client
> 
> ```
> 
> into a terminal.
> 
> As always, make sure all Julia and Atom packages are up-to-date.

* * *

> [@stillyslalom](#):
>
> Seems as if it’d be worth automatically calling `includet` when a breakpoint is set outside of a module with Revise loaded.

Hm, that does result in running all code in that file whenever you set your first breakpoint. Doesn’t seem like something I’d expect to happen.  
I also wanted to avoid loading Revise when the user tries to set a breakpoint because it’s such a big change in behaviour. Not sure what would be the best way to streamline source breakpoints though…

**Edit** : I suppose we could automatically `Revise.track` files if Revise is loaded. This might also make sense for Debugger.jl (or even JuliaInterpreter.jl). What do you think, @tim.holy/@kristoffer.carlsson?

---

<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:** [March 25, 2019, 9:39am UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/24 "2019-03-25T09:39:53Z")

</div>

Yes, if possible, just having Revise track a file without running any code in it would be good to do when setting a breakpoint in a file. I’m not really familiar with the internals of Revise so not sure if the methods actually have to be defined for the tracking to work.

---

<div class="post-metadata">

**Author:** ![tim.holy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tim.holy/32/52_2.png) [@tim.holy](https://discourse.julialang.org/u/tim.holy)\
**Post date:** [March 25, 2019, 11:48am UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/25 "2019-03-25T11:48:03Z")

</div>

Long-term, automatically tracking is a good solution. To avoid derailing this thread, I answered this in a new one: [Future development goals with the new Revise](https://discourse.julialang.org/t/future-development-goals-with-the-new-revise/22298).

---

<div class="post-metadata">

**Author:** ![BioTurboNick](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bioturbonick/32/6380_2.png) [@BioTurboNick](https://discourse.julialang.org/u/BioTurboNick)\
**Post date:** [March 25, 2019, 3:17pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/26 "2019-03-25T15:17:39Z")

</div>

My Atom Julia 1.1 install is stuck on Atom.jl 0.7.14. I tried to Pkg.free() it, but no change.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [March 25, 2019, 3:30pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/27 "2019-03-25T15:30:53Z")

</div>

Try explicitly adding v0.8 and the deinstalling packages that are incompatible.

---

<div class="post-metadata">

**Author:** ![jebej](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jebej/32/1784_2.png) [@jebej](https://discourse.julialang.org/u/jebej)\
**Post date:** [March 25, 2019, 3:47pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/28 "2019-03-25T15:47:49Z")

</div>

To update now I actually fully close Atom and run `apm update`

---

<div class="post-metadata">

**Author:** ![jebej](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jebej/32/1784_2.png) [@jebej](https://discourse.julialang.org/u/jebej)\
**Post date:** [March 25, 2019, 3:49pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/29 "2019-03-25T15:49:54Z")

</div>

I had a question regarding the file links e.g. when an error occurs. It looks as if the links are clickable, because the cursor changes when I hover over one. However, nothing actually happens when I click, is that normal?

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [March 25, 2019, 3:57pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/30 "2019-03-25T15:57:00Z")

</div>

Definitely not normal, no. What files are you trying to open when nothing happens (if e.g. Juno can’t find the file nothing happens when you click on the link)?

---

<div class="post-metadata">

**Author:** ![jebej](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jebej/32/1784_2.png) [@jebej](https://discourse.julialang.org/u/jebej)\
**Post date:** [March 25, 2019, 4:03pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/31 "2019-03-25T16:03:44Z")

</div>

So after checking again, it works with base julia files, but not with my own. Nothing happens, no errors.

---

<div class="post-metadata">

**Author:** ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)\
**Post date:** [March 25, 2019, 4:40pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/32 "2019-03-25T16:40:12Z")

</div>

I think I don’t understand the workflow…

I’m trying what I think would be the simplest scenario:  
1 - I have a julia file, `debugtest.jl`, containing

```julia
function foo(x = 0)
  for i = 1:10
    x += i^2 # breakpoint here, I want to watch x
  end

  x
end

foo(10)

```

2 - I open the file in Atom

3 - I set a breakpoint where the comment is as I want to see the value of x at each iteration.

Upon setting the breakpoint I get

```julia
no signatures found at /Users/adrian/Downloads/debugtest.jl, 3.
Restarting and `using Revise` and the relevant package may fix this problem

```

`Revise` is added to `startup.jl` and is being used.

 ![image](https://global.discourse-cdn.com/julialang/original/3X/6/6/6618a660d5c3a907bbcbcd930888490f14424e9c.png)  
(Sorry for the screenshot, as a side note, a super-hyper-mega annoying thing is that the Julia REPL in Atom doesn’t allow selecting and copying, my selection is immediately cleared the second I let go of the mouse)

 ![image](https://global.discourse-cdn.com/julialang/original/3X/6/d/6d5b355f7b0ca165e6f0c50c9645e22b0c78a39f.png)

I checked all the posts, I updated the packages, I removed and reinstalled the Atom packages as instructed here… nothing.

---

<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:** [March 25, 2019, 4:42pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/33 "2019-03-25T16:42:06Z")

</div>

`includet("debugtest.jl")` before setting the breakpoint.

---

<div class="post-metadata">

**Author:** ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)\
**Post date:** [March 25, 2019, 4:53pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/34 "2019-03-25T16:53:05Z")

</div>

@kristoffer.carlsson Thank you, now the error is gone. I run `includet("debugtest.jl")` in the Juno REPL. I presume this is about configuring the entry point into the program for the debugger.

To quote Nemo, “now what”? Upon pressing the `Debug: Next expression` I get

```julia
You can start debugging by calling `@enter f(args...)`.

```

When I try that, I get

 ![image](https://global.discourse-cdn.com/julialang/original/3X/2/6/267f1a3e222f49a409ed95ed2a906cdfee03185c.png)  
🙉

Ideally, I’d like the debugger to kick in every time I use `Run block` or `Run file` in Juno, now the the breakpoint is set…

---

<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:** [March 25, 2019, 4:55pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/35 "2019-03-25T16:55:50Z")

</div>

Use `Juno.@enter` (which is what the first post says).

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [March 25, 2019, 4:57pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/36 "2019-03-25T16:57:49Z")

</div>

Do take a look at our [docs](http://docs.junolab.org/latest/man/debugging/).

In short: You need `Juno.@enter` or `Juno.@run`. I’ll add a checkbox in the Debugger pane to make all code run with `Juno.@run`.

---

<div class="post-metadata">

**Author:** ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)\
**Post date:** [March 25, 2019, 5:02pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/37 "2019-03-25T17:02:05Z")

</div>

It works!!!

![happy my heart GIF](https://global.discourse-cdn.com/julialang/original/3X/7/d/7d5bf0a3ac9c95e8407caa91bc7ba7425aa89cae.gif)

---

<div class="post-metadata">

**Author:** ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)\
**Post date:** [March 25, 2019, 5:06pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/38 "2019-03-25T17:06:57Z")

</div>

Thank you, I did! However it’s been difficult navigating all the updates in the last few days, as we were given multiple options and workflows with little details (with Juno, with Rebugger, etc). So the docs pretty much lost me at `Open a console and type Juno.@enter split("Hello, world", isspace)` as I expected the debugging to work with `run block` or `run file` or the debug toolbar and this sounded like a non-IDE workflow.

Now I get it:  
1 - one needs `includet` to set the entry point for the debugger  
2 - one needs to kickstart the debugging by invoking the “main” function, again in the Juno REPL, with `Juno.@enter` or `Juno.@run`

---

<div class="post-metadata">

**Author:** ![braamvandyk](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/braamvandyk/32/5086_2.png) [@braamvandyk](https://discourse.julialang.org/u/braamvandyk)\
**Post date:** [March 25, 2019, 5:48pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/39 "2019-03-25T17:48:49Z")

</div>

Try uninstalling and reinstalling the Julia-client package. Mine breaks at every update, so I just un/reinstall to update.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [March 25, 2019, 5:50pm UTC](https://discourse.julialang.org/t/ann-juno-0-8/22157/40 "2019-03-25T17:50:00Z")

</div>

> [@essenciary](#):
>
> 1 - one needs `includet` to set the entry point for the debugger

You only need Revise and `includet` for source breakpoints, everything else works without that step.

[Previous page](https://discourse.julialang.org/t/ann-juno-0-8/22157.md?page=1)

[Next page](https://discourse.julialang.org/t/ann-juno-0-8/22157.md?page=3)
