Skip to content
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

Rconsole: there is no package called ‘kableExtra’ #34

Open
squeezer44 opened this issue Jul 8, 2019 · 5 comments
Open

Rconsole: there is no package called ‘kableExtra’ #34

squeezer44 opened this issue Jul 8, 2019 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@squeezer44
Copy link

After pkginfo has started properly a click on the link CRAN Check (and all the other marked navigation points which are red marked) are showing the same error:
grafik

During that errors was shown the Rconsole is showing:
`125:
Warning: Error in loadNamespace: there is no package called ‘kableExtra’

165:
Warning: Error in loadNamespace: there is no package called ‘kableExtra’

165:
Warning: Error in loadNamespace: there is no package called ‘kableExtra’

165:
Warning: Unknown or uninitialised column: 'Branches'.
Warning: Error in loadNamespace: there is no package called ‘kableExtra’

165:
Warning: Error in loadNamespace: there is no package called ‘kableExtra’

120:
Warning: Error in loadNamespace: there is no package called ‘kableExtra’

120:
Warning: Error in loadNamespace: there is no package called ‘kableExtra’

165:
Warning: Error in loadNamespace: there is no package called ‘kableExtra’

165: `

@aravindhebbali aravindhebbali self-assigned this Jul 9, 2019
@aravindhebbali aravindhebbali added the bug Something isn't working label Jul 9, 2019
@aravindhebbali
Copy link
Member

The app seems to work fine when querying info for kableExtra. Can you check again? Below are the screenshots when I checked:

kableExtra_stack_overflow
kableExtra_releases
kableExtra_open_pull_requests
kableExtra_open_issues
kableExtra_github_branches
kableExtra_dependencies
kableExtra_cran_check_result

@squeezer44
Copy link
Author

@aravindhebbali
I've just rechecked this case: result is unchanged.

  • Steps I did before the error occured
  1. I've updated pkginfo locally successfully, empty my browser cache before starting the test.
  2. Than started the app
  3. openend the window in a browser
  4. Search for shiny
  5. Press Find User/Org
  6. Press retrieve information
  7. Click on http://127.0.0.1:6483/#shiny-tab-cran_check
    -> Same error occured.
  • Console output below

pkginfo_dashboard()

Listening on http://127.0.0.1:6483
Warning: Error in loadNamespace: there is no package called ‘kableExtra’
165:

  • Screenshot below
    grafik

Could it be you've fixed it locally but didn't deploy it into GitHub?

@squeezer44
Copy link
Author

squeezer44 commented Jul 10, 2019

@aravindhebbali
I found and fixed the reason: installed the package kableExtra locally and rerun the query - result: given result equal expected result and the error disappeared.

It seems pkginfo has a precondition for a few queries (f.e.: CRAN Check) and others (f.e. Downloads) don't. The error occured because my local environment missed the package kableExtra and ran so far into this error.

My Recommendation:
Before launching the app check whether the preconditions for a propper runing pkginfo are fullfilled.

@aravindhebbali
Copy link
Member

Hey @squeezer44, thanks for testing it again. Are you saying that if the package is not installed locally, pkginfo throws the error?

@squeezer44
Copy link
Author

squeezer44 commented Jul 10, 2019

Hi @aravindhebbali ,
First I want to thank you for that excellent package (it has already saved me a lot of time).

I'm just saying pkginfo calls the package kableExtra (inst/application/app.R - line number: 780) without having checked whether the package is available or not). That occured the error message locally at my computer (at the time of the errors I had not installed locally) and interrupted the proper running pkginfo. Not from the beginning but with clicking on CRAN check.
Because you already installed it locally you didn't notice it during the test - probably.

My recommendation: consider what's the best way to check whether the preconditions for a propper running pkginfo are fullfilled before the app is launching. That would avoid confusion on users side (and reduce effort on your side to find out the reason ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants