Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

segmentation fault hero.sass #191

Closed
osixia opened this issue Apr 27, 2016 · 6 comments
Closed

segmentation fault hero.sass #191

osixia opened this issue Apr 27, 2016 · 6 comments

Comments

@osixia
Copy link

osixia commented Apr 27, 2016

Hi thanks for this great tool !

I use Bulma v0.0.24 and I get a segmentation fault from gulp-sass compiler,
the file hero.sass seems to be the probleme.

I'm not familiar with sass so i tried to convert it to scss and it failed. Other files are fine.

The problems seems to come from the each loop but i don't know mutch...
do you have any solution ?

Thanks

@jgthms
Copy link
Owner

jgthms commented Apr 27, 2016

I have no idea what a segmentation problem is.

Can you share the full error message?

@tdnl
Copy link

tdnl commented Apr 28, 2016

Yeah, I am also having a segfault but it doesn't show any error.

After some investigation, I think this has something to do with Node-Sass. All I could find about this problem was this article:

https://medium.com/@xzyfer/why-node-sass-broke-your-code-and-semver-1b3e409c57b9#.wyz74h9bp

The interesting part is the last one:

If your code does not compile with the Sass compiler, it is broken, and will eventually break in LibSass and Node Sass without warning.

Your code looks good to me though...

@3noch
Copy link

3noch commented Apr 28, 2016

@jgthms You know programming has progressed when...people no longer recognize the term "segmentation fault." 😜

@tdnl
Copy link

tdnl commented Apr 28, 2016

Alright, the problem comes from the :not selector inside the sass/layout/hero.sass file, at line 74

.header-item > a:not(.button)

@tdnl
Copy link

tdnl commented Apr 28, 2016

sass/libsass#2032

Updating node-sass to 3.6.0 (and libsass) fixes the problem. Thanks!

@osixia
Copy link
Author

osixia commented Apr 29, 2016

indeed it fixes the problem :)
thanks !

@osixia osixia closed this as completed Apr 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants