The Elm server crashed 5 times in the last 3 minutes #103
Comments
|
Do you get any more logs? Go to the I just tried on windows and it seems to work fine for me. |
|
I had the same thing the past few days. On my home network on my desktop it works fine but on my laptop over a vpn i get the this error: |
|
Can you check if |
|
I try re-run that and found no packages in the elm stuff folder. this was started using elm init to start. May the package be in a global folder then in the project |
elm.json |
|
Packages don't get put into elm-stuff unless you change your elm-home env
to do that. Which is probably not wise, as it's a global thing.
…On Mon, 4 May 2020, 19:13 Joseph Karp, ***@***.***> wrote:
{
"type": "application",
"source-directories": [
"src"
],
"elm-version": "0.19.1",
"dependencies": {
"direct": {
"elm/browser": "1.0.2",
"elm/core": "1.0.5",
"elm/html": "1.0.0"
},
"indirect": {
"elm/json": "1.1.3",
"elm/time": "1.0.0",
"elm/url": "1.0.0",
"elm/virtual-dom": "1.0.2"
}
},
"test-dependencies": {
"direct": {},
"indirect": {}
}
}
elm.json
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#103 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNLEZGF6YCT6D5KH7A4NPDRP3ZPDANCNFSM4MYL5JGQ>
.
|
|
I have not change anything this is off a clean install |
|
Hmm, @ZergRushJoe mentioning VPN makes me think this may be may be related somehow to VPN and/or Forcepoint (our corporate firewall). I will try again on my personal Macbook and see if I'm successful. In the meantime, here is a Gist containing everything from the |
looking at your output seems to be the same error in mine @johncmunson |
|
Looking at the output, this seems to be a problem with We will need a fix in upstream I guess, I found this issue exploring the problem stil4m/elm-analyse#218 |
|
Disabling elm-analyze partially solved the problem. The error popup no longer appears, and several other features seem to be working now. "format on save" still broken though |
|
Can you be more explicit? Any logs? Is elm format working from the command line? |
Same for me! It crashes if elm analyser is acting on "change" or on "save", and stops crashing if I put never, but then "format on save" is not working anymore. I always had some crashes now and then until some months ago (didnt know that disabling elm analyze could fix it). I stopped using Elm since 1 or 2 months, and now that I came back this error happens 100% of the time. Maybe its a side effect from other package in VS Code? @razzeee Which type of log would you need and how to generate them? Im not used to generate logs for this type of situation. |
|
Interesting. On VScode terminal I run: |
|
Interesting, not sure how that's possible. Can you run format file from cli or get it to work in the elm-spa-example? |
|
I guess the easiest would be, if one of you could just locally debug the extension. |
|
Closing this due to inactivitiy. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
Several seconds after opening an elm project, I get a popup with the following error message.
Currently, the only feature that seems to be working is syntax highlighting. Formatting, etc, are not working.
Steps to Reproduce
npm install -g elm elm-format elm-testContext
Mainly, I would just like for the "format on save" feature to work. But I'd prefer that all of the features from the plugin started working.
Your Environment
The text was updated successfully, but these errors were encountered: