-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
more informative error messages for update_packages() #223
Comments
+1. Just encountered this in the even less informative case where I hadn't yet installed from the bad remote, so I didn't even have a sha to work from. To reproduce:
Result:
|
Yet another 🤦♂️ that could potentially use a better remotes::update_packages("remedy")
#> Skipping 1 packages not available: remedy Huh? But I know that {remedy} is installed. sessioninfo::package_info("remedy")
#> package * version date lib source
#> assertthat 0.2.0 2017-04-11 [1] CRAN (R 3.5.1)
#> cli 1.0.1 2018-09-25 [1] CRAN (R 3.5.1)
#> crayon 1.3.4 2017-09-16 [1] CRAN (R 3.5.1)
#> evaluate 0.12 2018-10-09 [1] CRAN (R 3.5.1)
#> fansi 0.4.0 2018-10-05 [1] CRAN (R 3.5.1)
#> glue 1.3.0 2018-07-17 [1] CRAN (R 3.5.1)
#> highr 0.7 2018-06-09 [1] CRAN (R 3.5.1)
#> jsonlite 1.5 2017-06-01 [1] CRAN (R 3.5.1)
#> knitr 1.20 2018-02-20 [1] CRAN (R 3.5.1)
#> magrittr 1.5 2014-11-22 [1] CRAN (R 3.5.1)
#> markdown 0.8 2017-04-20 [1] CRAN (R 3.5.1)
#> mime 0.6 2018-10-05 [1] CRAN (R 3.5.1)
#> pillar 1.3.0.9000 2018-08-16 [1] Github (hadley/colformat@3fabb4e)
#> rematch2 2.0.1 2017-06-20 [1] CRAN (R 3.5.1)
#> remedy 0.0.0.9800 2018-09-17 [1] local
#> rlang 0.3.0.1 2018-10-25 [1] CRAN (R 3.5.1)
#> rstudioapi 0.8 2018-10-02 [1] CRAN (R 3.5.1)
#> stringi 1.2.4 2018-07-20 [1] CRAN (R 3.5.1)
#> stringr 1.3.1 2018-05-10 [1] CRAN (R 3.5.1)
#> tibble 1.4.2 2018-01-22 [1] CRAN (R 3.5.1)
#> utf8 1.1.4 2018-05-24 [1] CRAN (R 3.5.1)
#> yaml 2.2.0 2018-07-25 [1] CRAN (R 3.5.1)
#>
#> [1] C:/Users/daniel/Documents/.R/win-library
#> [2] C:/Program Files/R/R-3.5.1/library Oh, so apparently I installed it from my local repo. |
@dpprdan that's not an error message, it is just a message. |
@gaborcsardi True, I've updated my post. |
I am getting the same error message, in my case for the package
|
There is issue for this: #274 |
Had the same problem for the package nlmr: Error: HTTP error 422.
No commit found for SHA: develop
Rate limit remaining: 4891/5000
Rate limit reset at: 2019-06-20 04:45:50 UTC Since it was my very first time using Side note: this is a really great function. Thank you! |
While trying to narrow it down, I also noticed that |
Oh, this is great! Thank you @jimhester for the change! |
I encountered the following error message from
update_packages()
today.I had no idea what (package) might have caused this, but subsequently narrowed it down to a package, which I installed at the time from a now deleted Github branch.
Now maybe this particular case is a very rare one but nevertheless I think it might be helpful to get more informative (error) messages if
update_packages()
fails (e.g. which package caused the error), so the user knows better, where to look.Session info
The text was updated successfully, but these errors were encountered: