Replies: 1 comment 2 replies
-
|
No idea why the underlying Process's In any case, it looks like the same issue could be reproduced by using |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have an open source project named Recyclarr, which is a console application currently utilizing CliWrap. A user of mine reported an exception (copied below) originating from CliWrap. The underlying exception is
AccessViolationExceptioncoming from what appears to be CliWrap's attempt to read from theStandardOutputstream of theProcessclass.The user is running on a Apple M1 Mac Mini. My primary question is: What would be the underlying issue causing this? My best guess right now is that there's a permission problem preventing .NET from accessing the stdout of the process (A
gitcommand is being executed in this case). It looks like stdout access is facilitated through network sockets, but it's unclear what corrective action the user must take.I'm doubtful that this is an issue in CliWrap itself. I'm hoping that the domain expertise of the maintainers here can help point me in the right direction.
If there's more information I can provide please let me know. Thank you in advance for your support!
Beta Was this translation helpful? Give feedback.
All reactions