Open philgruneich opened 10 years ago
I'm also getting this same issue.
Not sure if it is anything to do with this but I am using global variables via the import feature (one main file pulling in all SCSS files /w variables declared at top, used throughout) sometimes it will flag that x.scss cannot find $v.
Issue is fixed if I cancel the current watch command and re-run it
Any news with this issue? I'm getting the same too.
I'm also getting this error on version 1.0.1. Any ideas on it?
Still an issue on 1.0.3...
Also reporting the issue on 1.0.3.
Same trouble, v1.0.3 too
same here Compass 1.0.3 (Polaris)
:+1:
A fix is terminating your compass watch and starting it back again.
@tomasdev Not much of a fix since you have to be constantly terminating and starting compass over and over again.
I agree wtih @joedaniels
I also agree with @joedaniels.
I also agree with @joedaniels.
same here. 1.0.3
Getting the same problem.
I've also been having this issue for months. I stop Compass and run the watch command again to get everything working but... yeah.
ETA: Thought it worth mentioning that the only Compass frameworks I have installed are: compass sassy-maps breakpoint
Same here :/
Getting this error as well.
Using: Bourbon Bourbon-Neat Custom Silent Classes and mixins/vars
Any word on a fix?
Also having this issue.
Same...
Ditto...
Same issue for me.
Same issue here. I have multiple projects running compass watch, some local, some on network drives and this seems to only occur when watching files on a network drive. Fixed by resaving the sass file but frustrating none the less. Another thing that I have done is changed where the cache is stored by modifying the config.rb for my network projects. cache_path = 'C:/temp/PROJECTNAME/.sass-cache'
No joy? Fixes?
Same here.
I've been having this problem for a while now and thought it was me. :-/
I'm using the following gems:
Same error for me
Same error ....
Same here too...
Same error here …
Same error too...
Just keeping this alive. This issue started out of the blue a couple of weeks ago. Only significant software change I can think of is I upgraded to Adobe Suite CC 2015.
Ruby v. 2.2.2p95 Sass v. 4.3.13 Compass v. 1.0.3
same here
lol but ... same here :)
solved by not using compass.
It seems to be Compass watch that's causing the problem here. I started using Gulp to watch my files and trigger a compass compile and that works fine.
same here
compass (1.0.3) sass (3.4.13)
Getting this too from time to time after saving a file.
I aslo have this problem. I think that this is a Compass bug.
i have the same problem. My "solution" is to make compass restart again with "ctrl"+"c" and "o". When it restarts, it works again.
Also have this bug, you may do : while :; do compass compile; sleep 2; done
Happening randomly here too "compass","1.0.1" "sass","3.4.18"
Only fix is to kill and restart the watcher process.
Using compass and compass-import-once is not recommended to use them at the same time, Only use Compass.
Same here..
if you have imports, you can save another file(add and remove a space) and it works, it's not a fix but still better than restart the watcher
@fabiofidanza Are you still seeing the problem, if so, please post your gruntfile so I can see what's wrong as well as a list of node_modules you are using.
@jgacuca567 I'm using a plain old compass watch, launched via nohup:
nohup bundle exec compass watch >compass.log &
here are the Gems that are used in one of the projects where I experience the problem:
chunky_png (1.3.4)
compass (1.0.1)
chunky_png (~> 1.2)
compass-core (~> 1.0.1)
compass-import-once (~> 1.0.5)
rb-fsevent (>= 0.9.3)
rb-inotify (>= 0.9)
sass (>= 3.3.13, < 3.5)
compass-core (1.0.3)
multi_json (~> 1.0)
sass (>= 3.3.0, < 3.5)
compass-import-once (1.0.5)
sass (>= 3.2, < 3.5)
ffi (1.9.10)
multi_json (1.11.2)
rb-fsevent (0.9.5)
rb-inotify (0.9.5)
ffi (>= 0.5.0)
sass (3.4.15)
Thanks
@fabiofidanza I guess, for me I have been using NPM Modules, see My gist file, see how I have setup file. As of now when I run sudo grunt, no errors from compass are found.
My guess would be that there's something wrong on line 80 in /var/lib/gems/2.1.0/gems/sass-3.4.19/lib/sass/plugin/staleness_checker.rb On that line the importer should be set to the given option filesystem_importer if it's nil . The importer however seems to end up as nil at /var/lib/gems/2.1.0/gems/sass-3.4.19/vendor/listen/lib/listen/adapter.rb :299 .
The other possibility is that somehow importer gets reset to nil. Which seems to be able to be because of the thread as mentioned in https://github.com/guard/listen/issues/219 . On a short test this Thread-timing-issues seems to fix the issue for me. I changed the DEFAULT_LATENCY on line 22 from 0.25 to 2 in the file : /var/lib/gems/2.1.0/gems/sass-3.4.19/vendor/listen/lib/listen/adapter.rb .
Same issue since today. Not viewed before.
autoprefixer-rails (6.0.3) bigdecimal (1.2.6) bootstrap-sass (3.3.5.1) chunky_png (1.3.4) compass (1.0.3) compass-core (1.0.3) compass-import-once (1.0.5) execjs (2.6.0) ffi (1.9.10 x86-minggw32) io-console (0.4.3) json (1.8.1) minitest (5.4.3) multi_json (1.11.2) power_assert (0.2.2) psych (2.0.8) rake (10.4.2) rb-fsevent (0.9.6) rb-inotify (0.9.5) rdoc (4.2.0) sass (3.4.19) test-unit (3.0.8)
same... compass (1.0.3), compass-core (1.0.3), compass-import-once (1.0.5), susy (2.2.6)
Sass 3.4.5 (Selective Steve) Compass 1.1.0.alpha.3 (Polaris) ruby 2.0.0p451 (2014-02-24 revision 45167) [universal.x86_64-darwin13]
Could be similar to https://github.com/Compass/compass/issues/1641