Skip to content
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

assertion left != right failed: The Python interpreter is not initialized and the auto-initialize feature is not enabled. #34

Open
mostafav7 opened this issue Jan 5, 2025 · 0 comments

Comments

@mostafav7
Copy link

I keep getting this error:

thread 'daily-emitter' panicked at /Users/daily/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.22.6/src/gil.rs:198:21:
assertion left != right failed: The Python interpreter is not initialized and the auto-initialize feature is not enabled.

Consider calling pyo3::prepare_freethreaded_python() before attempting to use Python APIs.
left: 0
right: 0
stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
4: std::sync::once::Once::call_once_force::{{closure}}
5: std::sys::sync::once::queue::Once::call
6: pyo3::gil::GILGuard::acquire
7: daily::call_client::delegate::on_event_native
8: daily_core::call_client::CallClient::_set_event_listener::{{closure}}
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
thread 'daily-emitter' panicked at core/src/panicking.rs:221:5:
panic in a function that cannot unwind
stack backtrace:
0: 0x112792268 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h7adefaad4a31afc0
1: 0x1127af440 - core::fmt::write::h381c0b0ce6ab972a
2: 0x11278f4b4 - std::io::Write::write_fmt::h75af97148630d8d3
3: 0x11279211c - std::sys::backtrace::BacktraceLock::print::h8baf33e22611de71
4: 0x112793044 - std::panicking::default_hook::{{closure}}::h369c7295ef58c5b1
5: 0x112792e88 - std::panicking::default_hook::h50746358288a9d6a
6: 0x1127937f8 - std::panicking::rust_panic_with_hook::h7d795911432661cb
7: 0x112793484 - std::panicking::begin_panic_handler::{{closure}}::h36f15310ecbde379
8: 0x11279272c - std::sys::backtrace::__rust_end_short_backtrace::heed121414170e0c7
9: 0x112793164 - _rust_begin_unwind
10: 0x1127f8b9c - core::panicking::panic_nounwind_fmt::h5d86a478a9d7437c
11: 0x1127f8c14 - core::panicking::panic_nounwind::he171ad52d328e60b
12: 0x1127f8d00 - core::panicking::panic_cannot_unwind::h2dd8cd735765e065
13: 0x11181df40 - daily::call_client::delegate::on_event_native::h090981fc6608f395
14: 0x1119897c4 - daily_core::call_client::CallClient::_set_event_listener::{{closure}}::h78e6573fd85f3be0
15: 0x1119e30f0 - std::sys::backtrace::__rust_begin_short_backtrace::h9b70b34f9443ffab
16: 0x1119ea194 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h20b6f745919e3266
17: 0x112795278 - std::sys::pal::unix::thread::Thread::new::thread_start::h44ebc83f14222f58
18: 0x19192ef94 - __pthread_joiner_wake
thread caused non-unwinding panic. aborting.
zsh: abort python test_daily.py

when running the following basic script as stated in their demos.

from daily import * Daily.init() client = CallClient() #client.join("https://api.daily.co/v1/rooms/<room_is>", meeting_token = )

I tried with different python versions and on macOS and linux and always getting the same error. How can I solve this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant