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
Update libsass to 3.6.4 #199
Conversation
This is a workaround for gitlab-ce. It should be fixed after rubygem-sassc updating libsass from 3.6.3 to 3.6.4. Reference: https://gitlab.com/gitlab-org/gitlab/-/issues/216740 sass/sassc-ruby#201 sass/sassc-ruby#199 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@535562 35697150-7ecd-e111-bb59-0022644237b5
- Bump PORTREVISION for dependency change This is a workaround for gitlab-ce. It should be fixed after rubygem-sassc updating libsass from 3.6.3 to 3.6.4. Reference: https://gitlab.com/gitlab-org/gitlab/-/issues/216740 sass/sassc-ruby#201 sass/sassc-ruby#199 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@535563 35697150-7ecd-e111-bb59-0022644237b5
This is a workaround for gitlab-ce. It should be fixed after rubygem-sassc updating libsass from 3.6.3 to 3.6.4. Reference: https://gitlab.com/gitlab-org/gitlab/-/issues/216740 sass/sassc-ruby#201 sass/sassc-ruby#199
- Bump PORTREVISION for dependency change This is a workaround for gitlab-ce. It should be fixed after rubygem-sassc updating libsass from 3.6.3 to 3.6.4. Reference: https://gitlab.com/gitlab-org/gitlab/-/issues/216740 sass/sassc-ruby#201 sass/sassc-ruby#199
This is a workaround for gitlab-ce. It should be fixed after rubygem-sassc updating libsass from 3.6.3 to 3.6.4. Reference: https://gitlab.com/gitlab-org/gitlab/-/issues/216740 sass/sassc-ruby#201 sass/sassc-ruby#199 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@535562 35697150-7ecd-e111-bb59-0022644237b5
- Bump PORTREVISION for dependency change This is a workaround for gitlab-ce. It should be fixed after rubygem-sassc updating libsass from 3.6.3 to 3.6.4. Reference: https://gitlab.com/gitlab-org/gitlab/-/issues/216740 sass/sassc-ruby#201 sass/sassc-ruby#199 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@535563 35697150-7ecd-e111-bb59-0022644237b5
This is a straightforward change. Any chances of pushing this update? |
Hello, I don't know much about libsass and and/or this gem, but I encountered a problem in one of my projects (Rails) with The problem appears in the rake task
...including a "Backtrace" and "Memory map" (I am not sure if it's relevant to post the full output here). After some desperate experiments, I found that libsass 3.6.4 addressed an issue that caused a "massive memory leak", so I installed this branch from @ahorek and then the rake task worked again. May be worth mentioning is that I spotted the problem when running Also: In the project I use Foundation CSS framework, which could be a trigger for the problem. In conclusion: I am looking forward to seeing a new version of this gem ;-) |
Update ruby-sassc to 2.4.0. **2.4.0** - [Update libsass to 3.6.4](sass/sassc-ruby#199) - [Use FFI::MemoryPointer instead of libc's malloc()](sass/sassc-ruby#205) - [Test against Ruby 2.7.0](sass/sassc-ruby#193)
libsass was updated to v3.6.4 in sassc-ruby v2.4.0 via sass#199.
This is a workaround for gitlab-ce. It should be fixed after rubygem-sassc updating libsass from 3.6.3 to 3.6.4. Reference: https://gitlab.com/gitlab-org/gitlab/-/issues/216740 sass/sassc-ruby#201 sass/sassc-ruby#199
- Bump PORTREVISION for dependency change This is a workaround for gitlab-ce. It should be fixed after rubygem-sassc updating libsass from 3.6.3 to 3.6.4. Reference: https://gitlab.com/gitlab-org/gitlab/-/issues/216740 sass/sassc-ruby#201 sass/sassc-ruby#199
https://github.com/sass/libsass/releases/tag/3.6.4
fixes #198