EBADF: bad file descriptor, close #1845
Unanswered
chrisdrackett
asked this question in
Q&A
Replies: 1 comment 4 replies
-
|
Hey Chris, I'd love to hear if this is still a problem for you. v4.3.0 changed some things to keep more stack trace information, hopefully making debugging I/O issues like these easier. |
Beta Was this translation helpful? Give feedback.
4 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 just went to run a script that successfully ran without errors and the second time I ended up getting the following error for all my DAT files:
WARN DATs/No-Intro Love Pack (Standard) (2025-08-24).zip|Redump BIOS/Sony - PlayStation 2 - BIOS Images (DoM Version) (116) (2025-02-15).dat: failed to parse DAT file: failed to read 'DATs/No-Intro Love Pack (Standard) (2025-08-24).zip|Redump BIOS/Sony - PlayStation 2 - BIOS Images (DoM Version) (116) (2025-02-15).dat': Error: EBADF: bad file descriptor, closeand then after getting this for all DATs:
ERROR No valid DAT files found!I've checked the DATs in question and they all seem valid. I am running the script via
npxso is it possible I got a new bad package?Beta Was this translation helpful? Give feedback.
All reactions