You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 11, 2019. It is now read-only.
I am doing a side Java project using JRI and twitteR to generate wordcloud using tweets. Since my R script is executed in a Java environment so JRI is used.
But JRI crashes with warning messages:
JRI Warning: jriReadConsole detected a possible deadlock [org.rosuda.JRI.Mutex@20ed2dc2[locked, by current thread]][Thread[qtp584131341-43,5,main]]. Proceeding without lock, but this is inherently unsafe.
Previously when the old twitter oauth setup functions, OAuthFactor and registerTwitterOAuth, were used, my project worked and the wordcloud was generated. But recently I picked this project up again and used the new OAuth setup function: setup_twitter_oauth, but JRI fails w/ warning messages given above.
Because only the authentication part of R script was changed, I guess it could be the existing oauth setup function in twitteR that causes this incompatibility. Anyone has any thoughts on this issue? Thanks a million.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am doing a side Java project using JRI and twitteR to generate wordcloud using tweets. Since my R script is executed in a Java environment so JRI is used.
But JRI crashes with warning messages:
Previously when the old twitter oauth setup functions, OAuthFactor and registerTwitterOAuth, were used, my project worked and the wordcloud was generated. But recently I picked this project up again and used the new OAuth setup function: setup_twitter_oauth, but JRI fails w/ warning messages given above.
Because only the authentication part of R script was changed, I guess it could be the existing oauth setup function in twitteR that causes this incompatibility. Anyone has any thoughts on this issue? Thanks a million.
The text was updated successfully, but these errors were encountered: