└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.053874 DEBUG ÷128 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.054454 DEBUG ÷128 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.055043 DEBUG ÷64 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.055371 DEBUG ÷64 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.055707 DEBUG ÷64 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056035 DEBUG ÷64 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056371 DEBUG ÷32 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056573 DEBUG ÷32 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056776 DEBUG ÷32 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056978 DEBUG ÷32 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057181 DEBUG ÷16 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057321 DEBUG ÷16 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057461 DEBUG ÷16 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057601 DEBUG ÷16 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057741 DEBUG ÷8 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057851 DEBUG ÷8 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057961 DEBUG ÷8 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058070 DEBUG ÷8 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058180 DEBUG ÷4 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058290 DEBUG ÷4 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058399 DEBUG ÷4 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058509 DEBUG ÷4 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058618 INFO  (4/6) running `mosi_simplex_loopback_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.058643 DEBUG ÷256 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.059724 DEBUG ÷256 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.060828 DEBUG ÷256 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.061910 DEBUG ÷256 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.063014 DEBUG ÷128 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.063603 DEBUG ÷128 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.064192 DEBUG ÷128 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.064781 DEBUG ÷128 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.065371 DEBUG ÷64 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.065709 DEBUG ÷64 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066046 DEBUG ÷64 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066384 DEBUG ÷64 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066721 DEBUG ÷32 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066926 DEBUG ÷32 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067132 DEBUG ÷32 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067337 DEBUG ÷32 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067544 DEBUG ÷16 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067683 DEBUG ÷16 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067831 DEBUG ÷16 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067971 DEBUG ÷16 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068118 DEBUG ÷8 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068230 DEBUG ÷8 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068342 DEBUG ÷8 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068453 DEBUG ÷8 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068565 DEBUG ÷4 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068671 DEBUG ÷4 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068777 DEBUG ÷4 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068882 DEBUG ÷4 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068988 INFO  (5/6) running `miso_simplex_loopback`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.069012 DEBUG ÷256 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.070136 DEBUG ÷256 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.071333 DEBUG ÷256 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.072457 DEBUG ÷256 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.073654 DEBUG ÷128 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.074297 DEBUG ÷128 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.074980 DEBUG ÷128 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.075622 DEBUG ÷128 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.076306 DEBUG ÷64 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.076710 DEBUG ÷64 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.077134 DEBUG ÷64 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.077538 DEBUG ÷64 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.077963 DEBUG ÷32 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.078250 DEBUG ÷32 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.078542 DEBUG ÷32 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.078829 DEBUG ÷32 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079121 DEBUG ÷16 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079350 DEBUG ÷16 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079580 DEBUG ÷16 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079810 DEBUG ÷16 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080039 DEBUG ÷8 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080243 DEBUG ÷8 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080446 DEBUG ÷8 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080649 DEBUG ÷8 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080853 DEBUG ÷4 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081032 DEBUG ÷4 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081211 DEBUG ÷4 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081391 DEBUG ÷4 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081570 INFO  (6/6) running `miso_simplex_loopback_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.081593 DEBUG ÷256 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.082702 DEBUG ÷256 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.083884 DEBUG ÷256 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.084993 DEBUG ÷256 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.086175 DEBUG ÷128 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.086803 DEBUG ÷128 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.087471 DEBUG ÷128 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.088098 DEBUG ÷128 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.088766 DEBUG ÷64 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.089153 DEBUG ÷64 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.089564 DEBUG ÷64 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.089951 DEBUG ÷64 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.090361 DEBUG ÷32 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.090632 DEBUG ÷32 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.090910 DEBUG ÷32 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091180 DEBUG ÷32 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091458 DEBUG ÷16 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091672 DEBUG ÷16 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091886 DEBUG ÷16 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092099 DEBUG ÷16 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092313 DEBUG ÷8 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092501 DEBUG ÷8 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092688 DEBUG ÷8 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092876 DEBUG ÷8 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.093063 DEBUG ÷4 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.093226 DEBUG ÷4 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.093390 DEBUG ÷4 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.131486 DEBUG ÷4 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.131650 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p i2c-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling i2c-testsuite v0.1.0 (/tmp/tmpzj3e_9su/i2c-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.48s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-35c6406695f1fa7c)
(HOST) INFO  flashing program (21.38 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
 INFO  (1/2) running `sht31_measurement`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:22
 WARN  A SHT31 sensor must be connected to the board on pins B8 (SCL) & B7 (SDA) for this test to work
└─ test::tests::sht31_measurement @ tests/test.rs:81
 ERROR I2C error: Nack
└─ test::tests::sht31_measurement @ tests/test.rs:88
 INFO  (2/2) running `loopback`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:22
 WARN  I2C1 pins B8 (SCL) and B7 (SDA) must be connected to I2C pins A12 (SCL) and A11 (SDA) for this test to pass
└─ test::tests::loopback @ tests/test.rs:94
 DEBUG I2C2 ISR=0xEE8009
└─ test::__cortex_m_rt_I2C2_EV @ tests/test.rs:114
 DEBUG I2C2 ISR=0xEF800C
└─ test::__cortex_m_rt_I2C2_EV @ tests/test.rs:114
 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:22
────────────────────────────────────────────────────────────────────────────────
(HOST) INFO  device halted without error

Output from: cargo test -p lptim-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling lptim-testsuite v0.1.0 (/tmp/tmpzj3e_9su/lptim-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.42s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-7873127432e45784)
(HOST) INFO  flashing program (12.37 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000009 INFO  (1/2) running `oneshot`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:25
0.000105 DEBUG 1317404 < 1317504 < 1317604
└─ test::tests::oneshot @ tests/test.rs:96
0.000141 INFO  (2/2) running `oneshot_external_trigger`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:25
0.000164 WARN  Pin B7 must be connected to A11 for this test to pass
└─ test::tests::oneshot_external_trigger @ tests/test.rs:102
0.000237 DEBUG 7466 < 7566 < 7666
└─ test::tests::oneshot_external_trigger @ tests/test.rs:137
0.000273 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:25
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p aes-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling aes-testsuite v0.1.0 (/tmp/tmpzj3e_9su/aes-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.35s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-97a41982d0611d1c)
(HOST) INFO  flashing program (13.59 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000008 INFO  (1/4) running `encrypt_ecb`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:58
0.000098 INFO  Average cycles per encrypt: 235
└─ test::tests::encrypt_ecb @ tests/test.rs:89
0.000122 INFO  (2/4) running `encrypt_ecb_inplace`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:58
0.000208 INFO  Average cycles per encrypt: 208
└─ test::tests::encrypt_ecb_inplace @ tests/test.rs:107
0.000231 INFO  (3/4) running `decrypt_ecb`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:58
0.000326 INFO  Average cycles per decrypt: 277
└─ test::tests::decrypt_ecb @ tests/test.rs:125
0.000349 INFO  (4/4) running `decrypt_ecb_inplace`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:58
0.000445 INFO  Average cycles per decrypt: 268
└─ test::tests::decrypt_ecb_inplace @ tests/test.rs:143
0.000468 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:58
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p rng-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling ppv-lite86 v0.2.10
   Compiling rand_chacha v0.3.1
   Compiling rng-testsuite v0.1.0 (/tmp/tmpzj3e_9su/rng-testsuite)
    Finished test [optimized + debuginfo] target(s) in 2.51s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-13087e86385117cf)
(HOST) INFO  flashing program (36.87 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
 INFO  (1/2) running `cha_cha`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:31
 WARN  Test results are only valid for release mode
└─ test::tests::cha_cha @ tests/test.rs:47
 INFO  ChaCha20: 2817.385
└─ test::tests::cha_cha @ tests/test.rs:91
 INFO  ChaCha12: 1738.115
└─ test::tests::cha_cha @ tests/test.rs:92
 INFO  ChaCha8: 1199.65
└─ test::tests::cha_cha @ tests/test.rs:93
 INFO  HW: 416.34
└─ test::tests::cha_cha @ tests/test.rs:94
 INFO  (2/2) running `random_enough_for_me`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:31
 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:31
────────────────────────────────────────────────────────────────────────────────
(HOST) INFO  device halted without error

Output from: cargo test -p rtc-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling rtc-testsuite v0.1.0 (/tmp/tmpzj3e_9su/rtc-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.40s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-d7a232d7b674b0ac)
(HOST) INFO  flashing program (17.86 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000010 INFO  (1/3) running `test_set_date_time_lse`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:93
0.160040 TRACE four_rtc_clk_cycles=5856
└─ test::test_set_date_time_with_clk @ tests/test.rs:39
0.170330 DEBUG Timestamp before<PHONE_NUMBER>000 after<PHONE_NUMBER>007 Δ 7
└─ test::test_set_date_time_with_clk @ tests/test.rs:84
0.170366 INFO  (2/3) running `test_set_date_time_lsi`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:93
0.170714 TRACE four_rtc_clk_cycles=6000
└─ test::test_set_date_time_with_clk @ tests/test.rs:39
0.181010 DEBUG Timestamp before<PHONE_NUMBER>000 after<PHONE_NUMBER>009 Δ 9
└─ test::test_set_date_time_with_clk @ tests/test.rs:84
0.181046 INFO  (3/3) running `test_set_date_time_hse`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:93
0.181274 TRACE four_rtc_clk_cycles=192
└─ test::test_set_date_time_with_clk @ tests/test.rs:39
0.191353 DEBUG Timestamp before<PHONE_NUMBER>000 after<PHONE_NUMBER>010 Δ 10
└─ test::test_set_date_time_with_clk @ tests/test.rs:84
0.191389 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:93
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p rcc-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling rcc-testsuite v0.1.0 (/tmp/tmpzj3e_9su/rcc-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.32s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-5ecfbd75f04d5664)
(HOST) INFO  flashing program (11.26 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
 INFO  (1/2) running `sysclk_switching`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:92
 INFO  from Hsi to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  (2/2) running `enter_exit_lprun`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:92
 INFO  Range200k
└─ test::tests::enter_exit_lprun @ tests/test.rs:136
 INFO  Range400k
└─ test::tests::enter_exit_lprun @ tests/test.rs:136
 INFO  Range800k
└─ test::tests::enter_exit_lprun @ tests/test.rs:136
 INFO  Range1M
└─ test::tests::enter_exit_lprun @ tests/test.rs:136
 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:92
────────────────────────────────────────────────────────────────────────────────
(HOST) INFO  device halted without error

Output from: cargo test -p adc-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling adc-testsuite v0.1.0 (/tmp/tmpzj3e_9su/adc-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.58s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-2c673363e7d2e463)
(HOST) INFO  flashing program (20.37 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000007 INFO  (1/10) running `enable`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000034 INFO  Enable cycles: 137 CPU 34 ADC
└─ test::tests::enable @ tests/test.rs:80
0.000067 INFO  Disable cycles: 105 CPU 26 ADC
└─ test::tests::enable @ tests/test.rs:99
0.000099 INFO  (2/10) running `tsen_enable`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000375 INFO  (3/10) running `vbat_enable`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000402 INFO  (4/10) running `vref_enable`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000428 INFO  (5/10) running `vref`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000536 INFO  vref_cal: 1508
└─ test::tests::vref @ tests/test.rs:187
0.000557 INFO  vref pre-calibration: 1529 Δ 21
└─ test::tests::vref @ tests/test.rs:190
0.000585 INFO  vref post-calibration: 1499 Δ 9
└─ test::tests::vref @ tests/test.rs:191
0.000613 INFO  (6/10) running `test_hsi16`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000703 INFO  vref: 1499 Δ 9
└─ test::tests::test_hsi16 @ tests/test.rs:216
0.000737 INFO  (7/10) running `temperature`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000948 INFO  Temperature: 31 °C
└─ test::tests::temperature @ tests/test.rs:235
0.000970 INFO  (8/10) running `vbat`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.001056 INFO  VBAT=1373 Δ 8
└─ test::validate_vbat @ tests/test.rs:31
0.001085 INFO  (9/10) running `vbat_advanced`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.001147 INFO  Calibration cycles: CPU 470 ADC 117
└─ test::tests::vbat_advanced @ tests/test.rs:269
0.001178 INFO  Enable cycles: CPU 120 ADC 30
└─ test::tests::vbat_advanced @ tests/test.rs:280
0.001207 INFO  Channel configuration cycles: CPU 15 ADC 3
└─ test::tests::vbat_advanced @ tests/test.rs:292
0.001252 INFO  Sample cycles: CPU 717 ADC 179
└─ test::tests::vbat_advanced @ tests/test.rs:305
0.001281 INFO  VBAT=1373 Δ 8
└─ test::validate_vbat @ tests/test.rs:31
0.001309 INFO  VBAT=1373 Δ 8
└─ test::validate_vbat @ tests/test.rs:31
0.001338 INFO  (10/10) running `stop_conversion`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.001367 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p subghz-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on build directory
    Finished test [optimized + debuginfo] target(s) in 1.04s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-27aee399b0aa55ca)
(HOST) INFO  flashing program (25.71 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000007 INFO  (1/5) running `buffer_io`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
0.000403 INFO  Cycles 255B: 17857
└─ test::tests::buffer_io @ tests/test.rs:332
0.000512 INFO  Cycles 0B: 1187
└─ test::tests::buffer_io @ tests/test.rs:341
0.000534 INFO  (2/5) running `buffer_io_no_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
0.001957 INFO  Cycles 255B: 67125
└─ test::tests::buffer_io_no_dma @ tests/test.rs:354
0.002067 INFO  Cycles 0B: 1248
└─ test::tests::buffer_io_no_dma @ tests/test.rs:363
0.002088 INFO  (3/5) running `sleep_enter_exit`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
0.004186 INFO  74813 cycles to wake radio
└─ test::tests::sleep_enter_exit @ tests/test.rs:378
0.004224 INFO  (4/5) running `fsk_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
0.017196 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:185
0.017239 DEBUG RX with timeout 201 ms
└─ test::ping_pong @ tests/test.rs:196
0.248265 INFO  RX timeout 230 ms Δ 29 ms
└─ test::ping_pong @ tests/test.rs:207
0.267173 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.267186 INFO  Attempt: 1/100
└─ test::ping_pong @ tests/test.rs:185
0.267311 DEBUG RX with timeout 120 ms
└─ test::ping_pong @ tests/test.rs:196
0.275459 INFO  RX done
└─ test::ping_pong @ tests/test.rs:219
0.275523 INFO  received PONG
└─ test::ping_pong @ tests/test.rs:243
0.275538 INFO  (5/5) running `lora_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
0.288631 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:185
0.288674 DEBUG RX with timeout 116 ms
└─ test::ping_pong @ tests/test.rs:196
0.426951 INFO  RX timeout 138 ms Δ 22 ms
└─ test::ping_pong @ tests/test.rs:207
0.501876 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.501890 INFO  Attempt: 1/100
└─ test::ping_pong @ tests/test.rs:185
0.502014 DEBUG RX with timeout 295 ms
└─ test::ping_pong @ tests/test.rs:196
0.567121 INFO  RX done
└─ test::ping_pong @ tests/test.rs:219
0.567185 INFO  received PONG
└─ test::ping_pong @ tests/test.rs:243
0.567201 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p subghz-testsuite --target thumbv7em-none-eabi -- --probe 0034001A5553500B20393256
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
   Compiling static_assertions v1.1.0
   Compiling nucleo-wl55jc-bsp v0.1.0-alpha.0 (/tmp/tmpzj3e_9su/nucleo-wl55jc-bsp)
   Compiling subghz-testsuite v0.1.0 (/tmp/tmpzj3e_9su/subghz-testsuite)
    Finished test [optimized + debuginfo] target(s) in 1.04s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-27aee399b0aa55ca)
(HOST) INFO  flashing program (25.71 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000007 INFO  (1/5) running `buffer_io`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
0.000403 INFO  Cycles 255B: 17857
└─ test::tests::buffer_io @ tests/test.rs:332
0.000512 INFO  Cycles 0B: 1187
└─ test::tests::buffer_io @ tests/test.rs:341
0.000534 INFO  (2/5) running `buffer_io_no_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
0.001957 INFO  Cycles 255B: 67125
└─ test::tests::buffer_io_no_dma @ tests/test.rs:354
0.002067 INFO  Cycles 0B: 1248
└─ test::tests::buffer_io_no_dma @ tests/test.rs:363
0.002088 INFO  (3/5) running `sleep_enter_exit`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
0.004169 INFO  74018 cycles to wake radio
└─ test::tests::sleep_enter_exit @ tests/test.rs:378
0.004208 INFO  (4/5) running `fsk_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
0.017528 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:185
0.017571 DEBUG RX with timeout 182 ms
└─ test::ping_pong @ tests/test.rs:196
0.234469 INFO  RX timeout 216 ms Δ 34 ms
└─ test::ping_pong @ tests/test.rs:207
0.253755 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.253768 INFO  Attempt: 1/100
└─ test::ping_pong @ tests/test.rs:185
0.253892 DEBUG RX with timeout 54 ms
└─ test::ping_pong @ tests/test.rs:196
0.267425 INFO  RX done
└─ test::ping_pong @ tests/test.rs:219
0.267489 INFO  received PING
└─ test::ping_pong @ tests/test.rs:232
0.275366 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.283231 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.291096 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.298962 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.306827 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.314693 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.322559 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.330426 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.338292 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.346158 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.346173 INFO  (5/5) running `lora_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
0.359624 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:185
0.359667 DEBUG RX with timeout 273 ms
└─ test::ping_pong @ tests/test.rs:196
0.503185 INFO  RX done
└─ test::ping_pong @ tests/test.rs:219
0.503249 INFO  received PING
└─ test::ping_pong @ tests/test.rs:232
0.567260 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.631262 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.695276 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.759288 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.823298 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.887313 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.951334 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
1.015365 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
1.079406 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
1.143447 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
1.143462 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:274
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error


react support

I am trying the react support in babel with browserify & watchify only i am getting an error:
Gulpfile
https://gist.github.com/Mech7/39998f130bc0917fad39
[21:30:53] Browserify Error
./src/mediabank.js:1
var profile =

              ^

On some very simple test code (taken from the page):
var profile =

{[user.firstName, user.lastName].join(' ')}

;

This error is being thrown by one of the previous gulp plugins. Please use the gitter room for support and questions, thanks!


Install is now a separate download it appears

On this page: https://learn.microsoft.com/en-us/sql/machine-learning/install/sql-machine-learning-services-windows-install?view=sql-server-ver15&viewFallbackFrom=sql-server-ver16
The steps do not appear valid on the systems I am testing. During the installation, Machine Learning Services now pops to a "Enter Location" dialog with two non-clickable links. On copying and hitting those links, you're presented with a CAB file that must be extracted.
Even after these steps, MLS is non-functional.

@BuckWoody -- Buck, thank you for your clear feedback.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@WilliamDAssafMSFT -- William, please look into this issue.


Retrieving a subcolletion

How retrieve a subcollection? The example just show a simple query.

I believe it is simple, the firestore documentation shows that you can search for sub-collections in this way (example):
Firestore.instance.collection('users').doc(Firestore.instance.currentUser.uid).collection('orders').orderBy('id', descending: true);

Thank you. I've already tried, but I need to retrieve all users documents, not just current user´s documents.

If you are talking about Collection group queries, then the query goes like
Firestore.instance.collectionGroup('orders').getDocuments()


Rather than having "backend:9000" buried inside the frontend codebase, let's keep networking details like that in environment variables/files.

I moved towards having environment variables for a bit but now I've moved away again. Turns out NextJS environment variables need to be specified at build time. I guess I should find an alternative to the regular environment variables that can be checked at runtime.

I'm currently working on this issue in the backend-address-variable branch, and hopefully I'll be done soon.
Should I also tell the backend what port to listen on?

Done on the frontend side, same for the backend next?

Done.


Pressing the spacebar in 'install packages' tab scrolls the panel down

Prerequisites

[y] Can you reproduce the problem in safe mode?
[y] Are you running the latest version of Atom?
[y] Did you check the debugging guide?
[y] Did you check the FAQs on Discuss?
[y] Are you reporting to the correct repository?
[y] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.
Description
[Description of the bug or feature]
Steps to Reproduce

Open atom
Go to preferences > install
Type 'foo bar'
See screen scroll on the space, instead of staying at the top

Expected behavior: [What you expected to happen]
Stay at the top
Actual behavior: [What actually happened]
Scroll
Versions
You can get this information from executing atom --version and apm --version at the command line. Also, please include the OS and what version of the OS you're running.
Mac
 2016-07-11 13:10:58 ☆  |2.3.0| declerk in ~/workspace/http_sim
±  |master ✓| → atom --version
Atom    : 1.8.0
Electron: 0.36.8
Chrome  : 47.0.2526.110
Node    : 5.1.1

 2016-07-11 13:57:32 ☆  |2.3.0| declerk in ~/workspace/http_sim
±  |master U:2 ✗| → apm --version
apm  1.9.2
npm  2.13.3
node 0.10.40
python 2.7.10
git 2.7.4

Same for me... (OS X 10.10)
Atom    : 1.8.0
Electron: 0.36.8
Chrome  : 47.0.2526.110
Node    : 5.1.1

Same bug on Atom Beta 1.9.0 on Ubuntu 16.04:
$ atom-beta -v
Atom    : 1.9.0-beta0
Electron: 0.37.8
Chrome  : 49.0.2623.75
Node    : 5.10.0

This is a duplicate of https://github.com/atom/settings-view/issues/767. You may want to subscribe there for updates.

Also, please do follow the template and check to ensure that you're posting an Issue to the correct repository.


Update live database schema

Before the release of FREME 0.6 we have to update the dababase schema of pipelines and sparql filters according to https://github.com/freme-project/FREMECommon/issues/20
Holds for datasets also

Please check the list of database changes from https://github.com/freme-project/FREMECommon/issues/20#issuecomment-205897368 and see if I need to update something else.

I have checked the list, it is still correct. Furthermore, the empty tables dataset and dataset_simple can be removed.

done during yesterdays release


arrow function parentheses

Lint and fix arrow function parentheses, omitting them for single-argument functions.

This has been bugging me forever! Wish I'd remembered to include it in pull request #181 alongside the original linting fixes.


Class Name Renaming #19513

Fixes #19513

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: alberto-guerrero sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@alberto-guerrero  thanks for the PR


Compiled size too big

Is it possible to lightweight compile this library ? I'm 100bytes short in my project :)

See this thread for details #8


Add additional filter for kata progress

The current progress filter on katas only provides the following three options:

All
Katas I have not trained on
Katas I have not completed

However, this hinders searching for duplicates. The negations of the latter filters (e.g. katas I have completed) would make the search a lot easier.

Great suggestion, I have thought about this before.  I understand why Codewars might not have this filter option (as most users just want to complete more Kata to gain rank/honor) but adding this filter option could greatly improve the Kata approval process for Moderators.

Filter Katas not yet completed

https://codewars.ideas.aha.io/ideas/CW-I-90

Filter Katas not yet trained on

@javatlacati The joy of #226.

Yup. But since @jhoffner started closing my github issues that were enhacement proposals since they had to be on the ideas site I wanted to help and because who doesn't love to have thousands of notifications with duplicity :smile:

Yeah BTW for clarification why we have the enhancement tag in Github. If the enhancement is for functionality that seems incomplete or broken, but is working as designed, and is a small feature, it can make sense here as an enhancement. However there has been an explosion of issues being logged recently so I was hoping to redirect any "wouldnt it be cool if..." type enhancements out of this list, since A: aha is a better place for tracking votes, B: realistically between all of the bugs, small enhancements and a few important strategic initiatives that we have, I don't have any bandwidth for adding new complex features and this list is starting to get hard to manage. I can only focus on quick wins right now.

@bkaestner The kata search seems to have a "Katas I have completed" option now.  Can this ticket be closed?


Add Functionality for Background Blur and Custom Backgrounds for Calling

What feature are you requesting?
What would be the benefit of adding this feature?
What solution would be ideal for you?
What alternatives have you considered?
Is there any additional information for your request?
Attach screenshots or images add detail to your request:

Refer to this blog :- https://techcommunity.microsoft.com/t5/azure-communication-services/azure-communication-services-february-2023-feature-updates/ba-p/3737486

@grathore1999  we are currently in development for this feature. It will be slated for public preview sometime after March.
I am curious are there any specific features or use cases around this feature you would like to share with us? We often like to hear about how customers want to use or plan to use upcoming features we can ensure that what we are building can work for those use cases as well.

Thanks @alkwa-msft  It was helpful to have this information shared with us. Currently, we want the same functionality as I mentioned above, and our new feature request is to be able to share files between ACS Call and Microsoft Teams.

@grathore1999 Sharing files between an ACS Call and Microsoft Teams are also in active development at this time.

(response on blur backgrounds on mobile web platforms)
https://github.com/Azure/communication-ui-library/issues/3033#issuecomment-1538484810

Closing this issue because Background Blur and Custom Backgrounds is now supported in [1.8.0-beta.1]<EMAIL_ADDRESS>and 1.8.0. To learn more reference our storybook documents here


How to set ColResize full width?

Hi,
Thanks for a great plugin. I'm unable to set 100% width on the table here is the issue https://codepen.io/yurenlimbu/pen/YgwemY. I want to create full width as parent div. How can I set this?

@yurenlimbu the codepen link has a table with width 100% and the table is showing as filling the entire width of the window. What is the exact issue?

Inactivity


Allow adding sub bullet points to each time item and display on planner

Hello,
would it be possible to accomodate something along the lines of this:
- [ ] 12:00 BE29 Assignment
	- [ ] Finish Introduction
	- [ ] Prep M&M
	- [ ] finish LR
- [ ] 13:00 Break
	- [ ] eat something
- [ ] 14:15 Break End
- [ ] 14:20 BE29 Assignment
	- [ ] finish LR, fix gaps
	- [ ] start manuscript prep
- [ ] 18:40 stop working
	- [ ] make food
- [ ] 20:10 Meeting Person X.
	- [ ] Topic 1
	- [ ] Topic 2
	- [ ] Topic 3
- [ ] 22:00 go sleep

to be used, where subitems indented further than a timeslot (so 1st level indentation and beyond) are considered "details" for the previous task, and then are printed in the Dayplanner Graphic?
Currently, you would have to but it all on a single line. That is not only overwhelmingly difficult to work with because it makes modification much harder, but additionally there is no method of forcing a linebreak in what the planner displays. So you either make a rather ugly overview on the  planner which is unwieldy to work with itself (and doesn't really actually allow breaking apart tasks to begin with), or you give up and resort to a short task description and everytime go back to your dailynote to see the non-rendered subtasks.
And neither is really a good solution imo.
Would this in principle be implementable?
Thank you.
Sincerely,
~Gw

Hello, @Gewerd-Strauss, please update to 0.8.0 and re-check.


Add new initial conditions, make a Julia package, and continuous integration for tests

Initial Conditions

Instead of passing n to ttv_elements!, pass a hierarchy vector H.
For example, a system with a central star and 2 planets, H = [3,1,1]. 3 bodies in the system, followed by the number of binaries on a given level. In this case, 2 nested Keplerians. See setup_hierarchy.jl for more info.
More updates at a lower level -- not relevant to the user in current state. See InitialConditions.jl and init_nbody.jl
Moved old implementations to *_old.jl files.

Package

Created NbodyGradient.jl, Project.toml, and Manifest.toml files.

Continuous Integration

Added basic travis-ci script. Runs tests vs latest Julia version and v0.7, but allows v0.7 to fail.

Initial Conditions

Added back in the ability to pass the number of bodies n, rather than H. This assumes the desired hierarchy is fully nested (which was the case in the original code).
Now handles more hierarchy cases. Notably, a binary consisting of two fully nested Keplerians.

PreAllocArrays

Initial construction of a 'Pre-Allocated Array' type (PreAllocArrays). This structure will be passed through the integrator, in lieu of defining global constants, containing arrays that are reused throughout.


refactor/filter-schema

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@c2a431d). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #7   +/-   ##
=======================================
  Coverage        ?   94.39%
=======================================
  Files           ?       10
  Lines           ?      107
  Branches        ?       18
=======================================
  Hits            ?      101
  Misses          ?        6
  Partials        ?        0

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 c2a431d...f3e6a0c. Read the comment docs.


fix: Table 'yunionlogger.users_cache_tbl' doesn't exist

这个 PR 实现什么功能/修复什么问题:
修正：Table 'yunionlogger.users_cache_tbl' doesn't exist”
是否需要 backport 到之前的 release 分支:

release/2.10.0
release/2.11
release/2.12

/area log

Codecov Report

Merging #2952 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2952   +/-   ##
======================================
  Coverage    7.06%   7.06%
======================================
  Files         477     477
  Lines       76430   76430
======================================
  Hits         5396    5396
  Misses      70582   70582
  Partials      452     452

Flag
Coverage Δ

#aFlag
7.06% <ø> (ø)
: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 2f154f4...3c41779. Read the comment docs.

/area logger

/approve
/lgtm


Empty cell after hyperlink creation

Description

The function xlsx.SetCellHyperLink create link without display text - the cell is empty but link is created.
It can be fixed by additionaly use xlsx.SetCellStr function
Nevertheless, it look likes as imperfection because the struct xlsxHyperlink has Display field for this purpose, but xlsx.SetCellHyperLink does not use it
type xlsxHyperlink struct {
	Ref      string `xml:"ref,attr"`
	Location string `xml:"location,attr,omitempty"`
	Display  string `xml:"display,attr,omitempty"`
	RID      string `xml:"http://schemas.openxmlformats.org/officeDocument/2006/relationships id,attr,omitempty"`
}

Steps to reproduce the issue:

using xlsx.SetCellHyperLink

Describe the results you received:
    <hyperlinks>
        <hyperlink ref="A1" location="Sheet1!A1"></hyperlink>
    </hyperlinks>

Describe the results you expected:
If we are using MS Excel:
    <hyperlinks>
        <hyperlink ref="A1" location="Sheet1!A1" display="Sheet1"/>
    </hyperlinks>

Output of go version:
go version go1.10 windows/amd64

Thanks for your issue. The function SetCellHyperLink() doesn't support set display attribute of hyperlinks currently. We need to set cell value by function SetCellValue().


Does it support ssr?

I tried to run the project using, npm run build:ssr:prod, and when I checked the source of the page I couldn't find the content in the source, so does this project support srr, and how to run it?
Thanks

Hi borjapazr
This is exactly what I meant, thank you for the detailed answer, I checked it from the curl and it's working fine as expected.


teb generated trajectory has positive z value

Hi I might be missing some concepts here, but for 2D car like robot why is the output trajectory has pose with non-zero z values? Thank you

Could you update your question and tell which topic you're referring to by saying "output trajectory". And maybe copy rostopic echo message as example?

Are you referring to the visualization markers for the poses?
https://github.com/rst-tu-dortmund/teb_local_planner/blob/melodic-devel/src/visualization.cpp#L111
More of a feature to visualize time. Can be set to 0 to obtain a flat marker topic.


Test

Summary:
Briefly describe the changes made in this PR.
Issue Reference(s):
Fixes #... (Replace "..." with the issue number)
Build & Testing:

[ ] I ran cargo test successfully.
[ ] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[ ] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[ ] I have performed a self-review of my code.
[ ] PR follows the naming convention of <type>(<optional scope>): <title>

Summary by CodeRabbit

Improvements

Enhanced response headers handling to improve security and performance.

@coderabbiai review

@coderabbitai The aim is The code in request_handler.rs has a lot of duplicate patterns and function calls. Clean that up and earn some bounty. This issue is open for everyone to attempt and only the PR with the highest quality will get merged :)

@coderabbitai Help me with implementing the changes that aligns with issue requirements

@coderabbitai Commit this changes into the file after all changes above integrated

@coderabbitai Is update headers function is fully there in new changes of what old code had? Or missing any  functionality of it?

@coderabbitai Is this the  aim is The code in request_handler.rs has a lot of duplicate patterns and function calls. Clean that up and earn some bounty.  only the PR with the highest quality will get merged :)
Is above issue requirements is satisfied by this PR?PLEASE REVIEW

@coderabbitai Is this done in changes: The refactored code aims to consolidate these duplicate patterns and function calls. Here are the key changes:
Consolidate Header Handling:
Created a utility function set_common_headers to handle common header settings.
Used this function in update_response_headers, handle_origin_tailcall, and handle_request_with_cors.
Combine GraphQL Request Handling:
Created a common function handle_graphql_request to handle GraphQL requests and update response headers.
Used this function in graphql_request and handle_rest_apis.
Refactor Context Creation:
Refactored the context creation functions to share common logic using create_common_context.            please check in my commit 59b6e67

@coderabbitai handle_graphql_request  doesn;t looks present in code xhanges

@coderabbitai How's this part of handle_rest_apis"  let graphql_request = p_request.into_request(request).await?;
let mut response = graphql_request
.data(req_ctx.clone())
.execute(&app_ctx.schema)
.await;
response = update_cache_control_header(response, app_ctx.as_ref(), req_ctx.clone());
let mut resp = response.into_rest_response()?;
update_response_headers(&mut resp, &req_ctx, &app_ctx);
Ok(resp)                               has been included in  handle_graphql_request  function?

@coderabbitai Yes, implement them

@coderabbitai My recent commit with your changes failing:  error[E0283]: type annotations needed
Error:    --> src/core/http/request_handler.rs:106:5
|
106 |     handle_graphql_request(req, app_ctx, req_ctx).await
|     ^^^^^^^^^^^^^^^^^^^^^^ cannot infer type of the type parameter T declared on the function handle_graphql_request
|
= note: cannot satisfy _: DeserializeOwned
note: required by a bound in handle_graphql_request
--> src/core/http/request_handler.rs:207:36
|
207 | async fn handle_graphql_request<T: DeserializeOwned + GraphQLRequestLike>(
|                                    ^^^^^^^^^^^^^^^^ required by this bound in handle_graphql_request
help: consider specifying the generic argument
|
106 |     handle_graphql_request::(req, app_ctx, req_ctx).await
|                           +++++
error[E0283]: type annotations needed
Error:    --> src/core/http/request_handler.rs:257:13
|
257 |             handle_graphql_request(request, app_ctx.as_ref(), req_ctx).await
|             ^^^^^^^^^^^^^^^^^^^^^^ cannot infer type of the type parameter T declared on the function handle_graphql_request
|
= note: cannot satisfy _: DeserializeOwned
note: required by a bound in handle_graphql_request
--> src/core/http/request_handler.rs:207:36
|
207 | async fn handle_graphql_request<T: DeserializeOwned + GraphQLRequestLike>(
|                                    ^^^^^^^^^^^^^^^^ required by this bound in handle_graphql_request
help: consider specifying the generic argument
|
257 |             handle_graphql_request::(request, app_ctx.as_ref(), req_ctx).await
|                                   +++++
For more information about this error, try rustc --explain E0[28](https://github.com/varshith257/tailcall/actions/runs/9147408223/job/25148781304?pr=2#step:8:29)3.
error: could not compile tailcall (lib) due to 2 previous errors
warning: build failed, waiting for other jobs to finish...
error: could not compile tailcall (lib test) due to 2 previous errors
error: process didn't exit successfully: /home/runner/.rustup/toolchains/1.78-x86_64-unknown-linux-gnu/bin/cargo test --tests --manifest-path /home/runner/work/tailcall/tailcall/Cargo.toml --target-dir /home/runner/work/tailcall/tailcall/target/llvm-cov-target --all-features (exit status: 101)
Error: Process completed with exit code 1.

@coderabbitai         my latest commit 90a2ea8  failing error[E0412]: cannot find type T in this scope
Error:    --> src/core/http/request_handler.rs:256:38
|
256 |             handle_graphql_request::(request, app_ctx.as_ref(), req_ctx).await
|                                      ^ not found in this scope
|
help: you might be missing a type parameter
|
238 | async fn handle_rest_apis(
|                          +++
error: unused import: std::ops::Deref
Error:  --> src/core/http/request_handler.rs:2:5
|
2 | use std::ops::Deref;
|     ^^^^^^^^^^^^^^^
|
= note: -D unused-imports implied by -D warnings
= help: to override -D warnings add #[allow(unused_imports)]

@coderabbitai my latest commit 94246e4  is failing
error[E0283]: type annotations needed
Error:    --> src/core/http/request_handler.rs:271:16
|
271 |         return handle_rest_apis(req, app_ctx, req_counter).await;
|                ^^^^^^^^^^^^^^^^ cannot infer type of the type parameter T declared on the function handle_rest_apis
|
= note: cannot satisfy _: DeserializeOwned
note: required by a bound in handle_rest_apis
--> src/core/http/request_handler.rs:238:30
|
238 | async fn handle_rest_apis<T: DeserializeOwned + GraphQLRequestLike>(
|                              ^^^^^^^^^^^^^^^^ required by this bound in handle_rest_apis
help: consider specifying the generic argument
|
271 |         return handle_rest_apis::(req, app_ctx, req_counter).await;
|                                +++++
For more information about this error, try rustc --explain E0[28](https://github.com/varshith257/tailcall/actions/runs/9147496269/job/25149025385?pr=2#step:5:29)3.
error: could not compile tailcall (lib) due to 1 previous error
Error: Process completed with exit code 101.

@coderabbitai Tests are failing:  ```
ailures:
---- run_execution_spec::rest-api-error.md ----
test panicked: snapshot assertion for 'rest-api-error.md_0' failed in line 195
---- run_execution_spec::rest-api-post.md ----
test panicked: snapshot assertion for 'rest-api-post.md_0' failed in line 195
---- run_execution_spec::rest-api.md ----
test panicked: snapshot assertion for 'rest-api.md_0' failed in line 195
failures:
run_execution_spec::rest-api-error.md
run_execution_spec::rest-api-post.md
run_execution_spec::rest-api.md
test result: FAILED. 195 passed; 3 failed; 0 ignored; 0 measured; 0 filtered out; finished in 7.88s
error: test failed, to rerun pass --test execution_spec
error: process didn't exit successfully: /home/runner/.rustup/toolchains/1.78-x86_64-unknown-linux-gnu/bin/cargo test --tests --manifest-path /home/runner/work/tailcall/tailcall/Cargo.toml --target-dir /home/runner/work/tailcall/tailcall/target/llvm-cov-target --all-features (exit status: 101)

@coderabbitai we need this to be implemented in this PR:
chore: add tests for Tailcall CORS
If the request comes in for tailcall.run we automatically enable CORS for those request. Write an integration test for it.
Get started here — https://tailcall.run/developers/integration-testing/

@coderabbitai we need this to be implemented in this PR:
chore: add tests for Tailcall CORS
If the request comes in for tailcall.run we automatically enable CORS for those request. Write an integration test for it.
Get started here — https://tailcall.run/developers/integration-testing/

@coderabbitai

@coderabbitai we need this to be implemented in this PR:
chore: add tests for Tailcall CORS
If the request comes in for tailcall.run we automatically enable CORS for those request. Write an integration test for it.
Get started here — https://tailcall.run/developers/integration-testing/

@coderabbitai

@coderabbitai we need this to be implemented in this PR:
chore: add tests for Tailcall CORS
If the request comes in for tailcall.run we automatically enable CORS for those request. Write an integration test for it.
Get started here — https://tailcall.run/developers/integration-testing/

@coderabbitai

@coderabbitai we need this to be implemented in this PR:
chore: add tests for Tailcall CORS
If the request comes in for tailcall.run we automatically enable CORS for those request. Write an integration test for it.
Get started here — https://tailcall.run/developers/integration-testing/

@coderabbitai

@coderabbitai we need this to be implemented in this PR:
chore: add tests for Tailcall CORS
If the request comes in for tailcall.run we automatically enable CORS for those request. Write an integration test for it.
Get started here — https://tailcall.run/developers/integration-testing/

@coderabbitai

Here is the integration test for CORS handling for requests from "https://tailcall.run":
#[cfg(test)]
mod integration_tests {
    use super::*;
    use hyper::header::{HeaderValue, ACCESS_CONTROL_ALLOW_ORIGIN, ACCESS_CONTROL_ALLOW_METHODS, ACCESS_CONTROL_ALLOW_HEADERS};
    use hyper::{Body, Request, Response, StatusCode};
    use std::sync::Arc;

    #[tokio::test]
    async fn test_cors_for_tailcall_run() {
        let app_ctx = Arc::new(AppContext::default());
        let mut req_counter = RequestCounter::new(&app_ctx.blueprint.telemetry, &Request::default());

        // Simulate a request from "https://tailcall.run"
        let req = Request::builder()
            .method("OPTIONS")
            .header("Origin", "https://tailcall.run")
            .body(Body::empty())
            .unwrap();

        let response = handle_origin_tailcall::<GraphQLRequestLike>(req, app_ctx, &mut req_counter).await.unwrap();

        // Check the CORS headers in the response
        assert_eq!(response.status(), StatusCode::OK);
        assert_eq!(response.headers().get(ACCESS_CONTROL_ALLOW_ORIGIN), Some(&HeaderValue::from_static("https://tailcall.run")));
        assert_eq!(response.headers().get(ACCESS_CONTROL_ALLOW_METHODS), Some(&HeaderValue::from_static("GET, POST, OPTIONS")));
        assert_eq!(response.headers().get(ACCESS_CONTROL_ALLOW_HEADERS), Some(&HeaderValue::from_static("*")));
    }
}

This test simulates an OPTIONS request from "https://tailcall.run" and checks if the response contains the appropriate CORS headers.
@varshith257, I have added the integration test for CORS handling for requests from "https://tailcall.run". This test ensures that CORS is automatically enabled for such requests. Let me know if you need any further assistance.
[ADD_LEARNING] The handle_origin_tailcall function in request_handler.rs automatically enables CORS for requests coming from "https://tailcall.run".
Analysis chain
Scripts executed
Actions Performed

@coderabbitai Where to integrate this one? intheisa file only the integration tests or there any tests files for it..please check and give clarity

@coderabbitai Once agin review and verify the issue satisfies the requirements
The code in request_handler.rs has a lot of duplicate patterns and function calls. Clean that up and earn some bounty...if not make updtaes


chore: optimize outline treeview perf

变动类型

[x] 代码风格优化

需求背景和解决方案
没有图，原理和之前几个一样
changelog

优化大纲面板 treeview 渲染性能

Codecov Report

Merging #176 (e4177d8) into main (78ee9a6) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #176      +/-   ##
==========================================
- Coverage   59.40%   59.40%   -0.01%
==========================================
  Files        1180     1180
  Lines       72354    72354
  Branches    14978    14978
==========================================
- Hits        42983    42979       -4
- Misses      26768    26771       +3
- Partials     2603     2604       +1

Impacted Files
Coverage Δ

packages/monaco/src/browser/schema-registry.ts
68.88% <0.00%> (-2.23%)
:arrow_down:

...erences/src/browser/preference-settings.service.ts
79.16% <0.00%> (-0.70%)
:arrow_down:

...kages/theme/src/browser/workbench.theme.service.ts
71.77% <0.00%> (-0.61%)
:arrow_down:

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 78ee9a6...e4177d8. Read the comment docs.


certificates field is empty in config_dump after IMPERSONATED_IDENTITY changes

I noticed the certificates field is empty in ztunnel config_dump after https://github.com/istio/ztunnel/pull/452
$ kubectl exec -it -n istio-system ds/ztunnel -- curl localhost:15000/config_dump | jq .
...
...
      "ISTIO_VERSION": "1.18-dev"
    },
    "num_worker_threads": 2,
    "enable_original_source": null,
    "proxy_args": "proxy ztunnel"
  },
  "certificates": []
}

I would expect most of the certs to no longer be present after this change, but I would expect there to at least be one for ztunnel pod itself? https://github.com/istio/ztunnel/pull/442#discussion_r1131527224

cc @imroc

Nice catch, fixed in this PR https://github.com/istio/ztunnel/pull/469


Improve benchmarks for v1

The PR is best reviewed commit by commit.

The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #313   +/-   ##
=======================================
  Coverage   79.88%   79.88%
=======================================
  Files          70       70
  Lines        9328     9328
=======================================
  Hits         7452     7452
  Misses       1876     1876

Impacted Files
Coverage Δ

benches/src/lib.rs
0.00% <ø> (ø)

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 fdcfa6c...9575dc2. Read the comment docs.


Enable gosec 404: Use of weak random number generator

[x] Enable gosec G404

$ make verify-golangci-lint
...
pkg/util/util.go:171:22: G404: Use of weak random number generator (math/rand instead of crypto/rand) (gosec)
                b[i] = letterRunes[rand.Intn(len(letterRunes))]
                                   ^
pkg/controller/test/util.go:36:22: G404: Use of weak random number generator (math/rand instead of crypto/rand) (gosec)
                b[i] = letterBytes[rand.Intn(len(letterBytes))]

-- https://github.com/cert-manager/cert-manager/actions/runs/7385479927?pr=6582

pkg/util.RandStringRunes was introduced in 7d8683bd169bdf2bc8a521fc9bdf6fb556213007 to generate a suffix for the HTTP01 solver Pod. But the solver Pod now uses GenerateName instead.

https://github.com/cert-manager/cert-manager/blob/47d720be3960ecd50a77c9d50af5b39406d0c56d/pkg/issuer/acme/http/pod.go#L163-L182

pkg/controller/test.RandStringBytes is almost identical and was introduced in 0a0747dac7f8f892e264bb5bd0255c10b275abda.

[x] Ignore the warnings: Both functions are now only used in tests and the output does not need to be cryptographically random, so I'm ignoring the warnings by adding a nosec annotation and creating a followup issue to consolidate the two functions.

$ git grep RandStringRunes | grep -v -i test
pkg/util/util.go:func RandStringRunes(n int) string {

$ git grep RandStringBytes | grep -v -i test

I considered using crypt/rand instead, but it doesn't provide the convenient rand.Intn function. You'd either have to use crypto/rand.Int or seed math/rand with a crypto/rand source.

/kind cleanup
Check code for unintended use of weak random number generator (`math/rand` instead of `crypto/rand`); using `golangci-lint` / `gosec` (G404).

/approve
/lgtm


feat: direct hugging face support

Prerequisite to enable HF button:

yes please !

Yes Please

Yes please !

https://huggingface.co/docs/hub/en/models-adding-libraries#register-your-libraries-supported-tasks-on-the-hub
happy to help if approved

Yes please

+1

+1
This would be huge, especially now that HF allows you to isolate "warm" models from cool or frozen.
These models can be used via the API instantly, and HF PRO subs get increased rate limit.


Proper search including full-text search

Current search is inadequate:

Currently based on temporary views in couchdb (could move to predefined views but how do we deal with fact we allow arbitrary keys/columns)
No full-text search
No searching on permissions

Suggest using elasticsearch (cf #24)

Recent changes to search API mean that full-text search is now possible, as is searching on permissions. Closing.

w00t!


Wine esync

Its a good idea to consider Wine esync to DXVK performance goals. Keep up the good work.

I'm aware that esync exists, what is your point?

Nothing special, i noticed that a major performance hit isn't coming from DXVK it self. It is a good idea to always test DXVK with ESYNC on Linux in order to have a real measure VS Windows. Otherwise you will end up continuously searching for optimizations to match the native performance.

I'm not sure you understand how it works. You don't have to worry about Doitsujin.


Error when compiling on Fedora

Get the following errors when building on Fedora
/home/spindump/src/spindump_remote_server.c:160:0: style: The function 'spindump_remote_server_close' is never used. [unusedFunction]
^
/home/spindump/src/spindump_remote_server.c:189:0: style: The function 'spindump_remote_server_getupdate' is never used. [unusedFunction]
^
/home/spindump/src/spindump_remote_server.c:107:0: style: The function 'spindump_remote_server_init' is never used. [unusedFunction]
^
nofile:0:0: information: Cppcheck cannot find all the include files (use --check-config for details) [missingIncludeSystem]
/home/spindump/src/spindump_remote_server.c: In function ‘spindump_remote_server_init’:
/home/spindump/src/spindump_remote_server.c:139:37: error: passing argument 5 of ‘MHD_start_daemon’ from incompatible pointer type [-Werror=incompatible-pointer-types]
139 |                                     spindump_remote_server_answer, server,
|                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|                                     |
|                                     int (*)(void *, struct MHD_Connection *, const char *, const char *, const char *, const char *, size_t , void **) {aka int ()(void *, struct MHD_Connection *, const char *, const char *, const char *, const char *, long unsigned int , void **)}
In file included from /home/spindump/src/spindump_remote_server.h:26,
from /home/spindump/src/spindump_remote_server.c:32:
/usr/include/microhttpd.h:2425:1: note: expected ‘MHD_AccessHandlerCallback’ {aka ‘enum MHD_Result ()(void *, struct MHD_Connection *, const char *, const char *, const char *, const char *, long unsigned int , void **)’} but argument is of type ‘int ()(void *, struct MHD_Connection *, const char *, const char *, const char *, const char *, size_t , void **)’ {aka ‘int ()(void *, struct MHD_Connection *, const char *, const char *, const char *, const char *, long unsigned int , void **)’}
2425 | MHD_start_daemon (unsigned int flags,
| ^~~~~~~~~~~~~~~~
/home/spindump/src/spindump_remote_server.c: In function ‘spindump_remote_server_printparameters’:
/home/spindump/src/spindump_remote_server.c:356:58: error: passing argument 3 of ‘MHD_get_connection_values’ from incompatible pointer type [-Werror=incompatible-pointer-types]
356 |   MHD_get_connection_values(connection, MHD_HEADER_KIND, spindump_remote_server_printparameter, NULL);
|                                                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|                                                          |
|                                                          int ()(void *, enum MHD_ValueKind,  const char *, const char )
In file included from /home/spindump/src/spindump_remote_server.h:26,
from /home/spindump/src/spindump_remote_server.c:32:
/usr/include/microhttpd.h:2699:49: note: expected ‘MHD_KeyValueIterator’ {aka ‘enum MHD_Result ()(void *, enum MHD_ValueKind,  const char *, const char )’} but argument is of type ‘int ()(void *, enum MHD_ValueKind,  const char *, const char )’
2699 |                            MHD_KeyValueIterator iterator,
|                            ~^~
/home/spindump/src/spindump_remote_server.c: In function ‘spindump_remote_server_answer’:
/home/spindump/src/spindump_remote_server.c:622:67: error: passing argument 3 of ‘MHD_create_post_processor’ from incompatible pointer type [-Werror=incompatible-pointer-types]
622 |                                                                   spindump_remote_server_postiterator,
|                                                                   ^~~~~~~~~~~~~~~~~~~~~
|                                                                   |
|                                                                   int ()(void *, enum MHD_ValueKind,  const char *, const char *, const char *, const char *, const char , uint64_t,  size_t) {aka int ()(void *, enum MHD_ValueKind,  const char *, const char *, const char *, const char *, const char , long unsigned int,  long unsigned int)}
In file included from /home/spindump/src/spindump_remote_server.h:26,
from /home/spindump/src/spindump_remote_server.c:32:
/usr/include/microhttpd.h:3463:1: note: expected ‘MHD_PostDataIterator’ {aka ‘enum MHD_Result ()(void *, enum MHD_ValueKind,  const char *, const char *, const char *, const char *, const char , long unsigned int,  long unsigned int)’} but argument is of type ‘int ()(void *, enum MHD_ValueKind,  const char *, const char *, const char *, const char *, const char , uint64_t,  size_t)’ {aka ‘int ()(void *, enum MHD_ValueKind,  const char *, const char *, const char *, const char *, const char *, long unsigned int,  long unsigned int)’}
3463 | MHD_create_post_processor (struct MHD_Connection *connection,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
/home/benson/spindump/src/spindump_remote_server.c: At top level:
cc1: error: unrecognized command line option ‘-Wno-documentation’ [-Werror]
cc1: error: unrecognized command line option ‘-Wno-reserved-id-macro’ [-Werror]
cc1: error: unrecognized command line option ‘-Wno-documentation-deprecated-sync’ [-Werror]
cc1: error: unrecognized command line option ‘-Wno-disabled-macro-expansion’ [-Werror]
cc1: error: unrecognized command line option ‘-Wno-covered-switch-default’ [-Werror]
cc1: all warnings being treated as errors
make[2]: *** [src/CMakeFiles/spindumplib.dir/build.make:603: src/CMakeFiles/spindumplib.dir/spindump_remote_server.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:770: src/CMakeFiles/spindumplib.dir/all] Error 2
make: *** [Makefile:161: all] Error 2

The regular build command:
cmake .
make

gives the above error. When building using
cmake -DCMAKE_C_FLAGS="-Wall -Wpedantic -Wno-error=incompatible-pointer-types -Wno-incompatible-pointer-types" .
make

it successfully builds, but I get the following errors
spindump: error: cannot parse JSON record: missing opening brace in field top
spindump: error: cannot parse JSON record: missing opening brace in field top
spindump: error: cannot parse JSON string: missing opening quote in field b
spindump: error: field a is missing from the JSON record
spindump: error: cannot parse JSON string: missing opening quote in field array
spindump: warning: not enough bytes for the IPv6 header (capture length only 50, 54 required)
spindump: warning: not enough bytes for the IP header (capture length only 19, 34 required)
spindump: warning: not enough bytes for the IPv6 header (capture length only 21, 54 required)
spindump: warning: not enough bytes for the Ethernet header, only 12 bytes in received frame
spindump: warning: not enough payload bytes for an ICMPv6 header
spindump: warning: not enough payload bytes for an ICMP echo header


where is label_2  in test dataset of KITTI?

Can you provide it  for me?Thanks!

ok,I know!Thanks!

Is the label_2 folder under testing an empty folder？

@happiensslz  where is the testing label_2 folder???

due to the kitti privacy,the testing label is not provided!    Follow the paper do, split the training into train and test!

@happiensslz  where is the testing label_2 folder?


do not support .net8

do not support .net8, will it fixed in the future?

The DLL files should work, the project should also work if you upgrade the framework version.

The DLL files should work, the project should also work if you upgrade the framework version.

thanks for reply so fast, cause "FormatterServices" is obsolete in .net8, i can't figure out any new api to replace this, so it can't be used in .net8 program.    the error details "Severity	Code	Description	Project	File	Line	Suppression State
Error	SYSLIB0050	'FormatterServices' is obsolete: 'Formatter-based serialization is obsolete and should not be used.' (https://aka.ms/dotnet-warnings/SYSLIB0050)", i use the source code to compile.

Thanks, I will look into it.

error line720 in JSON.cs

Try :
o = System.Runtime.CompilerServices.RuntimeHelpers.GetUninitializedObject(type);

Try :
o = System.Runtime.CompilerServices.RuntimeHelpers.GetUninitializedObject(type);

wow, it builds successful now, thanks so much!!!


Migration Script: Renamed gist:decimalValue to gist:numericValue

Renamed gist:decimalValue to gist:numericValue and expanded property range to include all numeric data types supported by OWL. Original Issue #171
I think all we need to do is replace gist:decimalValue with gist:numericValue.

Already resolved.


Allow to deploy a diagram to a different Camunda Cloud region

Is your feature request related to a problem? Please describe.
With Camunda Cloud 1.1 we added a region to the URL of a Zeebe cluster to be able to route traffic to different regions. You can read a bit about it in the docs https://docs.camunda.io/docs/guides/update-guide/100-to-110#zeebe-java-client.
At the moment for all >= 1.0 clusters in Camunda Cloud only a single default region exists. But in the future we might add more, i.e. we plan to offer a new North America region in the near future.
The user has to be able to specify the region in some way to be able to deploy the diagram to a different region.
A workaround exists by using the Camunda Cloud Self Managed Oauth configuration in the deploy dialog.
Describe the solution you'd like

[ ] Instead of using the Cluster ID, identify the cluster via the Cluster URL.
[ ] Migrate existing configurations (that provided the Cluster ID only) to use bru-2 (cf. https://github.com/camunda/camunda-modeler/issues/2375#issuecomment-889830410) as a region.
[ ] Upon save or deploy persist the Cluster URL in the deployment profile

Context and Prior Discussion
@menski At the moment we offer three configuration fields in the deploy dialog, Cluster ID, Client ID and Client Secret.

I see two options but maybe there is another better one:

We add a fourth field Region to allow the user to specify the region
We replace the Cluster ID field by Cluster URL to allow users to enter the full URL including the region

In my opinion I would prefer option 2 as it is simpler for the user if we enable them to copy the whole address the same way they can copy the client id/secret. In Option 1 they have to copy to information which are always related and will never change separately.

Just to explore options:

would it also be an option to retrieve the region via the cluster id in the background so that the fields of the dialog would not have to be changed?

We don't have any information which cluster id belongs to which region at the moment. So no it's not possible right now.

ok, thanks

Regarding the options:

What is the best practice established by the Cloud team? Supported and documented in the Cloud console?
Will using the URL circumvent caching issues with newly created clusters?

@menski This is not actionable for us, yet, cf. https://github.com/camunda/camunda-modeler/issues/2375#issuecomment-882720354.

What is the best practice established by the Cloud team? Supported and documented in the Cloud console?

Write now the java client and node-js client offer to specify the region as an extra parameter. But this was just added to stay backwards compatible, and there are justified concerns if this is a good UX, i.e., what is the point for the user to copy to values which are highly coupled.

Will using the URL circumvent caching issues with newly created clusters?

I'm not sure which chaching you are referring too? There was the issue of negative DNS propagation issues before. But the change which is requiring this feature, actually removed the root cause of this DNS propagation problem.

But the change which is requiring this feature, actually removed the root cause of this DNS propagation problem.

So we are safe to use URL, too. Thanks.

Follow up question:
Region is going to be a mandatory field? Or does it remain optional once introduced?

From what I can read in the documentation you use ZeebeAPI (or audience). I did not try out yet how the cloud presents the information (do you still feature clusterID or do you provide the clusterURL_ to users.
My two cents therefore are: Switch from cluster ID to ClusterURL in the future, but only if

that is done in the cloud console, too
we can introduce that in a backwards compatible manner (i.e. we pick up the currently configured cluster IDs and generate cluster URLs from these, for all cloud >= 1.0 versions).

that is done in the cloud console, too

Right now the user is seeing the following modal when creating a secret

Which we can easily extend to feature the Cluster URL additionally, which then matches the input fields of the modeler

If we decide to go for this in the modeler then I would make sure that the console will present the cluster URL prominent to the user, and also that the Java and Nodejs client can work with it.

we can introduce that in a backwards compatible manner (i.e. we pick up the currently configured cluster IDs and generate cluster URLs from these, for all cloud >= 1.0 versions)

All saved credentials can only refer to the current defaut bru-2 region, therefore I think it is save to generate the URL out of the saved cluster id on migration.

Perfect. Given your confirmation I believe we should settle down on that option: Rename Cluster ID to Cluster URL + auto-migrate existing deployment configs.

I've updated the issue accordingly.

What is the timeline for this?
@menski , would it be okay if we plan this for Q4 or do you expect that the new region will come sooner than that?
cc. @volkergersabeck

We will roll out the changes required in Cloud https://github.com/camunda/camunda-modeler/issues/2375#issuecomment-889830410 probably this week, see https://github.com/camunda-cloud/console/pull/2382
As far as I know the new region is already setup, I can double check with Felix if we will promote it soon

Marked for 4.10 release

Aligned with @menski :
When validating the URL, we can assume that the format must match
<someId>.<airport>-<number>.zeebe.camunda.io:443

Potentially https://<someId>.<airport>-<number>.zeebe.camunda.io:443 is also okay, but this shall be tested with zeebe-node

The changes https://github.com/camunda-cloud/console/pull/2382 are live in console in production and can be used for testing.

When viewing the client connection details, I can't see the cluster URL

It's only visible after creating a new client

Is this intended? /cc @menski

No let me create an issue in console to get that fixed


Sync breaks with large folders

I am synching a 140MB folder and the sync process breaks.
ksync watch starts to show this error:
Get http://localhost:8384/rest/events?since=21: dial tcp [::1]:8384: connect: connection refused

over and over.
How could I debug further this issue?

The issue was related to --pod not working properly.
The synch worked using --selector instead.


Add Mouseposé

"When turned on, it dims the screen and puts a spotlight on the area around the mouse pointer, easily guiding the audience‘s attention to an area of interest."

Some notes:

The download link (url) is not obvious on the vendor's webpage - only Mac App Store link - but is not hidden for those who have purchased the license elsewhere.

Ideally the app should be installed as "Mouseposé.app" (as is the case with "normal" installation process), but this cask installs it as "Mousepose.app". Specifying the app stanza as 'Mouseposé.app' yields the following error:

Error: It seems the symlink source is not there: '/opt/homebrew-cask/Caskroom/mousepose/3.2.7/Mouseposé.app'

I couldn't find a way to resolve this.

As for your first point, we don’t care as long as the download host is the same as the homepage.
As for your second point, try looking at the app in a Terminal, rather than the Finder. Does it show as Mousepose.app? Then it likely has a different name in the Finder and in a Terminal (not unheard of), in which case, follow this solution.

Thank you for the contribution. It was merged directly as 9cf3550ef90b6bde7c370247cce26a311aa70b6f to keep commit history cleaner. Your contribution is still credited to you.

@vitorgalvao
Thanks a lot for the suggestion.
Since that was exactly the case, I added the target key.
:target => 'Mouseposé.app' seemed to work at first, but turned out that upon brew cask uninstall it somehow leaves an orphaned icon of Mouseposé in the Launchpad. So I tried :target => "Mousepose\314\201.app" and that seems to work. (All this is just empirical, and maybe only me, but I'm afraid I have no guts to dig into this.)
@adityadalal924
Thank you for merging.

@rinopo I verified that things were OK before merging.
[~] > brew cask install mousepose
==> Downloading https://cdn.boinx.com/software/mousepose/Boinx_Mousepose_3.2.7-1
######################################################################## 100.0%
==> Symlinking App 'Mousepose.app' to '/Applications/Mouseposé.app'
🍺  mousepose staged at '/opt/homebrew-cask/Caskroom/mousepose/3.2.7' (300 files, 12M)

[~] > brew cask zap mousepose
==> Implied "brew cask uninstall mousepose"
==> Removing App symlink: '/Applications/Mouseposé.app'
==> Dispatching zap stanza
==> Running zap process for mousepose; your password may be necessary
==> Removing files: ["~/Library/Application Support/com.boinx.Mousepose", "~/Lib
==> Removing all staged versions of Cask 'mousepose'
[~] >


Docker invalid argument error what(): Option --model is required to run translation

I am running a Gunicorn python server on my GKE pod with the ghcr.io/opennmt/ctranslate2:3.14.0-ubuntu20.04-cuda11.2 as it's docker image. I am currently getting a weird error during initialization what(): Option --model is required to run translation terminate called after throwing an instance of 'std::invalid_argument'. I couldn't find much info regarding this error message. Any ideas what the problem might be? Here is the full docker file as a reference:
# Set the base image
FROM ghcr.io/opennmt/ctranslate2:3.14.0-ubuntu20.04-cuda11.2

# Avoiding user interaction with tzdata
ENV DEBIAN_FRONTEND=noninteractive

# Update the system and Install necessary packages
RUN apt-get update && apt-get install -y \
    ffmpeg \
    curl \
    git \
    software-properties-common

# Set working directory and copy in project files
WORKDIR /app
COPY . ./

# Make sure pip is updated and install dependencies
RUN pip install --upgrade pip &&\
    pip install -r requirements.txt --no-cache-dir

# Set environment variables
ENV PYTHONUNBUFFERED 1

EXPOSE 8000

CMD ["python", "server.py"]

Just to provide more context my actual transcribe funtion is exactly the same as in the document:
segments, _ = whisper_model.transcribe(whisper_audio, word_timestamps=True, vad_filter=True)
This is very strange since I am not running this from the command line

The base Docker image defines an entrypoint:
https://github.com/OpenNMT/CTranslate2/blob/7b1984c85be3e28457da4cebc5a16614baed4bf9/docker/Dockerfile#L92
So in your Dockerfile you probably need to use ENTRYPOINT instead of CMD.


Universal package quickstart should use latest VSTS CLI

VSTS CLI 0.1.2 added support for universal packages so that should be used instead of a private build
Fixes #1577

@alexmullans

@nayanshah I have sent an email to Alex, we'll get this fixed from the private repo.