-
Notifications
You must be signed in to change notification settings - Fork 146
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
StrictXmir
throws Premature end of file
#3760
Comments
@maxonfjvipon @yegor256 Please, have a look |
@volodya-lombrozo could you please provide a couple of details about how do you use |
@volodya-lombrozo I'm asking because we've already made a couple of concurrency tests for |
@maxonfjvipon Sure. I have the final Collection<Defect> defects = new Program(new StrictXmir(res)).defects()
.stream()
.filter(defect -> defect.severity() == Severity.ERROR)
.collect(Collectors.toList()); It's the exact place where the problem occurs. I create many |
…ict-classpath bug(#3760): Synchronized `StrictXmir`
@volodya-lombrozo try version 0.49.4 please |
@yegor256 Amazing news! We have managed to update |
I've updated
eo
version up to0.49.3
and now I'm getting the following exception:Full log:
build.log.txt
You can find the filed pipeline here:
https://github.com/objectionary/jeo-maven-plugin/actions/runs/12492715546/job/34860344624?pr=942#logs
Filesystem snippet is here:
https://github.com/objectionary/jeo-maven-plugin/actions/runs/12492715546/artifacts/2361347598
The text was updated successfully, but these errors were encountered: