App makes noise when I save SCSS, but doesn't actually build CSS

[theletterandrew]

I've noticed that when I save, Scout will make a noise as in "we've saved and updated", but the CSS doesn't actually get built. However, if I click stop on the project, then click the play button again, it will build the CSS.

Has anyone else encountered this problem?

I ensured that I am using the most up to date version of Scout. Also, I do not experience this problem on my laptop, which presumably has the same set up.

[TheJaredWilcurt]

@theletterandrew

Yeah it's an issue in the latest version (2.12.12), the last version doesn't have it (2.6.8). However, as you mentioned, one machine has the issue and the other doesn't. I've not yet tracked down what the cause of the bug is.

What OS are each of your computers. Are they 32-bit or 64-bit.

[theletterandrew]

Both are Windows 7 and 64 bit.

On Thu, May 4, 2017 at 4:09 PM The Jared Wilcurt ***@***.***> wrote: @theletterandrew <https://github.com/theletterandrew> Yeah it's an issue in the latest version (2.12.12), the last version doesn't have it (2.6.8). However, as you mentioned, one machine has the issue and the other doesn't. I've not yet tracked down what the cause of the bug is. What OS are each of your computers. Are they 32-bit or 64-bit. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#333 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXz47ck4ai-dHxE66C01pN_Nh69H8lpsks5r2j6NgaJpZM4NQ1pO> .

-- Andrew Phillips andrew.austen.phillips@gmail.com | 832-296-3223 Undergraduate Student University of Houston College of Natural Sciences and Mathematics

[pzaul]

On my Win7 PC, when I edit and save an .scss file with Sublime Text 3 (x64 build 3126), Scout-App doesn't compile it to css. When I edit and save the same file in Notepad++, it compiles perfectly. I also uninstalled Sublime and deleted the ST3 folders under ...AppData\Local and ...AppData\Roaming, then reinstalled ST3 but no ST3 plugins, and it still does not compile the scss file after editing and saving. So is this a problem with how ST3 saves, not a problem with Scout?

[TheJaredWilcurt]

@pzaul

This is likely related to atomic saves.

More info here:

• Error (0x01) - Line: xx Col xx - File to import not found or unreadable #274 (comment)

[JamieBohannaWebDev]

On my iMac running Sierra 10.12.5 (16F73), when using Brackets text editor, I get the exact same issue as @theletterandrew. Compiles perfectly if I stop and start, but not automatically.

Haven't tried any other editors.

SCSS into CSS.

[Jyotsna-Singh]

I am facing the same issue. App just makes the error sound and doesnt compile the scss. I was using Sublime 2, Windows-7, 64-bit. Banged my head for an hour, clearing temp files. Ended up on this thread. Used both v2.12.12 and v2.6.8.
However, when I moved to Brackets it started working.

[dshastry]

Able to replicate @JamieBohannaWebDev's issue as well on my end. Using Brackets on Mac OS Sierra as well. Checked to see that Brackets is not compiling SASS for me (disabled in config). I'm also able to fix by closing and restarting Scout

[mashedkeyboard]

I'm also having this issue on Win10 64-bit using Visual Studio Code, with no SCSS compilation turned on natively in the editor.

[TheJaredWilcurt]

@theletterandrew @pzaul @JamieBohannaWebDev @Jyotsna-Singh @dshastry @mashedkeyboard @benjamenhogben

The latest version of Scout-App's master branch has a new setting for atomic saves. I'm unable to reproduce the bug you have reported, so I can't verify if this new setting actually fixes the bug or not.

Could one of you:

1. Download it
2. Then run npm install (You need Node installed for this)
3. Run npm start and test it.
4. Report back if it worked.

[dshastry]

I'll try and tackle this week @TheJaredWilcurt and report back

[benjamenjohnsondev]

@TheJaredWilcurt can confirm css grid specification is working + compiling just fine.

Can't contribute to other issues as I never experienced them (but it's not happened with this build either), great job!

[TheJaredWilcurt]

@theletterandrew @pzaul @JamieBohannaWebDev @Jyotsna-Singh @dshastry @mashedkeyboard @benjamenhogben

It's been a few months and I've not heard anything from anyone.

I'm wanting to do a new release in December. And since this bug has more reported cases than any other, I want to ensure that it gets resolved in the new version. However I cannot reproduce it. So I'm asking one of you to try it out.

1. Download the latest code
2. Then run npm install (You need Node installed for this)
3. Run npm start and test it.
4. Report back if it worked.

[theletterandrew]

I’ll be your huckleberry.

On Wed, Nov 22, 2017 at 10:36 AM The Jared Wilcurt ***@***.***> wrote: @theletterandrew <https://github.com/theletterandrew> @pzaul <https://github.com/pzaul> @JamieBohannaWebDev <https://github.com/jamiebohannawebdev> @Jyotsna-Singh <https://github.com/jyotsna-singh> @dshastry <https://github.com/dshastry> @mashedkeyboard <https://github.com/mashedkeyboard> @benjamenhogben <https://github.com/benjamenhogben> It's been a few months and I've not heard anything from anyone. I'm wanting to do a new release in December. And since this bug has more reported cases than any other, I want to ensure that it gets resolved in the new version. However I cannot reproduce it. So I'm asking one of you to try it out. 1. Download the latest code <https://github.com/scout-app/scout-app/archive/master.zip> 1. Then run npm install (You need Node <https://nodejs.org/en/download> installed for this) 2. Run npm start and test it. 3. Report back if it worked. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#333 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXz47SGtvbewsxiVzhkd49_HguyYbYXGks5s5E1-gaJpZM4NQ1pO> .

-- Andrew Phillips andrew.austen.phillips@gmail.com | 832-296-3223 Undergraduate Student University of Houston College of Natural Sciences and Mathematics

[SweetMuffins]

I'm having this issue on the version 2.12.12 for Windows and I'm using the VS Code text editor. I already have node and ran npm before the installation of the Scout App. Should I redo the node installation to fix this?

[Shwetha9]

It was a write/ permissions issue. The minute I moved the project out of the htdocs folder, scout started watching and compiling as usual.

[ahmadirshad888]

same issue

[TheJaredWilcurt]

@theletterandrew @pzaul @JamieBohannaWebDev @Jyotsna-Singh @dshastry @mashedkeyboard @benjamenhogben @SweetMuffins @Shwetha9 @ahmadirshad888

Closing issue. Fix/Feature has been released in Scout-App v2.18.16.

There is now a control in the preferences to adjust atomic saving delays, which seems to be the cause. That's as much as we can do from Scout-App's side. If adjusting this setting does not fix the issue then you will need to change settings in the application that is making the changes to the file (atomic saves setting).