delay starting executors for graal compilation #572
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Graal does not like it when
Thread
objects are initialized at build time (statically)e.g. error:
Wrapping the statically defined
connection-pool
s andexecutor
s withdelay
ensures that the threads are not started until runtime.Also upgrading
netty
resolves this object initialization error when compiling with graal:And finally when clj-commons/byte-streams#50 gets merged I would like to include up-versioning
byte-streams
in this pr.