timholy / timholy/ProgressMeter.jl
`Main.IJulia` cause problems with JET.jl
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 789
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
Minor issue, but adding ProgressMeter to a package adds noise to JET due to IJulia not being available:
┌ (::Rasters.var"#5677#threadsfor_fun#239")(tid::Any; onethread::Any) @ Rasters C:\Users\rafael.schouten\.julia\dev\Rasters\src\utils.jl:469
│┌ next!(p::Union{ProgressMeter.Progress, ProgressMeter.ProgressUnknown}) @ ProgressMeter C:\Users\rafael.schouten\.julia\packages\ProgressMeter\kVZZH\src\ProgressMeter.jl:470
││┌ next!(p::ProgressMeter.Progress; step::Int64, options::@Kwargs{}) @ ProgressMeter C:\Users\rafael.schouten\.julia\packages\ProgressMeter\kVZZH\src\ProgressMeter.jl:471
│││┌ lock_if_threading(f::ProgressMeter.var"#16#17"{Int64, @Kwargs{}, ProgressMeter.Progress}, p::ProgressMeter.Progress) @ ProgressMeter C:\Users\rafael.schouten\.julia\packages\ProgressMeter\kVZZH\src\ProgressMeter.jl:453
││││┌ lock(f::ProgressMeter.var"#13#14"{ProgressMeter.var"#16#17"{…}}, l::ReentrantLock) @ Base ./lock.jl:232
│││││┌ (::ProgressMeter.var"#13#14"{ProgressMeter.var"#16#17"{Int64, @Kwargs{}, ProgressMeter.Progress}})() @ ProgressMeter C:\Users\rafael.schouten\.julia\packages\ProgressMeter\kVZZH\src\ProgressMeter.jl:454
││││││┌ (::ProgressMeter.var"#16#17"{Int64, @Kwargs{}, ProgressMeter.Progress})() @ ProgressMeter C:\Users\rafael.schouten\.julia\packages\ProgressMeter\kVZZH\src\ProgressMeter.jl:473
│││││││┌ kwcall(::@NamedTuple{ignore_predictor::Bool}, ::typeof(ProgressMeter.updateProgress!), p::ProgressMeter.Progress) @ ProgressMeter C:\Users\rafael.schouten\.julia\packages\ProgressMeter\kVZZH\src\ProgressMeter.jl:210
││││││││┌ updateProgress!(p::ProgressMeter.Progress; options::@Kwargs{ignore_predictor::Bool}) @ ProgressMeter C:\Users\rafael.schouten\.julia\packages\ProgressMeter\kVZZH\src\ProgressMeter.jl:212
│││││││││┌ kwcall(::@NamedTuple{ignore_predictor::Bool}, ::typeof(ProgressMeter._updateProgress!), p::ProgressMeter.Progress) @ ProgressMeter C:\Users\rafael.schouten\.julia\packages\ProgressMeter\kVZZH\src\ProgressMeter.jl:216
││││││││││┌ _updateProgress!(p::ProgressMeter.Progress; showvalues::Tuple{}, truncate_lines::Bool, valuecolor::Symbol, offset::Int64, keep::Bool, desc::Nothing, ignore_predictor::Bool, force::Bool, color::Symbol, max_steps::Int64) @ ProgressMeter C:\Users\rafael.schouten\.julia\packages\ProgressMeter\kVZZH\src\ProgressMeter.jl:250
│││││││││││┌ move_cursor_up_while_clearing_lines(io::IO, numlinesup::Int64) @ ProgressMeter C:\Users\rafael.schouten\.julia\packages\ProgressMeter\kVZZH\src\ProgressMeter.jl:592
││││││││││││┌ getproperty(x::Module, f::Symbol) @ Base ./Base.jl:42
│││││││││││││ `IJulia` is not defined: Base.getglobal(x::Module, f::Symbol)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the JET.jl diagnostic with a package that adds ProgressMeter while IJulia is unavailable. Read ProgressMeter.jl around updateProgress! and move_cursor_up_while_clearing_lines; done means the ProgressMeter path no longer produces the IJulia undefined warning under that setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100