Hermanverschooten
My typst package was recently updated, and I wanted to release a new version. I am using rustler precompiled to precompile the rust bindings to typst.
although the change to the code was minimal, the compilation for 2 targets fails with a segfault.
Compiling typst_nif v0.1.1 (/home/runner/work/typst/typst/native/typst_nif)
error: rustc interrupted by SIGSEGV, printing backtrace
...
help: you can increase rustc's stack size by setting RUST_MIN_STACK=16777216
error: could not compile `typst_nif` (lib)
Caused by:
process didn't exit successfully: `rustc --crate-name typst_nif --edition=2021 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type cdylib --emit=dep-info,link -C opt-level=3 -C lto --cfg 'feature="default"' --cfg 'feature="nif_version_2_15"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "nif_version_2_15", "nif_version_2_16", "nif_version_2_17"))' -C metadata=684f38727e91bcf8 --out-dir /target/aarch64-unknown-linux-gnu/release/deps --target aarch64-unknown-linux-gnu -C linker=aarch64-linux-gnu-gcc -C strip=debuginfo -L dependency=/target/aarch64-unknown-linux-gnu/release/deps -L dependency=/target/release/deps --extern comemo=/target/aarch64-unknown-linux-gnu/release/deps/libcomemo-c278774ab144f6c8.rlib --extern rustler=/target/aarch64-unknown-linux-gnu/release/deps/librustler-c7f63b2eafc93dbf.rlib --extern tar=/target/aarch64-unknown-linux-gnu/release/deps/libtar-5166b6795e27638f.rlib --extern time=/target/aarch64-unknown-linux-
Done.
I followed the directions and added a step to the workflow to set the RUST_MIN_STACK env var,
- name: Set Rust stack size
shell: bash
run: |
echo "RUST_MIN_STACK=16777216" >> $GITHUB_ENV
But alas this doesn’t make a difference.
Has anyone encountered something similar and know how to resolve this?
Thanks,
Herman
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted”
Version...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Hermanverschooten
Reading throught the docs for rustler-precompiled, I added:
to my
Cargo.toml, but still the same error.dimitarvp
I would try the following:
Hermanverschooten
Hey @dimitarvp, what do you mean by your first point?
dimitarvp
I meant those:
I would try with the newest first.
Hermanverschooten
Oh I see, this is handled by (I think) by the
nif: ["2.15"]in the workflow. I updated it to include 2.17, but the same 2 fail with the same error.Hermanverschooten
I just tried changing from Ubuntu 22.04 → 24.04 but that doesn’t help either.
dimitarvp
Hm, which Rust version?
Hermanverschooten
rustc 1.87.0
Hmm, when I look at the previous release’s actions, they were using rustc 1.86.0.
But I don’t know if I can specify that anywhere.
Hermanverschooten
I changed the workflow to use:
instead of
Now it uses rust 1.86 and that works!
Thanks for the assist!
dimitarvp
Whoa, that would be pretty nasty if they broke it in Rust 1.87.
Glad you fixed it!