Several crashes when running cargo test

zebra latest main
Got several crashes after I ran cargo test -- --test-threads=2
Crash logs.zip

Thanks for this bug report!
We need a bit more information to work out what Zebra is doing here.

zebra latest main

The commit at the tip of the main branch can change multiple times each day.
What git release tag or a git commit hash did you use?

Got several crashes after I ran cargo test -- --test-threads=2

Which directory were you in when you ran that command?

Crash logs.zip

These logs don't contain the terminal output of the tests. We need that output to identify which tests failed. (Our CI is passing on macOS, so we'll need the logs to work out what's different about your machine.)
Can you please copy and paste the output from the failing tests?
Or you could open a new Terminal window, run the command, save the output, and upload it as a file.
There's a few other details that can help us diagnose issues.
So we've put together a "bug report" template:
https://github.com/ZcashFoundation/zebra/issues/new/choose
No need to use it this time, but it might be handy for future bug reports!

Triage notes
For Zebra developers:

I've marked this as a high priority issue, because it's a crash (not a panic)
Once we know the working directory, we should run cargo test -- --test-threads=2 on Linux and macOS and see if we can reproduce the issue
We should try with nightly and stable Rust

Partial Backtrace
The top of the call stack for one of the crashes appears to be a NULL pointer dereference in the state service:
[{"imageOffset":4595,"symbol":"_platform_memmove$VARIANT$Haswell","symbolLocation":83,"imageIndex":0},{"imageOffset":10103652,"symbol":"core::iter::sources::once::once::h4d7bef0c726e24f5","symbolLocation":36,"imageIndex":1},{"imageOffset":9975862,"symbol":"rocksdb::db::DBWithThreadMode$LT$T$GT$::open_cf_descriptors_internal::h948422d4514ce3c8","symbolLocation":182,"imageIndex":1},{"imageOffset":9975662,"symbol":"rocksdb::db::DBWithThreadMode$LT$T$GT$::open_cf_descriptors::h8528a3e22a54ffcf","symbolLocation":62,"imageIndex":1},{"imageOffset":10894611,"symbol":"zebra_state::service::finalized_state::FinalizedState::new::h27302f1ea06606f1","symbolLocation":1411,"imageIndex":1},{"imageOffset":10791739,"symbol":"zebra_state::service::StateService::new::h995a104965cdc3d3","symbolLocation":75,"imageIndex":1},

We need a bit more information to work out what Zebra is doing here.

We also need the version of Rust that you're using to compile Zebra.

Commit e9d2ba835ec40de89370a188f7ebc9801769b8e0
rustc 1.58.0-nightly (ff0e14829 2021-10-31)
cargo 1.58.0-nightly (6c1bc24b8 2021-10-24)
Directory that I run the tests from is ~/zebra on branch main AKA the root of the repo.
Here is the terminal log.

     Running unittests (target/debug/deps/tower_batch-5e320dadb4ff2944)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running tests/ed25519.rs (target/debug/deps/ed25519-b927231a4ae51a78)

running 3 tests
test batch_flushes_on_max_items ... ok
test fallback_verification ... ok
test batch_flushes_on_max_latency ... ok

test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.53s

     Running tests/worker.rs (target/debug/deps/worker-a1d30551d9418d87)

running 2 tests
test wakes_pending_waiters_on_failure ... ok
test wakes_pending_waiters_on_close ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s

     Running unittests (target/debug/deps/tower_fallback-e83fc1897226a79b)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running tests/fallback.rs (target/debug/deps/fallback-b592a559159d8f1c)

running 1 test
test fallback ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s

     Running unittests (target/debug/deps/zebra_chain-df561c4d629df493)

running 226 tests
test amount::tests::prop::amount_deserialization ... ok
test amount::tests::vectors::add_with_diff_constraints ... ok
test amount::tests::prop::amount_serialization ... ok
test amount::tests::vectors::deserialize_checks_bounds ... ok
test amount::tests::vectors::ordering_constraints ... ok
test amount::tests::vectors::hash ... ok
test amount::tests::vectors::test_add_assign ... ok
test amount::tests::vectors::test_add_bare ... ok
test amount::tests::vectors::test_add_opt_both ... ok
test amount::tests::vectors::test_add_opt_lhs ... ok
test amount::tests::vectors::test_add_opt_rhs ... ok
test amount::tests::vectors::test_sub_assign ... ok
test amount::tests::vectors::test_sub_bare ... ok
test amount::tests::vectors::test_sub_opt_lhs ... ok
test amount::tests::vectors::test_sub_opt_rhs ... ok
test block::height::operator_tests ... ok
test amount::tests::vectors::test_sum ... ok
test block::merkle::tests::auth_data_padding ... ok
test block::merkle::tests::auth_data_pre_v5 ... ok
test block::merkle::tests::auth_digest ... ok
test block::merkle::tests::block_test_vectors ... ok
test block::tests::preallocate::block_hash_size_is_correct ... ok
test block::tests::preallocate::counted_header_max_allocation ... ok
test block::tests::preallocate::counted_header_min_length ... ok
test block::tests::preallocate::block_hash_max_allocation ... ok
test block::tests::prop::block_genesis_strategy ... ok
test block::tests::prop::block_hash_display_fromstr_roundtrip ... ok
test block::tests::prop::block_hash_roundtrip ... ok
test block::tests::prop::block_roundtrip ... ok
test block::tests::prop::blockheader_roundtrip ... ok
test block::tests::prop::blocks_have_coinbase ... ok
test block::tests::prop::commitment_roundtrip ... ok
test block::tests::prop::genesis_partial_chain_strategy ... ok
test block::tests::vectors::block_commitment_mainnet ... ok
test block::tests::vectors::block_commitment_testnet ... ok
test block::tests::vectors::block_limits_multi_tx ... ok
test block::tests::vectors::block_limits_single_tx ... ok
test block::tests::vectors::block_test_vectors_height_mainnet ... ok
test block::tests::vectors::block_test_vectors_height_testnet ... ok
test block::tests::vectors::block_test_vectors_unique ... ok
test block::tests::vectors::blockheaderhash_debug ... ok
test block::tests::vectors::blockheaderhash_from_blockheader ... ok
test block::tests::vectors::coinbase_parsing_rejects_above_0x80 ... ok
test block::tests::vectors::deserialize_blockheader ... ok
test block::tests::vectors::round_trip_blocks ... ok
test block::tests::vectors::time_check_fixed ... ok
test block::tests::vectors::time_check_now ... ok
test history_tree::tests::vectors::push_and_prune ... ok
test history_tree::tests::vectors::upgrade ... ok
test orchard::address::tests::derive_keys_and_addresses ... ok
test orchard::commitment::tests::add ... ok
test orchard::commitment::tests::add_assign ... ok
test orchard::commitment::tests::sub ... ok
test orchard::commitment::tests::sub_assign ... ok
test orchard::commitment::tests::sum ... ok
test block::tests::prop::arbitrary_height_partial_chain_strategy ... ok
test orchard::keys::tests::generate_keys_from_test_vectors ... ok
test orchard::note::ciphertexts::encrypted_ciphertext_roundtrip ... ok
test orchard::note::ciphertexts::out_ciphertext_roundtrip ... ok
test orchard::sinsemilla::tests::hackworks_group_hash_test_vectors ... ok
test orchard::sinsemilla::tests::hackworks_test_vectors ... ok
test orchard::sinsemilla::tests::single_test_vector ... ok
test orchard::tests::preallocate::authorized_action_max_allocation_is_big_enough ... ok
test orchard::tests::preallocate::authorized_action_size_is_small_enough ... ok
test orchard::tests::prop::flag_roundtrip_bytes ... ok
test orchard::keys::tests::generate_keys ... ok
test orchard::tests::tree::empty_roots ... ok
test parameters::tests::activation_bijective ... ok
test parameters::tests::activation_consistent_mainnet ... ok
test parameters::tests::activation_consistent_testnet ... ok
test parameters::tests::activation_extremes_mainnet ... ok
test parameters::tests::activation_extremes_testnet ... ok
test parameters::tests::branch_id_bijective ... ok
test parameters::tests::branch_id_consistent_mainnet ... ok
test parameters::tests::branch_id_consistent_testnet ... ok
test parameters::tests::branch_id_extremes_mainnet ... ok
test parameters::tests::branch_id_extremes_testnet ... ok
test primitives::redpallas::tests::basepoints::orchard_binding_basepoint ... ok
test primitives::redpallas::tests::basepoints::orchard_spendauth_basepoint ... ok
test primitives::redpallas::tests::batch::alternating_batch_verify ... ok
test primitives::redpallas::tests::batch::bad_binding_in_batch_verify ... ok
test primitives::redpallas::tests::batch::bad_spendauth_in_batch_verify ... ok
test primitives::redpallas::tests::batch::binding_batch_verify ... ok
test primitives::redpallas::tests::batch::spendauth_batch_verify ... ok
test primitives::redpallas::tests::prop::randomization_commutes_with_pubkey_homomorphism ... ok
test primitives::redpallas::tests::prop::tweak_signature ... ok
test primitives::zcash_history::tests::vectors::tree ... ok
test sapling::address::sapling_address_roundtrip ... ok
test sapling::address::tests::derive_keys_and_addresses ... ok
test sapling::address::tests::from_str_display ... ok
test sapling::commitment::tests::add ... ok
test sapling::commitment::tests::add_assign ... ok
test sapling::commitment::tests::pedersen_hash_to_point_test_vectors ... ok
test sapling::commitment::tests::sub ... ok
test sapling::commitment::tests::sub_assign ... ok
test sapling::commitment::tests::sum ... ok
test sapling::keys::tests::string_roundtrips ... ok
test sapling::keys::tests::tests::derive_for_each_test_vector ... ok
test sapling::note::ciphertexts::encrypted_ciphertext_roundtrip ... ok
test sapling::note::ciphertexts::out_ciphertext_roundtrip ... ok
test sapling::tests::preallocate::anchor_per_spend_max_allocation_is_big_enough ... ok
test sapling::tests::preallocate::anchor_per_spend_size_is_small_enough ... ok
test orchard::tests::tree::incremental_roots ... ok
test sapling::tests::preallocate::output_size_is_small_enough ... ok
test sapling::tests::preallocate::output_max_allocation_is_big_enough ... ok
test sapling::tests::preallocate::shared_anchor_spend_size_is_small_enough ... ok
test sapling::tests::prop::output_roundtrip ... ok
test sapling::tests::preallocate::shared_spend_max_allocation_is_big_enough ... ok
test sapling::tests::prop::sapling_shielded_data_v4_outputs_only ... ok
test sapling::tests::prop::sapling_shielded_data_v4_roundtrip ... ok
test sapling::tests::prop::sapling_shielded_data_v5_outputs_only ... ok
test sapling::tests::prop::spend_v4_roundtrip ... ok
test sapling::tests::prop::sapling_shielded_data_v5_roundtrip ... ok
test sapling::tests::tree::empty_roots ... ok
test sapling::tests::prop::spend_v5_roundtrip ... ok
test sapling::tests::tree::incremental_roots_with_blocks ... ok
test serialization::sha256d::tests::sha256d_checksum ... ok
test serialization::sha256d::tests::sha256d_checksum_debug ... ok
test serialization::tests::preallocate::u8_deser_accepts_max_valid_input ... ok
test serialization::tests::preallocate::u8_deser_throws_when_input_too_large ... ok
test serialization::tests::preallocate::u8_max_allocation_is_correct ... ok
test serialization::tests::preallocate::u8_ser_deser_roundtrip ... ok
test serialization::tests::preallocate::u8_size_is_correct ... ok
test serialization::tests::prop::compactsize_read_then_write_round_trip ... ok
test serialization::tests::prop::compactsize_write_then_read_round_trip ... ok
test sapling::tests::tree::incremental_roots ... ok
test sprout::address::tests::from_string_debug ... ok
test sprout::address::zcash_base58check_roundtrip ... ok
test sprout::address::zcash_de_serialize_roundtrip ... ok
test sprout::keys::incoming_viewing_key_roundtrip ... ok
test serialization::tests::prop::transaction_serialized_size ... ok
test sprout::keys::spending_key_roundtrip ... ok
test sprout::keys::incoming_viewing_key_string_roundtrip ... ok
test sprout::keys::tests::derive_keys ... ok
test sprout::keys::spending_key_string_roundtrip ... ok
test sprout::note::ciphertexts::encrypted_ciphertext_roundtrip ... ok
test sprout::tests::preallocate::joinsplit_btcv14_size_is_correct ... ok
test sprout::tests::preallocate::joinsplit_btcv14_max_allocation_is_correct ... ok
test sprout::tests::preallocate::joinsplit_groth16_size_is_correct ... ok
test sprout::tree::tests::empty_roots ... ok
test sprout::tree::tests::incremental_roots ... ok
test transaction::memo::memo_fmt ... ok
test transaction::memo::memo_from_string ... ok
test sprout::tests::preallocate::joinsplit_groth16_max_allocation_is_correct ... ok
test transaction::tests::preallocate::input_max_allocation_is_big_enough ... ok
test transaction::tests::preallocate::transparent_input_size_is_small_enough ... ok
test transaction::tests::preallocate::transparent_output_size_is_small_enough ... ok
test transaction::tests::preallocate::output_max_allocation_is_big_enough ... ok
test transaction::tests::preallocate::tx_size_is_small_enough ... ok
test transaction::tests::prop::arbitrary_transaction_version_strategy ... ok
test transaction::tests::prop::locktime_roundtrip ... ok
test transaction::tests::prop::transaction_auth_digest_string_parse_roundtrip ... ok
test transaction::tests::prop::transaction_auth_digest_struct_display_roundtrip ... ok
test transaction::tests::prop::transaction_hash_string_parse_roundtrip ... ok
test transaction::tests::prop::transaction_hash_struct_display_roundtrip ... ok
test transaction::tests::prop::transaction_roundtrip ... ok
test transaction::tests::preallocate::tx_max_allocation_is_big_enough ... ok
test transaction::tests::prop::transaction_wtx_id_string_parse_roundtrip ... ok
test transaction::tests::prop::transaction_wtx_id_struct_display_roundtrip ... ok
test transaction::tests::vectors::auth_digest_struct_from_str_roundtrip ... ok
test transaction::tests::vectors::binding_signatures ... ok
test transaction::tests::vectors::deserialize_large_transaction ... ok
test transaction::tests::vectors::doesnt_deserialize_transaction_with_invalid_value_balance ... ok
test transaction::tests::vectors::empty_v4_round_trip ... ok
test transaction::tests::vectors::empty_v5_librustzcash_round_trip ... ok
test transaction::tests::vectors::empty_v5_round_trip ... ok
test transaction::tests::vectors::fake_v5_librustzcash_round_trip ... ok
test transaction::tests::vectors::fake_v5_round_trip ... ok
test transaction::tests::vectors::invalid_orchard_nullifier ... ok
test transaction::tests::vectors::librustzcash_tx_deserialize_and_round_trip ... ok
test transaction::tests::vectors::librustzcash_tx_hash ... ok
test transaction::tests::vectors::test_vec143_1 ... ok
test transaction::tests::vectors::test_vec143_2 ... ok
test transaction::tests::vectors::test_vec243_1 ... ok
test transaction::tests::vectors::test_vec243_2 ... ok
test transaction::tests::vectors::test_vec243_3 ... ok
test transaction::tests::vectors::transactionhash_struct_from_str_roundtrip ... ok
test transaction::tests::vectors::wtx_id_struct_from_str_roundtrip ... ok
test transaction::tests::vectors::zip143_deserialize_and_round_trip ... ok
test transaction::tests::vectors::zip143_sighash ... ok
test transaction::tests::vectors::zip243_deserialize_and_round_trip ... ok
test transaction::tests::vectors::zip243_sighash ... ok
test transaction::tests::vectors::zip244_auth_digest ... ok
test transaction::tests::vectors::zip244_round_trip ... ok
test transaction::tests::vectors::zip244_sighash ... ok
test transaction::tests::vectors::zip244_txid ... ok
test transparent::address::tests::debug ... ok
test transparent::address::tests::empty_script_mainnet ... ok
test transparent::address::tests::empty_script_testnet ... ok
test transparent::address::tests::from_string ... ok
test transparent::address::tests::pubkey_mainnet ... ok
test transparent::address::tests::pubkey_testnet ... ok
test transparent::address::transparent_address_roundtrip ... ok
test transparent::prop::coinbase_has_height ... ok
test transparent::prop::input_coinbase_vecs_only_have_coinbase_input ... ok
test transparent::script::proptests::script_roundtrip ... ok
test value_balance::tests::prop::value_balance_deserialization ... ok
test value_balance::tests::prop::value_balance_serialization ... ok
test value_balance::tests::prop::value_balance_sub ... ok
test value_balance::tests::prop::value_balance_sum ... ok
test value_balance::tests::prop::value_blance_add ... ok
test work::difficulty::tests::prop::prop_compact_roundtrip ... ok
test work::difficulty::tests::prop::prop_difficulty_conversion ... ok
test work::difficulty::tests::prop::prop_expanded_cmp ... ok
test work::difficulty::tests::prop::prop_expanded_hash_cmp ... ok
test work::difficulty::tests::prop::prop_expanded_roundtrip ... ok
test work::difficulty::tests::prop::prop_hash_cmp ... ok
test work::difficulty::tests::prop::prop_work_conversion ... ok
test work::difficulty::tests::prop::prop_work_sum ... ok
test work::difficulty::tests::vectors::block_difficulty ... ok
test work::difficulty::tests::vectors::compact_bitcoin_test_vectors ... ok
test work::difficulty::tests::vectors::compact_extremes ... ok
test work::difficulty::tests::vectors::compact_zero ... ok
test work::difficulty::tests::vectors::debug_format ... ok
test work::difficulty::tests::vectors::expanded_hash_order ... ok
test work::difficulty::tests::vectors::expanded_order ... ok
test work::difficulty::tests::vectors::genesis_block_difficulty ... ok
test work::difficulty::tests::vectors::testnet_minimum_difficulty ... ok
test work::equihash::tests::equihash_solution_size_field ... ok
test transaction::tests::prop::transaction_valid_network_upgrade_strategy ... ok
test work::tests::prop::equihash_prop_test_nonce ... ok
test work::tests::prop::equihash_prop_test_input ... ok
test work::tests::prop::equihash_solution_roundtrip ... ok
test work::tests::vectors::equihash_solution_test_vectors ... ok
test work::tests::vectors::equihash_solution_test_vectors_are_valid ... ok
test work::tests::prop::equihash_prop_test_solution ... ok

test result: ok. 226 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 95.01s

     Running unittests (target/debug/deps/zebra_client-034a73142463629f)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/zebra_consensus-0bb1c771252a91d1)

running 77 tests
test block::subsidy::founders_reward::test::test_founders_reward ... ok
test block::subsidy::general::test::block_subsidy_test ... ok
test block::subsidy::general::test::halving_test ... ok
test block::subsidy::general::test::miner_subsidy_test ... ok
test block::tests::coinbase_validation_failure ... ok
test block::tests::difficulty_is_valid_for_historical_blocks ... ok
test block::tests::coinbase_is_first_for_historical_blocks ... ok
test block::tests::difficulty_validation_failure ... ok
test block::tests::founders_reward_validation_failure ... ok
test block::tests::merkle_root_is_valid ... ok
test block::tests::subsidy_is_valid_for_historical_blocks ... ok
test block::tests::time_is_valid_for_historical_blocks ... ok
test chain::tests::round_trip_checkpoint_test ... ok
test chain::tests::verify_checkpoint_test ... ok
test block::tests::equihash_is_valid_for_historical_blocks ... ok
test chain::tests::verify_fail_add_block_checkpoint_test ... ok
test checkpoint::list::tests::checkpoint_list_bad_height_fail ... ok
test checkpoint::list::tests::checkpoint_list_duplicate_blocks_fail ... ok
test checkpoint::list::tests::checkpoint_list_duplicate_hashes_fail ... ok
test checkpoint::list::tests::checkpoint_list_duplicate_heights_fail ... ok
test checkpoint::list::tests::checkpoint_list_empty_fail ... ok
test checkpoint::list::tests::checkpoint_list_genesis ... ok
test checkpoint::list::tests::checkpoint_list_hard_coded_mandatory_mainnet ... ok
test checkpoint::list::tests::checkpoint_list_hard_coded_mandatory_testnet ... ok
test checkpoint::list::tests::checkpoint_list_hard_coded_max_gap_mainnet ... ok
test checkpoint::list::tests::checkpoint_list_hard_coded_max_gap_testnet ... ok
test chain::tests::verify_fail_no_coinbase_test ... ok
test checkpoint::list::tests::checkpoint_list_multiple ... ok
test checkpoint::list::tests::checkpoint_list_no_genesis_fail ... ok
test checkpoint::list::tests::checkpoint_list_null_hash_fail ... ok
test checkpoint::list::tests::checkpoint_list_load_hard_coded ... ok
test checkpoint::tests::block_higher_than_max_checkpoint_fail_test ... ok
test checkpoint::tests::checkpoint_drop_cancel_test ... ok
test checkpoint::tests::continuous_blockchain_no_restart ... ok
test checkpoint::tests::hard_coded_mainnet_test ... ok
test checkpoint::tests::multi_item_checkpoint_list_test ... ok
test checkpoint::tests::single_item_checkpoint_list_test ... ok
test checkpoint::tests::wrong_checkpoint_hash_fail_test ... ok
test parameters::tests::minimum_difficulty_mainnet ... ok
test parameters::tests::minimum_difficulty_testnet ... ok
test primitives::ed25519::tests::batch_flushes_on_max_items_test ... ok
test primitives::ed25519::tests::batch_flushes_on_max_latency_test ... ok
test checkpoint::tests::continuous_blockchain_restart ... ok
test primitives::groth16::tests::correctly_err_on_invalid_output_proof ... ok
test primitives::redjubjub::tests::batch_flushes_on_max_items_test ... ok
test primitives::redjubjub::tests::batch_flushes_on_max_latency_test ... ok
test primitives::redpallas::tests::batch_flushes_on_max_items ... ok
test primitives::redpallas::tests::batch_flushes_on_max_latency ... ok
test transaction::tests::add_to_sprout_pool_after_nu ... ok
test transaction::tests::fake_v5_transaction_with_orchard_actions_has_inputs_and_outputs ... ok
test transaction::tests::v4_coinbase_transaction_is_accepted ... ok
test transaction::tests::v4_transaction_with_conflicting_sprout_nullifier_across_joinsplits_is_rejected ... ok
test transaction::tests::v4_transaction_with_conflicting_sprout_nullifier_inside_joinsplit_is_rejected ... ok
test transaction::tests::v4_transaction_with_conflicting_transparent_spend_is_rejected ... ok
test transaction::tests::v4_transaction_with_transparent_transfer_is_accepted ... ok
test transaction::tests::v4_transaction_with_transparent_transfer_is_rejected_by_the_script ... ok
test transaction::tests::v4_with_duplicate_sapling_spends ... ok
test transaction::tests::v4_with_sapling_outputs_and_no_spends ... ok
test transaction::tests::v4_with_sapling_spends ... ok
test transaction::tests::v4_with_signed_sprout_transfer_is_accepted ... ok
test transaction::tests::v4_with_unsigned_sprout_transfer_is_rejected ... ok
test transaction::tests::v5_coinbase_transaction_is_accepted ... ok
test transaction::tests::v5_coinbase_transaction_with_enable_spends_flag_fails_validation ... ok
test transaction::tests::v5_coinbase_transaction_without_enable_spends_flag_passes_validation ... ok
test transaction::tests::v5_fake_transactions ... ok
test transaction::tests::v5_transaction_is_accepted_after_nu5_activation_mainnet - should panic ... ok
test transaction::tests::v5_transaction_is_accepted_after_nu5_activation_testnet ... ok
test transaction::tests::v5_transaction_is_rejected_before_nu5_activation ... ok
test transaction::tests::v5_transaction_with_conflicting_transparent_spend_is_rejected ... ok
test transaction::tests::v5_transaction_with_no_inputs_fails_validation ... ok
test transaction::tests::v5_transaction_with_no_outputs_fails_validation ... ok
test transaction::tests::v5_transaction_with_transparent_transfer_is_accepted ... ok
test transaction::tests::v5_transaction_with_transparent_transfer_is_rejected_by_the_script ... ok
test transaction::tests::v5_with_duplicate_orchard_action ... ok
test transaction::tests::v5_with_duplicate_sapling_spends ... ok
test transaction::tests::v5_with_sapling_spends - should panic ... ok
test primitives::groth16::tests::verify_sapling_groth16 ... ok

test result: ok. 77 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 23.66s

     Running unittests (target/debug/deps/zebra_network-e201c4f43817f1b1)

running 80 tests
test config::tests::parse_config_listen_addr ... ok
test constants::tests::ensure_live_peer_duration_value_matches_others ... ok
test constants::tests::ensure_timeouts_consistent ... ok
test isolated::tests::connect_isolated_sends_minimally_distinguished_version_message ... ok
test address_book::tests::prop::only_recently_reachable_are_gossiped ... ok
test meta_addr::tests::preallocate::meta_addr_size_is_correct ... ok
test meta_addr::tests::prop::gossiped_roundtrip ... ok
test meta_addr::tests::prop::individual_peer_retry_limit_candidate_set ... ok
test meta_addr::tests::prop::individual_peer_retry_limit_meta_addr ... ok
test meta_addr::tests::prop::multiple_peer_retry_order_meta_addr ... ok
test meta_addr::tests::prop::preserve_initial_untrusted_values ... ok
test meta_addr::tests::prop::sanitize_avoids_leaks ... ok
test meta_addr::tests::prop::sanitized_address_book_contains_local_listener ... ok
test meta_addr::tests::prop::sanitized_roundtrip ... ok
test meta_addr::tests::vectors::gossiped_peer_reportedly_seen_in_the_future_is_gossipable ... ok
test meta_addr::tests::vectors::gossiped_peer_reportedly_seen_long_ago_is_not_gossipable ... ok
test meta_addr::tests::vectors::gossiped_peer_reportedly_to_be_seen_recently_is_gossipable ... ok
test meta_addr::tests::vectors::new_alternate_peer_address_is_not_gossipable ... ok
test meta_addr::tests::vectors::new_local_listener_is_gossipable ... ok
test meta_addr::tests::vectors::not_so_recently_responded_peer_is_still_gossipable ... ok
test meta_addr::tests::vectors::recently_responded_peer_is_gossipable ... ok
test meta_addr::tests::vectors::responded_long_ago_peer_is_not_gossipable ... ok
test meta_addr::tests::vectors::sanitize_extremes ... ok
test peer_set::candidate_set::tests::prop::new_outbound_peer_connections_are_rate_limited ... ok
test peer_set::candidate_set::tests::prop::no_last_seen_times_are_in_the_future ... ok
test peer_set::candidate_set::tests::prop::skipping_outbound_peer_connection_skips_rate_limit ... ok
test peer_set::candidate_set::tests::vectors::candidate_set_update_after_update_initial_is_rate_limited ... ok
test peer_set::candidate_set::tests::vectors::candidate_set_updates_are_rate_limited ... ok
test peer_set::candidate_set::tests::vectors::doesnt_offset_last_seen_times_in_the_past ... ok
test peer_set::candidate_set::tests::vectors::doesnt_offsets_if_most_recent_last_seen_times_is_exactly_the_limit ... ok
test peer_set::candidate_set::tests::vectors::offsets_all_last_seen_times_if_one_is_in_the_future ... ok
test peer_set::candidate_set::tests::vectors::offsets_last_seen_times_in_the_future ... ok
test peer_set::candidate_set::tests::vectors::rejects_all_addresses_if_applying_offset_causes_an_underflow ... ok
test peer_set::initialize::tests::vectors::add_initial_peers_is_rate_limited ... ok
test meta_addr::tests::preallocate::meta_addr_max_allocation_is_correct ... ok
test peer_set::initialize::tests::vectors::crawler_peer_limit_default_connect_error ... ok
test peer_set::initialize::tests::vectors::crawler_peer_limit_default_connect_ok_stay_open ... ok
test peer_set::initialize::tests::vectors::crawler_peer_limit_default_connect_ok_then_drop ... ok
test peer_set::initialize::tests::vectors::crawler_peer_limit_one_connect_error ... ok
test peer_set::initialize::tests::vectors::crawler_peer_limit_one_connect_ok_stay_open ... ok
test peer_set::initialize::tests::vectors::crawler_peer_limit_one_connect_ok_then_drop ... ok
test peer_set::initialize::tests::vectors::crawler_peer_limit_zero_connect_panic ... ok
test peer_set::initialize::tests::vectors::listener_peer_limit_default_handshake_error ... ok
test peer_set::initialize::tests::vectors::listener_peer_limit_default_handshake_ok_stay_open ... ok
test peer_set::initialize::tests::vectors::listener_peer_limit_default_handshake_ok_then_drop ... ok
test peer_set::initialize::tests::vectors::listener_peer_limit_one_handshake_error ... ok
test peer_set::initialize::tests::vectors::listener_peer_limit_one_handshake_ok_stay_open ... ok
test peer_set::initialize::tests::vectors::listener_peer_limit_one_handshake_ok_then_drop ... ok
test peer_set::initialize::tests::vectors::local_listener_fixed_port_localhost_addr_v4 ... ok
test peer_set::initialize::tests::vectors::local_listener_fixed_port_localhost_addr_v6 ... ok
test peer_set::initialize::tests::vectors::local_listener_unspecified_port_localhost_addr_v4 ... ok
test peer_set::initialize::tests::vectors::local_listener_unspecified_port_localhost_addr_v6 ... ok
test peer_set::initialize::tests::vectors::local_listener_unspecified_port_unspecified_addr_v4 ... ok
test peer_set::initialize::tests::vectors::local_listener_unspecified_port_unspecified_addr_v6 ... ok
test peer_set::initialize::tests::vectors::listener_peer_limit_zero_handshake_panic ... ok
test peer_set::initialize::tests::vectors::peer_limit_one_mainnet ... ok
test peer_set::initialize::tests::vectors::peer_limit_one_testnet ... ok
test peer_set::initialize::tests::vectors::peer_limit_two_testnet ... ok
test peer_set::initialize::tests::vectors::peer_limit_zero_mainnet - should panic ... ok
test peer_set::initialize::tests::vectors::peer_limit_zero_testnet - should panic ... ok
test protocol::external::codec::tests::filterload_message_round_trip ... ok
test protocol::external::codec::tests::filterload_message_too_large_round_trip ... ok
test protocol::external::codec::tests::max_msg_size_round_trip ... ok
test protocol::external::codec::tests::reject_message_extra_data_round_trip ... ok
test protocol::external::codec::tests::reject_message_no_extra_data_round_trip ... ok
test protocol::external::codec::tests::version_message_round_trip ... ok
test protocol::external::codec::tests::version_timestamp_out_of_range ... ok
test protocol::external::tests::preallocate::inv_hash_max_allocation_is_correct ... ok
test protocol::external::tests::preallocate::inv_hash_size_is_correct ... ok
test protocol::external::tests::prop::inv_and_getdata_message_roundtrip ... ok
test protocol::external::tests::prop::inventory_hash_from_random_bytes ... ok
test protocol::external::tests::prop::inventory_hash_roundtrip ... ok
test protocol::external::tests::vectors::parses_msg_wtx_inventory_type ... ok
test protocol::external::types::proptest::magic_debug ... ok
test protocol::external::types::proptest::proptest_magic_from_array ... ok
test protocol::external::types::test::version_consistent_mainnet ... ok
test protocol::external::types::test::version_consistent_testnet ... ok
test protocol::external::types::test::version_extremes_mainnet ... ok
test protocol::external::types::test::version_extremes_testnet ... ok
test peer_set::initialize::tests::vectors::peer_limit_two_mainnet ... ok

test result: ok. 80 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 138.93s

     Running unittests (target/debug/deps/zebra_rpc-37f30f7bf7411238)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/zebra_script-4706e198fbec1ae5)

running 6 tests
test tests::fail_invalid_script ... ok
test tests::reuse_script_verifier_fail_fail ... ok
test tests::reuse_script_verifier_fail_pass ... ok
test tests::reuse_script_verifier_pass_fail ... ok
test tests::reuse_script_verifier_pass_pass ... ok
test tests::verify_valid_script ... ok

test result: ok. 6 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s

     Running unittests (target/debug/deps/zebra_state-4fd2e0a8250cfd7a)

running 72 tests
test service::chain_tip::tests::vectors::chain_tip_change_is_initially_not_ready ... ok
test service::chain_tip::tests::vectors::current_best_tip_is_initially_empty ... ok
test service::chain_tip::tests::vectors::empty_latest_chain_tip_is_empty ... ok
test service::check::tests::nullifier::accept_distinct_arbitrary_orchard_nullifiers_in_one_block ... ok
test service::check::tests::nullifier::accept_distinct_arbitrary_sapling_nullifiers_in_one_block ... ok
test service::check::tests::nullifier::accept_distinct_arbitrary_sprout_nullifiers_in_one_block ... ok
test service::check::tests::nullifier::reject_duplicate_orchard_nullifiers_in_block ... ok
test service::chain_tip::tests::prop::best_tip_is_latest_non_finalized_then_latest_finalized ... ok
test service::check::tests::nullifier::reject_duplicate_orchard_nullifiers_in_chain ... ok
test service::check::tests::nullifier::reject_duplicate_orchard_nullifiers_in_transaction ... ok
test service::check::tests::nullifier::reject_duplicate_sapling_nullifiers_in_block ... ok
test service::check::tests::nullifier::reject_duplicate_sapling_nullifiers_in_transaction ... ok
test service::check::tests::nullifier::reject_duplicate_sprout_nullifiers_in_block ... ok
test service::check::tests::nullifier::reject_duplicate_sapling_nullifiers_in_chain ... ok
test service::check::tests::nullifier::reject_duplicate_sprout_nullifiers_in_chain ... ok
test service::check::tests::nullifier::reject_duplicate_sprout_nullifiers_in_joinsplit ... ok
test service::check::tests::nullifier::reject_duplicate_sprout_nullifiers_in_transaction ... ok
test service::check::tests::utxo::accept_arbitrary_transparent_spend_from_previous_block ... ok
test service::check::tests::utxo::accept_shielded_mature_coinbase_utxo_spend ... ok
test service::check::tests::utxo::accept_later_transparent_spend_from_this_block ... ok
test service::check::tests::utxo::reject_duplicate_transparent_spend_in_same_block_from_previous_block ... ok
test service::check::tests::utxo::reject_duplicate_transparent_spend_in_same_chain_from_previous_block ... ok
test service::check::tests::utxo::reject_duplicate_transparent_spend_in_same_transaction_from_previous_block ... ok
test service::check::tests::utxo::reject_duplicate_transparent_spend_in_same_transaction_from_same_block ... ok
test service::check::tests::utxo::reject_immature_coinbase_utxo_spend ... ok
test service::check::tests::utxo::reject_earlier_transparent_spend_from_this_block ... ok
test service::check::tests::utxo::reject_unshielded_coinbase_utxo_spend ... ok
test service::check::tests::vectors::test_orphan_consensus_check ... ok
test service::check::tests::vectors::test_sequential_height_check ... ok
test service::check::tests::utxo::reject_missing_transparent_spend ... ok
test service::finalized_state::disk_format::tests::roundtrip_block_hash ... ok
test service::finalized_state::disk_format::tests::roundtrip_block_height ... ok
test service::finalized_state::disk_format::tests::roundtrip_transaction_location ... ok
test service::finalized_state::disk_format::tests::roundtrip_transparent_output ... ok
test service::finalized_state::disk_format::tests::roundtrip_value_balance ... ok
test service::finalized_state::disk_format::tests::roundtrip_block ... ok
test service::finalized_state::tests::vectors::orchard_note_commitment_tree_serialization ... ok
test service::finalized_state::tests::vectors::sapling_note_commitment_tree_serialization ... ok
test service::non_finalized_state::queued_blocks::tests::dequeue_gives_right_children ... ok
test service::non_finalized_state::queued_blocks::tests::prune_removes_right_children ... ok
test service::non_finalized_state::tests::prop::different_blocks_different_chains ... ok
test service::finalized_state::tests::prop::blocks_with_v5_transactions ... ok
test service::non_finalized_state::tests::prop::finalized_equals_pushed_genesis has been running for over 60 seconds
test service::non_finalized_state::tests::prop::finalized_equals_pushed_history_tree has been running for over 60 seconds
test service::non_finalized_state::tests::prop::finalized_equals_pushed_genesis ... ok
test service::non_finalized_state::tests::prop::finalized_equals_pushed_history_tree ... ok
test service::non_finalized_state::tests::prop::forked_equals_pushed_genesis has been running for over 60 seconds
test service::non_finalized_state::tests::prop::forked_equals_pushed_history_tree has been running for over 60 seconds
test service::non_finalized_state::tests::prop::forked_equals_pushed_history_tree ... ok
test service::non_finalized_state::tests::prop::forked_equals_pushed_genesis ... ok
test service::non_finalized_state::tests::prop::push_history_tree_chain ... ok
test service::non_finalized_state::tests::prop::push_genesis_chain ... ok
test service::non_finalized_state::tests::vectors::best_chain_wins ... ok
test service::non_finalized_state::tests::vectors::commit_block_extending_best_chain_doesnt_drop_worst_chains ... ok
test service::non_finalized_state::tests::vectors::commitment_is_validated ... ok
test service::non_finalized_state::tests::vectors::construct_empty ... ok
test service::non_finalized_state::tests::vectors::construct_many ... ok
test service::non_finalized_state::tests::vectors::construct_single ... ok
test service::non_finalized_state::tests::vectors::equal_length_goes_to_more_work ... ok
test service::non_finalized_state::tests::vectors::finalize_pops_from_best_chain ... ok
test service::non_finalized_state::tests::vectors::history_tree_is_updated ... ok
test service::non_finalized_state::tests::vectors::longer_chain_with_more_work_wins ... ok
test service::non_finalized_state::tests::vectors::ord_matches_work ... ok
test service::non_finalized_state::tests::vectors::shorter_chain_can_be_best_chain ... ok
test service::tests::at_least_one_transaction_with_inconsistent_network_upgrade ... ok
test service::tests::at_least_one_transaction_with_valid_network_upgrade ... ok
test service::tests::chain_tip_sender_is_updated ... ok
test service::tests::empty_state_still_responds_to_requests ... ok
test service::tests::no_transaction_with_network_upgrade ... ok
test service::tests::some_block_less_than_network_upgrade ... ok
test service::tests::state_behaves_when_blocks_are_committed_in_order ... ok
test service::tests::state_behaves_when_blocks_are_committed_out_of_order ... ok
test service::tests::value_pool_is_updated ... ok
test tests::round_trip_work_expanded ... ok
test tests::test_block_locator_heights ... ok
test service::non_finalized_state::tests::prop::rejection_restores_internal_state_genesis ... ok

test result: ok. 72 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 290.55s

     Running tests/basic.rs (target/debug/deps/basic-56f50589b8cd1be4)

running 2 tests
test check_transcripts_mainnet ... ok
test check_transcripts_testnet ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.22s

     Running unittests (target/debug/deps/zebra_test-8ef4b61e88f5bf67)

running 2 tests
test vectors::block::test::block_test_vectors_count ... ok
test vectors::block::test::block_test_vectors_unique ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.09s

     Running tests/command.rs (target/debug/deps/command-68dcd1f5d3e27ea2)

running 3 tests
test finish_before_timeout_short_output_no_newlines ... ok
test finish_before_timeout_output_single_line ... ok
test kill_on_timeout_output_continuous_lines ... ok

test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2.07s

     Running tests/transcript.rs (target/debug/deps/transcript-0fda2a6ffe9804d2)

running 4 tests
test self_check ... ok
test self_check_err ... ok
test transcript_errors_wrong_request ... ok
test transcript_returns_responses_and_ends ... ok

test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s

     Running unittests (target/debug/deps/zebra_utils-1412775e24c838c2)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/zebra_checkpoints-916ca36852837feb)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/zebrad-e6d073a81710707e)

running 41 tests
test components::inbound::tests::mempool_advertise_transaction_ids ... ok
test components::inbound::tests::mempool_push_transaction ... ok
test components::inbound::tests::mempool_transaction_expiration ... ok
test components::inbound::tests::mempool_requests_for_transactions ... ok
test components::mempool::crawler::tests::crawled_transactions_are_forwarded_to_downloader ... ok
test components::mempool::crawler::tests::transaction_id_forwarding_errors_dont_stop_the_crawler ... ok
test components::mempool::storage::tests::prop::conflicting_transactions_are_rejected ... ok
test components::mempool::storage::tests::prop::eviction_list_refresh - should panic ... ok
test components::mempool::storage::tests::prop::eviction_list_size ... ok
test components::mempool::storage::tests::prop::eviction_list_time ... ok
test components::mempool::storage::tests::prop::eviction_list_time_mixed ... ok
test components::mempool::crawler::tests::crawler_requests_for_transaction_ids ... ok
test components::mempool::storage::tests::prop::reject_lists_are_limited_insert_conflict ... ok
test components::mempool::storage::tests::prop::reject_lists_are_limited_insert_eviction ... ok
test components::mempool::storage::tests::prop::reject_lists_are_limited_reject ... ok
test components::mempool::storage::tests::prop::reject_lists_are_time_pruned ... ok
test components::mempool::storage::tests::prop::removal_of_multiple_transactions ... ok
test components::mempool::storage::tests::vectors::mempool_expired_basic ... ok
test components::mempool::storage::tests::vectors::mempool_storage_basic ... ok
test components::mempool::storage::tests::vectors::mempool_storage_crud_exact_mainnet ... ok
test components::mempool::storage::tests::vectors::mempool_storage_crud_same_effects_mainnet ... ok
test components::mempool::tests::prop::storage_is_cleared_if_syncer_falls_behind ... ok
test components::mempool::storage::tests::prop::rejected_transactions_are_properly_rolled_back ... ok
test components::mempool::tests::prop::storage_is_cleared_on_chain_reset ... ok
test components::mempool::tests::vector::mempool_cancel_downloads_after_network_upgrade ... ok
test components::mempool::tests::vector::mempool_cancel_mined ... ok
test components::mempool::tests::vector::mempool_failed_download_is_not_rejected ... ok
test components::mempool::tests::vector::mempool_failed_verification_is_rejected ... ok
test components::mempool::tests::vector::mempool_queue ... ok
test components::mempool::tests::vector::mempool_service_basic ... ok
test components::mempool::tests::vector::mempool_service_disabled ... ok
test components::sync::recent_sync_lengths::tests::prop::latest_first ... ok
test components::sync::recent_sync_lengths::tests::prop::max_recent_lengths ... ok
test components::sync::recent_sync_lengths::tests::vectors::recent_sync_lengths_are_initially_empty ... ok
test components::sync::status::tests::empty_sync_lengths ... ok
test components::sync::status::tests::high_sync_lengths ... ok
test components::mempool::tests::prop::storage_is_cleared_on_chain_resets ... ok
test components::sync::status::tests::zero_sync_lengths ... ok
test components::sync::tests::timing::ensure_timeouts_consistent ... ok
test components::sync::status::tests::waits_until_close_to_tip ... ok
test components::sync::tests::timing::request_genesis_is_rate_limited ... ok

test result: ok. 41 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 57.21s

     Running unittests (target/debug/deps/zebrad-fc2f7c6544e8cdd6)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running tests/acceptance.rs (target/debug/deps/acceptance-301d19a279e7b864)

running 27 tests
test app_no_args ... ok
test ephemeral_existing_directory ... ok
test ephemeral_missing_directory ... ok
test generate_args ... ok
test generate_no_args ... ok
test help_args ... ok
test help_no_args ... ok
test metrics_endpoint ... ok
test misconfigured_ephemeral_existing_directory ... ok
test misconfigured_ephemeral_missing_directory ... ok
test activate_mempool_mainnet has been running for over 60 seconds
test persistent_mode ... ok
test activate_mempool_mainnet ... ok
test start_args ... ok
test restart_stop_at_height ... ok
test sync_large_checkpoints_mainnet ... ignored
test sync_large_checkpoints_mempool_mainnet ... ignored
test start_no_args ... ok
test sync_one_checkpoint_testnet ... ok
test sync_one_checkpoint_mainnet ... ok
test tracing_endpoint ... ok
test version_args ... ok
test version_no_args ... ok
test valid_generated_config_test ... ok
test zebra_metrics_conflict ... ok
test zebra_state_conflict ... ok
test zebra_tracing_conflict ... ok
test zebra_zcash_listener_conflict ... ok

test result: ok. 25 passed; 0 failed; 2 ignored; 0 measured; 0 filtered out; finished in 181.48s

   Doc-tests tower-batch

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests tower-fallback

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests zebra-chain

running 9 tests
test src/amount.rs - amount::NonNegative (line 473) ... ok
test src/amount.rs - amount::NegativeAllowed (line 455) ... ok
test src/serialization/constraint.rs - serialization::constraint::AtLeastOne (line 13) ... ok
test src/serialization/constraint.rs - serialization::constraint::AtLeastOne (line 34) ... ok
test src/serialization/constraint.rs - serialization::constraint::AtLeastOne (line 55) ... ok
test src/serialization/read_zcash.rs - serialization::read_zcash::ReadZcashExt::read_compactsize (line 33) ... ok
test src/serialization/read_zcash.rs - serialization::read_zcash::ReadZcashExt::read_compactsize (line 56) ... ok
test src/serialization/write_zcash.rs - serialization::write_zcash::WriteZcashExt::write_compactsize (line 25) ... ok
test src/serialization/write_zcash.rs - serialization::write_zcash::WriteZcashExt::write_compactsize (line 43) ... ok

test result: ok. 9 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 8.11s

   Doc-tests zebra-client

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests zebra-consensus

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests zebra-network

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests zebra-rpc

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests zebra-script

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests zebra-state

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests zebra-test

running 10 tests
test src/mock_service.rs - mock_service::MockService<Request,Response,PanicAssertion,Error>::expect_no_requests (line 388) ... ok
test src/mock_service.rs - mock_service (line 10) ... ok
test src/mock_service.rs - mock_service::MockService<Request,Response,PanicAssertion,Error>::expect_request (line 295) ... ok
test src/mock_service.rs - mock_service::MockService<Request,Response,PanicAssertion,Error>::expect_request_that (line 345) ... ok
test src/mock_service.rs - mock_service::MockService<Request,Response,PropTestAssertion,Error>::expect_no_requests (line 562) ... ok
test src/mock_service.rs - mock_service::MockService<Request,Response,PropTestAssertion,Error>::expect_request (line 450) ... ok
test src/mock_service.rs - mock_service::MockService<Request,Response,PropTestAssertion,Error>::expect_request_that (line 510) ... ok
test src/mock_service.rs - mock_service::MockServiceBuilder::with_max_request_delay (line 217) ... ok
test src/mock_service.rs - mock_service::MockServiceBuilder::with_proxy_channel_size (line 193) ... ok
test src/mock_service.rs - mock_service::ResponseSender<Request,Response,Error>::respond (line 700) ... ok

test result: ok. 10 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 7.72s

   Doc-tests zebra-utils

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests zebrad

running 3 tests
test src/async_ext/now_or_later.rs - async_ext::now_or_later::NowOrLater (line 39) ... ok
test src/components/mempool/crawler.rs - components::mempool::crawler (line 16) - compile fail ... ok
test src/async_ext/now_or_later.rs - async_ext::now_or_later::NowOrLater (line 26) ... ok

test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2.39s

The above log produced the following crashes.
Crash logs.zip
But in the terminal log all appears to be ok.
Although the crashes happened while the last entry in the terminal was test zebra_tracing_conflict so the crashes must have occurred somewhere there.

The above log produced the following crashes.
Crash logs.zip
But in the terminal log all appears to be ok.
Although the crashes happened while the last entry in the terminal was test zebra_tracing_conflict so the crashes must have occurred somewhere there.

I had a look at the crash reports on my macOS machine, and it looks like they come from expected errors in the tests.
Some of Zebra's tests deliberately cause errors that make Zebra abort with a Rust panic. Then macOS records these aborts as crash reports.
If you are seeing "Crash Reporter" dialogs during Zebra tests, you can disable them using this Terminal.app command:
defaults write com.apple.CrashReporter DialogType none


Add contribution steps to readme/contributing.md for Gitpod users

Is your feature request related to a problem? Please describe.
I can add a section to the readme called "Contribute to Daytona using Daytona and Gitpod as workspace" with details on how to set up a workspace with a repository fork. This will make contributing simpler and more appealing in general.
Describe the solution you'd like
Since Gitpod comes up with pre-installed docker, therefore, many users use it. Thus, if we write contribution guidelines for that, then the contribution process will become easy.

You are allowed to add the contribution steps for the Gitpod users to readme/contributing.md for their betterment .

Working

I was shortlisted for the swags giveaway. I had posted the screenshot they
asked. Do I need to fill the form again and post it? Or everything's
perfect?
On Mon, 24 Jun 2024, 9:28 am Rohan Sharma, @.***> wrote:

Working
—
Reply to this email directly, view it on GitHub
https://github.com/daytonaio/daytona/issues/705#issuecomment-2185549754,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFEV2XE4GE7YUPVAJVX7XM3ZI6KOJAVCNFSM6AAAAABJXILHF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBVGU2DSNZVGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I was shortlisted for the swags giveaway. I had posted the screenshot they
asked. Do I need to fill the form again and post it? Or everything's
perfect?

@AnmollCodes which giveaway and form are you referring to?

WIll be finished by today!

Our focus is currently on maintaining and improving our current setup and documentation, and we want to ensure a consistent experience for all contributors using the existing recommended tools.
We will create a contribution guide that uses Daytona to contribute back to Daytona and, with the latest performance improvements coming in the next few releases, it should make the entire process much more seamless.
We encourage contributors to use our established setup guidelines and reach out if they encounter any issues.
Thank you for understanding.


Versioning for Definitions

Definitions should have a version as well.

In our scenario, we have a bunch of Parquet files in a S3 bucket. The schema evolved over time in terms of data type changes, newly added columns etc. From my understanding I don't have the ability to reflect those changes, neither in the server.location property, nor the model definition itself.
Is this what you mean when saying

Definitions should have a version as well.

?
Even if I have the ability to tag a model with a certain version (e.g. by introducing a property), I also need to be able to to tell the checker which S3 objects match the which model/schema version. As stated above, in our case we might have n files that match version 1.0.0 and m files that match version 1.1.0 all stored under the same S3 path. However, we don't have the ability to specify exactly which of these files match the 1.0.0 definition and which the 1.1.0.
I hope this issue was the right one for this discussion and my description makes sense.


a

Location

[ ] [

[ ] ]()

Hey, @Rubensky2021 can you please describe the issue so that we can work on it?


Color picker

Changes

Added color picker

https://user-images.githubusercontent.com/32574227/122842556-a007ec80-d2cb-11eb-8b85-441765839f12.mov

I paused on adding this because I was running into some performance issues. Instead, I decided to put this component into PHC. After adding it in this morning, @ynotdraw pointed out that maybe the performance issue was caused because the story was rendering a lot of ColorPickers... which was the case. 🤦♀  Once this is approved I will update this PR to just use this component.


replace isl_space_{un}named_set_from_params by isl_space_add{un}named_tuple*

The old names do not work out very well in the C++ bindings.
The new functions are also more generic and also support
creating a map space from a domain space.

On Tue, Jul 10, 2018 at 05:45:45PM +0000, ftynse wrote:

ftynse commented on this pull request.
Why does the 'named' function have the ui suffix (for unsigned integer) but the unnamed does not?  It's last argument is also an unsigned integer.  Do you expect other types for the dimension of the tuple in the future?

No, but possibly for the next to last argument.
However, if we want to extend the bindings generator to drop suffixes
corresponding to arguments that are not the last, then I think it
should first drop suffixes corresponding to later arguments.
I updated the commit message.
skimo

No, but possibly for the next to last argument.
However, if we want to extend the bindings generator to drop suffixes
corresponding to arguments that are not the last, then I think it
should first drop suffixes corresponding to later arguments.

If we want to extend the bindings generator, wouldn't it make sense to have isl_space_add_unnamed_tuple_ui ?
Alternatively, you may swap the last two arguments in isl_space_add_named_tuple_?? so that only the last argument needs to be dropped.

On Wed, Jul 11, 2018 at 02:07:28AM -0700, ftynse wrote:

No, but possibly for the next to last argument.
However, if we want to extend the bindings generator to drop suffixes
corresponding to arguments that are not the last, then I think it
should first drop suffixes corresponding to later arguments.

If we want to extend the bindings generator, wouldn't it make sense to have isl_space_add_unnamed_tuple_ui ?

I don't see the connection.
Why would we need to add a suffix there?
skimo

For consistency with the other one.

On Wed, Jul 11, 2018 at 02:18:03AM -0700, ftynse wrote:

For consistency with the other one.

ok then...
skimo


[StyleCop] Fix warnings in ApplicationInsights projects

Fix spacing
Add trailing comma
Fix documentation

Pull Request Test Coverage Report for Build 51642

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 75.588%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder.ApplicationInsights/BotTelemetryClient.cs
1
98.85%

Totals

Change from base Build 51599:
0.0%

Covered Lines:
4304

Relevant Lines:
5694

💛  - Coveralls


ReadFlatFileStructure / ReadTreeFileStructure

Hi,
I couldn't read the FileStructure but reading the Groups and Datasets work fine. On debugging your code.
It throw an exception on a group with many attributes. (An attempt was made to read or write to protected memory. Often times, this is an indication that other memory is damaged.) It's thrown on H5A.iterate!
`            int Callback(long elementId, IntPtr intPtrName, ref H5L.info_t info, IntPtr intPtrUserData)
{
ulong idx2 = 0;
long groupId = -1;
long datasetId = -1;
H5O.type_t objectType;
var name = Marshal.PtrToStringAnsi(intPtrName);
var userData = Marshal.PtrToStringAnsi(intPtrUserData);
var fullName = CombinePath(userData, name);
Hdf5ElementType elementType = Hdf5ElementType.Unknown;
// this is necessary, since H5Oget_info_by_name is slow because it wants verbose object header data
// and H5G_loc_info is not directly accessible
// only chance is to modify source code (H5Oget_info_by_name)
groupId = (H5L.exists(elementId, name) >= 0) ? H5G.open(elementId, name) : -1L;
if (H5I.is_valid(groupId) > 0)
{
                objectType = H5O.type_t.GROUP;
                elementType = Hdf5ElementType.Group;
                ulong attId = 0;
                **_var index = H5A.iterate(groupId, H5.index_t.NAME, H5.iter_order_t.INC, ref attId, AttributeCallback,
                            Marshal.StringToHGlobalAnsi("/"));_**

            }...`

here is some Testdata which produces that error!
TEST_2.zip

Thanks! I'll check this out🙂

Hi, @Tomes14 ,
a fix for ReadStructure should be ready in the coming days. FYI

fine thank you!!!

There were many changes/fixes in latest version
https://github.com/LiorBanai/HDF5-CSharp/releases/tag/V1.14.0
You can give it a try if report problems/issues.
Please create new issue if problem persist.


Idea: Add validation in CI that the API files are not modified

We want to catch when people are making manual edits to the API docs, rather than the edits coming from the API generation. This would look like in CI regenerating the API docs and checking that there are no changes made according to Git.
Before we can do this, we need to make the API generation deterministic, e.g. via https://github.com/Qiskit/documentation/issues/8 and https://github.com/Qiskit/documentation/issues/63.
Although, this requires regenerating the API docs, which is slow. That will especially be slow when we have historical versions. I'm not sure we actually want this.
A much simpler and faster algorithm would be if we somehow error on changes to the relevant folder if there has not been a subsequent change to the JSON config file from https://github.com/Qiskit/documentation/issues/8 to say which files to generate the docs with. Basically, if for version 0.25, we say to use URL x, we shouldn't allow any changes to its folder unless we also update the config to now use URL y. We don't actually care what the content change was—only that the folder's changes were accompanied by an update to the config file.

I don't think this is very viable to implement easily. We're going to have the user specify the URL to generate from as a runtime arg, rather than checking in a file to version control. So there's no deterministic way to rebuild the docs.
And it's so slow also it's not worth it. Code review should be sufficient.


Explicit pocket and keep chains

added the keep chain arg too with test included and documentation, all should be working

typo in the docs:
chose -> choose

i don't see the outputs in sample in the merge request, i deleted the modified output in the data folder


⚠ Bofrost.es has degraded performance

In c59ecc6, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 2063 ms

Resolved: Bofrost.es performance has improved in 813a8a5 after 6 minutes.


Extend core protos per request

I need to benchmark this, but if we utilize proto per-request to extend the request/response protos we can have multiple varying version of express co-exist in the same process

done


Remove PyCQA/bandit pre-commit check

Part of #2030
More context: https://github.com/intel/intel-xpu-backend-for-triton/issues/2913
Remaining bandit check in https://github.com/intel/intel-xpu-backend-for-triton/blob/main/.github/workflows/bandit-check.yml

Given the comment: https://github.com/intel/intel-xpu-backend-for-triton/issues/2913#issuecomment-2518200301 I guess I can just remove this check from pre-commit file and not move it to the workflow.

@vlad-penkin are we ok to remove bandit scans?

only for PRs, scheduled launches remain


Sphinx docs

Description
Prepare documentation folder to make it build-able with Sphinx (see #960 for reasons why).
I tried to modify one of the original sphinx themes to use a dark background. The results of how it currently looks like are shown in the screenshot below:

In order to build the docs locally, you'd need to first run pip install -r requirements.txt, and then make html.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors and are passing (See Contributor Guide).
[x] My PR does not decrease the code coverage, or I have a very special case and explained on the PR description why this PR decreases the coverage.
[x] I updated/added relevant documentation (doc comments with ///) and updated/added examples in doc/examples.
[x] I have formatted my code with ./scripts/format.sh and the Flame analyzer (./scripts/analyze.sh) does not report any problems.
[x] I read and followed the Flame Style Guide.
[ ] I have added a description of the change under [next] in CHANGELOG.md.
[x] I removed the Draft status, by clicking on the Ready for review button in this PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flame users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md).
[x] No, this is not a breaking change.

Related Issues
WIP for #960

Great idea! We do need to find a way to wire it up for the website deploy

should we use flame icon & logo instead of Blue Fire? since this is flame-related doc?

I thought the change to Blue Fire / blue color was across the board. But if you're saying Flame remains orange/red as it was before, then it's my misunderstanding. I've changed the logo and favicon to use the correct colors now.

can the static folder be inside the config folder too? (not sure if possible)

The folder can be renamed/moved, no problem. However, the purpose of this folder is not to provide build configuration, but rather it's a store for static content that will end up being copied into the resulting HTML website. This typically includes things like stylesheets, images, scripts, etc. It is pretty much equivalent to the assets folder in Android/iOS project. Perhaps we should rename it as such?
It would probably make sense to move the current images folder inside that folder -- but that's better to do as a separate PR.

After all the tweaks, the doc now renders like this:

After all the tweaks, the doc now renders like this:

Very nice!!

the purpose of this folder is not to provide build configuration

I was thinking more of a way to separate any and all "build" files from the markdowns, so someone browsing on github doesn't get lost reading some config file or css. but maybe the name isn't the best then, how about:
+ /doc
|--+ /sphinx
|   |-- /config
|   |-- /static
|-- actual md files

woudl that work?

@luanpotter  We could make nested folders like you're suggesting. The only question then is what do we do with images/? Conceptually, they're part of the static assets, so should go into that folder. But at the same time, they are very close to being the "content", and in fact, aren't really sphinx-specific. I guess we could have a rule that those images that are embedded into the page(s) will go into the root images/ folder, while those images/assets that are needed specifically for sphinx would go into the sphinx/images folder? It is possible that at some point we'd want to add custom fonts (if Arial is too boring), or scripts (for example in order to embed dart samples into the page) -- but these won't be renderable on GitHub anyway.
Btw, sphinx uses _ in front of a name to signify "special" folders, resembling the convention for private variables in a class. Do we want to stick to this convention (so it'd be _sphinx/ instead sphinx/)?

@st-pasha totally agree with your distinction between two kinds of images folders, one for actual content and one for sphinx related stuff!
for the _, if it's a normal sphinx convention, I am ok with naming it _sphinx!


Create quality README file

I worked on User Story and Acceptance Criteria today.

OOPs not closed , just trying to move it to in process or progress...


on_scheduler_exit unused

Description
Is there a reason on_scheduler_exit is unused? (https://github.com/stan-dev/math/blob/develop/stan/math/rev/core/init_chainablestack.hpp#L50)
Should we put it in the destructor or not use it?
Current Version:
v3.1.0

Also why is this second if here: https://github.com/stan-dev/math/blob/develop/stan/math/rev/core/autodiffstackstorage.hpp#L128

From the doc:
How is thread safety ensured for creating the singleton?  It looks like creating instance_ would cause a race condition as the doc says:

The singleton instance_ is a global static pointer

Is there a reason we can't  not just use this?
static const AutodiffStackStorage* singleton() {
  static  const AutodiffStackStorage instance;
  return &instance;
}

I thought it was guaranteed to be thread safe and only called once.  But I feel like we had this discussion already.
If the init() static class function's needed for some reason, then it might be easier to understand written as:
static bool init() {
  static STAN_THREADS_DEF bool is_initialized = false;
  if (is_initialized && instance_) { return false; }
  is_initialized = true;
  instance_ = new AutodiffStackStorage();
  return true;
};

@bbbales2 on_scheduler_exit is unused in the Stan programs as we use them, because thread cease to exist on program termination. In other applications there could be the possibility that the C++ application creates threads, uses them with the TBB and then terminates the thread before exiting the program. In this case the on_scheduler_exit is used.
@bob-carpenter What you propose is a Mayer singleton approach. We used that in the past, but it is slow as it gives you a ~20% performance hit when this thing is thread local. The admittedly odd gymnastic in init() is needed to avoid a static init order catastrophe, which requires that we do not access any globals where we cannot be sure of initialization status at the time-point when the program flows over it.

On Feb 26, 2020, at 12:32 AM, wds15<EMAIL_ADDRESS>wrote:
@bbbales2 on_scheduler_exit is unused in the Stan programs as we use them, because thread cease to exist on program termination. In other applications there could be the possibility that the C++ application creates threads, uses them with the TBB and then terminates the thread before exiting the program. In this case the on_scheduler_exit is used.

Should we have the exit called before exiting a main() so we
don't dangle resources (even if they will go away).

@bob-carpenter What you propose is a Mayer singleton approach. We used that in the past, but it is slow as it gives you a ~20% performance hit when this thing is thread local. The admittedly odd gymnastic in init() is needed to avoid a static init order catastrophe, which requires that we do not access any globals where we cannot be sure of initialization status at the time-point when the program flows over it.

Thanks for the reminder.  I couldn't remember if the
pattern I was suggesting was broken or slow, but I do remember
it from before.

There are no resources left behind. The unique ptr will manage the stack resource. The main point about the exit function is to deregister the exiting thread from the unordered map which is obsolete as it is destructed.

on_scheduler_exit is unused in the Stan programs as we use them, because thread cease to exist on program termination'

Should we have the exit called before exiting a main() so we don't dangle resources (even if they will go away).

By adding an on_scheduler_exit function to the destructor do we solve this?

Oh I see. All it is doing is deleting something from a map.

Also regarding the init(), is this attached to the rstan segfault at all? That code is using an older init() which only has one if in it.

By adding an on_scheduler_exit function to the destructor do we solve this?

I don't think we need to care about this. All of this is managed by the Intel TBB.

Oh I see. All it is doing is deleting something from a map.

Yup. Resources are not managed by the object directly.

Also regarding the init(), is this attached to the rstan segfault at all? That code is using an older init() which only has one if in it.

I don't think so as rstan is with 2.19 where we did not yet have the new TLS stuff in 2.19.
Can we close this issue?

Nono, I was talking about the rstan issue we're talking to BGoodrich about now. That is develop RStan and some new StanHeaders.

Can we close this issue?

Yeah but this code needs doc'd.

Actually wait I think we need to leave this open? I'm confused. I don't understand the execution context of this. We should probably just talk through it at the next Math meeting.
If it makes sense to ever destruct these objects and build them again, the destruction better be threadsafe, and it sure seems like from on_scheduler_exit there's some locks and whatnot in the deallocation of the map.

Should we change the issue? I mean the method is used for sure in some contexts. Talking about this is probably easiest.

Yeah rename to whatever. @syclik hopefully we can remember to talk about this in next Math meeting.


Use a geometric shape for the menu symbol (rather than the Taoist Bagua trigram for Heaven)

I'm a little on the fence about this one, but it seems wrong to use U+2630 TRIGRAM FOR HEAVEN for representing a menu because the glyph happens to look approximately as desired. This geometric symbol (U+25A4 SQUARE WITH HORIZONTAL FILL) is the best substitute I could find in Unicode, but alternatively we could just use an SVG.

Before
After

Why does it seem wrong? The ☰ icon is a very widely used icon to indicate a menu, and the origin of a glyph is only relevant if people think of that when they see it, and are confused or offended. Is either of those a concrete complaint here?

It's at least poor form to (ab)use a code point because the associated glyph has convenient characteristics, and generally troublesome for people using a screen reader (although I do not know for certain that such is the case here). Unicode is clear about "character" corresponding with abstract meaning rather than shape.

I agree the current thing is an abuse of Unicode, though I think it's kind of a shame they haven't officially blessed this usage (or given "hamburger menu" its own code point).
Concretely, I'd be happier with an SVG or faking it with CSS rather than ▤. Here's a dead simple SVG I just wrote by hand (I am not an expert):
<svg viewBox='0 0 30 30' xmlns='http://www.w3.org/2000/svg'><path stroke='rgba(0, 0, 0, 1)' stroke-width='3' stroke-linecap='round' d='M4 7H26M4 15H26M4 23H26'/></svg>

or as a data URI:
data:image/svg+xml;charset=utf8,<svg viewBox='0 0 30 30' xmlns='http://www.w3.org/2000/svg'><path stroke='rgba(0, 0, 0, 1)' stroke-width='3' stroke-linecap='round' d='M4 7H26M4 15H26M4 23H26'/></svg>

I was reminded of this by the ecmarkup preview in Matrix. Should it land using U+25A4 SQUARE WITH HORIZONTAL FILL, or switch to SVG? And either way, I'm now also thinking about a followup that leverages ARIA like https://www.w3.org/TR/wai-aria-practices/#menu and/or https://til.simonwillison.net/javascript/dropdown-menu-with-details-summary .

Let's use an SVG. I'm fine with the one I suggested above if you don't want to come up with a new one, but I'm not attached to it if you have something you'd prefer.
Re: ARAI, there's definitely room for improvement, and I'd be happy to review such a PR (though I currently lack the knowledge to write one).

Let's use an SVG.

Done.

Thanks for following up, and sorry for letting this sit so long.

Not at all, the fault was mine.


IronPython install modules error (there is a simplier way ?)

Description
Hello everyone, thank you in advance for your help. I'm developing an application in C# on visual studio that aims to launch .py files using voice commands, so I use the ironpython library. The problem is that I would like to import modules to have more possibilities such as pressing keys.
But the problem is that I can't find an easy way to install modules for users. And even then, I can't install a module myself.... I tried importing it directly into the searchpath, but there was a lot of libraries missing so I gave up. And then I tried to install the ironpython.exe to go through ipy.exe, but there are only problems. I receive the following error message with each installation attempt:
You are using pip version 8.1.1, however version <IP_ADDRESS> is available.
You should consider upgrading via the'python -m pip install --upgrade pip' command.
While I have the latest version of IronPython (I even ordered: ipy -X:Frames -m ensurepip).
I've been straightening my hair for a few weeks now and I'm afraid I can't find a simple way to install modules
So would you have either a fix for ipy or a simpler way to install modules so that my users don't get lost? Thank you very much and have a good day!
Steps to Reproduce
1.Install IronPython
2.Go to IronPython installation folder
3.Type in cmd: cd IRONPYTHONPATH
4.Type: ipy -X:Frames -m pip install pynput (or another package)
Expected behavior: Install the package
Actual behavior: Error (describe on the top)
Versions
IronPython 2.7.9 (<IP_ADDRESS>) on .NET 4.0.30319.42000 (64-bit)

The message:
You are using pip version 8.1.1, however version 19.1.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.

is not the error message (it appears even when you do something that works). Having the actual error message would be useful in helping you out.
Without seeing the error message, my guess would be that IronPython is installed in C:\Program Files\IronPython 2.7 and that when you are running pip install it fails to copy to the C:\Program Files\IronPython 2.7\Lib\site-packages folder. This occurs because you need elevated privileges to write to that folder. If this is indeed the issue you could try to run cmd as administrator. The other option is to install the package to a user folder using for example ipy -m pip install --user pynput.

Thank you for your answer, indeed with the cmd open as administrator the module was downloaded, so I moved the downloaded files (available here: %appdata%/Python/IronPython27/site-packages) in a folder in the searchpath of my application. But I had an error when I started the script: ImportError: No module named Xlib.display.
So Pip didn't download everything... I tried to import the library manually and I got: ImportError: No module named fcntl...
So I don't know what to do, are the modules well managed by IronPython? Thank you very much good evening!

fcntl is a Unix module which is why it does not work. I think Xlib.display does not support Windows?
Support of 3rd party packages varies, there are some known issues, for example:

Modules that require C extensions will now work
str in IronPython is equivalent to unicode instead of bytes so this may cause issues
sys.platform == "cli" so this may cause issues if the Python code checks for "win32"

Ok , so there isn't a complete compatibility ? :(

Unfortunately not, although we try to support pure Python modules as much as possible.
Closing this issue since the original problem was resolved.

I am new python learner
Whey I try to install any package for ironpython I am into trouble like:

C:\Program Files\IronPython 2.7> ipy -m pip install matplotlib
Unhandled exception:
Traceback (most recent call last):
File "C:\Program Files\IronPython 2.7\Lib\runpy.py", line 182, in run_module
File "C:\Program Files\IronPython 2.7\Lib\runpy.py", line 107, in get_module
details
ImportError: No module named pip

or next

C:\Program Files\IronPython 2.7>ipy -m ensurepip
Ignoring indexes: https://pypi.python.org/simple
Collecting setuptools
Exception:
Traceback (most recent call last):
File "c:\users\администратор\appdata\local\temp\tmplcobae\pip-8.1.1-py2.py3-no
ne-any.whl\pip\basecommand.py", line 209, in main
status = self.run(options, args)
File "c:\users\администратор\appdata\local\temp\tmplcobae\pip-8.1.1-py2.py3-no
ne-any.whl\pip\commands\install.py", line 299, in run
requirement_set.prepare_files(finder)
File "c:\users\администратор\appdata\local\temp\tmplcobae\pip-8.1.1-py2.py3-no
ne-any.whl\pip\req\req_set.py", line 356, in prepare_files
discovered_reqs.extend(self._prepare_file(
File "C:\Program Files\IronPython 2.7\Lib\contextlib.py", line 35, in exit
self.gen.throw(type, value, traceback)

File "c:\users\администратор\appdata\local\temp\tmplcobae\pip-8.1.1-py2.py3-no
ne-any.whl\pip\utils\logging.py", line 36, in indent_log
yield
KeyError: а

or next

C:\Program Files\IronPython 2.7>ipy -X:Frames -m ensurepip
Ignoring indexes: https://pypi.python.org/simple
Collecting setuptools
Exception:
Traceback (most recent call last):
File "c:\users\администратор\appdata\local\temp\tmppn5jtr\pip-8.1.1-py2.py3-no
ne-any.whl\pip\basecommand.py", line 209, in main
status = self.run(options, args)
File "c:\users\администратор\appdata\local\temp\tmppn5jtr\pip-8.1.1-py2.py3-no
ne-any.whl\pip\commands\install.py", line 299, in run
requirement_set.prepare_files(finder)
File "c:\users\администратор\appdata\local\temp\tmppn5jtr\pip-8.1.1-py2.py3-no
ne-any.whl\pip\req\req_set.py", line 356, in prepare_files
discovered_reqs.extend(self._prepare_file(
File "C:\Program Files\IronPython 2.7\Lib\contextlib.py", line 35, in exit
self.gen.throw(type, value, traceback)

File "c:\users\администратор\appdata\local\temp\tmppn5jtr\pip-8.1.1-py2.py3-no
ne-any.whl\pip\utils\logging.py", line 36, in indent_log
yield
KeyError: а

During installation of Ironpython "pip" was selected to be installed.
I supposed pip was not installed for ironpython, after that i tried install it from local folder:
C:\Program Files\IronPython 2.7>ipy c:\pip-8.1.1-py2.py3-none-any.whl install
can't find 'main' module in 'c:\pip-8.1.1-py2.py3-none-any.whl'

I tried different version of pip, but no success!!!

pip on python works very well, packades are easely installing, problem only with ironpython.
also, I tried different verisons of ironpython, no positiv result. Can any body halp me? Please!!!!
CMD runed as a admin
Windows 7   64 bit
IronPython version:
C:\Program Files\IronPython 2.7>ipy -V
IronPython 2.7.9 <IP_ADDRESS> on .NET 4.0.30319.42000
python version
c:>py -V
Python 3.5.2
pip verson on python
c:>py -m pip -V
pip 8.1.1 from C:\Program Files\Python35\lib\site-packages (python 3.5)
pip version on ipy
C:\Program Files\IronPython 2.7>ipy -m pip -V
Unhandled exception:
Traceback (most recent call last):
File "C:\Program Files\IronPython 2.7\Lib\runpy.py", line 182, in run_module
File "C:\Program Files\IronPython 2.7\Lib\runpy.py", line 107, in get_module
details
ImportError: No module named pip


Add Docker support

This pull request adds the necessary files to run the app using Docker and Docker Compose. It should works in any environment that runs Docker, but I just tested on Linux. Also the README.md file was updated with usage instructions in case someone using a Mac or Windows machine would like to test it.

Getting fancy!!!! I love it thanks.


Use Meshes.centroid in hilbert example and add compat

See https://github.com/JuliaGeometry/Meshes.jl/commit/f1cb2e413145bc4c3a728fefe8e46b2aa3a1804b

Thanks!


(PUP-9257) Add pp syntax check to heredoc

This adds syntax checkers for 'pp' and 'epp' to heredoc.
This is of value when sending a heredoc to a Deferred function as it is preferable to get syntax errors when compiling as opposed to when applying a catalog.
To use @(EOT:pp) for puppet, and @(EOT:epp) for EPP.

CLA signed by all contributors.


Add French translations

Merci!
Sent from my iPhone

On 21 Dec 2020, at 15:42, Franck Delache<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/pilotmoon/Scroll-Reverser/pull/105
Commit Summary
Add French translations
File Changes
A resources/fr.lproj/Localizable.strings (95)
Patch Links:
https://github.com/pilotmoon/Scroll-Reverser/pull/105.patch
https://github.com/pilotmoon/Scroll-Reverser/pull/105.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Using simulated acquisition source and sample rate = 1 Hz, slows down the application

if the sample rate is set to 1 Hz in the example 11_acquisition_simulated_memory, then the performance is severely impacted. If the sample rate of the simulated acquisition source is 10 or more, this problem goes away.

Found the bug


Cannot read property 'setConfig' of undefined

hi,
i tried to use thise card, but i have thise messagge in the ui editor....
i tried with type js and module in the main config lovelace...
what can i do ?

Hey @AngelofromTurin, just found this gem myself! I realized after playing around that you have to put the attribute name next to the entity in the key field:
Not sure if this is where your issue was, but hope it helps someone :)
key: binary_sensor.hallway_sensor_motion.**battery_level**
  - type: custom:entity-attributes-card     title: Attributes     heading_name: Entity     heading_state: Battery Level     filter:       include:         - key: binary_sensor.hallway_sensor_motion.battery_level           name: Hallway Sensor


More unit test improvements

BaseFakerTest.java > Allow callers to optionally specify a regex to match against.
UnitTest classes > Use newer unit test infrastructure where practical.

Signed-off-by: kingthorin<EMAIL_ADDRESS>

I plan to continue through this, just wanted to submit it in case: 1) Anyone hated how I'd changed things. 2) You'd know it was being worked on 😉

Codecov Report

Merging #682 (d2453f5) into main (4707012) will decrease coverage by 0.04%.
The diff coverage is n/a.

:exclamation: Current head d2453f5 differs from pull request most recent head 31caefc. Consider uploading reports for the commit 31caefc to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main     #682      +/-   ##
============================================
- Coverage     92.64%   92.61%   -0.04%
+ Complexity     2624     2610      -14
============================================
  Files           284      283       -1
  Lines          5356     5319      -37
  Branches        581      574       -7
============================================
- Hits           4962     4926      -36
  Misses          248      248
+ Partials        146      145       -1

Impacted Files
Coverage Δ

...ker/idnumbers/pt/br/IdNumberGeneratorPtBrUtil.java
92.59% <0.00%> (-3.71%)
:arrow_down:

src/main/java/net/datafaker/formats/Yaml.java

.../datafaker/transformations/sql/SqlTransformer.java
85.92% <0.00%> (+0.72%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

No longer WIP, ready for review.

I didn't get where regex is checked in new way?

I didn't get where regex is checked in new way?

Ugh, thanks. I lost it along the way in some step of the implementation/re-implementation. Fixed now.

@snuyanzin I think I've addressed both your concerns. I put the Pattern.compile inside the regex assertion, let me know if you think it should be in the of method. Checking regex string isEmpty seemed easiest. But, I guess I could try/catch on PatternSyntaxException or check empty pattern ^$ and set it null, then null check it prior to the assertion if that's preferable.

Fixed the build/test failure.


Focus minimized pdf viewer on build

If the pdf preview window is already open but not in the foreground, it is not focused after the build process is finished. Would be cool if this would work the way that the preview window comes back to the foreground after the build command is triggered.

Good idea! Will check if the feature can be implemented.

@James-Yu thanks for considering this :)
Unfortunately, the pdf viewer isn't brought into focus at all since the 0.7.0 release. Even when building a pdf for the first time. Guess something went wrong. Let me know if you need further information.

The viewer window will be brought to the front, but the atom window will maintain focus. If the default viewer position is covered by that, it will not be shown.
Any suggestions on how the bring-to-top-but-not-focus feature should work? the viewer window should not gain focus after building because that will cause trouble for those who regularly press ctrl+s

Ah, I see. Misunderstood that feature. Mhh ok, we have people who don't want to be annoyed when pressing ctrl+s and we have people who want to immediately see the result when building the document.
What about a conditional behavior: Bring it to the front when the button is pressed or the build command is fired manually but not when the build is triggered after save?

I will think of both options. The first one might be not very intuitive as it is called build instead of build and show. Though nothing confirmed.
Thanks for the suggestions!

While writing... I just noticed that invoking the preview function from command pallet or shortcut works fine while clicking the magnifier icon has no effect when the preview window is already in the background. Guess this is related and should also be consistent.

Still not completely solved. Will introduce a new setting to control this behavior.

This should satisfies the most.

I would like to point out that this issue is back for a while. When the pdf viewer window is minimized, a new build will not focus the preview window. Pressing the magnifier icon also has no effect in this case.
Maybe you can reopen @ashthespy

@exploide I can't seem to reproduce this - any more details?
My settings:
  "atom-latex":
    build_after_save: false
    focus_viewer: true
    save_on_build: true

Both the preview and build buttons focus a minimised preview window in my case (v0.8.1)

Current settings:
  "atom-latex":
    build_after_save: false
    file_ext_to_clean: "*.aux, *.bbl, *.blg, *.idx, *.ind, *.lof, *.lot, *.out, *.toc, *.acn, *.acr, *.alg, *.glg, *.glo, *.gls, *.ist, *.fls, *.log, *.fdb_latexmk, *.bcf, *.run.xml, *.synctex.gz"
    focus_viewer: true
    hide_log_if_success: true
    latexmk_param: "-synctex=1 -interaction=nonstopmode -file-line-error -pdf -shell-escape"
    save_on_build: true

Version<EMAIL_ADDRESS>with Atom 1.19.7
System: Fedora Linux with Cinnamon Desktop
Screencapture:

@exploide
Can you check if you get any errors in the dev console if you try to focus the window with either atom_latex.latex.viewer.window.focus() or atom_latex.latex.viewer.window.show()?
Unfortunately, this seems to be something system specific that I can't reproduce here (Win10/8) to debug.

atom_latex.latex.viewer.window.focus() returns undefined and nothing happens.
atom_latex.latex.viewer.window.show() also returns undefined but the viewer window comes to the front.

Seems focus() doesn't have the same behaviour across Linux and Windows platforms - will switch to show() as it 'Shows and gives focus to the window.' - what we want :-)


Update G0 vendor svds to V1.2

In progress. Some stuff was invalidated.
Also related to

#716 which seems to be present here
#695

Replaced by #947


Echinus*border being interpreted as color value causes crash

There's something wrong with the implementation of the Echinus*border setting.
It works fine as long as you have both Echinus*normal.border and Echinus*selected.border (which define colors) set in echinusrc. But as soon as you drop one of them, things break.
On my Slackware 14.2 system, the X server exits saying:
error, cannot allocate color '1'

1 is the value of Echinus*border in this case. I have also tested this on Devuan 2.0.0. The error message is just e color '1' there, for whatever reason, but the effect is exactly the same.
This error even seems to make sense. If I understand Xresources syntax right, Echinus*border is simply a way to refer to Echinus*normal.border and Echinus*normal.border at the same time because the asterisk acts as a wildcard. So, the solution is probably to rename Echinus*border.
The naming scheme for Echinus' settings should probably be revised a bit in general.

Hi, sorry for the long reply. I think your explanation is correct. Unfortunately, echinus is no longer maintained (I just added a note to README).
Thinking about it, replacing * with . in echinusrc might work, I think.


MISRA-C fixes

#9895
#9886
#9889

Codecov Report

Merging #14426 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master   #14426      +/-   ##
==========================================
+ Coverage   51.98%   51.98%   +<.01%
==========================================
  Files         308      308
  Lines       45505    45506       +1
  Branches    10543    10543
==========================================
+ Hits        23655    23656       +1
  Misses      17050    17050
  Partials     4800     4800

Impacted Files
Coverage Δ

include/atomic.h
100% <ø> (ø)
:arrow_up:

include/arch/bits_portable.h
100% <ø> (ø)
:arrow_up:

include/misc/sflist.h
72.97% <ø> (ø)
:arrow_up:

include/ring_buffer.h
87.5% <ø> (ø)
:arrow_up:

include/logging/log_msg.h
71.15% <ø> (ø)
:arrow_up:

include/logging/log_core.h
100% <ø> (ø)
:arrow_up:

kernel/mempool.c
89.47% <100%> (ø)
:arrow_up:

include/misc/util.h
50% <100%> (ø)
:arrow_up:

kernel/sched.c
84.01% <100%> (ø)
:arrow_up:

kernel/include/ksched.h
91.86% <100%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8104c6c...51f5d70. Read the comment docs.

#9895
#9886
#9889

what about those? Does it fix them? fully or partially? Please add more context and use "Fixes #" to enable auto-losing when this is merged.

#9895
#9886
#9889

what about those? Does it fix them? fully or partially? Please add more context and use "Fixes #" to enable auto-losing when this is merged.

They partially fix them. There are still violations, some of them will probably be addressed in deviations.
I'm adding the MISRA-C rule in commit message to make easier identify commits fixing MISRA-C.
Would like me to add "FIXES" tag in commit message even not fully fixing the issue ?

@galak done :)

@galak @nashif I got a timeout in our CI, can one of you trigger a new build to see if it happens again ?


debug - support async callstacks with nodejs

In chrome and node dev tools you enable async callstacks which means calls like setTimeout are not without parent but it shows where setTimeout was invoked when debugging its callback function. Pretty handy

The v8 debugger protocol does not provide enough information for doing this. So this will require more code injection.

Hijacking this issue for the async callstack exploration.
Async callstacks show the origin of an asynchronous call. For example, if the debugger pauses in a then handler on a promise, the async callstack will show the stack that caused the promise to be resolved. Or if the debugger is paused in a setTimeout handler, it will show the stack that lead setTimeout to be called.
In F12 and Chrome Devtools, async callstacks can be enabled or disabled with a button next to the callstack. In the inspector protocol, we use Debugger.setAsyncCallStackDepth to set the number of async calls to trace back. This could be incredibly large, like if a timeout handler calls setTimeout on each call. Chrome Devtools uses 4.
UI
In Edge's F12, async calls are shown in collapsible tree sections

In Chrome Devtools, async sections are demarcated by a non-clickable label row with a description of the async call.

We will get this description too via the inspector protocol.
Visual Studio is similar - it shows an extra row that says [Async Call]

For VS Code, if we show the async frames and include their info in the existing callstack, it might look like this:

But there are some downsides to this, like you can't tell how many different Promise.resolve calls are in that stack.
Alternately, we could allow a debug adapter to add a non-clickable frame or even collapsible sections like F12.

We either need to

Make async frames a first-class citizen in the debug protocol
Build on the presentationHint property introduced in 1.9 to indicate a 'label' row that doesn't try to open a file when you click on it
Or just change the way VS Code interprets existing frames, and don't complain if a frame omits the 'source' property

Clicking an async call
Async frames are not 'live' frames - we can't get their locals or evaluate code in their context. We only have their function names and locations. So when clicking on a frame, we would show the line in the editor, but show an empty variables window. So it needs to be obvious that a frame is an async frame.
FYI @weinand @isidorn

@roblourens great analysis!
Following the "Do The Simplest Thing That Could Possibly Work" principle I suggest that we proceed along the lines of @roblourens bullets from above:

we use the Chrome Devtools approach with non-clickable labels as separators
we enable this feature by default for node2 and initially provide no nice UI to turn if off (because we believe that it will be always useful; but maybe we need a setting for it)
we will not promote async frames to become first-class citizen in the DAP
we surface the label frames and async frames as stack frames that have no source. I'm pretty sure that this is already supported. Without source clicking them doesn't do anything.
we use the presentationHint value deemphasize to deemphasize the label frames. If needed we could introduce a new presentationHint value label which results in a centered, deemphasized look.
if an async frame is selected the DA has to make sure that scope, variables, and evaluate requests (which use the async frame as a parameter) are returning empty results (or a warning).

Sounds good. I would add a launch config option to disable this, since it can always be enabled/disabled in other devtools (I'm not totally sure why people would disable it, maybe they just want to eliminate noise).
I was trying to return frames with no source, but was getting errors when I clicked on them. If it's supposed to work, I'll look at it again or file an issue.
I'm not sure I want to 'deemphasize' them, since it may be user code. And there may be skipped async frames, and I don't want to eliminate the contrast between async user code and skipped async code. But it needs to be obvious that they're different, so maybe I will.

Yep, launch config option sounds good to me.
Yes, please file a bug for the source-less frames.
I only meant to 'deemphasize' the label frames (which are basically "headers"), but not the async frames. In Chrome Devtools the label frames look 'deemphasized' as well (they are grey).

Someone filed https://github.com/Microsoft/vscode/issues/20622 which is what I was seeing.

There is nothing to test in this milestone because it was only an exploration.

Reopening for implementing this in March

@roblourens I've added an optional presentationHint attribute to type StackFrame.
The only supported value for now is label.
Available in<EMAIL_ADDRESS>

Implemented


Fixed broken shields and links

I fixed the links and removed the logo (as there isn't one yet).

I will re-open this in a second


fix: disable cypress video capture for github check workflow

Problem

Solution

Additional Notes

Links
Ticket

GitHub issue:
Other links
Verification
Manual tests

Automated tests

[ ] Unit tests added/updated
[ ] E2E tests added/updated
[ ] N/A - (provide a reason)
[ ] deferred - (provide GitHub issue for tracking)

Housekeeping

[ ] No non-essential console logs
[ ] All new files contain license notice

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #1056 (ddb76d3) into main (e9d0beb) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##             main    #1056   +/-   ##
=======================================
  Coverage   93.84%   93.84%
=======================================
  Files         124      124
  Lines        5797     5797
  Branches     1752     1752
=======================================
  Hits         5440     5440
  Misses        339      339
  Partials       18       18

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e9d0beb...ddb76d3. Read the comment docs.


Profile Sync

I have dozens of profiles depending on the customer I am supporting. Can these profiles also get synced?
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1fa7eda4-6e4c-c2c8-a29a-ef2eead7f04f
Version Independent ID: 414db256-c14b-ca11-b2a7-835aa9c9e041
Content: Configure Microsoft Edge enterprise sync
Content Source: edgeenterprise/microsoft-edge-enterprise-sync.md
Product: microsoft-edge
GitHub Login: @dan-wesley
Microsoft Alias: scottbo

@makdaddy8888 , I have Microsoft personal account, whenever  I sign in new device profiles, favourites and passwordsare synced automatically across the devices until you sync is disabled in GPO

@makdaddy8888 If you are still having an issue with sync, Please reach out to support   https://microsoftedgesupport.microsoft.com/hc/en-us  They should be able to gather logs and help investigate your specific case.   Thanks!