Publish job failed, what to do?

archismanp · November 23, 2025, 3:20am

I encountered this issue and am not sure how to proceed

github.com/flathub/io.github.archisman_panigrahi.QuickBib

Stable publish job failed for io.github.archisman_panigrahi.QuickBib

opened 06:19PM - 22 Nov 25 UTC

The publish job for `io.github.archisman_panigrahi.QuickBib` failed in the stabl…e repository. **Build Information:** - Commit SHA: b46b5b127ba54b66157e41f4a648cabdba681175 - Build ID: 229993 - Build log: https://github.com/flathub-infra/vorarbeiter/actions/runs/19598728472 **Job Details:** - Job ID: 437982 - Job status: https://hub.flathub.org/status/437982 **Error Details:** ``` ... 5: std::rt::lang_start::{{closure}} 6: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/core/src/ops/function.rs:284:13 7: std::panicking::try::do_call at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/panicking.rs:504:40 8: std::panicking::try at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/panicking.rs:468:19 9: std::panic::catch_unwind at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/panic.rs:142:14 10: std::rt::lang_start_internal::{{closure}} at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/rt.rs:148:48 11: std::panicking::try::do_call at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/panicking.rs:504:40 12: std::panicking::try at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/panicking.rs:468:19 13: std::panic::catch_unwind at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/panic.rs:142:14 14: std::rt::lang_start_internal at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/rt.rs:148:20 15: main 16: __libc_start_call_main at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16 17: __libc_start_main_impl at ./csu/../csu/libc-start.c:360:3 18: _start ``` cc @flathub/build-moderation

archismanp · November 23, 2025, 8:32pm

It got fixed after rebuilding

hub · November 29, 2025, 1:00pm

This topic was automatically closed after 4 days. New replies are no longer allowed.