Reporting bug with new builder
preetpatel
PROOP

2 years ago

Hi there,

I'm trying the new builder for my project because I'd like to use private db connections during build times for my nextjs project.

However I get the following error during its build step. I don't expect a fix but just reporting here in case it has not been observed before:

thread '' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.38.1/src/runtime/scheduler/multi_thread/worker.rs:455:13:

OS can't spawn worker thread: Resource temporarily unavailable (os error 11)

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

thread '' panicked at core/src/panicking.rs:221:5:

panic in a function that cannot unwind

stack backtrace:

0: 0x7f9afd7f77d9 -

1: 0x7f9afcfe014b -

2: 0x7f9afd7d00d2 -

3: 0x7f9afd7fc378 -

4: 0x7f9afd7fd238 -

5: 0x7f9afd7fcce2 -

6: 0x7f9afd7fcc79 -

7: 0x7f9afd7fcc64 -

8: 0x7f9afcea7354 -

9: 0x7f9afcea73bc -

10: 0x7f9afcea7369 -

11: 0x7f9afd34ab74 - napi_register_module_v1

12: 0xa7bf2b - _Z30napi_module_register_by_symbolN2v85LocalINS_6ObjectEEENS0_INS_5ValueEEENS0_INS_7ContextEEEPFP12napi_value__P10napi_env__S8_Ei

13: 0xa83393 - ZNSt17_Function_handlerIFbPN4node7binding4DLibEEZNS1_6DLOpenERKN2v820FunctionCallbackInfoINS5_5ValueEEEEUlS3_E_E9_M_invokeERKSt9_Any_dataOS3

14: 0xa345ed - _ZN4node11Environment12TryLoadAddonEPKciRKSt8functionIFbPNS_7binding4DLibEEE

15: 0xa8270b - _ZN4node7binding6DLOpenERKN2v820FunctionCallbackInfoINS1_5ValueEEE

16: 0xd2627e - _ZN2v88internal25FunctionCallbackArguments4CallENS0_15CallHandlerInfoE

17: 0xd268a1 - _ZN2v88internal12_GLOBAL__N_119HandleApiCallHelperILb0EEENS0_11MaybeHandleINS0_6ObjectEEEPNS0_7IsolateENS0_6HandleINS0_10HeapObjectEEESA_NS8_INS0_20FunctionTemplateInfoEEENS8_IS4_EENS0_16BuiltinArgumentsE

18: 0xd27197 - _ZN2v88internal21Builtin_HandleApiCallEiPmPNS0_7IsolateE

19: 0x16c25b9 - Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_BuiltinExit

thread caused non-unwinding panic. aborting.

⨯ Static worker exited with code: null and signal: SIGABRT

 ELIFECYCLE  Command failed with exit code 1.

error building image: error building stage: failed to execute command: waiting for process to exit: exit status 1

View Deploy details

> ⓘ Deployment information is only viewable by project members and Railway employees.

Solved

1 Replies

2 years ago

Hello,

Thank you for the report, but it's currently in an unmainted beta state so we can't prioritize fixes for it at the moment.


Status changed to Awaiting User Response Railway over 1 year ago


Railway
BOT

9 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 10 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...