Installing R Packages in Jupyter in Domo

I don't seem to be able to install new packages in R in Jupyter in Domo anymore.

In Domo the documentation, it shows an example of installing 'SentimentAnalysis' using install.packages().

https://domo-support.domo.com/s/article/36004740075?language=en_US

When I try that, or any other package, I get this warning:

Warning message:“unable to access index for repository https://cran.r-project.org/src/contrib:  cannot open URL 'https://cran.r-project.org/src/contrib/PACKAGES'”Warning message:“package ‘SentimentAnalysis’ is not available for this version of RA version of this package for your version of R might be available elsewhere,see the ideas athttps://cran.r-project.org/doc/manuals/r-patched/R-admin.html#Installing-packages”

I have been able to install packages in the past, so there appears to be some new problem. The error makes me think the version of R supported by Domo (4.1) is too old. 4.1 was released over 3 years ago, and the current version is 4.4, which gives credence to that, but SentimentAnalysis only depends on (R>2.1), so maybe there's something more locked down in the admin settings from Domo than before.

Anyone know what's going on?

Please 💡/💖/👍/😊 this post if you read it and found it helpful.

Please accept the answer if it solved your problem.

Answers

  • The warning about being unable to access the CRAN repository seems to indicate the environment in Domo might be blocked from making outgoing connections. Possibly due to network or firewall settings…on Domo's side? Can you install from a mirror?

    install.packages('SentimentAnalysis', repos = 'https://cloud.r-project.org')
    

    Sentiment Analysis appears to only require R >= 2.1, which should be compatible with your version.

    ** Was this post helpful? Click Agree or Like below. **
    ** Did this solve your problem? Accept it as a solution! **

  • No, can't install from a mirror or directly from GitHub

    Please 💡/💖/👍/😊 this post if you read it and found it helpful.

    Please accept the answer if it solved your problem.

  • I'd recommend logging a ticket with Support as it appears to be a backend issue

    **Was this post helpful? Click Agree or Like below**
    **Did this solve your problem? Accept it as a solution!**