Let qlever index fail if setting the initial ulimit fails
#130
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hannahbast
changed the title
qlever index fail if the initial ulimit fails
hannahbast
changed the title
qlever index fail if the initial ulimit failsqlever index fail if setting the initial ulimit fails
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The command used by
qlever indexnow looks like this:ulimit -Sn <ulimit> && IndexBuilderMain ...(so far, the&&was a;). The defaultulimitfor inputs larger than 10 GB has been reduced from 1048576 to 500000.NOTE: If the reason for a failure was a too large
ulimit, see #132