Skip to content

db.connect panics when used in a single threaded environment #2032

New issue
New issue
Open
#2033
Open
db.connect panics when used in a single threaded environment#2032
#2033
Labels
embedded replicasoffline writes
@avinassh

Description

@avinassh
avinassh
opened on Apr 15, 2025

Consider this code (introduced via this PR: #2029)

libsql/libsql/src/database.rs

Lines 685 to 695 in 10f5dd8

let _ = tokio::task::block_in_place(move || {
let rt = tokio::runtime::Builder::new_current_thread()
.enable_all()
.build()
.unwrap();
rt.block_on(async {
// we will ignore if any errors occurred during the bootstrapping the db,
// because the client could be offline when trying to connect.
let _ = db.bootstrap_db().await;
})
});

If libsql library is used in a single threaded environment, then it fails with following error:

can call blocking only when running on the multi-threaded runtime

This is happening due to incorrect use of block_in_place which should be used only in multiple threaded environments.

Metadata

Metadata

Assignees

No one assigned

    Labels

    embedded replicasoffline writes

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions