Greg Poisson

Results 10 comments of Greg Poisson

Confusing error message "OSError: [Errno 22] Invalid argument" when incorrect filepath is specified for `open`

Also encountering this issue, here is an example of r2pipe claiming my argument is invalid: ``` C:\Users\sordidlist λ python3 -c "import r2pipe; r = r2pipe.open('C:/Users/sordidlist/Desktop/brainpan.exe', flags=['-A']); r.cmd('iz')" Warning: set your...

Confusing error message "OSError: [Errno 22] Invalid argument" when incorrect filepath is specified for `open`

I gave it a try with the latest build from git, but got the same behavior. I discovered that if I copy the file to the current dir AND take...

Confusing error message "OSError: [Errno 22] Invalid argument" when incorrect filepath is specified for `open`

I'd be happy to take a crack at it, if you don't mind helping me with specific places and things to test. Regarding the /, yeah, I should have also...

Confusing error message "OSError: [Errno 22] Invalid argument" when incorrect filepath is specified for `open`

Can confirm it works if I escape the backslashes like `\\`, and also if I use `r'string'`. I've used byte strings in python before but I didn't know about raw...

Confusing error message "OSError: [Errno 22] Invalid argument" when incorrect filepath is specified for `open`

The only other thing is the `flags=['-A']` thing but the workaround of doing `r.cmd('aaa')` works just fine for me. I'll re-test the flags issue with the binary in the local...

Confusing error message "OSError: [Errno 22] Invalid argument" when incorrect filepath is specified for `open`

If you've got bigger bugs to squash, I'm okay with closing this issue.

Confusing error message "OSError: [Errno 22] Invalid argument" when incorrect filepath is specified for `open`

Yep I can test that out this evening for sure

docker: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: detection error: nvml error: function not found: unknown.

I've also encountered this error, using Docker Desktop for Windows 10. And for some reason, downgrading to 3.3.0 hasn't changed the error at all. nvidia-smi gives me proper output (SMI...

docker: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: detection error: nvml error: function not found: unknown.

Yes, I rebooted after downgrading and also tried deleting and recreating the image.

docker: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: detection error: nvml error: function not found: unknown.

Weird. I switched from linux containers to windows containers, and then back to linux containers, and now the container seems to run.