elm-make: Map.!: given key is not an element in the map

[matthieu VIDAL]

Hi

I've got this poor error message :

elm-make: Map.!: given key is not an element in the map

when working with this sample :

http://elm-lang.org/examples/http


I've done the update from 0.17 to 018

Thanks

[Tom Ayerst]

Have you tried deleting elm-stuff (just build artefacts might work) and then rebuilding everything?

[matthieu VIDAL]

Hi

yes it solves the problem.

Thanks

[Anthony Naddeo]

Thanks a lot, was pretty confused about this one...

I'm assuming this should actually never happen. I'll have to see if anyone filed a bug on this. My project was brand new and all Elm .18, so this could probably happen to a new Elm user. It started happening after I installed the decoder pipeline package which also caused elm-make to upgrade the virtual dom version to 2.0.2 for some reason.

[maria nemcova]

Hi Anthony for me it's the same. Did u find some solution to fix it? thanks Maria

[Anthony Naddeo]

I actually just followed the advice in this thread and deleted the elm-stuff folder. Retrying from that point resulted in a re-download of the packages and everything worked out. I didn't have to do anything special beyond that unfortunately. 

--
You received this message because you are subscribed to a topic in the Google Groups "Elm Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elm-discuss/cN0GFZpw_b0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elm-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rex van der Spuy]

I'm assuming this should actually never happen.

Yes, "have you tried deleting elm-stuff?" is a bit of oral tradition folklore that can magically cure all manner of ailments.   

It's Elm's take on "Have you tried turning it off and on again?"

It burned me as a beginner too, and has been a problem since I started using Elm with 0.15

Does anyone know if it's possible to prevent this from being necessary? 

Or is there a technical reason why the complier can't forcibly clear the elm-stuff cache?

[Nick H]

The situation should be much improved now in 0.18. I don't see it mentioned in the release notes, but from the beta announcement:

Fix elm-make bug where build artifacts could get corrupted, requiring delete of elm-stuff/build-artifacts/

But it appears that we still need to delete elm-stuff sometimes. So it's probably a workaround for more than one bug.

Anthony, the situation you describe sounds like it must be related to elm-package. If you can reproduce your problem and there isn't already a relevant bug report, I would recommend opening one!

--
You received this message because you are subscribed to the Google Groups "Elm Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscribe@googlegroups.com.

[Anthony Naddeo]

Definitely. Looks like I'm problem free at the moment. Hopefully I  can reproduce.

To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to a topic in the Google Groups "Elm Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elm-discuss/cN0GFZpw_b0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elm-discuss...@googlegroups.com.

[matthieu VIDAL]

I kept the whole directory : https://github.com/elm-lang/elm-package/issues/254

To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss...@googlegroups.com.

[matthieu VIDAL]

This bug is here again

after : elm-package install elm-lang/websocket

really annoying !