└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.046001 DEBUG ÷8 MODE_0
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.046304 DEBUG ÷8 MODE_1
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.046607 DEBUG ÷8 MODE_2
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.046910 DEBUG ÷8 MODE_3
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.047214 DEBUG ÷4 MODE_0
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.047492 DEBUG ÷4 MODE_1
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.047769 DEBUG ÷4 MODE_2
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.048048 DEBUG ÷4 MODE_3
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.048325 INFO  (3/6) running `mosi_simplex_loopback`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.048349 DEBUG ÷256 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.049425 DEBUG ÷256 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.050526 DEBUG ÷256 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.051602 DEBUG ÷256 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.052703 DEBUG ÷128 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.053283 DEBUG ÷128 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.053872 DEBUG ÷128 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.054452 DEBUG ÷128 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.055042 DEBUG ÷64 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.055370 DEBUG ÷64 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.055705 DEBUG ÷64 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056034 DEBUG ÷64 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056369 DEBUG ÷32 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056571 DEBUG ÷32 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056775 DEBUG ÷32 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056977 DEBUG ÷32 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057180 DEBUG ÷16 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057320 DEBUG ÷16 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057460 DEBUG ÷16 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057600 DEBUG ÷16 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057740 DEBUG ÷8 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057850 DEBUG ÷8 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057959 DEBUG ÷8 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058069 DEBUG ÷8 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058179 DEBUG ÷4 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058288 DEBUG ÷4 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058398 DEBUG ÷4 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058508 DEBUG ÷4 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058617 INFO  (4/6) running `mosi_simplex_loopback_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.058641 DEBUG ÷256 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.059723 DEBUG ÷256 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.060827 DEBUG ÷256 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.061909 DEBUG ÷256 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.063013 DEBUG ÷128 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.063601 DEBUG ÷128 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.064191 DEBUG ÷128 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.064780 DEBUG ÷128 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.065369 DEBUG ÷64 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.065708 DEBUG ÷64 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066044 DEBUG ÷64 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066383 DEBUG ÷64 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066719 DEBUG ÷32 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066925 DEBUG ÷32 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067131 DEBUG ÷32 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067336 DEBUG ÷32 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067542 DEBUG ÷16 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067682 DEBUG ÷16 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067830 DEBUG ÷16 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067969 DEBUG ÷16 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068117 DEBUG ÷8 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068229 DEBUG ÷8 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068340 DEBUG ÷8 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068452 DEBUG ÷8 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068564 DEBUG ÷4 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068670 DEBUG ÷4 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068775 DEBUG ÷4 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068881 DEBUG ÷4 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068987 INFO  (5/6) running `miso_simplex_loopback`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.069011 DEBUG ÷256 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.070135 DEBUG ÷256 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.071331 DEBUG ÷256 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.072456 DEBUG ÷256 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.073653 DEBUG ÷128 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.074296 DEBUG ÷128 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.074979 DEBUG ÷128 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.075621 DEBUG ÷128 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.076304 DEBUG ÷64 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.076709 DEBUG ÷64 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.077133 DEBUG ÷64 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.077537 DEBUG ÷64 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.077962 DEBUG ÷32 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.078249 DEBUG ÷32 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.078541 DEBUG ÷32 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.078827 DEBUG ÷32 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079119 DEBUG ÷16 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079349 DEBUG ÷16 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079579 DEBUG ÷16 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079808 DEBUG ÷16 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080038 DEBUG ÷8 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080242 DEBUG ÷8 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080445 DEBUG ÷8 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080648 DEBUG ÷8 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080852 DEBUG ÷4 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081031 DEBUG ÷4 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081210 DEBUG ÷4 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081389 DEBUG ÷4 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081568 INFO  (6/6) running `miso_simplex_loopback_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.081592 DEBUG ÷256 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.082701 DEBUG ÷256 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.083883 DEBUG ÷256 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.084992 DEBUG ÷256 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.086174 DEBUG ÷128 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.086801 DEBUG ÷128 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.087469 DEBUG ÷128 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.088097 DEBUG ÷128 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.088765 DEBUG ÷64 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.089152 DEBUG ÷64 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.089562 DEBUG ÷64 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.089949 DEBUG ÷64 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.090360 DEBUG ÷32 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.090630 DEBUG ÷32 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.090908 DEBUG ÷32 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091179 DEBUG ÷32 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091457 DEBUG ÷16 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091671 DEBUG ÷16 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091885 DEBUG ÷16 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092098 DEBUG ÷16 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092312 DEBUG ÷8 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092500 DEBUG ÷8 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092687 DEBUG ÷8 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092874 DEBUG ÷8 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.093062 DEBUG ÷4 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.093225 DEBUG ÷4 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.093389 DEBUG ÷4 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.093552 DEBUG ÷4 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.135888 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/tmplhy_1epo/i2c-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.48s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-4a58f6b85b8c68fd)
(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/tmplhy_1epo/lptim-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.43s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-7e3059787ba94315)
(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 hex-literal v0.3.3
   Compiling aes-testsuite v0.1.0 (/tmp/tmplhy_1epo/aes-testsuite)
    Finished test [optimized + debuginfo] target(s) in 1.26s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-63f23314b915b7e6)
(HOST) INFO  flashing program (50.21 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000008 INFO  (1/13) running `encrypt_ecb_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.000285 INFO  Approximate cycles per 128-bit encrypt: 215
└─ test::tests::encrypt_ecb_128 @ tests/test.rs:1529
0.000306 INFO  (2/13) running `encrypt_ecb_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.000543 INFO  Approximate cycles per 256-bit encrypt: 267
└─ test::tests::encrypt_ecb_256 @ tests/test.rs:1554
0.000564 INFO  (3/13) running `encrypt_ecb_inplace_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.000837 INFO  Approximate cycles per 128-bit encrypt: 210
└─ test::tests::encrypt_ecb_inplace_128 @ tests/test.rs:1580
0.000859 INFO  (4/13) running `encrypt_ecb_inplace_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.001089 INFO  Approximate cycles per 256-bit encrypt: 254
└─ test::tests::encrypt_ecb_inplace_256 @ tests/test.rs:1604
0.001111 INFO  (5/13) running `encrypt_gcm_inplace_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.002495 INFO  Approximate cycles per 128-bit encrypt: 661
└─ test::tests::encrypt_gcm_inplace_128 @ tests/test.rs:1637
0.002516 INFO  (6/13) running `encrypt_gcm_inplace_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.004008 INFO  Approximate cycles per 256-bit encrypt: 749
└─ test::tests::encrypt_gcm_inplace_256 @ tests/test.rs:1670
0.004029 INFO  (7/13) running `decrypt_ecb_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.004331 INFO  Average cycles per 128-bit decrypt: 265
└─ test::tests::decrypt_ecb_128 @ tests/test.rs:1695
0.004353 INFO  (8/13) running `decrypt_ecb_inplace_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.004662 INFO  Average cycles per 128-bit decrypt: 265
└─ test::tests::decrypt_ecb_inplace_128 @ tests/test.rs:1719
0.004683 INFO  (9/13) running `decrypt_ecb_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.004945 INFO  Average cycles per 256-bit decrypt: 332
└─ test::tests::decrypt_ecb_256 @ tests/test.rs:1744
0.004967 INFO  (10/13) running `decrypt_ecb_inplace_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.005234 INFO  Average cycles per 256-bit decrypt: 332
└─ test::tests::decrypt_ecb_inplace_256 @ tests/test.rs:1768
0.005256 INFO  (11/13) running `decrypt_gcm_inplace_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.006653 INFO  Approximate cycles per 128-bit decrypt: 664
└─ test::tests::decrypt_gcm_inplace_128 @ tests/test.rs:1801
0.006674 INFO  (12/13) running `decrypt_gcm_inplace_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.008196 INFO  Approximate cycles per 256-bit decrypt: 760
└─ test::tests::decrypt_gcm_inplace_256 @ tests/test.rs:1834
0.008218 INFO  (13/13) running `gcm_inplace_non_native_size`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.008433 INFO  Encrypting 445 bytes: 9170 cycles
└─ test::tests::gcm_inplace_non_native_size @ tests/test.rs:1864
0.008749 INFO  Decrypting 445 bytes: 9150 cycles
└─ test::tests::gcm_inplace_non_native_size @ tests/test.rs:1887
0.008779 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
────────────────────────────────────────────────────────────────────────────────
  (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/tmplhy_1epo/rng-testsuite)
    Finished test [optimized + debuginfo] target(s) in 2.46s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-c767ac65602b86db)
(HOST) INFO  flashing program (36.82 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.405
└─ test::tests::cha_cha @ tests/test.rs:91
 INFO  ChaCha12: 1737.98
└─ test::tests::cha_cha @ tests/test.rs:92
 INFO  ChaCha8: 1199.65
└─ test::tests::cha_cha @ tests/test.rs:93
 INFO  HW: 409.915
└─ 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/tmplhy_1epo/rtc-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.39s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-bfb705fa412c01af)
(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.159330 TRACE four_rtc_clk_cycles=5856
└─ test::test_set_date_time_with_clk @ tests/test.rs:39
0.169621 DEBUG Timestamp before<PHONE_NUMBER>000 after<PHONE_NUMBER>007 Δ 7
└─ test::test_set_date_time_with_clk @ tests/test.rs:84
0.169657 INFO  (2/3) running `test_set_date_time_lsi`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:93
0.170005 TRACE four_rtc_clk_cycles=6000
└─ test::test_set_date_time_with_clk @ tests/test.rs:39
0.180302 DEBUG Timestamp before<PHONE_NUMBER>000 after<PHONE_NUMBER>009 Δ 9
└─ test::test_set_date_time_with_clk @ tests/test.rs:84
0.180338 INFO  (3/3) running `test_set_date_time_hse`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:93
0.180561 TRACE four_rtc_clk_cycles=192
└─ test::test_set_date_time_with_clk @ tests/test.rs:39
0.190640 DEBUG Timestamp before<PHONE_NUMBER>000 after<PHONE_NUMBER>010 Δ 10
└─ test::test_set_date_time_with_clk @ tests/test.rs:84
0.190676 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/tmplhy_1epo/rcc-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.40s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-b944c20e483c3ba4)
(HOST) INFO  flashing program (13.90 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
 INFO  (1/3) 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/3) 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  (3/3) running `lsi_to_from`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:92
 INFO  LSI disabled from Div1 to Div1
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:179
 INFO  LSI disabled from Div1 to Div128
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:179
 INFO  LSI disabled from Div128 to Div1
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:179
 INFO  LSI disabled from Div128 to Div128
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:179
 INFO  LSI enabled from Div1 to Div1
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:191
 INFO  LSI enabled from Div1 to Div128
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:191
 INFO  LSI enabled from Div128 to Div1
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:191
 INFO  LSI enabled from Div128 to Div128
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:191
 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/tmplhy_1epo/adc-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.58s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-25ac4abb6638d544)
(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: 1498 Δ 10
└─ 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: 32 °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=1371 Δ 6
└─ 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=1371 Δ 6
└─ test::validate_vbat @ tests/test.rs:31
0.001309 INFO  VBAT=1371 Δ 6
└─ 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
   Compiling static_assertions v1.1.0
   Compiling nucleo-wl55jc-bsp v0.1.0-alpha.0 (/tmp/tmplhy_1epo/nucleo-wl55jc-bsp)
   Compiling subghz-testsuite v0.1.0 (/tmp/tmplhy_1epo/subghz-testsuite)
    Finished test [optimized + debuginfo] target(s) in 1.06s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-fbb389608b5f5d95)
(HOST) INFO  flashing program (26.26 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000007 INFO  (1/5) running `buffer_io`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
0.000405 INFO  Cycles 255B: 17933
└─ test::tests::buffer_io @ tests/test.rs:337
0.000514 INFO  Cycles 0B: 1186
└─ test::tests::buffer_io @ tests/test.rs:346
0.000536 INFO  (2/5) running `buffer_io_no_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
0.001931 INFO  Cycles 255B: 65826
└─ test::tests::buffer_io_no_dma @ tests/test.rs:359
0.002044 INFO  Cycles 0B: 1347
└─ test::tests::buffer_io_no_dma @ tests/test.rs:368
0.002066 INFO  (3/5) running `sleep_enter_exit`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
0.004166 INFO  74943 cycles to wake radio
└─ test::tests::sleep_enter_exit @ tests/test.rs:383
0.004204 INFO  (4/5) running `fsk_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
0.017186 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:185
0.017216 DEBUG RX with timeout 92 ms
└─ test::ping_pong @ tests/test.rs:194
0.129096 INFO  RX timeout 111 ms Δ 19 ms
└─ test::ping_pong @ tests/test.rs:205
0.148412 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.148426 INFO  Attempt: 1/100
└─ test::ping_pong @ tests/test.rs:185
0.148538 DEBUG RX with timeout 150 ms
└─ test::ping_pong @ tests/test.rs:194
0.157227 INFO  RX done
└─ test::ping_pong @ tests/test.rs:217
0.157268 INFO  Ok(FskPacketStatus {
    status: Status { mode: Ok(StandbyHse), cmd: Ok(Avaliable) },
    preamble_err: false,
    sync_err: false,
    addr_err: false,
    crc_err: false,
    length_err: false,
    abort_err: false,
    pkt_received: true,
    pkt_sent: false,
    rssi_sync: -43,
    rssi_avg: -43,
})
└─ test::ping_pong @ tests/test.rs:222
0.157418 INFO  received PONG
└─ test::ping_pong @ tests/test.rs:248
0.157432 INFO  (5/5) running `lora_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
0.170510 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:185
0.170540 DEBUG RX with timeout 128 ms
└─ test::ping_pong @ tests/test.rs:194
0.322062 INFO  RX timeout 151 ms Δ 23 ms
└─ test::ping_pong @ tests/test.rs:205
0.397029 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.397043 INFO  Attempt: 1/100
└─ test::ping_pong @ tests/test.rs:185
0.397072 DEBUG RX with timeout 120 ms
└─ test::ping_pong @ tests/test.rs:194
0.462416 INFO  RX done
└─ test::ping_pong @ tests/test.rs:217
0.462457 INFO  Ok(LoRaPacketStatus {
    status: Status { mode: Ok(StandbyHse), cmd: Ok(Avaliable) },
    rssi_pkt: -42,
    snr_pkt: 13,
    signal_rssi_pkt: -45,
})
└─ test::ping_pong @ tests/test.rs:223
0.462582 INFO  received PONG
└─ test::ping_pong @ tests/test.rs:248
0.462597 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
────────────────────────────────────────────────────────────────────────────────
  (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
    Blocking waiting for file lock on build directory
    Finished test [optimized + debuginfo] target(s) in 1.06s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-fbb389608b5f5d95)
(HOST) INFO  flashing program (26.26 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000007 INFO  (1/5) running `buffer_io`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
0.000405 INFO  Cycles 255B: 17933
└─ test::tests::buffer_io @ tests/test.rs:337
0.000514 INFO  Cycles 0B: 1186
└─ test::tests::buffer_io @ tests/test.rs:346
0.000536 INFO  (2/5) running `buffer_io_no_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
0.001931 INFO  Cycles 255B: 65826
└─ test::tests::buffer_io_no_dma @ tests/test.rs:359
0.002044 INFO  Cycles 0B: 1347
└─ test::tests::buffer_io_no_dma @ tests/test.rs:368
0.002066 INFO  (3/5) running `sleep_enter_exit`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
0.004147 INFO  74042 cycles to wake radio
└─ test::tests::sleep_enter_exit @ tests/test.rs:383
0.004185 INFO  (4/5) running `fsk_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
0.017521 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:185
0.017551 DEBUG RX with timeout 248 ms
└─ test::ping_pong @ tests/test.rs:194
0.144803 INFO  RX done
└─ test::ping_pong @ tests/test.rs:217
0.144844 INFO  Ok(FskPacketStatus {
    status: Status { mode: Ok(StandbyHse), cmd: Ok(Avaliable) },
    preamble_err: false,
    sync_err: false,
    addr_err: false,
    crc_err: false,
    length_err: false,
    abort_err: false,
    pkt_received: true,
    pkt_sent: false,
    rssi_sync: -40,
    rssi_avg: -40,
})
└─ test::ping_pong @ tests/test.rs:222
0.144994 INFO  received PING
└─ test::ping_pong @ tests/test.rs:237
0.153279 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.161545 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.169815 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.178084 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.186356 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.194627 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.202899 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.211166 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.219437 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.227711 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.227726 INFO  (5/5) running `lora_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
0.241166 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:185
0.241278 DEBUG RX with timeout 295 ms
└─ test::ping_pong @ tests/test.rs:194
0.394531 INFO  RX done
└─ test::ping_pong @ tests/test.rs:217
0.394572 INFO  Ok(LoRaPacketStatus {
    status: Status { mode: Ok(StandbyHse), cmd: Ok(Avaliable) },
    rssi_pkt: -40,
    snr_pkt: 14,
    signal_rssi_pkt: -43,
})
└─ test::ping_pong @ tests/test.rs:223
0.394697 INFO  received PING
└─ test::ping_pong @ tests/test.rs:237
0.458757 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.522799 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.586845 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.650897 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.714954 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.779011 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.843071 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.907131 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
0.971198 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
1.035270 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:116
1.035286 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:279
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error


9.4.8.Final

Upgrade Infinispan Version

Should we move the changes from https://github.com/infinispan/infinispan-spring-boot/pull/103/files to infinispan:boot-1.5.x ?

@diegolovison I don't think is necessary atm

Thanks @karesti


Kuzu: fix query 2

Query 2,  Person_knows_Person should be bidirectional.

Hi, edges in the kuzu implementation are inserted both ways: https://github.com/ldbc/lsqb/blob/main/kuz/load.py#L39-L42
Hence, there is no need to query them with direction in mind.

😭 ,my bad!


TabView appears to not be implementing the Selection pattern

I copied two TabView samples out of the Xaml Controls Gallery. Accessibility Insights for Windows identified this as a problem.
The following accessibility issue needs investigation.
App: WinUI_2-4_Test
Element path: tab ''
Issue Details: An element of the given ControlType must support the Selection pattern. Section 508 502.3.10
How To Fix: 1. Make sure the element has the appropriate ControlType property for its function.
2. If the current ControlType is correct, modify the element to support the Selection pattern.
This accessibility issue was found using Accessibility Insights for Windows, a tool that helps debug and find accessibility issues earlier. Get more information and download this tool at https://aka.ms/AccessibilityInsights.

@teaP  FYI

@teaP I assume you will be looking into this issue? Or would you like me to/would you be fine with me looking into this? @ranjeshj FYI

@chingucoding go for it. TabView uses ListView under the covers which should be implementing the selection pattern. Perhaps there is some wire up missing.

The list inside tabview (the tab strip, if you will) has the selection pattern. I'm not certain if that is good enough or if there is some other adjustment that should be made.


DGB transactions

Overview
Implement DigiByte transactions and broadcasting
Outcome
Fully functioning DigiByte transactions with tx signing and broadcasting

closed in #25


[skip ci] Fix onnx/models URLs

These are broken in CI: https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/2500/pipeline/275
The upstream changed their default branch from master -> main which broke the links used in these tests. This pins to a specific commit (the latest one at the time of filing this PR).

It'd be nice to re-host all these assets (others are used that could go offline at any time) in S3 or some repo like tlcpack/ci-data


Yosys can't parse port renames in module declaration

Steps to reproduce the issue
This file compiles successfully in vivado
module foo (
         .another_name_for_a(a),
	 .another_name_for_b(b),
	 c
);

input a;
input b;
output c;

assign c = a ^ b;

endmodule

Expected behavior
I would expect to parse correctly, as specified in the verilog grammar:

(source: https://www.verilog.com/VerilogBNF.html)
and giving the following elaborated result (this is from Vivado):

Actual behavior
 Yosys 0.17+41 (git sha1 c525b5f91, gcc 10.3.0-1ubuntu1~20.04 -fPIC -Os)

yosys> read_verilog module-decl-rename.v
1. Executing Verilog-2005 frontend: module-decl-rename.v
Parsing Verilog input from `module-decl-rename.v' to AST representation.
module-decl-rename.v:2: ERROR: syntax error, unexpected TOK_ID, expecting '.'

I think it is because of this rule in verilog_lexer.l:
[a-zA-Z_$][a-zA-Z0-9_$\.]* {
	yylval->string = new std::string(std::string("\\") + yytext);
	return TOK_ID;
}

The rule should match the literal dot only in the middle of the token, not at the beginning of the token

There is actually no lexer rule for this syntax:
 Yosys 0.17+41 (git sha1 c525b5f91, gcc 10.3.0-1ubuntu1~20.04 -fPIC -Os)

-- Running command `read_verilog bug.v' --

1. Executing Verilog-2005 frontend: bug.v
Parsing Verilog input from `bug.v' to AST representation.
--(end of buffer or a NUL)
--accepting rule at line 142 ("`file_push "bug.v"")
--accepting rule at line 592 ("
")
--accepting rule at line 205 ("module")
--accepting rule at line 592 (" ")
--accepting rule at line 425 ("foo")
--accepting rule at line 592 (" ")
--accepting rule at line 596 ("(")
--accepting rule at line 592 ("
")
--accepting rule at line 592 (" ")
--accepting rule at line 592 (" ")
--accepting rule at line 592 (" ")
--accepting rule at line 592 (" ")
--accepting rule at line 592 (" ")
--accepting rule at line 592 (" ")
--accepting rule at line 592 (" ")
--accepting rule at line 592 (" ")
--accepting rule at line 592 (" ")
--accepting rule at line 596 (".")
--accepting rule at line 425 ("another_name_for_a")
bug.v:2: ERROR: syntax error, unexpected TOK_ID, expecting '.'

because the rule that reads the "." is a default rule:

My fix would give the following result:


Changes to compile on OSX

In OSX, 'endian.h' is now in 'machine/endian.h' and use 'libkern/OSByteOrder.h'.
Fix is similar to the issue n https://github.com/br101/horst/issues/3

I believe I have addressed your concerns. Please have a look


Slack notification fails to notify

Similar to the previous issue I raised, the slack notification is no longer working. I have used it in the past and received notifications, however today there was a bestbuy drop and I was not notified. Looking through the log, I can see that I should have been notified, but nothing appeared on slack. Further testing continues this trend, even though the slack webhook was correct before and has not changed.
Here I attach the log using an in stock item to show that it is occurring, but no slack notifications are arriving.
bestbuy_rtx_3070 - Copy (2).txt

This is also occuring for newegg, so I believe the problem is universal, not just a problem for the puppeteer usage on bestbuy


Women in War

Your checklist for this pull request
Author name
Author:
cupcakes
About your game
What is your game about?
My game is about women's roles during the world wars. They were able to gain some rights and open new doors by entering the workforce while the men had gone to fight int he war. But when the soldiers returned, women were usually forced to give up their jobs or settle for low-paying ones. My game aims to depict their story. A player moves the crown (symbolizes the metamorphosis of women from fragile princesses to queens running a kingdom) around to pick up rights and opportunities. The player must pick up all items available in order to advance to the next part of the story.
How do you play your game?
Press WAD to move, W captures items, A & D move the crown left and right.
Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[x] The game is placed in the in the /games directory.
[x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x] The game runs without errors.
[x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x] The game name is not the same as the others from gallery

Image (If an image is used)

[x] The image is in the /games/img directory.
[x] The name of the image matches the name of your file.

I can do that!

Oopsie ;) I'll fix that! Thank you so much for helping me


celcius to fahrenheit and fahrenheit to celcius in c and c++

I am a GSSOC participant and would like to work on this issue

You can assign the Issue for yourself by using the '/assign' command. Make sure The algorithm/ data structure you are trying to add doesn't already exist. read the Doc before you proceed.

Need to add a description and your approach. Thanks, Closing as of now.


Cannot find name 'figma'.

When I compile ts via tsc code.ts i get
code.ts:9:1 - error TS2304: Cannot find name 'figma'.

9 figma.showUI(__html__);
  ~~~~~

code.ts:9:14 - error TS2304: Cannot find name '__html__'.

9 figma.showUI(__html__);
               ~~~~~~~~

code.ts:14:1 - error TS2304: Cannot find name 'figma'.

14 figma.ui.onmessage = msg => {
   ~~~~~

code.ts:18:18 - error TS2304: Cannot find name 'SceneNode'.

18     const nodes: SceneNode[] = [];
                    ~~~~~~~~~

code.ts:20:20 - error TS2304: Cannot find name 'figma'.

20       const rect = figma.createRectangle();
                      ~~~~~

code.ts:23:7 - error TS2304: Cannot find name 'figma'.

23       figma.currentPage.appendChild(rect);
         ~~~~~

code.ts:26:5 - error TS2304: Cannot find name 'figma'.

26     figma.currentPage.selection = nodes;
       ~~~~~

code.ts:27:5 - error TS2304: Cannot find name 'figma'.

27     figma.viewport.scrollAndZoomIntoView(nodes);
       ~~~~~

code.ts:32:3 - error TS2304: Cannot find name 'figma'.

32   figma.closePlugin();
     ~~~~~

Found 9 errors.

Could you please fix it?
I installed the typings. My tsconfig looks like this:
  "compilerOptions": {
    "target": "es6",
    "lib": ["es6"],
    "typeRoots": [
      "./node_modules/@types",
      "./node_modules/@figma"
    ]
  }
}```

Simply run tsc instead of tsc code.ts, otherwise you need to also specify your tsconfig.json, so the full explicit command would be tsc code.ts -p tsconfig.json.

Simply run tsc instead of tsc code.ts, otherwise you need to also specify your tsconfig.json, so the full explicit command would be tsc code.ts -p tsconfig.json.

Thanks a lot, that fixed the issue. I'm surprised I'm the first who posted in "issues"

Simply run tsc instead of tsc code.ts, otherwise you need to also specify your tsconfig.json, so the full explicit command would be tsc code.ts -p tsconfig.json.

thank you so much I was getting crazy!


Update plugins for BP 9.1.1 testing

Update the following plugins (first on msudev, then on hcdev):
msudev:

[x] buddypress 9.0.0 to 9.1.1
[x] buddypress-group-email-subscription 3.7.2 to 4.0.0
[x] classic-editor 1.6 to 1.6.2
[x] buddypress-restrict-group-creation 1.1.1 to 1.1.2
[x] buddypress-sitewide-activity-widget 1.3.2 to 1.3.5
[ ] elementor 3.4.2 to 3.4.4
[x] events-manager <IP_ADDRESS> to 5.11
[x] akismet 4.1.9 to 4.1.12
[x] autoptimize 2.8.3 to 2.9.2

hcdev:

[x] buddypress 9.0.0 to 9.1.1
[x] buddypress-group-email-subscription 3.7.2 to 4.0.0
[x] classic-editor 1.6 to 1.6.2
[x] buddypress-restrict-group-creation 1.1.1 to 1.1.2
[x] buddypress-sitewide-activity-widget 1.3.2 to 1.3.5
[x] elementor 3.4.2 to 3.4.4
[x] events-manager <IP_ADDRESS> to 5.11
[x] akismet 4.1.9 to 4.1.12
[x] autoptimize 2.8.3 to 2.9.2

Updating elementor to 3.4.4 caused a fatal error on msudev.

Was able to update elementor on hcdev without issue.

Tried updating elasticpress on msudev, caused a fatal error. Going to hold off on that one for now.


High CPU usage when +3 sessions are open

I'm using macOS HighSierra, when open 3 terminals and a new session in each one of them (simply run tmux) the CPU spikes and the terminal usage keeps at 100% even though nothing is being used.
I tested with bash as the shell but I've seen the same behavior with fish and zsh. Tried with iTerm2 too.
I also tested with the unmodified tmux.conf/tmux.conf.local files.
Finally, I tested with an Empty tmux file and I can open as many terminals I want and the CPU keeps in check with low usage.

Hello @danielporto,
What do you exactly call "3 terminals"? 3 instances of Terminal.app, each attached to a different tmux session?

Yep, 3 instances of Terminal.app or iTerm2 or a mix of them. each one creating a new tmux session.
opening Bash (or fish or zsh)
Unmodified tmux.conf.local and tmux.conf

Well, what's going to happen with 3 tmux client running is that each of them is going to refresh its status line at a regular basis.
Each time the status bar refreshes itself, things are happening: typically cut -c3- ~/.tmux.conf |sh -s <some function name> runs and this creates activity.
If you do
$ tmux set -g status-left ''
$ tmux set -g status-right ''

And if CPU spikes disappear, it will validate the activity is caused by launching shell processes when refreshing the status bar

Indeed, the commands (specially the second one) eliminate the CPU spikes along side all the bar features.
I was using the latest version of tmux. 2.9a then upgraded to HEAD (3.0) but the problem shows in both.

You may want to try removing segments in your ~/.tmux.conf.local copy to see which causes the most activity

I've  removed the tmux.conf.local.
still see CPU spikes :-(

Not removing ~/.tmux.conf.local, editing it and altering the content of tmux_conf_theme_status_left and tmux_conf_theme_status_right

When disabling tmux_conf_theme_status_right, tmux_conf_theme_status_left is responsible for about 33% of cpu usage after 3 terminals open.
when disabling tmux_conf_theme_status_left (let the string ' ❐ #S | ' only) , tmux_conf_theme_status_right enabled, hits 100% after the 4th terminal open.
the the following minimum settings:
tmux_conf_theme_status_left=' ❐ #S | '
tmux_conf_theme_status_right='%R , %d %b | #{username}#{root} | #{hostname} '
CPU is in normal state, with mostly low CPU usage even with 8 Terminal.app open all with new sessions

I will keep the battery information and uptime disabled.
Thanks.

Thanks the tests. I'm keeping this open so that I can investigate further and hopefully find a way to reduce the CPU usage

I can't seem to reproduce the CPU spikes here 🤔
So there are 2 things:

how often the status bar gets refreshed, triggering computations
how heavy these computations are

Can you please make the following experiment which consists in launching tmux with stock / empty configuration then alter status-right to trigger computations upon status bar refresh. To better observe CPU usage, close other tmux sessions, web browser (here Chromes does a lot in the background), ...
$ tmux -f /dev/null

Then create multiple sessions, say 4.
Then open 4 terminal instances and in each attach to tmux
$ tmux attach

Now. open a 5th terminal instance and do
$ touch /tmp/log.txt
$ tail -f /tmp/log.txt

Now go back to any of the terminals in which you attached to tmux and do
$ tmux set -g status-right '#(date +%%s >> /tmp/log.txt)'

You should see 4 entries in /tmp/log.txt with the same timestamp (it's the 4 tmux clients refreshing their status bar) then entries shouldn't appear in packets of 4 and should appear way less often (roughly every 10 - 15s).
Then you can try replacing the date +%%s command by sysctl -q -n kern.boottime | awk -F'[ ,:]+' '{ print $4 }' which is what I use for uptime computations. And see whether calling sysctl makes you observe higher CPU usage.
Thanks!

Sure, thanks, I will do that over the weekend and get back with the results. Thanks for your patience.

@danielporto 👋
Did you find the time to make more tests by chance?

Hello @gpakosz , Sorry for the long delay. Since disabling stuff worked for me this test has to go down the todo list. But now I did it.
And...
CPU usage for both commands is barely minimum. Nothing changed even with 5 tmux sessions in 5 different iterm + 1 to monitor the log file (excerpt at the end).
Btw, I updated tmux.conf and tmux.conf.local to the latest version and the problem remains. >.<
I also formatted my laptop. It's a brand new system. No macOS Mojave.
output:
1561714261
1561714261
1561714261
1561714261
1561714261
1561714263
1561714264
1561714264
1561714266
1561714275
1561714278
1561714279
1561714279
...
1561714461
1561714470
1561714473
1561714474
1561714474
1561714476
1561714476
{ sec =<PHONE_NUMBER>, usec = 957101 } Wed Jun 26 10:33:57 2019
{ sec =<PHONE_NUMBER>, usec = 957101 } Wed Jun 26 10:33:57 2019
{ sec =<PHONE_NUMBER>, usec = 957101 } Wed Jun 26 10:33:57 2019
{ sec =<PHONE_NUMBER>, usec = 957101 } Wed Jun 26 10:33:57 2019
{ sec =<PHONE_NUMBER>, usec = 957101 } Wed Jun 26 10:33:57 2019
{ sec =<PHONE_NUMBER>, usec = 957101 } Wed Jun 26 10:33:57 2019
{ sec =<PHONE_NUMBER>, usec = 957101 } Wed Jun 26 10:33:57 2019
{ sec =<PHONE_NUMBER>, usec = 957101 } Wed Jun 26 10:33:57 2019

Hello @danielporto
The experiment's goal is for you to have a sense of whether tmux updates the status line too often.
My expectation is that status line should be updated every x seconds, where x corresponds to the value of status-interval.
Or the status line should be updated when you switch pane ← this is because I use #D as an argument to some of the helpers that implement the custom variables (e.g. #{root}, #{username}, #{hostname}, ...).
In any case I have ideas on 2 fronts:

throttle helpers invocations (#{uptime_y}, #{uptime_d}, #{uptime_m}, #{battery_status}, ...)
make each helper consume less CPU

Which I'll try to address soon 🤞

There's the optimizations branch in which I started optimizing

Thank you.
On Sun, Sep 22, 2019, 1:43 PM Gregory Pakosz<EMAIL_ADDRESS>wrote:

There's the optimizations branch in which I started optimizing
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gpakosz/.tmux/issues/247?email_source=notifications&email_token=AAMTRG6SI4GKKTPCYSYPD5LQK5SA7A5CNFSM4HNYLARKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7JFQSI#issuecomment-533878857,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMTRG33CLULFVVCKS24UALQK5SA7ANCNFSM4HNYLARA
.

👋
I'm close to land the optimizations branch, those following this issue can you please give it a try?
$ cd ~/.tmux
$ git stash
$ git fetch -p
$ git checkout optimizations
$ git reset --hard origin/optimizations

Then hit <prefix> + r to reload the configuration.
Thanks! 🙏

Hi, I'm seeing the same issue even with just 2 terminals open, the top processes are:
sh -s _uptime
sh -s _battery
sh -s _hostname ....
sh -s _username ....
sh -s _root ....

is there a way to configure how often to update the status bar?

Hi, I'm seeing the same issue even with just 2 terminals open, the top processes are:
sh -s _uptime
sh -s _battery
sh -s _hostname ....
sh -s _username ....
sh -s _root ....

is there a way to configure how often to update the status bar?

@luisdavim Are you sure you checked out the latest optimizations branch and you reloaded your configuration?

Oh, I wasn't using the optimizations branch but once I've switched to that and killed all my terminals I was unable to open new terminals as tmux would crash an the terminal would close itself...

@luisdavim I'm surprised anything in my configuration would make tmux crash. We can discuss this again when I merge the branch

This is my tmux.conf.local: https://github.com/luisdavim/dotfiles/blob/master/files/shell/tmux.conf.local (it's not that different from the one in your repo)
and I'm using the oh-my-zsh tmux plugin to start tmux https://github.com/luisdavim/dotfiles/blob/master/files/shell/zsh/zshrc

hi, any updates on this? When will the optimisations brach be merged?

Using the optimizations for a while and it is great! Please merge it.


[Bug]: Feedback loop interface has has misnamed property...

Language
Javascript/Typescript
Version
1.6.0
Description
The interface FeedbackLoopData states the data coming back is in the actionValue property, but looks like it should be actionType (or the data returned is incorrect).
Not sure if the response contains the incorrect property name, or if the interface is incorrect... suspect the latter...
  import {
    Application,
    ActionPlanner,
    DefaultConversationState,
++  FeedbackLoopData,
    Memory,
    OpenAIModel,
    PromptManager,
    TurnState
  } from "@microsoft/teams-ai";

  // ... omitted for brevity

  const app = new Application({
    storage,
    ai: {
      planner,
++    enable_feedback_loop: true,
    },
  });

  // ... omitted for brevity

++// PATCH to fix interface bug:
++// > FeedbackLoopData expects `actionValue` but data returned is in `actionType`
++export interface FeedbackLoopDataPatch extends FeedbackLoopData {
++  actionType: {
++    reaction: string;
++    feedback: string;
++  };
++}
++app.feedbackLoop(async (context: TurnContext, state: TurnState, feedbackLoopData: FeedbackLoopData) => {
++  // what do you get back normally... rut-ro... you get `actionType`, not `actionValue`
++  console.log('Feedback loop data:', feedbackLoopData);
++
++  // patch the bug with custom interface from above
++  const fbData = feedbackLoopData as FeedbackLoopDataPatch;
++  if (fbData.actionType?.reaction === 'like') {
++    console.log(`👍 ${fbData.actionType?.feedback}`);
++  } else {
++    console.log(`👎 ${fbData.actionType?.feedback}`);
++  }
++});

Console output from above test:
Feedback loop data: {
  actionName: 'feedback',
  actionType: { reaction: 'like', feedback: 'rut ro' },
  replyToId: undefined
}
👍 rut to

Reproduction Steps

Create simple chat bot (VSC TTK > New App > Custom Engine Agent > Basic AI Chat Bot
Implement feedback using the steps above.
Add necessary Azure AI deployment details to ./env/.env.testtool.user
Run in Teams Test Test
Send message to get bot to respond
Add reaction
Look at console that validates what's in the description above

Hi @andrewconnell, I spoke with the team working on feedback loop and they have confirmed that the data being passed is actionValue not actionType:

I'm going to close this issue, but if you could please reproduce the problem and share the data response with the repro I will re-open the issue.


IntegrityError when deleting plugin, Key is not present in table "cms_cmsplugin".

When I delete a plugin in my project, django throws an IntegrityError because the CMSPlugin relation cannot be found or has already been deleted.
Following this old issue, https://github.com/divio/django-cms/issues/2197, I'm unable to delete the plugin from the command line, by either deleting the plugin instance or the CMSPlugin instance first because the same error is thrown.
I'm using django-cms==3.2.5 and Django==1.9.6.
Any idea on how to remedy the issue?
Plugin Model:
from cms.models import Page

@python_2_unicode_compatible
class OfferingPlugin(CMSPlugin):
    image = VersatileImageField(upload_to=unique_upload, ppoi_field='ppoi')
    ppoi = PPOIField()
    title = models.CharField(max_length=50)
    subtitle = models.CharField(max_length=140)
    link_copy = models.CharField(max_length=20)
    link_address = models.ForeignKey(Page, blank=True, null=True, on_delete=models.CASCADE)

    def __str__(self):
        return "Offering Plugin: {}, {}".format(self.title, self.image)

Stack Trace:
Internal Server Error: /admin/offering/offeringplugin/
Traceback (most recent call last):
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/core/handlers/base.py", line 149, in get_response
    response = self.process_exception_by_middleware(e, request)
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/core/handlers/base.py", line 147, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/contrib/admin/options.py", line 541, in wrapper
    return self.admin_site.admin_view(view)(*args, **kwargs)
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/utils/decorators.py", line 149, in _wrapped_view
    response = view_func(request, *args, **kwargs)
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/views/decorators/cache.py", line 57, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/contrib/admin/sites.py", line 244, in inner
    return view(request, *args, **kwargs)
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/reversion/admin.py", line 238, in changelist_view
    return super(VersionAdmin, self).changelist_view(request, context)
  File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/contextlib.py", line 24, in __exit__
    self.gen.next()
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/reversion/admin.py", line 89, in _create_revision
    yield
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/transaction.py", line 223, in __exit__
    connection.commit()
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/backends/base/base.py", line 242, in commit
    self._commit()
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/backends/base/base.py", line 211, in _commit
    return self.connection.commit()
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/utils.py", line 95, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/backends/base/base.py", line 211, in _commit
    return self.connection.commit()
IntegrityError: insert or update on table "offering_offeringplugin" violates foreign key constraint "offering_offering_cmsplugin_ptr_id_9a9e9998_fk_cms_cmsplugin_id"
DETAIL:  Key (cmsplugin_ptr_id)=(1) is not present in table "cms_cmsplugin".

@agconti
Thanks for reporting.
Do you mind removing reversion from your INSTALLED_APPS? Just for the sake of testing.
Then try and reproduce the issue.

@czpython thank you for taking a look.
I removed reversion from my installed apps and reproduced the issue. I also cleared my local db, migrated and reproduced the issue again.

@agconti This is quite strange. I'll try to reproduce tomorrow.
In the meantime, some questions :)
Which database are you using?
What are the exact steps you're doing to reproduce the problem?

@czpython I'm using Postgresql v9.5.2.
Here's the steps to reproduce the error form deleteing both the CMSPlugin and the OfferingPlugin:
Setup:
from cms.models import CMSPlugin
from offering.models import OfferingPlugin

offering_plugin = OfferingPlugin.objects.all()[0]
offering_plugin_cms_id = offering_plugin.cmsplugin_ptr_id
# >>> offering_plugin.cmsplugin_ptr_id
# =>  1

related_cms_plugin = CMSPlugin.objects.get(pk=offering_plugin_cms_id)
# >>> CMSPlugin.objects.get(pk=offering_plugin_cms_id)
# <CMSPlugin: 1>

CMSPlugin Delete:
In [16]: related_cms_plugin.delete()

---------------------------------------------------------------------------
IntegrityError                            Traceback (most recent call last)
<ipython-input-16-1f8ee41efd4e> in <module>()
----> 1 related_cms_plugin.delete()

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/cms/models/pluginmodel.pyc in delete(self, no_mp, *args, **kwargs)
    481             Model.delete(self, *args, **kwargs)
    482         else:
--> 483             super(CMSPlugin, self).delete(*args, **kwargs)
    484
    485     def get_action_urls(self, js_compat=True):

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/treebeard/models.pyc in delete(self)
    504     def delete(self):
    505         """Removes a node and all it's descendants."""
--> 506         self.__class__.objects.filter(pk=self.pk).delete()
    507
    508     def _prepare_pos_var(self, pos, method_name, valid_pos, valid_sorted_pos):

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/treebeard/mp_tree.pyc in delete(self)
     96         if toremove:
     97             qset = get_result_class(self.model).objects.filter(reduce(operator.or_, toremove))
---> 98             super(MP_NodeQuerySet, qset).delete()
     99
    100

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/models/query.pyc in delete(self)
    598         collector = Collector(using=del_query.db)
    599         collector.collect(del_query)
--> 600         deleted, _rows_count = collector.delete()
    601
    602         # Clear the result cache, in case this QuerySet gets reused.

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/models/deletion.pyc in delete(self)
    314                     for obj in instances:
    315                         signals.post_delete.send(
--> 316                             sender=model, instance=obj, using=self.using
    317                         )
    318

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/transaction.pyc in __exit__(self, exc_type, exc_value, traceback)
    221                     # Commit transaction
    222                     try:
--> 223                         connection.commit()
    224                     except DatabaseError:
    225                         try:

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/backends/base/base.pyc in commit(self)
    240         self.validate_thread_sharing()
    241         self.validate_no_atomic_block()
--> 242         self._commit()
    243         # A successful commit means that the database connection works.
    244         self.errors_occurred = False

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/backends/base/base.pyc in _commit(self)
    209         if self.connection is not None:
    210             with self.wrap_database_errors:
--> 211                 return self.connection.commit()
    212
    213     def _rollback(self):

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/utils.pyc in __exit__(self, exc_type, exc_value, traceback)
     93                 if dj_exc_type not in (DataError, IntegrityError):
     94                     self.wrapper.errors_occurred = True
---> 95                 six.reraise(dj_exc_type, dj_exc_value, traceback)
     96
     97     def __call__(self, func):

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/backends/base/base.pyc in _commit(self)
    209         if self.connection is not None:
    210             with self.wrap_database_errors:
--> 211                 return self.connection.commit()
    212
    213     def _rollback(self):

IntegrityError: insert or update on table "offering_offeringplugin" violates foreign key constraint "offering_offering_cmsplugin_ptr_id_9a9e9998_fk_cms_cmsplugin_id"
DETAIL:  Key (cmsplugin_ptr_id)=(1) is not present in table "cms_cmsplugin".

OfferingPlugin Delete:
In [15]: offering_plugin.delete()

---------------------------------------------------------------------------
IntegrityError                            Traceback (most recent call last)
<ipython-input-15-e4f2a078053a> in <module>()
----> 1 offering_plugin.delete()

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/cms/models/pluginmodel.pyc in delete(self, no_mp, *args, **kwargs)
    481             Model.delete(self, *args, **kwargs)
    482         else:
--> 483             super(CMSPlugin, self).delete(*args, **kwargs)
    484
    485     def get_action_urls(self, js_compat=True):

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/treebeard/models.pyc in delete(self)
    504     def delete(self):
    505         """Removes a node and all it's descendants."""
--> 506         self.__class__.objects.filter(pk=self.pk).delete()
    507
    508     def _prepare_pos_var(self, pos, method_name, valid_pos, valid_sorted_pos):

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/treebeard/mp_tree.pyc in delete(self)
     96         if toremove:
     97             qset = get_result_class(self.model).objects.filter(reduce(operator.or_, toremove))
---> 98             super(MP_NodeQuerySet, qset).delete()
     99
    100

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/models/query.pyc in delete(self)
    598         collector = Collector(using=del_query.db)
    599         collector.collect(del_query)
--> 600         deleted, _rows_count = collector.delete()
    601
    602         # Clear the result cache, in case this QuerySet gets reused.

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/models/deletion.pyc in delete(self)
    314                     for obj in instances:
    315                         signals.post_delete.send(
--> 316                             sender=model, instance=obj, using=self.using
    317                         )
    318

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/transaction.pyc in __exit__(self, exc_type, exc_value, traceback)
    221                     # Commit transaction
    222                     try:
--> 223                         connection.commit()
    224                     except DatabaseError:
    225                         try:

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/backends/base/base.pyc in commit(self)
    240         self.validate_thread_sharing()
    241         self.validate_no_atomic_block()
--> 242         self._commit()
    243         # A successful commit means that the database connection works.
    244         self.errors_occurred = False

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/backends/base/base.pyc in _commit(self)
    209         if self.connection is not None:
    210             with self.wrap_database_errors:
--> 211                 return self.connection.commit()
    212
    213     def _rollback(self):

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/utils.pyc in __exit__(self, exc_type, exc_value, traceback)
     93                 if dj_exc_type not in (DataError, IntegrityError):
     94                     self.wrapper.errors_occurred = True
---> 95                 six.reraise(dj_exc_type, dj_exc_value, traceback)
     96
     97     def __call__(self, func):

/Users/conti/dev/my-app/env/lib/python2.7/site-packages/django/db/backends/base/base.pyc in _commit(self)
    209         if self.connection is not None:
    210             with self.wrap_database_errors:
--> 211                 return self.connection.commit()
    212
    213     def _rollback(self):

IntegrityError: insert or update on table "offering_offeringplugin" violates foreign key constraint "offering_offering_cmsplugin_ptr_id_9a9e9998_fk_cms_cmsplugin_id"
DETAIL:  Key (cmsplugin_ptr_id)=(1) is not present in table "cms_cmsplugin".

Also @czpython, its worth mentioning that I'm having this issue with several plugins. I've only included the OfferingPlugin here so that we could zero in a single representative problem.

@czpython, I found that I needed to remove admin.py's that us a reversion admin in addition to removing reversion from my INSTALLED_APPS.
Once they're all removed, the problem no longer occurs. Do you have any insight on why this might be happening with Django-cms?

@agconti are you using aldryn-reversion anywhere? (most aldryn addons use it).

I was using django-reversion==1.10.1.  Should I be using  aldryn-reversion instead?

@agconti Aldryn reversion is an extension of django-reversion to encapsulate cms specific reversion logic for cms apps. The reason I mention it is because if you do have it in your installed apps but not reversion then it still uses it. But seems like this is not the case.
I'm very intrigued though as to how it was still failing with the reversion out of installed apps.
Just to be sure, are you positive that the error stopped only when removing the admin.py?

@czpython yes.
That's why I originally reported that django-reversion must not be related; because I removed it from my installed apps when I tested. Later, Just to exhaust all testing possibilities and because you mentioned that django-reversion might be the issue,  I removed it and the admin.pys and tried again.

I did many tests and I figure out that the problem is when have null=True inside ForeignKey. Django don't to do CASCADE Operation even passing on_delete=models.CASCADE.
link_address = models.ForeignKey(Page, blank=True, null=True, on_delete=models.CASCADE) -> dont work CASCADE
link_address = models.ForeignKey(Page, on_delete=models.CASCADE) -> will work CASCADE
I believe this is bug in Django.

UPDATE: I did more tests and i figure out that my constraint was without the options Deferrable and Deferred assigned, because my current DB PostgreSQL was migrate from MySQL.
More information about this options on the link bellow:
http://stackoverflow.com/questions/16323236/deferrable-check-constraint-in-postgresql
I hope this can help.


Ferroli Titano Twin Water not detected anymore after last update.

Hello everyone,
last integration's update broked the detection and support of "Ferroli Titano Twin" that is now suggested as abalon_bcm700d_curtain.

This is not a bug report.  At least include logs along with it, otherwise it is just a negative comment


Gallery selection is stuck when first photo was not granted permission

Describe the bug
The gallery view automatically selects the first photo and shows preview.  If the first photo was not given permission by the user,
it shows up a blank on the YPPicker gallery and it tries to show the preview of this.  This is where the picker view gets stuck.  User cannot select on a different picker.  It also happens when the users selects a blank space (OS did not give permission for access) item.
To Reproduce
Steps to reproduce the behavior:

Go to YP image picker
OS will prompt for "Select More Photos" and "Keep Current Selection"
Unselect the first photo (do not give access) and click done
See error (screenshot attached)

Expected behavior
YP Picker should be able to handle photos that was not given permission (better the gallery only shows images that was given perimission
Screenshots

Environment (please complete the following information):

Device: iPhone 6s/Simulator
OS: 14
Xcode Version 12
Swift Version 4.2

Installation Type

Carthage
Cocoapods
Manual

Additional context
Add any other context about the problem here.

+1


Warning prop type: the prop 'searchable' is marked required in 'RightElement', but it's value is 'null'

I am using "react-native": "0.48.4",

Update material ui to the last version. The warning will disappear

Thank you ...
The warning has gone


Clarify, reformat, and add to documentation guides

This is quite a big PR so I can squash it if requested 😄.
I've gone through all the guides in the documentation directory and standardised them to a regular format. I've further clarified many of the sections, and added new sections in exceptions, blueprints, deploying, contributing, getting started, and middleware.
Thanks to the efforts of previous contributors, the docs were already in good shape. My alterations are designed to create a more cohesive learning experience, and for this reason I have re-ordered the table of contents and added links between each guide to creating a "reading path". 🎆

I am going to squash and merge this though


strings in predicates failures

There's two invocations here that fail differently, but I think one bug may be responsible.
To start with, this works:
# bpftrace -e 'tracepoint:syscalls:sys_enter_write /pid == 23506/ { printf("hi\n"); }'
Attaching 1 probe...
hi
hi
hi

That's the PID of a bash shell. Matching on the process name, and including -v:
# bpftrace -v -e 'tracepoint:syscalls:sys_enter_write /comm == "bash"/ { printf("hi\n"); }'
Attaching 1 probe...

Error log:
0: (bf) r6 = r1
1: (b7) r1 = 0
2: (7b) *(u64 *)(r10 -16) = r1
3: (7b) *(u64 *)(r10 -24) = r1
4: (bf) r7 = r10
5: (07) r7 += -24
6: (bf) r1 = r7
7: (b7) r2 = 16
8: (85) call bpf_get_current_comm#16
9: (bf) r1 = r10
10: (07) r1 += -5
11: (b7) r2 = 8
12: (bf) r3 = r7
13: (85) call bpf_probe_read#4
invalid stack type R1 off=-5 access_size=8

Error loading program: tracepoint:syscalls:sys_enter_write

Ok, looks like an alignment issue of the "bash" string.
Now changing the action performed:
# bpftrace -e 'tracepoint:syscalls:sys_enter_write /comm == "bash"/ { printf("%d\n", 123); }'
Attaching 1 probe...
^C

This time it compiles, but no events fire.

The problem doesn't seem to be restricted to predicates, using if (comm == "bash") doesn't work as well.

I'm hitting this as well. Another test case (because more is always better):
$ sudo ./build/src/bpftrace -e 'tracepoint:syscalls:sys_enter_read /comm == "a.out"/ { printf("hit\n") }'
chdir(/lib/modules/4.18.9-200.fc28.x86_64/build): No such file or directory
definitions.h:9:3: error: unknown type name 'u64'
definitions.h:11:3: error: unknown type name 'size_t'
Attaching 1 probe...
Error loading program: tracepoint:syscalls:sys_enter_read (try -v)

$ sudo ./build/src/bpftrace -e 'tracepoint:syscalls:sys_enter_read /comm == "a.out"/ { printf("hit %d\n", args->fd) }'
chdir(/lib/modules/4.18.9-200.fc28.x86_64/build): No such file or directory
definitions.h:9:3: error: unknown type name 'u64'
definitions.h:11:3: error: unknown type name 'size_t'
Attaching 1 probe...
^C

Super annoying bug, working on this now.

Yes, this is super annoying so a fix would be good to see soon. We do need more than this though for pattern matching in a predicate. I  often need to do the equivalent of 't:syscall:whatever/comm == "hhvm*" as I am interested in a range of processes whose name begins with "hhvm". In DTrace you could do something like /strstr(execname, "hhvm") != NULL/ if my memory serves me right.

By the error message, it seems comm is trying to do a jump too far.

@tyroguru this seems like a useful feature. Do you mind opening another issue for it?

:+1:


Support DevContainers - Cosmos version

User story
As a software engineer / code contributer, I want to be able to use dev container with vscode so that developer environment will be easier to set up
Acceptance criteria

When I do 'run  in a container' I am able to run the code (with cosmos db) and debug it. without installing additional components locally

We aren't aware of a way that we could do this in cosmos so going to close


Reduction in 99th percentile PictureCache usage and increase in 90th percentile and average.

99th percentile: https://flutter-flutter-perf.skia.org/e/?begin=1649109790&end=1649193450&keys=X5b16b3afaa91c5bb314317bf821f59dd&num_commits=50&request_type=1&xbaroffset=28200
90th percentile: https://flutter-flutter-perf.skia.org/e/?begin=1649109790&end=1649193450&keys=X75e3a22ea8969a496224318a78de08e6&num_commits=50&request_type=1&xbaroffset=28200
This is attributed to https://github.com/flutter/flutter/commit/647044c969af6d7ecf08057683731b8f23b17572 but doesn't seem like this commit or the changes around it would cause this to happen.

parent issue closed. see comments there.


Getting ReferenceError: process is not defined when attempting to import Schema into Astro React component

Environment information
System:
  OS: macOS 14.4.1
  CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Memory: 75.01 MB / 16.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node
  Yarn: undefined - undefined
  npm: 10.2.1 - ~/.nvm/versions/node/v18.18.2/bin/npm
  pnpm: 8.12.1 - /usr/local/bin/pnpm
NPM Packages:
  @aws-amplify/auth-construct: 1.2.0
  @aws-amplify/backend: 1.0.4
  @aws-amplify/backend-auth: 1.1.1
  @aws-amplify/backend-cli: 1.2.2
  @aws-amplify/backend-data: 1.1.0
  @aws-amplify/backend-deployer: 1.0.3
  @aws-amplify/backend-function: 1.3.0
  @aws-amplify/backend-output-schemas: 1.1.0
  @aws-amplify/backend-output-storage: 1.0.2
  @aws-amplify/backend-secret: 1.0.0
  @aws-amplify/backend-storage: 1.0.4
  @aws-amplify/cli-core: 1.1.1
  @aws-amplify/client-config: 1.1.2
  @aws-amplify/deployed-backend-client: 1.2.0
  @aws-amplify/form-generator: 1.0.0
  @aws-amplify/model-generator: 1.0.3
  @aws-amplify/platform-core: 1.0.4
  @aws-amplify/plugin-types: 1.1.0
  @aws-amplify/sandbox: 1.1.1
  @aws-amplify/schema-generator: 1.2.0
  aws-amplify: 6.5.0
  aws-cdk: 2.151.0
  aws-cdk-lib: 2.151.0
  typescript: 5.5.4
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description
I'm trying out Astro with Amplify Gen2 and came across an error when attempting to import the Schema from defineData into a React component in Astro
Here are my components
todo/[...slug].astro
---
import { amplifyDataClient } from "@/components/react/ConfigureAmplifyClientSide";
import { TodoCard } from "@/components/react/TodoCard";
import type { Schema } from "amplify/data/resource"; // <-- this doesn't throw an error

export async function getStaticPaths() {
  const { data } = await amplifyDataClient.models.Todo.list();
  return data.map((todo) => ({
    params: { slug: todo.id },
    props: todo,
  }));
}

type Props = Schema["Todo"]["type"];
const todo = Astro.props;
---

<TodoCard todo={todo} client:load />

TodoCard.tsx

import { type Schema } from "amplify/data/resource"; // <-- This throws an error by simply importing it
type Todo = Schema["Todo"]["type"];

export const TodoCard = ({ todo }: { todo: Todo }) => {

  return JSON.stringify(todo);
}

With this I get the following error in the browser console

Just solved this I think, the issue seems to be the syntax
import { type Schema } from "amplify/data/resource"; // <-- Throws an error
import type { Schema } from "amplify/data/resource"; // <-- Works

Not sure if its something specific to astro, as I haven't had this issue before and Im relatively new to astro

Hey,👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂


Load test resources by absolute paths

References to test resource files are resolved into absolute paths into the unpacked source tree used to build the tests so that tests requiring resources can run from stack test or stack repl. The resources must be listed in extra-source-files. The source tree must remain unpacked while the tests are run.
We discussed the possibility of doing this with the generated Paths module; that would work, but it would require that the test resources be listed as data-files that would be installed when the library is installed. To keep the test resources from leaving the source tree, a small test-specific Paths module is implemented using Template Haskell.
I also opted to use hpack for matching-logic; language-kore was already using it, so I assume it's allowed. Besides reducing redundancy in the package description, it helps avoid errors due to unlisted modules.

Can one of the admins verify this patch?

@bmmoore I changed dataFileName so that test resource file names are resolved relative to the package root.

@bmmoore Would you mind reviewing this again?

Looks pretty good. I would only ask to have the Paths.hs  at test/Paths.hs in both packages.
Now that it's looking up the filesystem for package.yaml rather than just relative to the source file it might work to do the search at runtime too, but keeping TH is fine.

I would only ask to have the Paths.hs at test/Paths.hs in both packages.

I have done this now.

Now that it's looking up the filesystem for package.yaml rather than just relative to the source file it might work to do the search at runtime too, but keeping TH is fine.

Even if we do the search at runtime, we still need Template Haskell to find the source file location at compile time.