From: merch-redmine@jeremyevans.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:103191] [Ruby master Bug#17770] Assets precompilation aborts with Segmentation fault
Date: Fri, 02 Apr 2021 20:53:55 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-91266.20210402205354.51369@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17770.20210401084925.51369@ruby-lang.org
Issue #17770 has been updated by jeremyevans0 (Jeremy Evans).
Status changed from Open to Third Party's Issue
This does appear to be a sassc bug: https://github.com/sass/sassc-ruby/issues/207
----------------------------------------
Bug #17770: Assets precompilation aborts with Segmentation fault
https://bugs.ruby-lang.org/issues/17770#change-91266
* Author: dvodvodvo (Jerome Camus)
* Status: Third Party's Issue
* Priority: Normal
* ruby -v: ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-linux]
What changed? I updated a gem version, administrate 0.14.0 to 0.15.0
when deploying to server the following error is constantly appearing.
Note: when reverting to version 0.14.0 the deployment process completes (I will also be reporting this to the administrate gem)
The same occurs if I log into the server, find the current release and run `bundle exec rake assets:precompile`
Log (capistrano) attached
---Files--------------------------------
capistrano_log_administrate.txt (318 KB)
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2021-04-02 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 8:49 [ruby-core:103147] [Ruby master Bug#17770] Assets precompilation aborts with Segmentation fault office
2021-04-01 14:13 ` [ruby-core:103151] " peter
2021-04-02 20:53 ` merch-redmine [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-91266.20210402205354.51369@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).