Resolver: Stable release stays frozen on initial screen on Java 21 · Issue #1066 · icpctools/icpctools · GitHub
More Web Proxy on the site http://driver.im/
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
I tried using the stable version but no matter what I tried, the initial screen was the only thing I could see.
I tried Windows with Java 8 first which did not even run because Java 9 is needed (I think).
Then Windows with Java 21 which froze on the main screen.
Then Linux (Arch) with Java 21 which froze on the main screen in the same way.
This was 100% reproducible, using different contests on Kattis, both by URL and by downloading the event log and running locally.
Using the pre-release version worked out better and during initial testing I could see the resolver working correctly in many test runs.
Ultimately, it didn't for the presentation but I don't have a formal bug report on what went wrong there yet.
The text was updated successfully, but these errors were encountered:
Tagl
changed the title
Stable release stays frozen on initial screen on Java 21
Resolver: Stable release stays frozen on initial screen on Java 21
Oct 5, 2024
I tried using the stable version but no matter what I tried, the initial screen was the only thing I could see.
I tried Windows with Java 8 first which did not even run because Java 9 is needed (I think).
Then Windows with Java 21 which froze on the main screen.
Then Linux (Arch) with Java 21 which froze on the main screen in the same way.
This was 100% reproducible, using different contests on Kattis, both by URL and by downloading the event log and running locally.
Using the pre-release version worked out better and during initial testing I could see the resolver working correctly in many test runs.
Ultimately, it didn't for the presentation but I don't have a formal bug report on what went wrong there yet.
The text was updated successfully, but these errors were encountered: