I'm uncertain if this is an issue with Brunch or elm-brunch or some configuration detail I've screwed up. Frequently, when I change an Elm file in my project, the compilation will appear to run, but the result will show elm compiler errors that were fixed on the last save. The errors disappear if I quit and rerun the watch command. I'm not sure why this is happening or even how to narrow down the possibilities.
For setup details, I'm running it using brunch-with-elm-and-electron as boilerplate. My brunch version is 2.9.1.
Your configuration is ok. This is both brunch and elm-brunch issue. Brunch plugins are designed to compile each file separately on change. elm-brunch, however, runs elm-make for elm modules instead. That's why brunch cache is not being updated properly, causing redundant error messages.
Unfortunately, there is no quick fix, but we are looking into the problem. Here's the GitHub issue to track a progress. Thanks a lot, this is a good catch!
UPD: Here's the pull request that should fix the issue.
Related
I'm trying to start a dotnet MAUI app following the tutorial of MS in their official docs
I'm just opening the startup MAUI project(the built-in default one) and VS22 just won't have it. I get 40+ errors most of them about reference missing and duplication of classes/functions
glimps from the errors I get
now I have already seen a post here having somewhat of the same problem but the solutions(restarting and downloading workloads from the CLI using - dotnet workload intall) just didn't work for me.
I haven't done any changes to the code whatsoever so I really don't get what is the problem here.
any help would be appreciated.
Edit 1:
The app do seems to be working when I run the android simulator… which makes it even weirder
This is a bug in the tooling at the moment it seems. If you look at the errors, especially the ones in your screenshot you can see that these talk about Android. If you expand the Project column for a little you will see the list of target platforms that it's talking about.
Because everything is in 1 project now, it gives errors about platform-specific stuff because it is only looking at that one target that it's building. In this case, maybe you were building iOS and it gives errors about not being able to find Android types. This makes sense, however, we shouldn't see these errors in this case.
It's a bit hard to explain like this, I hope it makes any sense.
Long story short, it's a bug, it's being worked on. And you should be able to ignore them and it would still run as you've already discovered yourself. It gives a lot of noise however and if there is an actual error, you will have to find that in this list and fix that.
Our system is using compass to compile sass files. Following the same workflow as usual today when I run compass compile there is a long pause followed by "killed" with no errors or warning.
I'm not even sure how to troubleshoot this issue. Has anyone else run into a similar problem? If so, how did you solve it?
Thank you in advance...
update
I have been through the code and I cannot find a pattern to it not compiling. After making a minor change it compiled successfully making another minor change it failed. Each time I believe the problem is resolved, I make a change that's very small in scope and it breaks it again... for example removing and id (#main) from a definition stops the compile... putting it back does not fix the problem... adding a comment fixes the problem... remove it and it stays fixed, until I make another change .... I've matched my braces and gone over every change made in the last 3 days... I cannot find a cause for the error, or why its not behaving consistently
If other commands on the server die with a "Killed" error message, it could be a resource issue. Check your server logs for out of memory errors.
I've run into an issue with a chain of webpack loaders for scss files, where sometimes using single quotes for a string (legal in Sass, as I understant) causes a compile fail. I have an example that can be run, here, based on small changes from the AngularClass angular starter app:
https://github.com/karptonite/angular2-webpack-starter
You can see the relevant Webpack rule here.
This commit shows the only changes from the vanilla starter from AngularClass necessary to reproduce the bug. Instructions to reproduce the compile failure are in the README of the repo.
I'd like to report this as a bug, but I'm having trouble determining which loader to blame. possible culprits include sass-loader, resolve-url-loader, css-loader, and the ExtractTextPlugin.
I know for a fact that the error does not occur when I remove the resolve-url-loader, but it also doesn't seem to occur when I don't use the ExtractTextPlugin.
I spent hours tracking down why the build wasn't working before discovering it was the single/double quote issue; I'd like to save other people that time by reporting it to the correct repo, if I can figure out what package is at fault, but I don't know enough about how these loaders work to track it down. Can someone who understands Webpack and/or Sass take a look at this, and tell me if I've found a legitimate bug, and, if so, which loader should be fixing it?
Xcode 4.5 (but also earlier I think) reports build errors, but I just created a successful build. And it also depends on which file I select in the project browser. Some files give errors, others don't.
This leads me to believe that there is a bug in the auto evaluation of my code. It seems to loose the #imports or deeper links to other headers...
I have been without the problem for a while, but today it returned. Very strange and annoying.
Is there an autocompletion cache to delete or something.
(Deleting derived data didn't help, or cleaning the build.)
Has anyone found a way to fix this?
edit: still happens in Xcode 4.6
Might help to use #class more in headers, but unverified.
Sometimes I update my Coffee code in Rails 3.1 and it doesn't detect any of the changes, ie. I refresh my browser/cache and it still invokes the old script. Anyone know what causes this?
EDIT: I even litter my entire scripts with "debugger" and none of them ever gets called. Any idea why it simply won't refresh the Coffeescripts?
EDIT2: I realize that it doesn't even detect javascript changes sometimes. Am I missing something? Note I am not bouncing my server when I change JS files... It used to work...
For the development environment you could try to rake assets:clean. Rails sometimes reads the precompiled assets in development environment, so this will clean them and the fresh ones will be loaded.
For the production environment try to rake assets:precompile, so that the changes are compiled and stored in the assets files.
For the curious, it suddenly started functioning correctly again by itself. I have reason to believe it was actually the Daylight Savings Time that caused this bug. Not sure if this could be the case but it suspiciously started working again naturally after a fixed amount of time (about 1 hour).
Try rake assets:precompile, if you haven't already.