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

Provider Error when parsing replay #65

Open
FranzHahn opened this issue Oct 1, 2023 · 2 comments
Open

Provider Error when parsing replay #65

FranzHahn opened this issue Oct 1, 2023 · 2 comments

Comments

@FranzHahn
Copy link

I used to have this running a couple years ago for a sideproject. Wanted to pick it back up and grabbed a new version of this parser and reused parts of my old code. When posting a current replay to the parser I keep getting thrown this Exception:

skadistats.clarity.ClarityException: oops. no provider found for required usage point interface opendota.processors.warding.OnWardKilled

I read in #29 that someone was having a similar problem in 2019, however they were running a wrong jdk version. To the best of my knowledge I'm running JDK 8.

I'd love if someone could chime in and help me figure this out.

@FranzHahn
Copy link
Author

I've tinkered around a bit, removed the automatically added JRE and added the 1.8 JRE again, still getting missing provider errors.

I'm not sure how to proceed. I remember getting it working quite easily the last time I used this parser. Although I also seem to be unable to get clarity/clarity-examples working, so it might just be me being dense.

@FranzHahn
Copy link
Author

I was made aware that I had to turn on "annotation processors" when compiling clarity. After doing so, however, I simply got a different Provider error:

skadistats.clarity.ClarityException: oops. no provider found for required usage point interface skadistats.clarity.processor.packet.UsesPacketReader

I also missed another error that was further above, regarding SLF4J:

SLF4J: No SLF4J providers were found. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.

I've unsuccessfully tried including a separate version of the slf4j-api-2.0.5.jar in the build path, but that didn't seem to solve the problem.

I'd really appreciate further assistance. I hope it's not just me being stupid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant