# Atom Juno stopped providing backtraces with in-function line numbers

**URL:** <https://discourse.julialang.org/t/atom-juno-stopped-providing-backtraces-with-in-function-line-numbers/9218>\
**Category:** General Usage\
**Tags:** juno\
**Created:** [February 20, 2018, 11:29pm UTC](https://discourse.julialang.org/t/atom-juno-stopped-providing-backtraces-with-in-function-line-numbers/9218 "2018-02-20T23:29:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![clinton](https://avatars.discourse-cdn.com/v4/letter/c/7ba0ec/32.png) [@clinton](https://discourse.julialang.org/u/clinton)\
**Post date:** [February 20, 2018, 11:29pm UTC](https://discourse.julialang.org/t/atom-juno-stopped-providing-backtraces-with-in-function-line-numbers/9218/1 "2018-02-20T23:29:09Z")

</div>

Since the latest updates of Juno, the line numbers no longer reference the specific location of any errors, and instead refer to the initial function call. This is true with both the legacy console and the integrated repl.

```julia

function willfail()
  i::Int = 2.5
end

willfail()

```

Output:

```julia

LoadError: InexactError()
while loading C:\[...]\test.jl, in expression starting on line 6
in at base\task.jl:80
in macro expansion at Atom\src\eval.jl:99 
in hideprompt at Atom\src\repl.jl:59
in withpath at Atom\src\eval.jl:38
in withpath at CodeTools\src\utils.jl:30
in at Atom\src\eval.jl:104

```