RatPoison-dev / RatPoison

Latest Ver: 1.7; Default Menu Key is F1; Charlatano's Successor; dn
GNU Affero General Public License v3.0
327 stars 95 forks source link

[BUG] #818

Closed SBMRocky closed 3 years ago

SBMRocky commented 3 years ago

Waiting for "Counter-Strike: Global Offensive" process... SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Game found. Launching. Waiting for App Initializing overlay Overlay initialized

sotakoira commented 3 years ago

get beta 1.8.5.8 from releases

aextise commented 3 years ago

awesome, beta 1.8 is still showing this result! You're the best sotakoira!

MaybeYouShould-GetTheHeckouttaHere commented 3 years ago

awesome, beta 1.8 is still showing this result! You're the best sotakoira!

the same thing happened to me on #817 (error #2) they don't give a f*ck

SPRAVEDLIVO commented 3 years ago

what is the bug here

sotakoira commented 3 years ago

oh he doesnt want that slf4j shit to appear, pretty sure wdal doesnt have it

theres also a way to disable it by dumping some jar file somewhere but this isnt really an error and shit works fine

If you are responsible for packaging an application and do not care about logging, then placing slf4j-nop.jar on the class path of your application will get rid of this warning message. Note that embedded components such as libraries or frameworks should not declare a dependency on any SLF4J binding but only depend on slf4j-api. When a library declares a compile-time dependency on a SLF4J binding, it imposes that binding on the end-user, thus negating SLF4J's purpose.

SPRAVEDLIVO commented 3 years ago

oh it is not a bug

sotakoira commented 3 years ago

819 yawn