-
Notifications
You must be signed in to change notification settings - Fork 40
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
BUG: "Could not read results" on large result file? #371
Comments
Added a
If that makes any sense to you... 🤔 |
Here's the result-file causing the crash: (Only available via my OneDrive for 2 weeks, so grab it while you can 🙂) |
Looks like you've found a pathological case for my file printing! I don't just read the file as text, but I actually
Should be an easy fix, I'll have a crack now. |
Should be fixed in 3.1.2! |
Awesome! Will test it at work tomorrow 👍 |
✅ Seems to work now, thanks 😊👍 |
I have the following
.betterer.ts
:Running
npx betterer
the first time works fine, and the.betterer.results
is generated. However, when I try to run it again, I get the following error:.betterer.results
, and.skip()
thestricter eslint
test, then it runs fine both times..betterer.results
, and.skip()
thestricter typescript
test, then I get the same error.In other words, the
stricter eslint
test caused the second run to fail, regardless of thestricter typescript
being part of it or not.Adding
@betterer/eslint
did make the.betterer.results
file grow from ~2k lines to ~15k lines. So from from what I can gather, this must probably have something to do with how you're trying to read that file? Is it running into some sort of size/buffer issue or something? Not sure why the file size should be an issue, but the way that file is read here does seem a bit... special... 🤔I guess it could also be related to the format of the output from
@betterer/eslint
vs@betterer/typescript
, but as far as I can see, those look pretty much identical, so... 🤷♂️The text was updated successfully, but these errors were encountered: