Support ProgressMeter or other progress logging utiliites such Term.jl?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the predefined controls that emit messages with @info, then inspect how their output interacts with ProgressMeter or Term.jl. The work is done when predefined-control messages no longer disrupt the progress meter and the relevant behavior is covered by an appropriate test.
Written by the indexing model from the issue text.
Description
Currently, predefined controls emits message by using @info which will break ProgressMeter. The issue is that the progress meter will no longer stay at the same place as the @info displays. The suggested fix is to wrap the message in rpad such as
@info rpad("my message ...", displaysize(stdout)[2])
However, with the predefined control behavior, it is impossible to wrap the message before @info.
- Dominant language
- Julia
- Stars
- 25
- Forks
- 1
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 6
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from JuliaAI/IterationControl.jl
-
Add an `IterationControl.warmup(control)` wrapper for controlsMay be free again @aviralgarg05 claimed this 11 days ago, and no pull request is open. Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 30/100
JuliaAI/IterationControl.jl#76 · 2 comments ·
Maintainers usually reply within 1 day
-
Have `train!` record, for inclusion in output, a history of the public state of every controlMay be free again @ablaom claimed this 45 days ago, and no pull request is open. Open
JuliaAI/IterationControl.jl#64 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
JuliaAI/IterationControl.jl#63 · 1 comment ·
Maintainers usually reply within 1 day
-
next breaking release
Difficulty 4/5 3-5 days Newbie friendliness 35/100
JuliaAI/IterationControl.jl#62 ·
Maintainers usually reply within 1 day
-
Remove unnecessary restriction that a callback function `<:Function`. That is, allow any callable.Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
JuliaAI/IterationControl.jl#59 ·
Maintainers usually reply within 1 day
All issues in JuliaAI/IterationControl.jl
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Sienna-Platform/PowerSimulations.jl#1737 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FluxML/Optimisers.jl#254 ·
-
Minor: floodplain warning percentage, scalar output error message and a never-true identity checkOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JuliaAI/MLJTransforms.jl#101 ·
Maintainers usually reply within 1 day
-
@contents blocks fail to render on Julia 1.14Possibly taken @sbfnk claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LuxDL/DocumenterVitepress.jl#410 ·