You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[examples/simple/src/main.rs:84:13] send_email.to = "hi@example.com"
[examples/simple/src/main.rs:84:13] send_email.body = "hello from mq!"
2024-05-07T03:09:24.833321Z ERROR surrealdb::api::engine::local::native: Error sending shutdown signal to task: sending on a closed channel
2024-05-07T03:09:24.833477Z ERROR surrealdb::api::engine::tasks: Node agent task failed: task 18 was cancelled
thread 'tokio-runtime-worker' panicked at /Users/prabirshrestha/.cargo/registry/src/index.crates.io-6f17d22bba15001f/surrealdb-1.4.2/src/api/engine/local/native.rs:224:31:
called `Result::unwrap()` on an `Err` value: Db(Unreachable("This feature won't go live with sql1, so delete this branching"))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Steps to reproduce
git clone https://github.com/prabirshrestha/mq.git
git checkout 2cff8f8
cd examples/simple
cargo run
Expected behaviour
Work without any error.
Checkout to 451faf14c9b981b173aad960a87345a478ff23bb from mq with older version of surrealdb.
SurrealDB version
1.4.2
Contact Details
No response
Is there an existing issue for this?
I have searched the existing issues
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Hi @prabirshrestha , this is happening because we had 2 query languages in 1.4.2, but we have 1 query language in 1.5.0-beta . You should be able to upgrade and this will resolve the issue.
Also @prabirshrestha , I would recommend pinning specific versions now that we have a new release model. Having specific checksums can be flakey as they don't go through the same amount of testing that we do for releases. So bugs like this can creep in. If you absolutely need that version (as opposed to 1.5.0-beta1 which was made on Friday) then you should enable the sql2 feature flag on the dependency
Describe the bug
Throws error when run the example.
Steps to reproduce
Expected behaviour
Work without any error.
Checkout to 451faf14c9b981b173aad960a87345a478ff23bb from mq with older version of surrealdb.
SurrealDB version
1.4.2
Contact Details
No response
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: