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

readCreateProcessWithExitCode: runInteractiveProcess: exec: resource exhausted (Argument list too long) #62

Closed
watashi opened this issue Mar 21, 2024 · 0 comments · Fixed by #63

Comments

@watashi
Copy link
Contributor

watashi commented Mar 21, 2024

This was an regression introduced by #31
The main purpose of xargs was to ensure the command line is never too long to exceed getconf ARG_MAX, which is likely 2M.
To repro:

LONG_DIR=$(echo $(seq 60) | tr ' ' '-')
mkdir $LONG_DIR
for i in $(seq 30000); do echo "foo bar" > $LONG_DIR/$i.hs; done
find -name '*.hs' | wc
#  30000   30000 5448894
retrie --adhoc 'forall x. foo (bar x) = x' -t . -v 2
# retrie: /bin/sh: readCreateProcessWithExitCode: runInteractiveProcess: exec: resource exhausted (Argument list too long)
watashi added a commit to watashi/retrie that referenced this issue Mar 22, 2024
Closes facebookincubator#62

We removed the depedency on xargs to for better windows compatibility.
However, xargs was mainly introduced to break shell call into multiple
ones to avoid hitting the system limit when we have tens of thousands
files. We need to simulate this behavior.
watashi added a commit to watashi/retrie that referenced this issue Mar 22, 2024
Closes facebookincubator#62

We removed the depedency on xargs to for better windows compatibility.
However, xargs was mainly introduced to break shell call into multiple
ones to avoid hitting the system limit when we have tens of thousands
files. We need to simulate this behavior.
josefs pushed a commit that referenced this issue Mar 22, 2024
#63)

Closes #62

We removed the depedency on xargs to for better windows compatibility.
However, xargs was mainly introduced to break shell call into multiple
ones to avoid hitting the system limit when we have tens of thousands
files. We need to simulate this behavior.
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

Successfully merging a pull request may close this issue.

1 participant