search

yetibot / core

:expressionless: Core yetibot utilities, extracted for shared use among Yetibot and its various plugins
https://yetibot.com
Eclipse Public License 1.0
27 stars 17 forks source link

warnings on startup #183

Open KlavsKlavsen opened 3 years ago

KlavsKlavsen commented 3 years ago

I updated to latest helm chart (v1.0.54) - appversion: 20210504.191238.645270c

and still get these

 WARNING: read already refers to: #'clojure.core/read in namespace: wordnik.core, being replaced by: #'clojure.data.json/read                                                                                                            
 WARNING: Inst already refers to: #'clojure.core/Inst in namespace: schema.core, being replaced by: #'schema.core/Inst                                                                                                                   
 WARNING: An illegal reflective access operation has occurred                                                                                                                                                                            
 WARNING: Illegal reflective access by clojure.lang.InjectedInvoker/0x0000000840062040 (file:/root/.m2/repository/org/clojure/clojure/1.10.0/clojure-1.10.0.jar) to method sun.net.www.protocol.jar.JarURLConnection.getJarFile()        
 WARNING: Please consider reporting this to the maintainers of clojure.lang.InjectedInvoker/0x0000000840062040                                                                                                                           
 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations                                                                                                                                   
 WARNING: All illegal access operations will be denied in a future release
devth commented 3 years ago

I think these are unavoidable unless the underlying libraries fix the warnings.

KlavsKlavsen commented 3 years ago

Should probably be reported upstream at some point.. leave this as "contribution_wanted" task? - then someone can pick it up.. Perhaps someone from my team can do it, if I get it working and we start to really use it :)

devth commented 3 years ago

Sounds good. I did look around for a solution to this before but it's probably been over a year so things may have been updated. Thanks!