Skip to content

refactor(engine): use get_runtime instead of creating new Runtime#129

Merged
zTgx merged 1 commit into
mainfrom
dev
May 14, 2026
Merged

refactor(engine): use get_runtime instead of creating new Runtime#129
zTgx merged 1 commit into
mainfrom
dev

Conversation

@zTgx
Copy link
Copy Markdown
Member

@zTgx zTgx commented May 14, 2026

Replace manual Runtime creation with get_runtime from pyo3_async_runtimes to properly integrate with the existing async runtime in Python context. This removes the dependency on tokio::runtime::Runtime and simplifies the async execution setup.

BREAKING CHANGE: The engine now relies on the existing Python async runtime instead of creating its own Tokio runtime.

Summary

Changes

Checklist

  • Code compiles (cargo build)
  • Tests pass (cargo test --lib --all-features)
  • No new clippy warnings (cargo clippy --all-features)
  • Public APIs have documentation comments
  • Python bindings updated (if Rust API changed)

Notes

Replace manual Runtime creation with get_runtime from pyo3_async_runtimes
to properly integrate with the existing async runtime in Python context.
This removes the dependency on tokio::runtime::Runtime and simplifies
the async execution setup.

BREAKING CHANGE: The engine now relies on the existing Python async
runtime instead of creating its own Tokio runtime.
@vercel
Copy link
Copy Markdown

vercel Bot commented May 14, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
vectorless Ready Ready Preview, Comment May 14, 2026 9:24am

@zTgx zTgx merged commit 66c7a02 into main May 14, 2026
8 checks passed
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

Successfully merging this pull request may close these issues.

Bug: Engine.__init__ creates a separate tokio runtime, conflicting with async environments

1 participant