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

elm-review stalls on Windows after upgrading to 2.13 #340

Closed
bdukes opened this issue Feb 21, 2025 · 2 comments
Closed

elm-review stalls on Windows after upgrading to 2.13 #340

bdukes opened this issue Feb 21, 2025 · 2 comments

Comments

@bdukes
Copy link
Contributor

bdukes commented Feb 21, 2025

We're having issues with elm-review after upgrading, I think it's Windows-only. The review application runs but never outputs anything or exits. I can reproduce with a simple example, e.g. https://github.com/bdukes/elm-review-repro (which runs fine on WSL).

I think there are two issues occurring here. The first looks like it has something to do with the tinyglobby npm library. When I duplicate the logic from elm-review in a separate example app, it stalls out with tinyglobby 0.2.10, but finds the files with tinyglobby 0.2.12. However, even on 0.2.12, it does not find the files when it's called from the root directory (i.e. when the file is a child of cwd), but only when called from a separate directory. I can try to open an issue on their repo for that (though I'm not 100% sure there's no issue with how elm-review is translating the Windows path to the glob path).

The second issue is that, since elm-review is finding zero files, it is never receiving the acknowledgeFileReceipt message and so never knows that it's done. It's not showing the "NO FILES FOUND" message because options.directoriesToAnalyze.length is 0, I'm not sure if that's a valid reason to bypass that message in this scenario or not.

Happy to debug and try resolutions.

bdukes added a commit to bdukes/node-elm-review that referenced this issue Feb 21, 2025
bdukes added a commit to bdukes/node-elm-review that referenced this issue Feb 21, 2025
bdukes added a commit to bdukes/node-elm-review that referenced this issue Feb 21, 2025
This was referenced Feb 21, 2025
bdukes added a commit to bdukes/node-elm-review that referenced this issue Feb 22, 2025
bdukes added a commit to bdukes/node-elm-review that referenced this issue Feb 22, 2025
@jfmengels
Copy link
Owner

@bdukes The fix is released in v2.13.2. I hope this allows you to start the week with a working elm-review!

@bdukes
Copy link
Contributor Author

bdukes commented Feb 24, 2025

I've upgraded and confirmed that everything is working as expected for us now. Thanks!

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

No branches or pull requests

2 participants