Closed pgomba closed 1 year ago
Interesting - I just tested and it only happens on my machine when I explicitly call progress_bar=TRUE
(but not when it is left out, even though TRUE
is the default). Can you confirm that this is the same on your machine?
Will look into this ASAP.
The issue still exists for me on a clean session with progress_bar=TRUE
left out.
I've tested it using a different subsample of my species list (n=400), and the progress bar stops at 98%.
Happy to have a Teams meeting if makes things easier!
Fixed in branch, will close when merged
Hi, the progress bar from
wcvp_match_names()
withprogress_bar=TRUE
works well the first time. But ifwcvp_match_names()
is used again the progress is spammed everytime the function uses a function fromcli::
. I have tested this only in one computer. If I runwcvp_match_names()
and afterwards I run, for examplecli::cli_h1("test")
, the message "test" appears in the console terminal followed by the last state of the progress bar (see attached file). I think the "problem" might be related to the functionedit_match()
, within the functionwcvp_match_fuzzy()
, in particuar this this bitwithr::local_options(list(cli.progress_show_after = 2, cli.progress_clear = FALSE))
, but I have not been able to solve it. Maybe the progress bar is not reaching 100% and the environment keeps the info?My main issue is that I use cli:: in other functions and now I have a frozen progress bar showing everywhere! :D