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

Too many files after moving from v1.2.0 to v2.0.0 and v2.2.0 #527

Open
jkleckner opened this issue Jul 12, 2024 · 0 comments
Open

Too many files after moving from v1.2.0 to v2.0.0 and v2.2.0 #527

jkleckner opened this issue Jul 12, 2024 · 0 comments

Comments

@jkleckner
Copy link

In a large Scala repo with submodules, I tested a lot of combinations of sbt versions and sbt-assembly versions and found that moving from sbt-assembly version 1.2.0 to 2.0.0 or 2.2.0 resulted in the message when running sbt assembly:

Could not create file /Users/.../data/target/streams/test/_global/_global/compileOutputs/previousjava.io.IOException: Too many open files

As mentioned in #463 (comment), there is increased memory use, but that is expected with the amount of caching going on.

The sbt-assembly version 1.2.0 worked with all sbt versions up to and including 1.10.1
But moving to 2.0.0 started getting that error on my Mac (64GB Intel Sonomo 14.5).
As described here, running ulimit -n 10240 (the maximum on a Mac) allowed sbt assembly to complete.

However, sbt Test/assembly would not work and would give "too many open files".
This part of an upgrade process from Scala 2.11.12 and Java 8 so perhaps that is a contributing factor.
Any suggestions on what to try?

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