build is triggered multiple times when editing library code
See original GitHub issueUnisay: I have a problem with plugin, and I suspect it wasn’t there before. And here it is: if my project not in the state when it could be build without errors (say, stack build runs fine) then plugin says “Haskell support is not available when Stack repl is not running” and then for any change in project files it re-tries to build it and fails. And because it does it for every change (I edited 1 character) it makes it harder to bring project back to the buildable state because it slows down IDE by continuously re-building it and failing. What I expect it to do is not to re-trigger build automatically (on change) but rather let me first fix it and then press “compile” button ☝️ 17. August 2017 17:31
rikvdkleij: So what I want to make clear, fixing library code would not trigger rebuild. Only when you navigate to test, exe or benchmark code. If you are experience also rebuilds in library code, it is a bug and I need some example project to reproduce this issue ☝️ 18. August 2017 11:12
I experienced the same issue in my project. A moment after I edit one of my library files in the src
directory a rebuild is triggered. If I wait a few seconds and edit again another rebuild is triggered even though the previous build might still be running. This can be done multiple times. Once I had 12 processes running at the same time. I don’t have this issue when I edit my exe main file.
Linux Stack 1.5.0 Intellij-Haskell 1.0.0-beta10 Intellij IDEA 2017.2.2
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:13 (7 by maintainers)
Top GitHub Comments
@rikvdkleij When I tried it before, I somehow managed to trigger the start of multiple processes. However, it didn’t happen on the first tries. I’m not sure if they were build processes. I tried to reproduce the issue again to check it, but I didn’t trigger any unexpected processes this time. I would say the main issue is fixed and you can do a regular release/upload. If I run into the problem again, I will reopen the issue again and add more details. Thanks for your efforts 👍
@maiermic Thanks for testing!