-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
"adding mine block to test server" #544
Conversation
Just picked this up and implemented extending the test RPC server blockchain. I made a The server is polling for updates, so it won't reflect blocks which were just added to the test RPC server. I added One option would be to add a function like this:
|
abc0520
to
12a0c78
Compare
What if we expose the `Index::index() method on the server so that it instantly indexes? Just some notes:
|
I converted some tests but am blocked on fixing the error below. I tried to debug for over an hour but didn't make any progress. ---- subcommand::server::tests::height_updates stdout ----
thread 'subcommand::server::tests::height_updates' panicked at 'assertion failed: self.live_write_transaction.lock().unwrap().is_none()', /Users/raphael/.cargo/registry/src/github.com-1ecc6299db9ec823/redb-0.6.1/src/db.rs:387:9
stack backtrace:
0: rust_begin_unwind
at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/panicking.rs:142:14
2: core::panicking::panic
at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/panicking.rs:48:5
3: redb::db::Database::begin_write
at /Users/raphael/.cargo/registry/src/github.com-1ecc6299db9ec823/redb-0.6.1/src/db.rs:387:9
4: ord::index::Index::index_ranges
at ./src/index.rs:152:19
5: ord::subcommand::server::tests::TestServer::get
at ./src/subcommand/server.rs:573:21
6: ord::subcommand::server::tests::height_updates
at ./src/subcommand/server.rs:853:20
7: ord::subcommand::server::tests::height_updates::{{closure}}
at ./src/subcommand/server.rs:850:3
8: core::ops::function::FnOnce::call_once
at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/ops/function.rs:248:5
9: core::ops::function::FnOnce::call_once
at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
failures:
subcommand::server::tests::height_updates
Its really weird because sometimes it passes: test subcommand::server::tests::height_updates ... ok When I run |
e0a9206
to
5c79037
Compare
Are tests executed in parallel? |
No description provided.