Closed TimTaylor closed 3 years ago
... so it's the vroom progress bar and can be suppressed with Sys.setenv("VROOM_SHOW_PROGRESS"="false")
and I guess possibly within the vroom call itself (not checked).
So it looks like this can be turned off manually. I guess there is a question of whether we should or leave it up to the user (a little like progressr
this seems to be implemented in a way that implies packages shouldn't decide for users?
(also thanks for flagging and investigating Tim).
I will push a PR to wrap this shortly
From a user perspective my main confusion was not knowing why I was getting 4/5 different progress bar remnants coming up. There seemed to be a disconnect from what the user thinks is happening versus what was going on behind the scenes (i.e. the user implements 1 operation but behind the scenes this is multiple things and the remnants reflect that). My inclination would be to try to combine the progess on these or, if tricky, just hide it.
That sounds so hard! Squashing time.....
On a serious note all good points and I agree we should hide if not able to do something better.
This is a little odd and potentially an rstudio thing but when using
get_regional_data()
I get some artefacts on the screen which I assume are timings. They don't appear when using R in the terminal or when generating a reprex with rmarkdown :man_shrugging:rstudio
rmarkdown