Can't flash MIMXRT1060 - fails to verify flash algorithm

Describe the bug
Can't flash MIMXRT1060 targets on lastest release (fails to verify flash algorithm).
        WARN probe_rs::config::sequences::nxp_armv7m > MIMXRT10xx core type supplied as Armv7m, but the actual core is a Armv7em
       ERROR probe_rs::flashing::flasher             > Failed to verify flash algorithm. Data mismatch at address 0x000000
       ERROR probe_rs::flashing::flasher             > Original instruction: 0xe00abe00
       ERROR probe_rs::flashing::flasher             > Readback instruction: 0x000000
       ERROR probe_rs::flashing::flasher             > Original: [e00abe00, 62d780d, 24084068, d3000040, 1e644058, 1c49d1fa, 2a001e52, 4770d1f, 4770ba40, 4770ba40, 4770ba40, 4770bac0, 4770bac0, 4770bac0, 4855b51c, 48559000, 8498901, 81010049, 890a4953, 520852, 8802810a, 7522304, da022a00, 439a8802, 88088002, d5020740, 43988808, 484c8008, 6041494a, 6081494b, 22806801, 22204391, 60014311, f8a8f000, 68014847, d54503c9, 60014946, 29006801, 6b01dafc, 3122201, 63014391, 29006b01, 4a42dafc, 60114940, 3092103, 69016101, dafc2900, 22016901, 43910412, 4b3b6101, 3b40493b, 493b6319, 610b2301, 4c3a694b, 544023, 2405191b, 43230264, 698b614b, 40234c36, 4a42403, 4c35191b, 618b4323, 4c3469cb, 24034023, 191b0764, 43234c32, 680161cb, 60014391, 43916b01, 69016301, 61014391, 466a492d, 20004449, f9d3f000, d1052800, 44494929, f9b8f000, d0002800, bd1c2001, 47702000, b5104924, 20004449, f9bbf000, d0002800, bd102001, 7492105, 491e1842, 2301b510, 4449041b, f0002000, 2800f9b8, 2001d000, 2105bd10, 7494613, 49161842, 4449b510, f0002000, 2800f995, 2001d000, bd10, c0000006, 400b8000, 400d0000, d928c520, 400bc000, ffff, 400d8000, 12018, 18131818, 400d8100, f1a2323, 400fc000, fff8e0ff, 1ff3fcff, e0000100, 9c7fff80, 3800001, c, 49d42001, 69c00540, 60084449, 4ad14770, 6812444a, 68526992, 49ce4710, 68094449, 68896989, 4acb4708, 6812444a, 68d26992, 49c84710, 68094449, 69096989, 4ac54708, 6812444a, 69526992, 49c24710, 68094449, 69896989, 49bf4708, 68094449, 69c96989, 49bc4708, 68094449, 6a096989, 4bb94708, 681b444b, 6a5b699b, 48b64718, 68004448, 6ac06980, 48b34700, 68004448, 6bc06980, 49b04700, 68094449, 6c096989, 49ad4708, 68094449, 6c496989, 49aa4708, 68094449, 6b096989, 48a74708, 68004448, 6b406980, 49a44700, 68094449, 6b896989, 48a14708, 68004448, 6c806980, 489e4700, 68004448, 6cc06980, 499b4700, 68094449, 6a896989, 4a984708, 6812444a, 32806992, 47106a52, 444a4a94, 69926812, 6b123280, 4a914710, 6812444a, 32806992, 47106a92, 4448488d, 69806800, 6ac03080, 498a4700, 68094449, 6d096989, 48874708, 68004448, 6d406980, 49844700, 68094449, 6d896989, 48814708, 68004448, 6dc06980, 497e4700, 68094449, 6e096989, 487b4708, 68004448, 6e406980, 49784700, 68094449, 6e896989, 48754708, 68004448, 6ec06980, 49724700, 68094449, 6f096989, 486f4708, 68004448, 6f406980, 496c4700, 68094449, 6f896989, 48694708, 68004448, 6fc06980, 49664700, 68094449, 31806989, 47086809, 44484862, 69806800, 68403080, 495f4700, 68094449, 31806989, 47086889, 444a4a5b, 69926812, 68d23280, 49584710, 68094449, 31806989, 47086909, 444a4a54, 69926812, 69523280, 49514710, 68094449, 31806989, 47086989, 4449494d, 69896809, 69c93180, 494a4708, 68094449, 31806989, 47086a09, 444a4a46, 69926812, 6b523280, 48434710, 68004448, 30806980, 47006b80, 444a4a3f, 69d26812, 47106a12, 4449493c, 69c96809, 47086809, 444a4a39, 69d26812, 47106852, 44494936, 69c96809, 47086889, 44494933, 6a096809, 47086809, 444a4a30, 6a126812, 47106852, 4449492d, 6a096809, 47086889, 4449492a, 6a096809, 47086989, 444a4a27, 6a126812, 471069d2, 44494924, 6a096809, 47086ac9, 444a4a21, 69126812, 47106852, 4c1eb430, 6824444c, 68a46924, bc3046a4, 4a1a4760, 6812444a, 68d26912, 4b174710, 681b444b, 6a5b691b, b4304718, 444c4c13, 69246824, 46a46924, 4760bc30, 9c04b538, 4c0e9400, 6824444c, 69646924, bd3847a0, 4c0ab430, 6824444c, 6a246924, bc3046a4, 4a064760, 6812444a, 69d26912, 49034710, 68094449, 69896909, 4708, 4, b5104770, 89014857, 490849, 49568101, 852890a, 810a0052, 23048802, 2a000752, 8802da02, 8002439a, 7408808, 8808d502, 80084398, 494d484e, 494e6041, 68016081, 43912280, 43112220, 484b6001, 7c96901, 6901d003, 490849, f7ff6101, bd10ffd1, 4d46b5f8, 4a466968, 1804946, 69a8d522, 31b2303, d0074018, 31b2301, d00c1ac0, d1084298, e0066b10, 3c06910, d5066910, f800400, 2000d001, 4608e008, 780e006, 2016d501, 2014e000, 43484936, 896969, e03d0f49, 3c06810, d5066810, f800400, 2700d001, 460fe006, 640e004, e404b2d, 8474358, 3c06b10, d5066b10, f800400, 2400d001, 460ce008, 7c0e006, 2416d001, 2414e000, 43444823, 30404821, 69006a06, f976f000, 23004632, f844f000, 190069a9, 40114a1d, 2201d011, 4b1c0492, d0161a89, d0171a89, d1074291, 7416928, 46380f49, f0001c49, e000f8b0, 69692000, f4904c9, f0001c49, 4912f8a8, 60084449, 6819bdf8, e0000c09, 6896819, f0000e89, 2112f89c, e7ea4348, 400b8000, 400d0000, d928c520, 400bc000, ffff, e000e000, 400fc000, 400d8000, 16e3600, c0000, 400d8100, 8, 4605b5fe, 460c4610, d0734318, 468c46ae, 1aad2000, 419c4601, 4666d367, 24012700, 1ab6463d, d302419d, 463a4613, 46652421, 42f4676, 433e0c36, 1ab60c2d, d304419d, 41b0c15, 412432b, 46653410, 62f4676, 433e0a36, 1ab60a2d, d304419d, 21b0e15, 212432b, 46653408, 72f4676, 433e0936, 1ab6092d, d304419d, 11b0f15, 112432b, 46651d24, 7af4676, 433e08b6, 1ab608ad, d304419d, 9b0f95, 92432b, 46651ca4, 7ef4676, 433e0876, 1ab6086d, d31a419d, 415b1892, e0161c64, 46761800, 41494665, 419d1ab7, 90009101, 4660d309, 41981ab1, 4684468e, 99019800, 1c402500, 7dd4169, 432a0852, 1e64085b, 4672d5e6, b0034663, e7ffbdf0, 46012000, 46c046c0, 4623462a, 2200e7f5, 428b0903, a03d32c, d311428b, 469c2300, 4603e04e, d43c430b, 8432200, d331428b, 428b0903, a03d31c, d301428b, e03f4694, 428b09c3, 1cbd301, 41521ac0, 428b0983, 18bd301, 41521ac0, 428b0943, 14bd301, 41521ac0, 428b0903, 10bd301, 41521ac0, 428b08c3, cbd301, 41521ac0, 428b0883, 8bd301, 41521ac0, 428b0843, 4bd301, 41521ac0, d2001a41, 41524601, 47704610, fcae05d, 4249d000, d3001003, 40534240, 469c2200, 428b0903, a03d32d, d312428b, 18922fc, a03ba12, d30c428b, 11920189, d308428b, 11920189, d304428b, d03a0189, e0001192, 9c30989, d301428b, 1ac001cb, 9834152, d301428b, 1ac0018b, 9434152, d301428b, 1ac0014b, 9034152, d301428b, 1ac0010b, 8c34152, d301428b, 1ac000cb, 8834152, d301428b, 1ac0008b, d2d94152, 428b0843, 4bd301, 41521ac0, d2001a41, 46634601, 105b4152, d3014610, 2b004240, 4249d500, 46634770, d300105b, b5014240, 46c02000, bd0246c0, c04b5f8, 4626b28b, 435eb282, 46100c0d, 43580c37, 19800436, 41792100, 436e4616, 4360c37, 41791980, 436e4626, bdf81989, 0, 0, 1f78a400, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
       ERROR probe_rs::flashing::flasher             > Readback: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
     Erasing sectors ⠁ [00:00:00] [###############################################################################]      0 B/     0 B @      0 B/s (eta 0s )

This was working while I was working on https://github.com/probe-rs/probe-rs/pull/1462, so I tried using that branch. That also failed, but I realized that the last commit was where I merged master to fix conflicts, and so it may have worked just up until that commit; if I checkout 586dc789ba0beb3d624ce2679d96a1e43c4759bd, then it works as I expected.
This is the merge commit that seems to break things: https://github.com/probe-rs/probe-rs/commit/e7f943bc3c0ce7f83f29e34022307e4c1a8d8e6f
Will see if I can sort it out.
To Reproduce
Steps to reproduce the behavior:

Flash a MIMXRT1060 target via cargo-embed

Expected behavior
Should flash successfully.
Stacktrace
N/A
Desktop (please complete the following information):

macOS Sonoma

Additional context
N/A

If I revert the changes made in https://github.com/probe-rs/probe-rs/pull/1676, then this works:
diff --git a/probe-rs/targets/MIMXRT1060.yaml b/probe-rs/targets/MIMXRT1060.yaml
index 9f2ffe48..93616fc7 100644
--- a/probe-rs/targets/MIMXRT1060.yaml
+++ b/probe-rs/targets/MIMXRT1060.yaml
@@ -20,14 +20,6 @@ variants:
           is_boot_memory: true
           cores:
             - main
-      - !Ram
-          name: ITCM
-          range:
-            start: 0x00000000
-            end:   0x00020000
-          is_boot_memory: false
-          cores:
-            - main
       - !Ram
           name: OCRAM2
           range:

        WARN probe_rs::config::target > Using custom sequence for MIMXRT10xx
        WARN probe_rs::architecture::arm::sequences::nxp > MIMXRT10xx core type supplied as Armv7m, but the actual core is a Armv7em
     Erasing sectors ✔ [00:00:07] [#############################################################################] 1.12 MiB/1.12 MiB @ 149.95 KiB/s (eta 0s )
 Programming pages   ✔ [00:00:56] [##############################################################################] 1.09 MiB/1.09 MiB @ 19.60 KiB/s (eta 0s )    Finished flashing in 64.667s
        WARN probe_rs::architecture::arm::sequences::nxp > MIMXRT10xx core type supplied as Armv7m, but the actual core is a Armv7em

FWIW, I have my flash banks configured as per: https://github.com/mciantyre/teensy4-rs/issues/86#issuecomment-1429052793
Not sure what's wrong / how to fix.
/cc @Hoohaha @mciantyre

Maybe the flash loader isn't position independent. You can try specifying the load address to point into OCRAM27.

@bugadani thanks for the feedback! Do you know if we have any way to specify a particular address by region name (e.g. OCRMA2)? I see --base-adress as an option in cargo flash, but not sure if it can accept a name (which would be more convenient than specifying a literal address), and maybe I'm missing it, but I don't see where I could configure this for cargo embed (per https://github.com/probe-rs/probe-rs/blob/master/probe-rs/src/bin/probe-rs/cmd/cargo_embed/config/default.toml).

All I'M suggesting is to replace load_address: ~ with an actual value in MIMXRT1060.yaml. --base-address changes where the binary is flashed, so I don't think that would help :)

Could you please test https://github.com/probe-rs/probe-rs/pull/2089 for me?

All I'M suggesting is to replace load_address: ~ with an actual value in MIMXRT1060.yaml. --base-address changes where the binary is flashed, so I don't think that would help :)

Ohhh. "load address" here is as in LMA, right? I must admit that I haven't given much thought (yet) to flash algorithms, and the precise meaning and implications of the settings in the *.yaml files.
If I'm following, then is the load address here just needed to know where to read from to verify that what was written to flash is written correctly, by reading it back from the expected Load Memory Address?
(Going to have to wrap my head around the flash algorithm stuff sooner or later -- I want to leverage your work in https://github.com/probe-rs/probe-rs/pull/1947 and add a miniz flash algorithm for the MIMXRT1060 😄).

Could you please test https://github.com/probe-rs/probe-rs/pull/2089 for me?

I'll give that a go once I'm back at my desk in another hour or two -- thanks!

@bugadani I tried copying the MIMXRT1060.yaml from your PR, and set my Embed.toml like so:
[default.general]
chip = "MIMXRT1060"
chip_descriptions = ["./MIMXRT1060.yaml"]

But I get:
     Erasing sectors ⠁ [00:00:00] [###################################]      0 B/     0 B @      0 B/s (eta 0s )       Error failed to flash /Users/cstrahan/src/tmm_flexio_lcd_driver/target/thumbv7em-none-eabihf/release/hello-teensy

             Caused by:
                 0: Error while flashing
                 1: Failed to load flash algorithm into RAM at address 201FFFE0. Is there space for the algorithm header?

Since the header seems to be 0x20 bytes long (0x20200000 - 0x201FFFE0), I tried setting the load_address to 0x20200020, and that flashes successfully.
Is the header always 0x20 bytes, or is that dependent on particular flash algo? Offsetting the address by 0x20 feels kinda suspicious, but I dunno. Is that a proper solution?

Right, so probe-rs prepends this to the flash algo. So you're right that this is going to be somewhat fragile but that's still better than not working. Thanks for the testing!

I don't have a debuggable 1060 target, but I can reproduce something similar on my 1010EVK.

On a different note, maybe ITCM isn't writeable in the state the CPU is in when the download happens.

That's the gist. The runtime Charles is using will disable ITCM. That runtime state persists up to the download phase. In order to reproduce this, I have to define an equivalent runtime for the program I'm flashing. (This persistence might be considered part of the issue; didn't expect this.)
On the other hand, OCRAM2 is always available. Using it by default should be safe.
Looks like we can change the !Ram region ordering in the target file to prefer OCRAM2, without touching the load address. This doesn't work:
      - !Ram
          name: ITCM
          # etc...
      - !Ram
          name: OCRAM2
          # etc...

But this does work:
      - !Ram
          name: OCRAM2
          # etc...
      - !Ram
          name: ITCM
          # etc...


Compose Lints

Check and follow Slack Compose Lints

Missing the usage of Immutable Collections Library for Kotlin con composables.
Open an issue to do an spike of this part: https://github.com/alex-amenos/Jetpack/issues/76


Fullscreen Permissions

Hello, I'm trying to write video player on embed system.
Standard googled chrome not allows me to run fullscreen video:
"""
Failed to execute 'requestFullscreen' on 'Element': API can only be initiated by a user gesture.
"""
Havent found any flag at settings to force this permission/disable limitation.
Same correct for 65.0.3325.181-1 ungoogled tested.
Is there way to modify ungoogled-chromium so it will accept some flag if started from shell, like:
--fullscreen-policy=no-user-gesture-required
Or may be someone knows the right existing startup key?

I'd prefer a solution that doesn't require a patch first. If it doesn't exist, then I welcome a PR to add this functionality behind a flag.

Judging by third_party/blink/renderer/core/fullscreen/fullscreen.cc there's no build-in key for that feature.

Have made estimated patch file but don't have disk space currently to compile this beast and don't know if it's the right way to implement feature.
allowanyfsr.patch.zip

@lefedor Is this still relevant or did you find another solution?
I'd recommend looking into puppeteers like Selenium that allow you to emulate all the user actions as if they were initiated by user. Also, there is WebDriver API which has an explicit endpoint for entering full-screen (no idea how widely it is supported, though).

@lefedor Also, I'd recommend looking into so-called "kiosk mode" which was designed to make Chrome display a page in full-screen mode without any browser UI elements.

Closing because this is pretty old. Let us know if you still have this issue.


validating compose.yml: services.backend Additional property develop is not allowe

start error，env information：
[root@klustron-test10 getting-started-todo-app]# docker compose up -d
validating /nvme2/data1/software/docker/getting-started-todo-app/compose.yml: services.backend Additional property develop is not allowed
[root@klustron-test10 getting-started-todo-app]# docker compose version
Docker Compose version v2.21.0
[root@klustron-test10 getting-started-todo-app]# docker --version
Docker version 24.0.7, build afdd53b
[root@klustron-test10 getting-started-todo-app]#

@ashanzhu Compose File Watch was introduced in 2.22.0. Can you update your Compose to the latest version?
Please update your Docker Desktop version to the latest version, if possible.


lint is failing for multiple projects

Versions
@angular-devkit/architect          0.5.10
@angular-devkit/build-angular      0.5.10
@angular-devkit/build-ng-packagr   0.5.10
@angular-devkit/build-optimizer    0.5.10
@angular-devkit/core               0.5.10
@angular-devkit/schematics         0.5.10
@angular/cli                       6.0.0-rc.7
@ngtools/json-schema               1.1.0
@ngtools/webpack                   6.0.0-rc.8
@schematics/angular                0.5.10
@schematics/update                 0.5.10
ng-packagr                         2.4.2
rxjs                               6.0.0
typescript                         2.7.2
webpack                            4.6.0

Repro steps

run ng lint
Observed behavior
Could not determine a single project for the 'lint target.
Error: Could not determine a single project for the 'lint target.
    at LintCommand.getProjectNamesByTarget

Desired behavior
run lint on all defined projects.
Mention any other details that might be useful (optional)
I believe it is tracked to this line:
https://github.com/angular/angular-cli/blob/7f8489c5b328833ef2fe4fccc5e4f749ec6cad06/packages/%40angular/cli/models/architect-command.ts#L20
Multi target is not set to true, although lint is defined as multi target.

Experiencing the same issue, on RC7, using lint, build, and test.
Could not determine a single project for the 'test target.

Could not determine a single project for the 'build target.

The quote mark before the target name seems suspicious.


make this repo public

Since this code is distributed under the BSD 3-Clause License, I would suggest to make this repo public.

Mission accomplished :ok_hand: :octocat:


maintenance command fails with mis-formatted .netrc

I noticed having a mis-formatted entry in .netrc file resulted in heroku maintenance:on / heroku maintenance:off command to fail.
For instance in my specific case having an entry missing the machine definition label prepending the hostname. The rest of the heroku commands work as expected with the mis-formatted entry.
somehost.herokuapp.com
  login user@host
  password XXXX

ah that makes sense. That command is one of the new v4 commands which uses a Go parser for the netrc: https://github.com/bgentry/go-netrc
I took a stab last week at converting the ruby netrc gem over to Go so it would act identically, but I discovered a bug that even the current ruby netrc implementation wouldn't work if you had the password specified before the login. I may try to fix that and port it over again.

Can we have an example of the wrong netrc entry? So i can track that

@ys There is an example in the description but here is one type as well:
Good:
machine somehost.herokuapp.com
  login user@host
  password XXXX

Bad
somehost.herokuapp.com
  login user@host
  password XXXX

Oh thanks, sorry about that part:D


Error: Model filename not in model list

Unexpected behaviour: For models ggml-mpt-7b-base, ggml-mpt-7b-instruct, ggml-gpt4all-j-v1, after the first prompt the model is not downloaded, instead an error occurs Error: Model filename not in model list: <model name>.

With Python gpt4all 1.0.8, I currently get the following models working with out of the box with llm + llm-gpt4all:

GPT4All-13B-snoozy
nous-hermes-13b
wizardLM-13B-Uncensored
orca-mini-3b
orca-mini-7b
ggml-model-gpt4all-falcon-q4_0
ggml-replit-code-v1-3b
orca-mini-13b

The following models give me the "Model filename not in model list" error out of the box:

ggml-all-MiniLM-L6-v2-f16
ggml-gpt4all-j-v1
ggml-vicuna-7b-1
ggml-wizardLM-7B
ggml-mpt-7b-base
ggml-mpt-7b-instruct
ggml-mpt-7b-chat
wizardlm-13b-v1
starcoderbase-3b-ggml
ggml-vicuna-13b-1
ggml-nous-gpt4-vicuna-13b
ggml-stable-vicuna-13B

However, I've found a workaround that works for some (all?). If you drop into a Python shell and run e.g.:
from gpt4all import GPT4All
model = GPT4All("ggml-vicuna-7b-1.1-q4_2.bin")

Using the filename from the exception, subsequent runs of llm seem be able to use the cached model.


Support CronJobs in a backwards compatible way

Description
This uses k8s discovery API to determine if v1/batch CronJob exists. If it does then use the informer for that, if not, then fall back to v1beta1. This does however mean that without more involved changes, that we cannot move forward from k8s client-go 1.24 which is the last version with v1beta1 for cron jobs (there isn't risk of this happening automatically as an API upgrade will cause a compilation error)
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
CI should test the v1 flow, but we'll have to manually test 3.11 and <4.6

There's this spot and I was trying to understand if we should make a change.
https://github.com/stackrox/stackrox/blob/46238c9ee8dc4345bf8fc0c13a8104542f525fa0/sensor/admission-control/manager/k8s_object.go#L36-L37

This does however mean that without more involved changes, that we cannot move forward from k8s client-go 1.24 which is the last version with v1beta1 for cron jobs

Given that we want to upgrade the client some time in the future, what changes would be expected?
I guess we cannot just include different versions of the client libs depending on the discovered k8s version, can we?
IIUC, the upgrade path would be blocked for as long as 1.24 is supported by ACS (which would be quite some time) correct?

After visually comparing
https://github.com/kubernetes/api/blob/master/batch/v1/generated.proto
and
https://github.com/kubernetes/api/blob/master/batch/v1beta1/generated.proto
I believe v1 CronJob is field-wise equivalent to v1beta1 CronJob. I wonder if we could actually modify version and deserialize the v1beta1 as v1.

@msugakov Yeah they are are equivalent (most of the time v1 vs the last beta is equivalent because it's just a promotion process)

@Maddosaurus It'll be more involved, but we either vendor multiple client versions or do some magic with deserialization with the dynamic API. All of which are too involved for what we're trying to do right now potentially with respect to 74. I do think that we may need to consider either tightening the support matrix OR creating a generic plan to support these objects going forward

Runtimes and network graph work on OCP 4.7.

Looks like this needs a rebase from master. https://srox.slack.com/archives/CELUQKESC/p1676392699199519


swift 5 warning 'withUnsafeMutableBytes' is deprecated: use withUnsafeMutableBytes<R>(_: (UnsafeMutableRawBufferPointer) throws -> R) rethrows -> R instead

Hi,is it foreseen to release an upgrade of RNCryptor that is compatible with swift 5 ?
Thx

Fixed in 5.1.0.


Taking to long to load

Expected Behavior
(What did you expect to happen?)
Actual Behavior
(What actually happened?)

Actual Behavior
(What actually happened?)
Steps to Reproduce the Problem

Specifications

Browser:
OS: Mac/Linux/Windows

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nicolasgarnier/drive-music-player/issues/36, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AquaRNeYy1X01dRu8FLzEXbzW-LLspTrks5vd99mgaJpZM4cf40B
.


Errors  about running example of surfdist

Hi~
When I test the example code in the readme, there is an error when I run  sd.analysis.dist_calc
Here are my codes:
cmap = 'coolwarm'
base_dir = 'path/2/Applications/freesurfer/subjects/'
surf = nib.freesurfer.read_geometry(os.path.join(base_dir, 'bert/surf/lh.pial'))
cort = np.sort(nib.freesurfer.read_label(os.path.join(base_dir, 'bert/label/lh.cortex.label')))
sulc = nib.freesurfer.read_morph_data(os.path.join(base_dir, 'bert/surf/lh.sulc'))
src  = sd.load.load_freesurfer_label(os.path.join(base_dir, 'bert/label/lh.aparc.a2009s.annot'), 'S_central', cort)
## All codes above run successfully~~

# calculate distance
dist = sd.analysis.dist_calc(surf, cort, src)

AND Here are the errors:
NumbaNotImplementedError                  Traceback (most recent call last)
File [~/anaconda3/envs/d2l/lib/python3.9/site-packages/numba/core/typing/typeof.py:244](https://vscode-remote+ssh-002dremote-002bchenzy-005fsever1.vscode-resource.vscode-cdn.net/export/bioinfo-team/home/chenzy/Desktop/PythonTutorial/MedicalImages_Deeplearning/fmri_learning/~/anaconda3/envs/d2l/lib/python3.9/site-packages/numba/core/typing/typeof.py:244), in _typeof_ndarray(val, c)
    243 try:
--> 244     dtype = numpy_support.from_dtype(val.dtype)
    245 except errors.NumbaNotImplementedError:

File [~/anaconda3/envs/d2l/lib/python3.9/site-packages/numba/np/numpy_support.py:114](https://vscode-remote+ssh-002dremote-002bchenzy-005fsever1.vscode-resource.vscode-cdn.net/export/bioinfo-team/home/chenzy/Desktop/PythonTutorial/MedicalImages_Deeplearning/fmri_learning/~/anaconda3/envs/d2l/lib/python3.9/site-packages/numba/np/numpy_support.py:114), in from_dtype(dtype)
    112         return types.NestedArray(subtype, dtype.shape)
--> 114 raise errors.NumbaNotImplementedError(dtype)

NumbaNotImplementedError: >i4

During handling of the above exception, another exception occurred:

NumbaValueError                           Traceback (most recent call last)
[/export/bioinfo-team/home/chenzy/Desktop/PythonTutorial/MedicalImages_Deeplearning/fmri_learning/test.ipynb](https://vscode-remote+ssh-002dremote-002bchenzy-005fsever1.vscode-resource.vscode-cdn.net/export/bioinfo-team/home/chenzy/Desktop/PythonTutorial/MedicalImages_Deeplearning/fmri_learning/test.ipynb) Cell 4 in ()
      [1](vscode-notebook-cell://ssh-remote%2Bchenzy_sever1/export/bioinfo-team/home/chenzy/Desktop/PythonTutorial/MedicalImages_Deeplearning/fmri_learning/test.ipynb#W3sdnNjb2RlLXJlbW90ZQ%3D%3D?line=0) # calculate distance
----> [2](vscode-notebook-cell://ssh-remote%2Bchenzy_sever1/export/bioinfo-team/home/chenzy/Desktop/PythonTutorial/MedicalImages_Deeplearning/fmri_learning/test.ipynb#W3sdnNjb2RlLXJlbW90ZQ%3D%3D?line=1) dist = sd.analysis.dist_calc(surf, cort, src)

File [~/anaconda3/envs/d2l/lib/python3.9/site-packages/surfdist-0.15.5-py3.9.egg/surfdist/analysis.py:14](https://vscode-remote+ssh-002dremote-002bchenzy-005fsever1.vscode-resource.vscode-cdn.net/export/bioinfo-team/home/chenzy/Desktop/PythonTutorial/MedicalImages_Deeplearning/fmri_learning/~/anaconda3/envs/d2l/lib/python3.9/site-packages/surfdist-0.15.5-py3.9.egg/surfdist/analysis.py:14), in dist_calc(surf, cortex, source_nodes)
      6 def dist_calc(surf, cortex, source_nodes):
      8     """
      9     Calculate exact geodesic distance along cortical surface from set of source nodes.
     10     "dist_type" specifies whether to calculate "min", "mean", "median", or "max" distance values
...
--> 246     raise errors.NumbaValueError(f"Unsupported array dtype: {val.dtype}")
    247 layout = numpy_support.map_layout(val)
    248 readonly = not val.flags.writeable

NumbaValueError: Unsupported array dtype: >i4

The requirements of my computer:
python 3.9.10
numpy 1.23.5
numba 0.56.4
Cython 0.29.33
tvb-gist 2.2
nibabel 3.2.2

Could you please help me to solve the problem, Thank you~

Thanks for your interest in the code and for pointing out this error. I've discussed this with @neurabenn, and we've created a PR that only removed the numba requirement. Could you try running the code from this PR #18 , and let us know if it resolves the issue?


Move system tests functionality to tester, and reuse in staging tests

@kkraune please review.

Basically the same tests, but moved code around a bit, so I could reuse it for staging tests. I also wondered if I should use the feed client there, but without a checked-in, ready feed it didn't make much sense to me.

Thanks for fixes.


Help needed: Word wrap without expanding cell height / CellFormat with multiline text

Is there any way to print some multi-line text in a cell without expanding the cell's height? Whenever I search for word-wrap or something related, I get pointed towards multicell. This does not work for me, as I wish to use the cell to stay same. If the multi-line text doesn't fit vertically, it shouldn't show up. When it does need to show up, the cell's height is already set to accommodate it.
I could try to achieve this manually but if there is some built-in way to do it, it would be much preferred.
Another related issue: to create a multiline string, I use SplitLines on the string and then strings.Join the array (after converting from [][]byte to []string) with a \n between each item. When log.Printing, the string is formatted correctly but when I use CellFormat to place it in the PDF, it still shows up as single-line.
Does CellFormat ignore line-breaks in the text param? If so, how do I get around it without using MultiCell due to the other issues mention above?

You'll have to accomplish this manually using SplitLines() and MultiCell(). (CellFormat() is for single lines of text only -- as you found, it does not honor newline characters.)
If the number of lines returned by SplitLines() is greater than can fit in your cell, skip. If it is the same as can fit, join as you did with strings.Join() and use MultiCell() to display. If it is fewer, you can augment the list returned by SplitLines() with some empty lines and then proceed with the preceding step.

@jung-kurt Thank you, the solution makes sense and I'm implementing it right now.
An issue came up with SplitLines(), however. If it detects that a word is going to put a line over the allowed width, it cuts that entire word, correct? Can the "cutting" be done by character/letter instead of the entire word?

An issue came up with SplitLines(), however. If it detects that a word is going to put a line over the allowed width, it cuts that entire word, correct?

Yes, it breaks on ' ', '\t', and '\n'.

Can the "cutting" be done by character/letter instead of the entire word?

Not as it stands. Your best bet my be to copy the source method and adjust the break logic accordingly.

Alright, will do that. Cheers for the help.

Good luck! If your solution is general, consider a pull request.

It is done but I'm not sure if it's worth a pull request. All I did was take Bruno Michel's SplitLines() method and replace
if c == ' ' || c == '\t' || c == '\n' { sep = i }
with
sep = i
This will split by character instead of space.

Thanks for the update, @igorsousa-b. Elegant change to meet your use case.

You'll have to accomplish this manually using SplitLines() and MultiCell(). (CellFormat() is for single lines of text only -- as you found, it does not honor newline characters.)
If the number of lines returned by SplitLines() is greater than can fit in your cell, skip. If it is the same as can fit, join as you did with strings.Join() and use MultiCell() to display. If it is fewer, you can augment the list returned by SplitLines() with some empty lines and then proceed with the preceding step.

can I get the example program?


syscalls to rust

chore: wip
chore: rewriting syscalls to rust

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Removed hash from application name (fix #1759)

Why make this change?
Proposed fix for #1759
What is this change?
Remove the hashed value after the "+" sign when injecting DAB version in the MSSQL connection string
How was this tested?

[ ] Integration Tests
[x] Unit Tests
[x] Manual Test

Sample Request(s)
N/A

Yep, I'll fix the test ASAP

@Aniruddh25 @seantleonard build is failing on "Check formatting", complaining that .NET 2 is not supported....

@Aniruddh25 @seantleonard build is failing on "Check formatting", complaining that .NET 2 is not supported....

Did you get a chance to setup this git pre-commit hook?
https://github.com/Azure/data-api-builder/blob/main/CONTRIBUTING.md#enforcing-code-style-with-git-hooks

@Aniruddh25 @seantleonard build is failing on "Check formatting", complaining that .NET 2 is not supported....

The actual error from here https://msdata.visualstudio.com/CosmosDB/_build/results?buildId=110183176&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=2b20c7d0-7587-5b0f-aadc-b456e6f0b807 is :

/home/vsts/work/1/s/src/Cli.Tests/EndToEndTests.cs(6,1): warning IDE0005: Using directive is unnecessary. [/home/vsts/work/1/s/src/Cli.Tests/Cli.Tests.csproj]

So, you need to remove the using directive from that EndToEndTests file on line 6

One test to fix in End2End tests to get pipeline passing. Also a test in that file can be updated to ensure commit hash is still included when expected to ensure nuget health check succeeds and doesn't regress.

Fixed

All green! :)

/azp run

/azp run


HDD Space not showing up

Checklist

[X] I have updated to the latest available Proxmox VE Custom Integration version, see the latest version here.

Describe the issue you are experiencing
Is it normal that the LXC/QEMU HDD Space will not be listed? (Only from the node)

In which version of Home Assistant Core do you have the problem?
2024.3.1
What version of Proxmox VE Custom Integration has the issue?
3.4.1
What version of Proxmox VE do you have the problem?
3.4.1
Diagnostics information
No response
Additional information
No response

See https://github.com/dougiteixeira/proxmoxve/issues/141

See https://github.com/dougiteixeira/proxmoxve/issues/141


CNN Regression with VGG-16 predicts the same value regardless of the input image.

So just a set up of the problem I am trying to solve. I have around 200k 64x64x3 RGB images of patches of terrain that a robot drove over. Each patch has a corresponding label of what the roughness of that image patch is. The roughness values range from 0-160. The data was collected with the robot driving at varying speeds, hence the range of the roughness values. My aim is to be able to predict the roughness of a patch. I am using the VGG-16 network, with the last layer modified to do regression. My batch size is 1024, the loss is mean sqaured error, the optimize is rmsprop. The network is shown below. My problem is that after training, the network predicts the exact same value for each test image. Another point to note is that the training loss is always higher than the validation loss which is odd. Lastly I tried with other optimizers such as SGD and Adam, as well as varying batch sizes. Right now I am trying to train the network from scratch but it does not seem too promising. I am not sure what is going wrong here, and I would really appreciate any help I can get. Thanks
    input_shape = _obtain_input_shape(input_shape,                                       default_size=224,                                       min_size=48,                                       data_format=K.image_data_format(),                                       require_flatten=include_top,                                       weights=weights)
if input_tensor is None:
    img_input = Input(shape=input_shape)
else:
    if not K.is_keras_tensor(input_tensor):
        img_input = Input(tensor=input_tensor, shape=input_shape)
    else:
        img_input = input_tensor
# Block 1
x = Conv2D(64, (3, 3), activation='relu', padding='same', name='block1_conv1')(img_input)
x = Conv2D(64, (3, 3), activation='relu', padding='same', name='block1_conv2')(x)
x = MaxPooling2D((2, 2), strides=(2, 2), name='block1_pool')(x)

# Block 2
x = Conv2D(128, (3, 3), activation='relu', padding='same', name='block2_conv1')(x)
x = Conv2D(128, (3, 3), activation='relu', padding='same', name='block2_conv2')(x)
x = MaxPooling2D((2, 2), strides=(2, 2), name='block2_pool')(x)

# Block 3
x = Conv2D(256, (3, 3), activation='relu', padding='same', name='block3_conv1')(x)
x = Conv2D(256, (3, 3), activation='relu', padding='same', name='block3_conv2')(x)
x = Conv2D(256, (3, 3), activation='relu', padding='same', name='block3_conv3')(x)
x = MaxPooling2D((2, 2), strides=(2, 2), name='block3_pool')(x)

# Block 4
x = Conv2D(512, (3, 3), activation='relu', padding='same', name='block4_conv1')(x)
x = Conv2D(512, (3, 3), activation='relu', padding='same', name='block4_conv2')(x)
x = Conv2D(512, (3, 3), activation='relu', padding='same', name='block4_conv3')(x)
x = MaxPooling2D((2, 2), strides=(2, 2), name='block4_pool')(x)

# Block 5
x = Conv2D(512, (3, 3), activation='relu', padding='same', name='block5_conv1')(x)
x = Conv2D(512, (3, 3), activation='relu', padding='same', name='block5_conv2')(x)
x = Conv2D(512, (3, 3), activation='relu', padding='same', name='block5_conv3')(x)
x = MaxPooling2D((2, 2), strides=(2, 2), name='block5_pool')(x)

x = Flatten(name='flatten')(x)
x = Dense(4096, activation='relu', name='fc1')(x)
x = Dense(4096, activation='relu', name='fc2')(x)
x = Dense(1,name='regression_dense')(x)  `

Dear,
I have the same question,
Could U share your project ,please?
I want to learn from you.
Thx


MF-1720 - Improve Test Reports

What does this do?
Updates test files, for better test reports, and overall making test functions more uniform.
Which issue(s) does this PR fix/relate to?
Resolves #1720

Codecov Report

Merging #1727 (ac100fc) into master (19dbf9f) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master    #1727   +/-   ##
=======================================
  Coverage   70.38%   70.39%
=======================================
  Files         146      146
  Lines       11394    11397    +3
=======================================
+ Hits         8020     8023    +3
  Misses       2724     2724
  Partials      650      650

Impacted Files
Coverage Δ

logger/logger.go
90.00% <ø> (ø)

things/postgres/things.go
68.47% <100.00%> (+0.32%)
:arrow_up:

users/service.go
66.19% <0.00%> (ø)

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


Fix: load trajectories with limited max_steps

This PR for #144 and #145.

Pass max_steps from restore_latest_n_traj to load_trajectories
Use same length (aka. max_steps) for actions
Add test to check above fixes

@ymd-h Thanks for your PR! I think it would be better to use next_obs key instead of taking next_obs from obs key with one step shift. This change should be fine (in the sense that we won't encounter key error) because we can assume the loaded paths are generated by passing the command line argument --save-path, and generated in evaluate_policy method.
I would merge the PR once you can apply the above change, or let me know if you have other idea or opinion..

@keiohta
Thank you for your review.
I added commits which utilizing next_obs key as you mentioned.

Thanks @ymd-h ! I believe the codes are improved and resolved #144 and #145.


Unable to store query results in a local file

I have followed the instructions and was able to query results and print in console, however, I wasn't able to store it in a local file, could you please advise?
When I run the command .\upsync.exe query --store-path .\store --package-type  microsoft-update, it works just fine. However, when I try to pipe it to a result file (.\upsync.exe query --store-path .\store --package-type  microsoft-update *> results.txt), it has an error. I have attached the error message in a file attached in this email.
I later found out this might be because the console library is being used in the MicrosoftUpdateMetadata.cs file. I tried to run it in a separate cmd inside Powershell but only generated partial results, I also attached the result in this email.
Do you know how to store the result in a local file? Thank you so much.
error-message.txt
partial-result.txt

Thank you @xiangkangjw  for reporting this issue!
When pretty printing update metadata, the code is directly manipulating the console cursor location in order to indent text. This manipulation is not supported when redirecting to a text file.
The issue is fixed by printing the required number of white spaces in order to maintain indenting. This is compatible with console redirection and should fix this issue.
See commit 542f6c4f1e8a6c40da4f5fdfe99f0c181ae922ac
However, further processing of the pretty printed output might be unwieldy. I also added a "--json-out-path <json_file_path>" command line switch that will output the result of the query to a specified JSON file. The JSON file will contain an array, each object in the array is package (update) metadata serialized to JSON.
See commit d124d142f05c2a6590efd1e13d893b95e18d08c5
Please let me know if you still encounter issues.


[Issue]: Flaky tests related to code execution

Describe the issue
Some tests that can fail due to non-deterministic behaviors of LLM especially when it comes to code generation.

test/coding/test_commandline_code_executor.py::test_local_commandline_executor_conversable_agent_capability
test/agentchat/test_cache_agent.py::test_legacy_disk_cache

Potential solution:

a mock LLM client for testing, could be a custom client, that generates a pre-determined list of output
turn off code execution for testing non-code execution related setups. e.g., caching.
Clean up the work_dir after each run.

What about removing the work_dir after first execution?

Occurred here https://github.com/microsoft/autogen/actions/runs/8023483515/job/21920034692?pr=1748

Could hardcoding the reply solve the flakiness? Instead of mocking the client https://github.com/microsoft/autogen/blob/08e26153227fb0b22bb914f07d3aa18097513d29/test/coding/test_commandline_code_executor.py#L176-L180

Update: this test
test/agentchat/test_cache_agent.py::test_legacy_disk_cache
Has been fixed in #1906 thanks to @WaelKarkoub

We are addressing this:
test/coding/test_commandline_code_executor.py::test_local_commandline_executor_conversable_agent_capability
by remove the executor's user capability and the test. So we can close this issue once #1933 is merged.


Moving apply(bytes) & apply(hex) into the Factory trait

This removes the redundant implementations of the two 'apply' functions found in all of our companion object factories to their common parent trait called 'Factory'. This was becoming boilerplate code added to every companion object factory - best to refactor it to its parent trait.

Coverage increased (+0.5%) to 91.622% when pulling 2a811518d0a1c5136558d37e998ff67950bbf9bf on Christewart:add_apply_functions_to_factory into 1d5a70b0395820cdcb2a35a3c56e34ee553697b3 on bitcoin-s:master.

ACK


hashing of identifiers

3 days

One way that may be good (and is generally accepted as good by what I've read) is to use HMAC. Basically having a secure key generated that is used for the pseudonomysation process and it always generates the same hash. We then destroy the key.  Something like this:
import hmac

value = "Some Value"
key = "some-secret-key"
byte_key = key.encode("UTF-8")
message = value.encode()
hashed_value = hmac.new(byte_key, message, hashlib.sha256).hexdigest()

print(hashed_value)
The reason I suggest a method like this is that some hashing methods could be vulnerable to things like dictionary attacks.  Let me know when you get to this point in the pipeline


My web interface is different from all images I found about InfluxDB

Also, clicking on the gear lets me to put login credentials (with a visible password), but it doesn't matter; always connect.
My web:

Other screenshots:

Because of that, I can't continue with any tutorial I found, because they say things like "In the top menu on the next page, click on Cluster Admins.", but obviously I don't have that option (or any other).
Example tutorial --> https://www.digitalocean.com/community/tutorials/how-to-analyze-system-metrics-with-influxdb-on-centos-7
How to reproduce (at least in my case):

Install the deb or rpm (I've tried on a Amazon EC2 (rpm) and on my working laptop (deb).
I've tried versions 0.8.8 and 0.9.4.
Go to http://IP:8083/

What's happening? How can I solve this?
Thanks a lot!

since 0.9, the web UI has changed, so what you saw is the right version and the tutorial is too old..

But when I installed v0.8.8 I got the same web UI :/ Not the old interface.

@Tak-MK It sounds like either a) your browser is caching the old page or b) the 0.9.x version is still running somewhere and serving up the pages. The admin UI is statically compiled into the binaries, so it's unlikely that you're actually getting the new version of the UI served up by the old binary.

@Tak-MK that is an 0.8 Admin UI page in your screenshot. It can only come from an 0.8 instance.
The tutorial to which you link was built using InfluxDB 0.8. The Admin UI is substantially different in InfluxDB 0.9, as all administrative functions have been moved into simple query commands.

Also, clicking on the gear lets me to put login credentials (with a visible password), but it doesn't matter; always connect.

Authentication is disabled by default in InfluxDB 0.9, so if you haven't enabled it, it's not running.

Because of that, I can't continue with any tutorial I found, because they say things like "In the top menu on the next page, click on Cluster Admins.", but obviously I don't have that option (or any other).

You cannot use any documentation for InfluxDB 0.8 with InfluxDB 0.9 and vice versa. The two are quite different in many ways.

I see... thanks a lot! :D


[csolution format] Format should support debug configuration data

MCUXpresso SDK/IDE wants to provide out-of-box debug experience for customers which means customers can directly import/copy project from pack and download/debug with one or 2 click without requiring manual configuration by the user.
To achieve this, some debug configuration should be provided in packs.
The reality is for a device, most examples can share the same debug configuration data, we plan to place it under "environment name="mcux"" in pdsc of DFP/BSP. But some examples may need special configuration due to many reasons. For example specific debug configuration data, like
<debug_configuration id="com.crt.advproject.config.exe.release" name="Release Configuration" probe="LinkServer">
          <scripts>
            <script type="init" silent="false" emulators="${gdb.stub} -mi -info-emu">
              <script>
set remotetimeout 60000
##target_extended_remote##
set mem inaccessible-by-default ${mem.access}
mon ondisconnect ${ondisconnect}
set arm force-mode thumb
${load}</script>
            </script>
            <script type="run" silent="false" emulators="${gdb.stub} -mi -info-emu">
              <script>${run}</script>
            </script>
          </scripts>
          <params>
            <params id="vector.catch.release.mcuxpresso" name="vector.catch" value="false"/>
            <params id="internal.cache.release.mcuxpresso" name="internal.cache" value="Disable"/>
          </params>
        </debug_configuration>

I see 2 place for such example specific data:

pdsc project environment. I don't think it is good, because name="mcux" only contain debug configuration data.

      <project>
        <environment name="uv" load="mdk/freertos_event.uvprojx"/>
        <environment name="iar" load="iar/freertos_event.ewp"/>
        <environment name="mcux" load="special_debug_configuration.xml"/>
        <environment name="csolution" load="csolution.yml" />
      </project>

csolution/cproject extension point. We need to translate above debug data into extension point. Our IDE can consume it then.

I know csolution/cprj focus on build, but it should provide place for debug configuration data.
Originally posted by @tcsunhao in https://github.com/Open-CMSIS-Pack/devtools/issues/171#issuecomment-1127362560

Let's discuss in the project meeting. How about placing a file with a unique file name or file extension side by side with the *.csolution.yml file containing the debug configuration data. This way the IDE will know that it needs to read this project local file rather than extracting the data from the DFP/BSP without the need to add this data in the csolution file itself?

During the meeting we did not have any voices opposing the idea to include debug configuration meta information being added to the csolution.yml format.
@tcsunhao please feel free to create a new issue proposing the meta information required for debug configuration.

Does cprj support a debug section?

@jankap, no the current cprj format does not specify meta information related to programming and debugging a device.


Fix: Filter out Measurements with NULL externalComputationId when view is COMPUTATION

Fix: Filter out Measurements with NULL externalComputationId when view is COMPUTATION

This change is


fix #1948 substitute a better word; documentation only.

In the top-level README.md, change

Its semantic syntax makes it easy and straightforward while
its rich standard components library fastens your development time and
lightens your email codebase.

to

Its semantic syntax makes the language easy and straightforward while
its rich standard components library reduces your development time and
lightens your email codebase.

No change to any JavaScript file.

Well that was here for a while 👍


Add support for RabbitMQ secrets engine

This adds support for the RabbitMQ secrets engine

@james-bjss  @jprelph  - this change is minor - could be included in next release ?


fix test running on windows

fix prettier settings
add cross-env

cc @juergba

Coverage remained the same at 90.77% when pulling 33d18b7e6fa8bd6f3e3bcd21be0e22d80353e599 on boneskull/issue/3643 into fc0507ed742cb7ab54bcf60f88a0ea0c64b38289 on master.

cc @juergba 	this work for you?


Add dark, light mode feature in home page also

Assign me this issue under GSSoC Exted'24

Its not preferable to add a dark mode on the home page ,it will not much effective, I am closing this issue for now
But yah, if you are eager to contribute to this project, have a look to other issues or create your own.


Replaced the sizeof parameter of the if statement with ARRAYSIZE

Summary of the Pull Request
The pull request fixes the issue where "sizeof" parameter was use instead of "ARRAYSIZE".
PR Checklist

[x] Closes #xxx
[x] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[x] Documentation updated. If checked, please file a pull request on our docs repo and link it here: #xxx
[ ] Schema updated.
[x] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments
This was a pretty straight forward issue, i just replace sizeof which gives the byte size with ARRAYSIZE which give the number of elements in the array.

This is intended to fix https://github.com/microsoft/terminal/issues/11761.

Thanks for your contribution @abdoulkkonate! Could you please edit the description to fill out the pull request template? We can see the change in the Files diff of GitHub, so that screenshot isn't strictly necessary. However, we do need to know things like the fact you signed the CLA, the linked issue that this will be resolving (for building the release changelist among other things), and how you validated this was fine and didn't make a mess (even if it was manually!)
Appreciated in advance!

Hello Michael, thank you for the fast response. I noted your notes and I'll have it done by end of day tomorrow.
Thank you
Abdoul k. Konate
-------- Original message --------
From: Michael Niksa @.>
Date: 1/27/22 2:48 PM (GMT-08:00)
To: microsoft/terminal @.>
Cc: "Konate, Abdoul-Karim" @.>, Mention @.>
Subject: Re: [microsoft/terminal] Replaced the sizeof parameter of the if statement with ARRAYSIZE (PR #12273)
[External Email]
Thanks for your contribution @abdoulkkonatehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_abdoulkkonate&d=DwMCaQ&c=sJ6xIWYx-zLMB3EPkvcnVg&r=Vt4tIfgGEJ_88rPPSGqF0g&m=Y5SylVZmZ6UApFLMCw9A3aLiqzRr_wdLDKMUsTI_8uqOI11jQeLfU-208wYCLAFs&s=Hn1Aw1Dk73fCEz9eKTti8M9uD4i-v4k5_K42Wi6UBKU&e=! Could you please edit the description to fill out the pull request template? We can see the change in the Files diff of GitHub, so that screenshot isn't strictly necessary. However, we do need to know things like the fact you signed the CLA, the linked issue that this will be resolving (for building the release changelist among other things), and how you validated this was fine and didn't make a mess (even if it was manually!)
Appreciated in advance!
—
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_microsoft_terminal_pull_12273-23issuecomment-2D1023711708&d=DwMCaQ&c=sJ6xIWYx-zLMB3EPkvcnVg&r=Vt4tIfgGEJ_88rPPSGqF0g&m=Y5SylVZmZ6UApFLMCw9A3aLiqzRr_wdLDKMUsTI_8uqOI11jQeLfU-208wYCLAFs&s=l7Uuc8MyY9CPityF9d9tGratcbs7-wLVqSOvAGAYgxU&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ARTCSUAYW7AB5KDJ6NYNHJ3UYHDS3ANCNFSM5M67MY6Q&d=DwMCaQ&c=sJ6xIWYx-zLMB3EPkvcnVg&r=Vt4tIfgGEJ_88rPPSGqF0g&m=Y5SylVZmZ6UApFLMCw9A3aLiqzRr_wdLDKMUsTI_8uqOI11jQeLfU-208wYCLAFs&s=6yA8fwLyDT6a8D4WeCs2CRr18sl-z0DpIuK6Kx6f9vs&e=.
Triage notifications on the go with GitHub Mobile for iOShttps://urldefense.proofpoint.com/v2/url?u=https-3A__apps.apple.com_app_apple-2Dstore_id1477376905-3Fct-3Dnotification-2Demail-26mt-3D8-26pt-3D524675&d=DwMCaQ&c=sJ6xIWYx-zLMB3EPkvcnVg&r=Vt4tIfgGEJ_88rPPSGqF0g&m=Y5SylVZmZ6UApFLMCw9A3aLiqzRr_wdLDKMUsTI_8uqOI11jQeLfU-208wYCLAFs&s=hyoUJaErOhsKpPKUGJd14gU__CYbBvNHrjHMw0B74C8&e= or Androidhttps://urldefense.proofpoint.com/v2/url?u=https-3A__play.google.com_store_apps_details-3Fid-3Dcom.github.android-26referrer-3Dutm-5Fcampaign-253Dnotification-2Demail-2526utm-5Fmedium-253Demail-2526utm-5Fsource-253Dgithub&d=DwMCaQ&c=sJ6xIWYx-zLMB3EPkvcnVg&r=Vt4tIfgGEJ_88rPPSGqF0g&m=Y5SylVZmZ6UApFLMCw9A3aLiqzRr_wdLDKMUsTI_8uqOI11jQeLfU-208wYCLAFs&s=2w88uKTCkbO6ipf18x-kORTnhG0Wg8vG2oAyF3fj_Ag&e=.
You are receiving this because you were mentioned.Message ID: @.***>

I've updated the pull request description to remove the hidden <!-- ... --> comments. Those are only intended to guide others, but are supposed to be removed before the pull request is merged. I also simplified the text a little bit.


Update actions when data has changed, row multi selection and fix for the blankslate

Update the table to render the action bar on data change to update the icon or the text
Add the row multi selection for the tableView
Move the rendered blankslate in the table instead of under the table
Add demo to show actions update
Add demo to show the multi selection for a table

Lib used: https://github.com/reduxjs/reselect

a little lintfix to make the build pass npm run lintfix 👍

This command add lint error... again

Codecov Report

Merging #636 into master will decrease coverage by 0.23%.
The diff coverage is 77.14%.

@@            Coverage Diff             @@
##           master     #636      +/-   ##
==========================================
- Coverage   99.72%   99.49%   -0.24%
==========================================
  Files         261      261
  Lines        6629     6674      +45
  Branches     1542     1562      +20
==========================================
+ Hits         6611     6640      +29
- Misses         18       34      +16

Impacted Files
Coverage Δ

...omponents/tables/table-children/TableChildBody.tsx
100% <ø> (ø)
:arrow_up:

src/components/tables/TableRowReducers.ts
100% <ø> (ø)
:arrow_up:

...ponents/tables/table-children/TableChildHeader.tsx
100% <100%> (ø)
:arrow_up:

src/components/tables/TableHeadingRowConnected.tsx
100% <100%> (ø)
:arrow_up:

src/components/tables/TableActions.ts
100% <100%> (ø)
:arrow_up:

src/components/tables/TableConstants.tsx
100% <100%> (ø)
:arrow_up:

src/components/tables/TableHeadingRow.tsx
100% <100%> (ø)
:arrow_up:

src/components/tables/TableRowActions.ts
100% <100%> (ø)
:arrow_up:

src/components/tables/TableReducers.ts
90.56% <66.66%> (-9.44%)
:arrow_down:

src/components/tables/TableConnected.tsx
86.48% <68.75%> (-13.52%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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

shall we have a demo for this? what lint errors did you get after running lintfix ?

Coverage in progess

Demo: https://coveo.github.io/react-vapor/new-update-table-row-actions-on-component-update/

demo works well 👍 , you can just ping when the coverage is up

small comments for me but overall looks good! you'll have a conflict in Index.tsx of the docs to fix before merging


Looking for new owners

When I forked this project, it was just to have a .NET Core compatible version of libsodium because I needed it in another project. That project was later abondoned, and thus I don't even use this library myself anymore. That, in addition to now having a full-time job, I don't have much time maintaining this project. As there's quite a few issues, it seems to have at least some usage.
Previously, there was discussions about merging some of the work done in this fork with the original project, but it lead nowhere at that time.
I'm really sorry for not being able to keep up the work needed, therefore I reach out to see if anyone might want to take ownership of it.
Best regards,
Trond

Thanks for all the work you've been putting into libsodium-core, Trond :smiley:
There has been some discussion here. tl;dr: The current state of libsodium bindings for .NET is a bit unsatisfying. I'm maintaining NSec, a library that uses libsodium internally. However, there seems to be a clear need for a more direct language binding. If it helps, I could to take over maintenance of libsodium-core to address that need. However, that maintenance would be very basic.
I also like the work @samuel-lucas6 is doing with Geralt. Maybe we could clean up the list of language bindings a bit and provide some guidance when to use Geralt, NSec, or libsodium-core (something along the lines of: if you need a simple language binding, use Geralt; if you need a more abstracted API, use NSec; if you're stuck with the libsodium-net/libsodium-core API, use libsodium-core, which however is in maintenance mode)...
@samuel-lucas6: Thoughts?

Indeed, thank you for your work on libsodium-core @tabrath. I've used the library many times.
That's a good idea @ektrah; I'm sure a note can be added to the libsodium documentation. In fact, it's probably worth adding in brackets whether the library is in maintenance mode for all of the libraries on that page as I know multiple are.
Thanks for the support regarding Geralt @ektrah! It's a bit messy currently but coming along. I now have a domain for the documentation. Trouble is I was thinking of converting everything to using Spans and only supporting newer versions of .NET, like NSec. Using span buffers may be problematic for optional parameters though, so I'm not sure. The API will be more like libsodium-core than NSec, but I'm still only going to expose the newer algorithms, such as Argon2 rather than Argon2 and scrypt, which may limit adoption. Then instead of my original plan of a misuse-resistant API, I'm exposing some lower level functions since I may want to use them but trying to make sensible higher level design decisions, such as allowing the user to not provide a nonce, having dedicated multi-input MAC and verify MAC functions, hopefully providing some Noise key exchange patterns, etc.
Geralt is not in a usable state currently, and I need to write tests for everything, which will take ages. Therefore, I think NSec should be the recommended .NET libsodium binding in all cases unless libsodium-core is required.
However, considering the popularity of libsodium-core, it seems logical to fix the small issues if possible, such as the wrong nonce size in the IETF version of ChaCha20-Poly1305 (#69), and push an update. Perhaps we can share the load on that @ektrah, but I also don't want to do anything beyond basic edits as I'm keeping myself very busy.

Great to hear from you both!
I really appreciate your kind words and will gladly hand over this project to you, which is clearly much better qualified to maintain such a library involving cryptography (in which I'm certainly lacking experience and knowledge to be able to continue maintaining it even if I had time for it).
As for your future plans, I don't have much input as you guys seems to have it pretty much figured out already (and to me, sounds like a good one). From what I can remember (from memory and past pr's and issues), I had some plans for the future:

Use Span (a pending PR exists #23)
Move CI to Azure Pipelines, which at that time was promising, but now I would definitely use GitHub Actions
Add missing interop, up to date with libsodium
The other bindings mentioned looks more promising to me, so putting this package into maintenance mode sounds like the right thing to do. But, I would suggest moving CI to GitHub actions, as I think that's easier than updating Appveyor (but that's your call really, I guess it's possible to transfer that project to you as well).

One last thing, you need to be owner of the NuGet package, so send me an email to exchange details around transferring both NuGet package ownership and the repo.

Sounds all good to me 👍
@tabrath, I've sent you a message from my nuget.org account.

Completed the transfer of both the repository and NuGet package to you. Please just reach of if there's anything I've forgotten.
Thank you and good luck ❤
Best regards,
Trond

Thank you @tabrath, and all the best for your new endeavors!

Hi @ektrah, I'm almost done on the libsodium binding page cleanup PR, but I wanted to check whether you'd prefer to have libsodium-core removed or kept but with a '(maintenance mode)' warning. I'm moving NSec to the top.


Cannot Edit Component for a struct pointer array

9.2 / linux
enum foobars {
    FOOBAR_1 = 1,
    FOOBAR_2 = 2,
    FOOBAR_3 = 3,
};
struct foobar {
    unsigned char *mem;
    unsigned int size;
};
struct foobar_list {
    foobar *[1000] items;
    enum foobars[1000] types;
    unsigned int pos;
};

If you have the above structs created as data types, trying to edit the component items in the Structure Editor results in an error Can only edit a structure, union or enum..  You can however edit the types
Is this an issue of a struct pointer array being treated as an opaque pointer array?

It appears that you can't edit the component if items is declared as foobar **items either. The getDataType method of an array or pointer is most likely only being invoked once instead of recursively.


relation ID page broken

mal seems to have updated the relation page logic, so cannot find approved entries anymore
I think I can still get anime to work but manga does not
https://myanimelist.net/info.php?search=+++&go=relationids&divname=relationGen1 seems to work for anime
https://myanimelist.net/info.php?search=___&go=relationids&divname=relationGen1 used to work but now just produces a 500 error

fixed in https://github.com/Hiyori-API/checker_mal/commit/517b9bbd23cd98636263afcb6557393822a0432f


WebApp - Navigate incorrect in case back to Import account

Describe the bug
Version test: https://fcc535f4.subwallet-webapp.pages.dev/
To reproduce the bug
Steps:

Go to Import account -> Import from seed phrase
Click on Back button
Observe the displayed screen

Actual: Back to Select account type screen

Expect: Back to the previous screen

In case of large screen (desktop, laptop): Back to the Import account (select import method screen)
In case mobile screen (iPad, mobile): Back to the Select account type screen

Currently, the logic is divided by UI (Extensions and WebApp).
On the Extended UI, use the state by selecting the type of method stored in storage.
On the WebApp UI, use the local state on the screen

Version test: https://09a66e58.subwallet-webapp.pages.dev/
Validation passed in cases:

Large screen: Back to select import account method
Small screen (web mobile): Back to Select account type


Unable to gain access to objects inside top-level repositories

Dear Alexander, hello
My setup inside Docker

Docker Registry 2
Keycloak as SSO server ( a custom image with your Provider )
Traefik as HTTPS reverse proxy

Both are exposed on internet using:

https://myregistry.mydomain.com/v2/
https://sso.mydomain.com

Keycloak exported adapter config is:
auth:
  token:
    realm: https://sso.mydomain.com/realms/registry/protocol/docker-v2/auth
    service: registry
    issuer: https://sso.mydomain.com/realms/registry

Keycloak certificate is in the Docker Registry Compose configuration.
My problem
My registry dont have a lot of groups, a lot of images are on the top-level. ( myregistry.mydomain.com/v2/<repository>/ ) without groups or usernames in the path.

My script authentication flow is made of 3 steps:

Phase 1: Basic Auth ( failing with Token Auth, moving to P2 )
Phase 2: SSO Auth with P1 Headers ( realm, service, scope )
Phase 3: Bearer Auth with Registry ( OK )

In the below example, the commands are:

version
catalog

INFO:registry:Phase 1: Testing Registry Basic Auth
{'method': 'Bearer', 'realm': 'https://sso.mydomain.com/realms/registry/protocol/docker-v2/auth', 'service': 'registry'}
INFO:registry:Phase 2: Basic Auth failed, fetching IDP with realm, service and scope
INFO:registry:Phase 3: Connecting to Registry with Credentials
{'method': 'Bearer', 'realm': 'https://sso.mydomain.com/realms/registry/protocol/docker-v2/auth', 'service': 'registry', 'scope': 'registry:catalog:*'}
{}

( Docker Registry dont send version on /v2/ )
INFO:registry:Phase 1: Testing Registry Basic Auth
{'method': 'Bearer', 'realm': 'https://sso.mydomain.com/realms/registry/protocol/docker-v2/auth', 'service': 'registry', 'scope': 'registry:catalog:*'}
INFO:registry:Phase 2: Basic Auth failed, fetching IDP with realm, service and scope
INFO:registry:Phase 3: Connecting to Registry with Credentials
{'method': 'Bearer', 'realm': 'https://sso.mydomain.com/realms/registry/protocol/docker-v2/auth', 'service': 'registry', 'scope': 'registry:catalog:*'}
{'repositories': ['REDACTED']}

The problem is that the Keycloak server is always sending 'scope': 'registry:catalog:*' for both Version and Catalog
Things i dont understand

I need to access: https://myregistry.mydomain.com/v2/<repository>/tags/list but Keycloak always sending me 'scope': 'registry:catalog:* and a 401 UNAUTHORIZED
How are groups used ? ( path format ? )
How are users used ? ( path format ? )

what i did wrong ???
If you need full configuration/output with debug you can message me.
Regards.

Hi Greg,
I think this seems to be a reverse proxy issue. I personally use NGINX as a gateway and had to enhance the requests with needed headers accordingly (especially CORS headers).
I oriented my settings with this link
Could you check your responses if there is anything related to CORS?

Hi Alexander,
The responses headers including CORS:
{'method': 'Bearer', 'realm': 'https://sso.mydomain.fr/realms/registry/protocol/docker-v2/auth', 'service': 'registry', 'scope': 'registry:catalog:*'}
DEBUG:registry:401
DEBUG:registry:{'Access-Control-Allow-Credentials': 'true', 'Access-Control-Allow-Headers': ['Authorization', 'Accept', 'Cache-Control'], 'Access-Control-Allow-Methods': ['HEAD', 'GET', 'OPTIONS', 'DELETE'], 'Access-Control-Expose-Headers': 'Docker-Content-Digest', 'Access-Control-Origin': ['https://registry.mydomain.fr', 'https://registry-ui.mydomain.fr'], 'Content-Length': '150', 'Content-Type': 'application/json; charset=utf-8', 'Date': 'Tue, 26 Mar 2024 10:14:51 GMT', 'Docker-Distribution-Api-Version': 'registry/2.0', 'Www-Authenticate': 'Bearer realm="https://sso.mydomain.fr/realms/registry/protocol/docker-v2/auth",service="registry",scope="repository:ansible:pull",error="insufficient_scope"', 'X-Content-Type-Options': 'nosniff'}
DEBUG:registry:b'{"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"repository","Class":"","Name":"ansible","Action":"pull"}]}]}\n'


Consul with turbine in Spring Cloud Dalston

I am using consul with turbine in spring cloud dalston.sr1 version, it had two service, turbine service run on port 15010, aservice run on port 15011.(follow sample _https://github.com/spencergibb/consul-turbine-example_)
Turbine application.properties
.........
spring.application.name=myturbine
server.port=15010
spring.profiles.active=development
spring.cloud.consul.host=localhost
spring.cloud.consul.port=8500
turbine.appConfig=aservice
turbine.aggregator.clusterConfig=aservice
........
When I visit http://localhost:15011/hystrix.stream, It show 'ping ...', I use hystrix dashboard to monitor _http://localhost:15011/hystrix.stream_, it is good.
Where I input _http://localhost:15010/turbine.stream_, it report 404 not found. When I use hystrix dashboard to monitor 'http://localhost:15010/turbine.stream', it report "Unable to connect to Command Metric Stream."
Turbine service's log show.
2018-03-12 17:54:44.556 INFO 21008 --- [io-15010-exec-9] c.n.t.s.servlet.TurbineStreamServlet : FilterCriteria: []
2018-03-12 17:54:44.556 INFO 21008 --- [io-15010-exec-6] c.n.t.s.servlet.TurbineStreamServlet : FilterCriteria: []
2018-03-12 17:54:44.556 INFO 21008 --- [io-15010-exec-9] c.n.t.s.servlet.TurbineStreamServlet : StatsType filters: []
2018-03-12 17:54:44.556 INFO 21008 --- [io-15010-exec-6] c.n.t.s.servlet.TurbineStreamServlet : StatsType filters: []
2018-03-12 17:54:44.564 WARN 21008 --- [io-15010-exec-4] ashboardConfiguration$ProxyStreamServlet : Failed opening connection to http://localhost:15010/turbine.stream : 404 : HTTP/1.1 404
2018-03-12 17:54:44.567 WARN 21008 --- [io-15010-exec-3] ashboardConfiguration$ProxyStreamServlet : Failed opening connection to http://localhost:15010/turbine.stream : 404 : HTTP/1.1 404
Note:
If I use turbine.aggregator.clusterConfig=aservice , /turbine.stream or /turbine.stream?cluster=aservice, reported 404 not found error.
If I not used turbine.aggregator.clusterConfig, /turbine.stream show correct. But hystrix dashboard did not show any data in it's UI, only show 'Loading ...'

@spencergibb

@AmramXing
Can you provide a complete, minimal, verifiable sample that reproduces the problem?

Closing due to age of the question. If you would like us to look at this issue, please comment and we will look at re-opening the issue.

@sigalmaya Dalston is no longer supported. Please try with Edgware, Finchley or Greenwich.
Can you provide a complete, minimal, verifiable sample that reproduces the problem?  It should be available as a GitHub (or similar) project or attached to this issue as a zip file.


rename em into italic, because it's confusing for me

What files do i need rename into italic

sorry i forget to add details here.
folder em^ https://github.com/LLazyEmail/markdown-regex/tree/main/tests/em

#215

#171

you can close this task

did we finish it?

I think we still didnt complete it(sadly) take a look at this link: https://github.com/LLazyEmail/markdown-regex/tree/main/tests/em


pod-to-b-multi-node-nodeport connectivity test failing on EKS with 1.8.0-rc3

When following the EKS GSG instructions to validate Cilium 1.8.0-rc3 for #11903 (including the fix for #12078), the connectivity check for pod-to-b-multi-node-nodeport is failing:
% kubectl get po
NAME                                                     READY   STATUS    RESTARTS   AGE
echo-a-58dd59998d-fcfsc                                  1/1     Running   0          133m
echo-b-865969889d-7qgfg                                  1/1     Running   0          133m
echo-b-host-659c674bb6-tvzxm                             1/1     Running   0          133m
host-to-b-multi-node-clusterip-6fb94d9df6-v25v4          1/1     Running   0          133m
host-to-b-multi-node-headless-7c4ff79cd-2dgct            1/1     Running   0          133m
pod-to-a-5c8dcf69f7-zq2zj                                1/1     Running   0          133m
pod-to-a-allowed-cnp-75684d58cc-tb5jm                    1/1     Running   0          133m
pod-to-a-external-1111-669ccfb85f-8l2p2                  1/1     Running   0          133m
pod-to-a-l3-denied-cnp-7b8bfcb66c-qg2wc                  1/1     Running   0          133m
pod-to-b-intra-node-74997967f8-c88x9                     1/1     Running   0          133m
pod-to-b-intra-node-nodeport-775f967f47-t426f            1/1     Running   0          133m
pod-to-b-multi-node-clusterip-587678cbc4-xskt6           1/1     Running   0          133m
pod-to-b-multi-node-headless-574d9f5894-xd2jq            1/1     Running   0          133m
pod-to-b-multi-node-nodeport-7944d9f9fc-qpv5r            0/1     Running   0          133m
pod-to-external-fqdn-allow-google-cnp-6dd57bc859-bqhhq   1/1     Running   0          133m

% kubectl get svc
NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
echo-a                 ClusterIP   <IP_ADDRESS>   <none>        80/TCP         136m
echo-b                 NodePort    <IP_ADDRESS>    <none>        80:31313/TCP   136m
echo-b-headless        ClusterIP   None             <none>        80/TCP         136m
echo-b-host-headless   ClusterIP   None             <none>        <none>         136m
kubernetes             ClusterIP   <IP_ADDRESS>       <none>        443/TCP        147m

% kubectl get ep
NAME                   ENDPOINTS                               AGE
echo-a                 <IP_ADDRESS>:80                       136m
echo-b                 <IP_ADDRESS>:80                       136m
echo-b-headless        <IP_ADDRESS>:80                       136m
echo-b-host-headless   <IP_ADDRESS>                          136m
kubernetes             <IP_ADDRESS>:443,<IP_ADDRESS>:443   147m

Follow-up for #12078
/cc @brb

@tklauser does it pass with Cilium 1.7? I can see this particular check was added after 1.7 (https://github.com/cilium/cilium/commit/3cc04e57aee6ea86b676cbef3e419556cae20999), but I'm guessing it's still meant to work with 1.7, right?

I'm seeing an RST:
-> stack flow 0x1ced2b76 identity 38656->1 state new ifindex 0 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:50938 -> <IP_ADDRESS>:31313 tcp SYN
-> endpoint 436 flow 0x0 identity 1->38656 state reply ifindex 0 orig-ip <IP_ADDRESS>: <IP_ADDRESS>:31313 -> <IP_ADDRESS>:50938 tcp ACK, RST

For my cluster, the reason is that the following:
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2020-04-21T12:36:08Z"
  name: echo-b
  namespace: default
  resourceVersion: "1915"
  selfLink: /api/v1/namespaces/default/services/echo-b
  uid: acb29a3b-83cc-11ea-80a1-025016633d8a
spec:
  clusterIP: <IP_ADDRESS>
  ports:
  - port: 80
    protocol: TCP
    targetPort: 80
  selector:
    name: echo-b
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

Should be of type NodePort but it is not.

I'm able to reproduce this. It happens with both kube-proxy and BPF NodePort.

The packet gets into the remote pod and the reply makes it out of the pod:
20:39:49.193719 IP <IP_ADDRESS>.44966 > <IP_ADDRESS>.80: Flags [S], seq<PHONE_NUMBER>, win 26883, options [mss 8961,sackOK,TS val 509552408 ecr 0,nop,wscale 7], length 0
20:39:49.193750 IP <IP_ADDRESS>.80 > <IP_ADDRESS>.44966: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 26847, options [mss 8961,sackOK,TS val 193777408 ecr 509552408,nop,wscale 7], length 0
20:39:50.196403 IP <IP_ADDRESS>.80 > <IP_ADDRESS>.44966: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 26847, options [mss 8961,sackOK,TS val 193778410 ecr 509552408,nop,wscale 7], length 0
20:39:50.197370 IP <IP_ADDRESS>.44966 > <IP_ADDRESS>.80: Flags [S], seq<PHONE_NUMBER>, win 26883, options [mss 8961,sackOK,TS val 509553411 ecr 0,nop,wscale 7], length 0
20:39:50.197391 IP <IP_ADDRESS>.80 > <IP_ADDRESS>.44966: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 26847, options [mss 8961,sackOK,TS val 193778411 ecr 509552408,nop,wscale 7], length 0
20:39:52.212402 IP <IP_ADDRESS>.80 > <IP_ADDRESS>.44966: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 26847, options [mss 8961,sackOK,TS val 193780426 ecr 509552408,nop,wscale 7], length 0
20:39:52.213415 IP <IP_ADDRESS>.44966 > <IP_ADDRESS>.80: Flags [S], seq<PHONE_NUMBER>, win 26883, options [mss 8961,sackOK,TS val 509555427 ecr 0,nop,wscale 7], length 0
20:39:52.213435 IP <IP_ADDRESS>.80 > <IP_ADDRESS>.44966: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 26847, options [mss 8961,sackOK,TS val 193780427 ecr 509552408,nop,wscale 7], length 0

The packet doesn't make it back out of eth0 so it is dropped in the stack of the remote node.
20:41:27.919172 IP <IP_ADDRESS>.45600 > <IP_ADDRESS>.31313: Flags [S], seq<PHONE_NUMBER>, win 26883, options [mss 8961,sackOK,TS val 509651132 ecr 0,nop,wscale 7], length 0
20:41:28.949256 IP <IP_ADDRESS>.45600 > <IP_ADDRESS>.31313: Flags [S], seq<PHONE_NUMBER>, win 26883, options [mss 8961,sackOK,TS val 509652162 ecr 0,nop,wscale 7], length 0
20:41:30.965266 IP <IP_ADDRESS>.45600 > <IP_ADDRESS>.31313: Flags [S], seq<PHONE_NUMBER>, win 26883, options [mss 8961,sackOK,TS val 509654178 ecr 0,nop,wscale 7], length 0
20:41:35.221258 IP <IP_ADDRESS>.45600 > <IP_ADDRESS>.31313: Flags [S], seq<PHONE_NUMBER>, win 26883, options [mss 8961,sackOK,TS val 509658434 ecr 0,nop,wscale 7], length 0
20:41:43.413259 IP <IP_ADDRESS>.45600 > <IP_ADDRESS>.31313: Flags [S], seq<PHONE_NUMBER>, win 26883, options [mss 8961,sackOK,TS val 509666626 ecr 0,nop,wscale 7], length 0

@errordeveloper checked with v1.7.5:
NAME                                                     READY   STATUS    RESTARTS   AGE
echo-a-58dd59998d-nd6x4                                  1/1     Running   0          91s
echo-b-865969889d-dvkcz                                  1/1     Running   0          90s
echo-b-host-659c674bb6-9dj58                             1/1     Running   0          89s
host-to-b-multi-node-clusterip-6fb94d9df6-9fxfx          1/1     Running   0          88s
host-to-b-multi-node-headless-7c4ff79cd-xrrw8            1/1     Running   0          88s
pod-to-a-5c8dcf69f7-2xn2w                                1/1     Running   0          85s
pod-to-a-allowed-cnp-75684d58cc-bfjc8                    1/1     Running   0          88s
pod-to-a-external-1111-669ccfb85f-jlwsw                  1/1     Running   0          83s
pod-to-a-l3-denied-cnp-7b8bfcb66c-nfcd2                  1/1     Running   0          86s
pod-to-b-intra-node-74997967f8-4r4r8                     1/1     Running   0          84s
pod-to-b-intra-node-nodeport-775f967f47-gcznq            0/1     Running   1          85s
pod-to-b-multi-node-clusterip-587678cbc4-c5xdn           1/1     Running   0          84s
pod-to-b-multi-node-headless-574d9f5894-5h8zd            1/1     Running   0          84s
pod-to-b-multi-node-nodeport-7944d9f9fc-dcrs5            0/1     Running   1          83s
pod-to-external-fqdn-allow-google-cnp-6dd57bc859-d7t47   1/1     Running   0          82s

Looks like this also occurs and in addition pod-to-b-intra-node-nodeport also fails.
% kubectl get svc
NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
echo-a                 ClusterIP   <IP_ADDRESS>   <none>        80/TCP    2m34s
echo-b                 ClusterIP   <IP_ADDRESS>     <none>        80/TCP    2m33s
echo-b-headless        ClusterIP   None             <none>        80/TCP    2m32s
echo-b-host-headless   ClusterIP   None             <none>        <none>    2m31s
kubernetes             ClusterIP   <IP_ADDRESS>       <none>        443/TCP   3h17m

% kubectl get ep
NAME                   ENDPOINTS                                 AGE
echo-a                 <IP_ADDRESS>:80                          3m7s
echo-b                 <IP_ADDRESS>:80                          3m6s
echo-b-headless        <IP_ADDRESS>:80                          3m5s
echo-b-host-headless   <IP_ADDRESS>                            3m4s
kubernetes             <IP_ADDRESS>:443,<IP_ADDRESS>:443   3h18m

% kubectl describe pod pod-to-b-multi-node-nodeport-7944d9f9fc-dcrs5
[...]
  Warning  Unhealthy  113s (x6 over 3m13s)   kubelet, ip-192-168-14-188.us-west-2.compute.internal  Liveness probe failed: curl: (7) Failed to connect to echo-b-host-headless port 31313: Connection refused
  Normal   Killing    113s (x2 over 2m53s)   kubelet, ip-192-168-14-188.us-west-2.compute.internal  Container pod-to-b-multi-node-nodeport failed liveness probe, will be restarted
  Warning  Unhealthy  95s (x11 over 3m15s)   kubelet, ip-192-168-14-188.us-west-2.compute.internal  Readiness probe failed: curl: (7) Failed to connect to echo-b-host-headless port 31313: Connection refused

% kubectl describe pod pod-to-b-intra-node-nodeport-775f967f47-gcznq
[...]
  Warning  Unhealthy  2m38s (x6 over 3m58s)  kubelet, ip-192-168-49-116.us-west-2.compute.internal  Liveness probe failed: curl: (7) Failed to connect to echo-b-host-headless port 31313: Connection refused
  Normal   Killing    2m38s (x2 over 3m38s)  kubelet, ip-192-168-49-116.us-west-2.compute.internal  Container pod-to-b-intra-node-hostport failed liveness probe, will be restarted
  Warning  Unhealthy  2m35s (x10 over 4m5s)  kubelet, ip-192-168-49-116.us-west-2.compute.internal  Readiness probe failed: curl: (7) Failed to connect to echo-b-host-headless port 31313: Connection refused

I found the cause, the routing is not symmetric.
The SYN is received on eth0:
21:44:37.544583 IP <IP_ADDRESS>.41456 > <IP_ADDRESS>.31313: Flags [S], seq<PHONE_NUMBER>, win 26883, options [mss 8961,sackOK,TS val 513440720 ecr 0,nop,wscale 7], length 0

The SYN-ACK is sent out over eth2:
21:44:37.544706 IP <IP_ADDRESS>.31313 > <IP_ADDRESS>.41456: Flags [S.], seq 520985781, ack<PHONE_NUMBER>, win 26847, options [mss 8961,sackOK,TS val 197665741 ecr 513440720,nop,wscale 7], length 0

@tklauser think it would makes sense to double check without Cilium, i.e. with just built-in CNI. It would be good eliminate a possibility of issues in the VPC configuration that eksctl implements.

The conntrack entry looks like this:
ipv4     2 tcp      6 59 SYN_RECV src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=47458 dport=31313 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=80 dport=47458 mark=128 zone=0 use=2

The mark indicates that the 0x80 has been set via this rule:
-A PREROUTING -i eth0 -m comment --comment "AWS, primary ENI" -m addrtype --dst-type LOCAL --limit-iface-in -j CONNMARK --set-xmark 0x80/0x80

For a yet unknown reason, the following ip rule matches:
110:	from <IP_ADDRESS> to <IP_ADDRESS>/16 lookup 27

It is meant to to lead all packets from the pod which uses an ENI IP of eth2 out of eth2 based on the source address.
It's not clear why this rule matches despite the reverse SNAT leading to source IP of <IP_ADDRESS>

Removing the above rule (matching the IP of the pod behind the NodePort), fixes the problem.

This does not seem to be a regression. The logic was already the same for 1.7. I'm removing the release blocker flag.

Fixing this will require to mark NodePort traffic, mark it, and route it out the same interface as it came in on.

I'm able to reproduce this. It happens with both kube-proxy and BPF NodePort.

@tgraf Have you checked whether BPF NodePort is affected when running without kube-proxy?

@tgraf Have you checked whether BPF NodePort is affected when running without kube-proxy?

Both are affected. The issue is in the routing of the reply. It doesn't matter who translates it back and forth.
Other ENI CNIs are using a rule like this:
-A PREROUTING -i eth0 -m comment --comment "AWS, primary ENI" -m addrtype --dst-type LOCAL --limit-iface-in -j CONNMARK --set-xmark 0x80/0x80

and then use an ip rule to force replies out that interface

OK, I see. The problem happens on a remote node in which BPF NodePort cannot bypass the stack.

I could reproduce the issue by following the GSG for AWS-EKS. I could also apply the manual fix from Thomas, with an additional step for the return-path filter on eth0.
The ENI CNI in the aws-node daemonset sets the following rules and configuration on the node:
$ ip rule | grep -w 0x80
1024:	from all fwmark 0x80/0x80 lookup main

$ iptables-save | grep -w 0x80
-A PREROUTING -i eth0 -m comment --comment "AWS, primary ENI" -m addrtype --dst-type LOCAL --limit-iface-in -j CONNMARK --set-xmark 0x80/0x80
-A PREROUTING -i eni+ -m comment --comment "AWS, primary ENI" -j CONNMARK --restore-mark --nfmask 0x80 --ctmask 0x80

$ sysctl net.ipv4.conf.eth0.rp_filter
2

Since the GSG instructs to remove the daemonset before deploying Cilium and creating the node, this configuration is not used, and we have instead:
$ ip rule | grep -w 0x80
[null]

$ iptables-save | grep -w 0x80
[null]

$ ip rule | grep 'from <IP_ADDRESS>'
110:	from <IP_ADDRESS> to <IP_ADDRESS>/16 lookup 3
$ ip route show table 3
default via <IP_ADDRESS> dev eth1
<IP_ADDRESS> dev eth1 scope link

$ sysctl net.ipv4.conf.eth0.rp_filter
1

Cilium sets net.ipv4.conf.all.rp_filter at 0, but the maximum value in conf/{all,interface}/rp_filter is used when doing source validation on an {interface}, so in our case rp_filter is in strict mode on eth0. This prevents the packets received from the first node on eth0 to be (SNAT-ed and) forwarded to the pod. Instead they are dropped by the host and no SYN/ACK is emitted back. Disabling rp_filter or setting it to loose mode fixes it, but the SYN/ACKs are not sent to the correct destination.
This is due to the ip rule that is matched for those packets, it tells the host to do a FIB lookup in table 3 (associated to interface at index 3, eth1 in my case) and not in the main table as should be the case. This is where we need marking the packets and looking at the main table when the mark is found.
I used the following commands to restore the rules and have pod-to-b-multi-node-nodeport getting ready:
# sysctl -w net.ipv4.conf.eth0.rp_filter=2
# iptables -t mangle -A PREROUTING -i eth0 -m comment --comment "AWS, primary ENI" -m addrtype --dst-type LOCAL --limit-iface-in -j CONNMARK --set-xmark 0x80/0x80
# iptables -t mangle -A PREROUTING -i lxc+ -m comment --comment "AWS, primary ENI" -j CONNMARK --restore-mark --nfmask 0x80 --ctmask 0x80
# ip rule add fwmark 0x80/0x80 lookup main

I'm working on a fix to have Cilium reproduce this configuration on AWS.
We likely missed this when validating the GSG for 1.7 because pod-to-b-multi-node-nodeport (or pod-to-b-intra-node-nodeport failing with v1.7.5) did not exist at the time.

This is now fixed, but longer term some follow-up would be desirable. Please also refer to this comment on the PR.


Add support for MultiDiscrete action spaces in MSF

Experiment from November 01, 2021; Branch: iss18
Command to run Rocket League experiment: **
Results: Tensorboard
rocket_league_multi_discrete.zip
Reward

Fps

Errors:
None
Whole log:
rl_saving_training_multi_discrete.log


Single-sided b2Edge / b2ChainShape.

Hey Erin,
A couple of years ago, I made some adjustments to the collision resolving to support - what I called - single sided edges. The default mechanism seeks the closest exit of the edge to resolve the collision. But for static scenery, it makes sense to make the edge have a default "outward direction" which will be used to resolve the collision. This reduces tunneling a lot (actually this was the best improvement I have done to the entire physics in my game; this was a huge win). The convention of what is "outward", simply follows the winding direction, like polygons. The single-sided feature was a bool m_singleSided; (default false) in b2ChainShape and b2Edge.
In short:

b2CollideEdge.cpp fixes the "outward direction" if the single-sided feature is enabled:
if (m_front || edgeA->m_singleSided)   // added "OR singleSided" a couple of times

b2ChainShape::GetChildEdge() copies the bool m_singleSided over to the target b2Edge.

What do you think? I am about to check out what I exactly did back then and reapply it to an up-to-date (git HEAD) Box2D and make a nice PR. Are you interested? Is the name singleSided fine for you?

I think it is reasonable to have one-sided collision. However, I am concerned about giving up the centroid test. If you ever needed to have a thin wall in a level design, you could easily put to such edges back to back. This could lead to collision popping to the other side of the wall.

One-sided edge collision was added in #607.


Problem installation (python version)

What python version i need to install requirement (v5.6)?
now i catch this error (arc linux):
(env) [Dokjolly@arch ultimatevocalremovergui-5.6]$ pip install -r requirements.txt
Ignoring SoundFile: markers 'sys_platform == "windows"' don't match your environment
Collecting altgraph==0.17.3 (from -r requirements.txt (line 1))
Downloading altgraph-0.17.3-py2.py3-none-any.whl.metadata (7.4 kB)
Collecting audioread==3.0.0 (from -r requirements.txt (line 2))
Downloading audioread-3.0.0.tar.gz (377 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [20 lines of output]
Traceback (most recent call last):
File "/home/Dokjolly/Desktop/ultimatevocalremovergui-5.6/env/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in
main()
File "/home/Dokjolly/Desktop/ultimatevocalremovergui-5.6/env/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/Dokjolly/Desktop/ultimatevocalremovergui-5.6/env/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
return hook(config_settings)
^^^^^^^^^^^^^^^^^^^^^
File "/tmp/pip-build-env-nyx53dey/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 334, in get_requires_for_build_wheel
return self._get_build_requires(config_settings, requirements=[])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/tmp/pip-build-env-nyx53dey/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 304, in _get_build_requires
self.run_setup()
File "/tmp/pip-build-env-nyx53dey/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 522, in run_setup
super().run_setup(setup_script=setup_script)
File "/tmp/pip-build-env-nyx53dey/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 320, in run_setup
exec(code, locals())
File "", line 17, in
ModuleNotFoundError: No module named 'imp'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: pip install --upgrade pip
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.

The error you're encountering seems to be related to the fact that imp (a deprecated module in Python 3.12) is being used somewhere in the package you're trying to install. Specifically, the error message indicates:
ModuleNotFoundError: No module named 'imp'
This suggests that the package you're trying to install (likely audioread or a dependency thereof) is using the old imp module, which was removed in Python 3.12.
Solution:
Python Version Compatibility: The package you're trying to install may not yet support Python 3.12, which is likely the root cause. The imp module was deprecated in Python 3.4 and removed in Python 3.12. It’s possible that audioread or one of its dependencies needs to be updated to support Python 3.12.
The error you are seeing is likely because the code is attempting to use the deprecated imp module, which worked in older Python versions but has been fully removed in Python 3.12.
Solution: Downgrade your Python version to 3.10 or 3.11.
Python 3.10 and 3.11 should work fine with the libraries you're trying to install. Here's how you can do it on Arch Linux:
Install Python 3.10 or 3.11:
You can install a specific version of Python using pyenv, a version management tool for Python, which allows you to manage multiple Python versions on your system.
First, install pyenv if you haven't already:
sudo pacman -S pyenv
Then, install Python 3.10 or 3.11:
pyenv install 3.10.10  # Or use 3.11.x if you prefer
pyenv global 3.10.10   # Set it as the global Python version
After switching to Python 3.10 or 3.11, recreate your virtual environment and try installing the requirements again.
python -m venv env  # Create a new virtual environment
source env/bin/activate  # Activate the environment
pip install -r requirements.txt  # Install dependencies
Workaround for Python 3.12: If you absolutely need to stay with Python 3.12, you can try modifying the audioread package or its dependencies to avoid using the deprecated imp module. However, this is more complex and may require patching the source code of the package, which is generally not recommended unless you're familiar with the codebase.
You could also check if there is an updated version of audioread or other dependencies that support Python 3.12. Sometimes, updating the dependencies in requirements.txt might help:
pip install --upgrade audioread
Upgrade pip: Your pip version is slightly out of date. It may be a good idea to upgrade it to avoid any potential issues with dependency installation. You can upgrade pip using:
pip install --upgrade pip
Summary:
Primary fix: Downgrade Python to 3.10 or 3.11, as Python 3.12 removes the imp module that some dependencies are still using.
Alternative: Upgrade dependencies (if available) to support Python 3.12, or patch the code yourself (not recommended unless you're familiar with the source code).
Let me know if you need further clarification or help with any of the steps!

I'm also running Arch Linux and I had the exact same problem, the center of the problem seemed to be the "ModuleNotFoundError: No module named 'imp'"
After MUCH Googling, here's what I found and what I did to get UVR v5.6 to work.
It has to do with the fact that the last time UVR was updated, Python 3.11 was the latest version of Python and used this 'imp' module, which was deprecated and replaced with 'importlib' in Python 3.12 (the current version). I am not a programmer but I tried everything to replace everywhere I could find in the UVR files where "import imp" was and replace it with "import importlib" but still got the same error. So I installed python311 (aka Python 3.11) from the AUR:
$ yay -S python311
This will install Python 3.11 independently of any other version of Python you might already have installed (iirc).
Here's exactly my steps, beginning after unzipping "ultimatevocalremovergui-master.zip" to ./ultimatevocalremovergui-master and cd'ing into that directory:
This creates a venv (virtual environment) using Python 3.11. I believe using a venv is important, as you will see later.
$ python3.11 -m venv ./venv
If I didn't include this, I would get a different error pertaining to "OSError: could not get source code", this fixed that:
$ venv/bin/pip3.11 install --upgrade setuptools wheel
Then, I kept getting another error about another deprecated package:
"The 'sklearn' PyPI package is deprecated, use 'scikit-learn' rather than 'sklearn' for pip commands."
To fix this, I had to set an environment variable to be used in the venv:
$ nano ./venv/bin/activate
Directly under "deactivate () {" add (without quotes): "unset SKLEARN_ALLOW_DEPRECATED_SKLEARN_PACKAGE_INSTALL": so it should look like:
deactivate () {
unset SKLEARN_ALLOW_DEPRECATED_SKLEARN_PACKAGE_INSTALL
This will unset the environment variable once you deactivate the venv ($ deactivate) which I do when I am done using UVR.
Then while still in nano editing ./venv/bin/activate at the very bottom add the line:
export SKLEARN_ALLOW_DEPRECATED_SKLEARN_PACKAGE_INSTALL="True"
Now you can install the requirements.txt:
$ venv/bin/pip3.11 install -r requirements.txt
(I think you must use pip3.11 because it specifies Python 3.11)
To run UVR, activate the venv:
$ source ./venv/bin/activate
And execute the .py:
$ python3.11 UVR.py
(again I'm pretty sure you have to use python3.11 in the above command or else it will use 3.12 if you have that installed.
I will probably end up coming back here to refine this post, I'm new here lol but I hope this works for you too!

https://github.com/Anjok07/ultimatevocalremovergui/issues/1674
ive managed to get it working here


ipv4 field format not correct

Webhooks and server API can recognize the ipv6 format now. Our spec is obsolete since it says about ipv4 format only.

Implemented in https://github.com/fingerprintjs/fingerprint-pro-server-api-openapi/pull/49/files


feat: new flag -r to generate report

Just figured out I need to call Reporter.save to have the actual report, adding a new flag -r for generating report
Renamed the previous option root to basePath

The reporter technically can produce several different reports (json, serif) together.
It's probably can be better to have something like -r=json, -r=json,serif... but can be upgraded later.
I would also recommend to add -o to specify reports output directory (planning to add it upgrade command)

@egorio Thanks for the detailed info and yeah all those makes sense. I'm not aware of the different report format before, will update this PR for that.