Non-termination or generation with 2.9.1
See original GitHub issueUnder the newly released 2.9.1, on some modules in my project (one so far) I seem to end up with the non-terminating compile phase in maven, with no classes being generated under target/generated-sources/annotations
.
This runs fine under 2.9.0 - what’s the best way to debug what immutables is doing?
Are there any debug flags I can enable to provide more information?
Issue Analytics
- State:
- Created a year ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Using Graph Neural Networks for Program Termination
The repository contains a sample dataset that can be used to train a classifier for program termination based on the abstract syntax tree...
Read more >mapbox-gl-js/CHANGELOG.md at main - GitHub
2.9.1. Bug fixes. Fix missing lines on some Windows devices. (#12017) ... Added localFontFamily map option that enables local generation of all font ......
Read more >CCES 2.9.0 C/C++ Compiler Manual for SHARC Processors
Multi-Threaded and Non-Terminating Applications . ... Disables the automatic generation of circular buffer code by the compiler. -no-const-strings.
Read more >Public Release Note - Intershop Order Management 2.9
Version Intershop Order Management / 2.9.1 ... can be downloaded here and used for automated REST-client generation for example.
Read more >Key Concepts -- The Annotated VRML97 Reference Manual
2.2.6 Generating VRML files ... 2.9.1 EXTERNPROTO interface semantics ... A generator is a human or computerized creator of VRML files.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I won’t submit my PR then 😃 Cheers.
The interesting about concurrent map is that
computeIfAbsent
call seems to be recursive, and if this is happening on the same map instance - this can be part of the issue / sort of deadlock (computing entry while computing another entry). looking into it. Thank you for the dump, definitely we have some pointers for now