"alert.type" property

Is there a way to set this property globally and have it apply to every flow? At the moment the only way I can figure out to set this property is through the override properties in the interface, and I'd much rather just set it in the job file or globally for all jobs.

@logiclord Tagging you because it seems like you're the only one contributing to this anymore.
Is the above thing an issue or am I doing something wrong? Happy to work on it if it's an issue.

@kddeisz You are right. alert.type is part of flow properties section, which can only be specified overriide properties interface. We do have a backlog item to specify flow properties as part of zip project like .job properties file. Feel free to contribute on this

Thanks @logiclord, is there already an existing issue? Otherwise I'll just reference this one in the future

I tried searching older ticket but couldn't find it. Feel free to propose something for this and refer this issue.

https://github.com/azkaban/azkaban/pull/1727


YAML Merge syntax is not supported for the localization files

This is more likely a feature request, but currently Im facing this as a bug, so I would like to post it here.
Im using PhraseApp for the Rails app and Im uploading translations in yml format and Im using YAML merge syntax (http://yaml.org/type/merge.html) to structure my texts and to avoid copy-pasting.
Here is a sample:
en:
  describe: &describe
    a: Something

  describe-other:
    <<: *describe
    b: Other

This should be translated with YAML parser to:
en:
  describe:
    a: Something

  describe-other:
    a: Something
    b: Other

But this is not happening when Im upload YML file via CLI. There should be 3 keys created with such upload:
describe.a
describe-other.a
describe-other.b

Instead only 2 are being created:
describe.a
describe-other.b

If I change uploaded file to
en:
  describe: &describe
    a: Something

  describe-other:
    <<: *describe

it will also create 2 keys:
describe.a
describe-other

but the last one will hold a blank value
P.S. here is .phraseapp.yml Im using
phraseapp:
  file_format: yml
  project_id: xxxxxxxx
  defaults:
    keys/list:
      sort: name
      order: asc
  push:
    sources:
      -
        file: ./config/locales/test.en.yml
        params:
          locale_id: yyyyyyyy
          tags: test

PhraseApp does not support YAML merge syntax, since this would cause quite some issues along the way. You would end up with duplicate keys in PhraseApp which is probably not what you want at all. Instead we recommend to get rid of the duplicate keys (or replace merge syntax with actual keys).
However I have noted your request and you will be notified once we're able to provide a better solution for this!


Tangram Activity: UI enhancement

Hey @llaske
I have identified a UI issue in the Tangram activity. In the Miscellaneous section, the size of the shopping cart container is very big as compared to the other containers and there is much space between the buttons.
I have attached a screenshot for your reference. Could you please take a look and share your thoughts on it?

I WANT TO WORK ON THIS ISSUE
UI can be updated in the following ways-
Padding
Margin
Border
Border radius
Thanks and regards
ADITYA DEY

No it's very dependent of the screen size.

Plus because it concern editing only, it's not important.

Ok @llaske


Added graphite support for storage of statistical data

A general hint regarding Pull Requests on Github: It is best to develop a feature like this in an appropriately named feature branch (e.g. "graphite-support") in your fork. To update the code that you want to have merged, you can then simply modify that branch (rebase it for example), and the pull request will automatically be adjusted, with no need to open another one.

The code looks good to me, but I think it would be much better to use the pickle protocol of graphite since the amount of data that is to be transferred could be quite big (we would have 350 nodes with 10 attributes each, making up a total of 3500 values.
That probably eliminates the other problem I have with the plaintext version: In the unlikely case that some community or Gluon itself adds attributes with spaces in their names, this would currently break.

Escaping of spaces is now implemented.

Great! If you could now please squash the commits, then I'd merge it.

All issues have been solved.
The case issue I mentioned in IRC was reported by a user working with the wrong branch in our fork.

I renamed ts to timestamp and merged this as 84fe43f.


Send out a reminder email for Hack Night on Friday

Hack Night's happening and we want to make sure our community knows.
Draft a reminder email recapping the details for the event that we can send out today. Run final copy by me before sending.

Done


Added Wii ASCII for wii-linux-ngx, whiite and gc-linux

wii-linux-ngx, whiite-linux and gc-linux are linux distros for Nintendo Wii. All can use the same Wii logo.

Thank you for your contribution!
This PR is merged into hyfetch since this repo (dylanaraps/neofetch) seems no longer maintained.
HyFetch is a fork of neofetch with LGBTQ pride flags, but the repo also maintains an updated version of the original neofetch, addressing many pull requests that are not merged in the original repo.
Read the "Running Updated Original Neofetch" section for more info!


Template for semi-automated checks

It may be possible to automate a check with the assistance of a little information provide via a parameter or config of some sort.
Page title might lend itself well to this, if a formula for the title were provide. For example, many BBC responsive pages will use a formula similar to "BBC - [site/brand name] - [H1 text]" to populate the title tag, where [site/brand name] should match the alt text on the brand logo, and [H1 text] the contents of the H1 tag.
The check that a page title exists is straightforward to automate and would render a boolean result.
The check that a title identifies the main content is complex. However, comparison with a provided formula could raise a warning if the formula is not met. The check could also compare the page title to other some other pages under the same URL space (bbc.co.uk/tld/xyz) to ensure they are not all the same. And the formula should probably reference the page H1 in some way.

One very general way this could work is if the user supplies a function, which can then be picked up by a standards check:
page("http://www.bbc.co.uk/news/uk-england-humber-39233017", {
   pageTitleFormat: $ => $('h1').text() + ' - BBC News'
})

Merged an example of a "semi-automated test" in https://github.com/bbc/bbc-a11y/commit/4c1c6c4faf7111de2144584d76b94eb38e212f2d


Ship a readsecret helper script in the docker image

What does this PR do?
In order to make using docker / kubernetes secrets more accessible, ship a helper script to use the agent's external secret feature.
This script allows to read secrets exposed as files, to avoid setting credentials in AD templates stored as docker labels / kubernetes annotations. It is disabled by default to avoid unknowingly exposing secrets, but setup instructions are provided in the README.md.
Security considerations:

has to be explicitly enabled
refuses to read files outside of a given root folder, to avoid exposing sensitive information stored in host volumes
script is chmod-ed 500, as per the agent's security recommendations. That means we don't support running in random-uid mode for this feature

Motivation
Make the external secrets feature easier to use
Additional Notes

For now, the agent does not support replacing ENC tokens in envvar values, one cannot use DD_API_KEY=ENC[apikey] for now, until viper allows for overrides: https://github.com/spf13/viper/pull/555

docker_integration_tests circleci step is renamed to docker_tests and includes the python tests for this script. We'll need to update the required ci statuses when merging to master


Add NXP i.MX RT support

The PR adds target definitions for various NXP i.MX RT 10xx targets. With these commits, I could use probe-rs to program the external flash of an i.MX RT 1010 EVK. I could also debug using GDB.
Although we're defining a custom debug sequence for these chips, we're not yet using any custom sequences. Instead, we're using the hooks to change how we implement system reset. Inline notes describe why I don't think we need any custom debug sequences today.
This might close #1138. However, I've only tested on a IMXRT1010 EVK using the on-board DAP coprocessor. I haven't tested on any other EVKs, or with any other non-CMSIS DAP debugger.
Update: As of this branch point, these commits weren't enough to program a 1060 EVK with an external J-Link. Thanks for testing @teburd.
These commits were enough to program a 1010 EVK with an external CMSIS DAP probe.

Rebase and resolve merge conflicts.
Change flash algorithm selection based on this idea. Looking for feedback.

Sorry this takes so long. I think this is still not correct. Maybe someone else will also add their thoughts :)

No problem. Thanks for your feedback on these ideas.
Could we answer the filter questions later? The rebased commits keep the filter as-is. Instead, we reduce the size of the MIMXRT NVM regions to match the flash algorithm's range. If the ranges are equal, the filter selects a flash algorithm. If we move forward with this, I'll open a separate issue to discuss the flash algorithm filter questions.

@mciantyre Should one of these target definitions (perhaps MIMXRT1060) work for MIMXRT1062, or would it require a new target YAML file?
I've modified my Teensy 4.1 for use with JTAG -- trying to get it working with probe-rs (ideally cargo embed specifically) :slightly_smiling_face:.

The MIMXRT1060 definition might be the closest approximation for a Teensy 4.1 target. A quick glance at the Winbond data sheet makes me think the flash algorithm could work with the Teensy's flash.
I had one report that there was trouble using these commits with a 1060 EVK. Specifically, there was trouble erasing the flash chip. Once you dig in, I'm happy to help you with any troubleshooting, although I don't have any JTAG-capable 1060 hardware.

@mciantyre Awesome, thanks!
This is as far as I get:
$ ../target/release/probe-rs-cli run ~/src/hello-teensy/target/thumbv7em-none-eabihf/debug/hello-teensy --chip MIMXRT1060  --protocol jtag
     Erasing sectors ⠁ [00:00:00] [##############################################################################################################################################################################]       0B/      0B @       0B/s (eta 0s )
 Programming pages   ⠁ [00:00:00] [##############################################################################################################################################################################]       0B/      0B @       0B/s (eta 0s ) ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 6
     Erasing sectors ⠁ [00:00:00] [##############################################################################################################################################################################]       0B/      0B @       0B/s (eta 0s )Error: The flashing procedure failed for '/home/cstrahan/src/hello-teensy/target/thumbv7em-none-eabihf/debug/hello-teensy'.

Caused by:
    0: Something during the interaction with the core went wrong
    1: A core architecture specific error occurred
    2: Failed to write register TAR at address 0x00000004
    3: An error specific to the selected architecture occurred
    4: Target device responded with a FAULT response to the request.

To sanity check that JTAG is working in general:
$ JLinkExe
SEGGER J-Link Commander V7.80d (Compiled Oct  4 2022 16:40:45)
DLL version V7.80d, compiled Oct  4 2022 16:40:22

Connecting to J-Link via USB...O.K.
Firmware: J-Link V10 compiled Sep 22 2022 14:59:36
Hardware version: V10.10
J-Link uptime (since boot): N/A (Not supported by this model)
S/N: 50122644
License(s): GDB
VTref=3.315V

Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: MIMXRT1062XXX6A
Type '?' for selection dialog
Device>
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  T) cJTAG
TIF>
Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MIMXRT1062XXX6A" selected.

Connecting to target via JTAG
InitTarget() start
InitTarget() end
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
 #0 Id: 0x0BA02477, IRLen: 04, CoreSight JTAG-DP
DPIDR: 0x0BD11477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x04770041)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FD000
CPUID register: 0x411FC271. Implementer code: 0x41 (ARM)
Found Cortex-M7 r1p1, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FD000
[0][0]: E00FE000 CID B105100D PID 000BB4C8 ROM Table
ROMTbl[1] @ E00FE000
[1][0]: E00FF000 CID B105100D PID 000BB4C7 ROM Table
ROMTbl[2] @ E00FF000
[2][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[2][1]: E0001000 CID B105E00D PID 000BB002 DWT
[2][2]: E0002000 CID B105E00D PID 000BB00E FPB-M7
[2][3]: E0000000 CID B105E00D PID 000BB001 ITM
[1][1]: E0041000 CID B105900D PID 001BB975 ETM-M7
[1][2]: E0042000 CID B105900D PID 004BB906 CTI
[0][1]: E0040000 CID B105900D PID 000BB9A9 TPIU-M7
[0][2]: E0043000 CID B105F00D PID 001BB101 TSG
Cache: Separate I- and D-cache.
I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
Cortex-M7 identified.
J-Link>Regs
PC = 00000FDC, CycleCnt = 4CE4D9D9
R0 = 000003E8, R1 = 00000000, R2 = 00000088, R3 = 0000008A
R4 = 20000938, R5 = 200004A4, R6 = 2000049C, R7 = 00000001
R8 = 0000008A, R9 = 200004A4, R10= 036D2E9A, R11= 0000032D
R12= 0000000F
SP(R13)= 20077FA0, MSP= 20077FA0, PSP= 20010000, R14(LR) = 0000015F
XPSR = 81000000: APSR = Nzcvq, EPSR = 01000000, IPSR = 000 (NoException)
CFBP = 04000000, CONTROL = 04, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00

FPS0 = 00000000, FPS1 = 00000000, FPS2 = 00000000, FPS3 = 00000000
FPS4 = 00000000, FPS5 = 00000000, FPS6 = 00000000, FPS7 = 00000000
FPS8 = 00000000, FPS9 = 00000000, FPS10= 449C8000, FPS11= 000004F2
FPS12= 40EB6DB7, FPS13= 000004EB, FPS14= 42CE0000, FPS15= 0000054B
FPS16= 00000000, FPS17= 00000000, FPS18= 00000000, FPS19= 00000000
FPS20= 00000000, FPS21= 00000000, FPS22= 00000000, FPS23= 00000000
FPS24= 00000000, FPS25= 00000000, FPS26= 00000000, FPS27= 00000000
FPS28= 00000000, FPS29= 00000000, FPS30= 00000000, FPS31= FFFFFFFF
FPSCR= 00000010
J-Link>

Kinda stumped at the moment :sweat_smile:.

[...] although I don't have any JTAG-capable 1060 hardware.

Also, if you'd be willing/interested in taking a look, I'd be happy to mail you a modified Teensy 4.1, free of charge :smile:.

From this view, it looks like it's failing on erase chip, but let's get some more logs. Note that I'm replacing run with download so that I can disable progress bars.
RUST_LOG=debug,probe_rs::probe=info ../target/release/probe-rs-cli download --disable-progressbars --chip MIMXRT1060 [path/to/your/elf]

I'm looking for more information about what we were doing when we see that fault response. This log should be verbose, so we can share it in a gist.

I notice you're using a J-Link. I only have various forms of CMSIS-DAP probes available. I've always wanted a debug-able Teensy, but even with custom board work, I couldn't perfectly replicate this setup. Thanks for the offer though 😄 let's see if we can make progress without hardware swaps.

@mciantyre
Here are the logs: https://gist.github.com/cstrahan/219a93abafc4c1abc96f599643daa4cc
I had to add --protocol jtag, as a fuse is burned during the production of Teensy's that disabled SWD.
Thanks for the help!

Taking baby steps: does a reset work? Just looking for a yes / no.
Here's the example command:
RUST_LOG=debug,probe_rs::probe=info ../target/release/probe-rs-cli reset --chip MIMXRT1060 --protocol jtag

My interpretation of the last log is that we're failing to reset. J-Link seems to report unexpected responses around our AIRCR write.
If resetting is the issue, try removing the custom reset method. This should fall back to a default reset implementation, and I'm curious if this would perform better.

Taking baby steps: does a reset work? Just looking for a yes / no.

No, looks like similar/same error as before. I'll see if I can figure out how I can use the default reset implementation.

Tried the following change, but still no luck with reset:
diff --git a/probe-rs/src/architecture/arm/sequences/nxp.rs b/probe-rs/src/architecture/arm/sequences/nxp.rs
index 9159de67..b3c49ee7 100644
--- a/probe-rs/src/architecture/arm/sequences/nxp.rs
+++ b/probe-rs/src/architecture/arm/sequences/nxp.rs
@@ -335,29 +335,30 @@ impl MIMXRT10xx {
     }
 }

-impl ArmDebugSequence for MIMXRT10xx {
-    fn reset_system(
-        &self,
-        interface: &mut crate::Memory,
-        core_type: crate::CoreType,
-        _: Option<u64>,
-    ) -> Result<(), crate::Error> {
-        self.check_core_type(core_type)?;
-
-        let mut aircr = Aircr(0);
-        aircr.vectkey();
-        aircr.set_sysresetreq(true);
-
-        // Reset happens very quickly, and takes a bit. Ignore write and flush
-        // errors that will occur due to the reset reaction.
-        interface.write_word_32(Aircr::ADDRESS, aircr.into()).ok();
-        interface.flush().ok();
-
-        // Wait for the reset to finish...
-        std::thread::sleep(Duration::from_millis(100));
-
-        // Clear the status bit. This read shouldn't fail.
-        interface.read_word_32(Dhcsr::ADDRESS)?;
-        Ok(())
-    }
-}
+impl ArmDebugSequence for MIMXRT10xx { }
+// impl ArmDebugSequence for MIMXRT10xx {
+//     fn reset_system(
+//         &self,
+//         interface: &mut crate::Memory,
+//         core_type: crate::CoreType,
+//         _: Option<u64>,
+//     ) -> Result<(), crate::Error> {
+//         self.check_core_type(core_type)?;
+
+//         let mut aircr = Aircr(0);
+//         aircr.vectkey();
+//         aircr.set_sysresetreq(true);
+
+//         // Reset happens very quickly, and takes a bit. Ignore write and flush
+//         // errors that will occur due to the reset reaction.
+//         interface.write_word_32(Aircr::ADDRESS, aircr.into()).ok();
+//         interface.flush().ok();
+
+//         // Wait for the reset to finish...
+//         std::thread::sleep(Duration::from_millis(100));
+
+//         // Clear the status bit. This read shouldn't fail.
+//         interface.read_word_32(Dhcsr::ADDRESS)?;
+//         Ok(())
+//     }
+// }

Here are the logs: https://gist.github.com/cstrahan/a9dfcf6c96a611aecbf3daeb97341c41

Hmmm... I just thought of an idea that might help.
On the Teensy, a MKL02 is used to flash programs (via JTAG) to the i.MX RT 1062. The idea is that you press a button on the Teensy and then the MKL02 takes over, at which point you use a flasher program on your computer to send your ELF file over to MKL02, which then does the actual flashing of the i.MX RT 1062.
If it might help, I could use my logic analyzer to capture that interaction between the MKL02 and the i.MX RT 1062.
Also, FWIW, I have a MIMXRT1060-EVKB on the way.

So, I decided to give the logic analyzer a spin. On my first modified Teensy, I cut the traces so I wouldn't have the MKL02 interfering, so I had to modify a second Teensy to collect the JTAG trace.
I used sigrok's PulseView to collect and decode the traces via my Hantek 4032L. I broke out the program switch to use as a trigger (triggered on low logic level). Configured PulseView to collect 50 M samples at 25 Mhz, clicked Run in PulseView, and then pressed the program button on the Teensy. So I believe the resulting trace should contain the reset bits.
I also wanted to collect a trace of the MKL02 programming the Teensy (assuming that all of that happens through JTAG and not some other side channel -- I've read something about there being several programming options for the i.MX RT 1062, including something involving serial, but I haven't read too far into that...). So I ran teensy_loader_cli --mcu=TEENSY41 -w blink_slow_Teensy41.hex and repeated the above.
Here are the two sessions respectively (in sigrok's session format, which can be view PulseView -- if you'd prefer a different format I'm sure I could export it how you desire):

teensy.zip
teensy-program.zip

This is the first time I've used a logic analyzer, so it's possible I've done something silly :sweat_smile:. Any way, time permitting, I'm going to read up on JTAG and try to comb through the trace, and as I start to understand things, I'll see if I can discern any obvious differences between what probe-rs is doing vs what the Teensy's MKL02 is doing.
I suspect you'd more readily spot any important bits, so if you're interested and have the time, I'd be super appreciative of you taking a look :smile:.

This helped me figure out the JTAG state machine: https://www.fpga4fun.com/JTAG.html
Now I need to figure out what the various IR values mean.

@mciantyre I wrote a little bash loop that tries resetting the device over and over again, and I've found that it eventually succeeds. Tried this a couple dozen times, and found that resetting would succeed anywhere between 1 and 10 attempts. This is true with or without the custom reset routine. Here's a log with a successfull reset: https://gist.github.com/cstrahan/a0d07cbf633263e510cb2716cdf21790
I've even successfully flashed the Teensy after about 20 attempts.
So maybe there's an issue with timing, or some other source of flakiness :thinking:.

Sorry for the delay. Thanks for your persistence with all this!

I wrote a little bash loop that tries resetting the device over and over again, and I've found that it eventually succeeds. [...] I've even successfully flashed the Teensy after about 20 attempts.

Great find. If it's not already used, know that we can supply a --speed flag to download and reset to control the JTAG protocol.
probe-rs-cli reset --chip MIMXRT1060 --protocol jtag --speed 100

I'm guessing 100 KHz because it's factors slower than the 4000 KHz noted in the JLinkExe output. Does playing with the protocol speed improve reliability? (Haven't dug into the code to see what the default speed might be.)
I'm otherwise unknowledgeable about the JTAG protocol, so we're in the same boat. But, you've inspired me to source a J-Link for myself. I'll try to repro this on an NXP EVK once I can find a not-priced-gouged J-Link. Thanks for sharing all these resources, too.

Is reset being done by toggling the reset line with the jtag? if so perhaps the attempt to check the status after reset is coming up too fast or some timing there. Great find!

Sorry for the delay. Thanks for your persistence with all this!

I wrote a little bash loop that tries resetting the device over and over again, and I've found that it eventually succeeds. [...] I've even successfully flashed the Teensy after about 20 attempts.

Great find. If it's not already used, know that we can supply a --speed flag to download and reset to control the JTAG protocol.
probe-rs-cli reset --chip MIMXRT1060 --protocol jtag --speed 100

I'm guessing 100 KHz because it's factors slower than the 4000 KHz noted in the JLinkExe output. Does playing with the protocol speed improve reliability? (Haven't dug into the code to see what the default speed might be.)
I'm otherwise unknowledgeable about the JTAG protocol, so we're in the same boat. But, you've inspired me to source a J-Link for myself. I'll try to repro this on an NXP EVK once I can find a not-priced-gouged J-Link. Thanks for sharing all these resources, too.

It's worth it to get the plus version

Does playing with the protocol speed improve reliability?

Indeed, setting speed to 100 makes flashing/resetting only fail maybe 1 in 10 times. But then flashing a simple LED blinky program becomes really slow :sweat_smile: -- about 90 seconds. Granted, it was pretty slow to start with.
I ordered a couple CMSIS-DAP devices that support JTAG to play around with, and will see if I have any better luck with them. Also, the EVKB board arrived, so I'll have to play around with that soonish.

Does playing with the protocol speed improve reliability?

Indeed, setting speed to 100 makes flashing/resetting only fail maybe 1 in 10 times. But then flashing a simple LED blinky program becomes really slow sweat_smile -- about 90 seconds. Granted, it was pretty slow to start with.
I ordered a couple CMSIS-DAP devices that support JTAG to play around with, and will see if I have any better luck with them. Also, the EVKB board arrived, so I'll have to play around with that soonish.

This really sounds like a missing delay between reset and checking the status of reset.

@teburd I think you're pretty much right.
First, some good news:
$ ../target/release/probe-rs-cli download --disable-progressbars --chip MIMXRT1060 ~/src/hello-teensy/target/thumbv7em-none-eabihf/debug/hello-teensy --protocol jtag --speed 8000
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
 ERROR probe_rs::probe::jlink::arm > Unexpected DAP response: 0
    Finished in 48.746s

Here's the diff that made that work:
diff --git a/probe-rs/src/architecture/arm/sequences/nxp.rs b/probe-rs/src/architecture/arm/sequences/nxp.rs
index 9159de67..acf6af45 100644
--- a/probe-rs/src/architecture/arm/sequences/nxp.rs
+++ b/probe-rs/src/architecture/arm/sequences/nxp.rs
@@ -8,7 +8,7 @@ use std::{

 use crate::{
     architecture::arm::{
-        ap::{ApAccess, GenericAp, IDR},
+        ap::{ApAccess, GenericAp, IDR, AccessPortError},
         communication_interface::Initialized,
         core::armv7m::{Aircr, Demcr, Dhcsr},
         dp::{Abort, Ctrl, DpAccess, Select, DPIDR},
@@ -356,8 +356,31 @@ impl ArmDebugSequence for MIMXRT10xx {
         // Wait for the reset to finish...
         std::thread::sleep(Duration::from_millis(100));

-        // Clear the status bit. This read shouldn't fail.
-        interface.read_word_32(Dhcsr::ADDRESS)?;
-        Ok(())
+        let start = Instant::now();
+
+        while start.elapsed() < Duration::from_micros(50_0000) {
+            let dhcsr = match interface.read_word_32(Dhcsr::ADDRESS) {
+                Ok(val) => Dhcsr(val),
+                Err(err) => {
+                    if let crate::Error::ArchitectureSpecific(ref arch_err) = err {
+                        if matches!(arch_err.downcast_ref::<AccessPortError>(), Some(AccessPortError::RegisterRead { .. } | AccessPortError::RegisterWrite { .. })) {
+                            // Some combinations of debug probe and target (in
+                            // particular, hs-probe and ATSAMD21) result in
+                            // register read errors while the target is
+                            // resetting.
+                            continue;
+                        }
+                    }
+                    return Err(err);
+                }
+            };
+
+            // Wait until the S_RESET_ST bit is cleared on a read
+            if !dhcsr.s_reset_st() {
+                return Ok(());
+            }
+        }
+
+        Err(crate::Error::Probe(DebugProbeError::Timeout))
     }
 }

A lot of that code was cribbed from cortex_m_reset_system:
https://github.com/probe-rs/probe-rs/blob/7fb62550d68e3813b4e75dadc09b60ff07c876f1/probe-rs/src/architecture/arm/sequences/mod.rs#L356-L394
So a couple things to note.
This can fail, at least under J-Link (maybe more generally JTAG?): interface.write_word_32(Aircr::ADDRESS, aircr.into())?;
While the write transfer succeeds, you'll find that perform_jtag_transfers performs an additional read in this case: https://github.com/probe-rs/probe-rs/blob/7fb62550d68e3813b4e75dadc09b60ff07c876f1/probe-rs/src/probe/jlink/arm.rs#L263-L264
It is this read transfer that subsequently fails. Perhaps this is because at that point the reset is already underway, which would make me wonder how something like a reset should be handled: should callers up the call stack know to discard this error instead of propagate it? If that's the case, and (I'm presuming) protocols like SWD don't require this write-followed-by-read dance, then we end up in strange scenario where error handling logic needs to give special consideration to the possibility that the protocol is JTAG. Feels like there might be a bit of a leaky abstraction at play, but I'm not familiar enough with the rest of the code base to say definitively.
At any rate, by ignoring the AIRCR write, we can move on to checking DHCSR.s_reset_st. However, as the code was before, this would also fail under J-Link/JTAG: in order to read from memory, we first have to write to TAR (see the following code), and this will fail shortly after reset.
https://github.com/probe-rs/probe-rs/blob/7fb62550d68e3813b4e75dadc09b60ff07c876f1/probe-rs/src/architecture/arm/memory/adi_v5_memory_interface.rs#L252-L272
This takes us to my modified version of cortex_m_reset_system, where I allow for retrying for either RegisterRead or RegisterWrite errors.
Et voilà -- everything (so far) works :)
I'm wiped, so I'm going to relax for now, but I think I'll try to open a PR tomorrow (unless someone wants to refine what I have and beet me to the punch).

Thanks for sharing this info. Your observations around the AIRCR write handling carried over to today's MIMXRT10xx reset handling behaviors. From my study, the CMSIS-DAP probe implementation has a command queue. If we're handling a batch of commands while the core is resetting -- due to the AIRCR write or the explicit queue flush -- we'll likely see an error. Just remarking that this seems similar to your observation, in that we're trying to talk with a resetting core and requiring its success.
Here's my summary of what's different across the reset behaviors based on this discussion, today's code, and the improvement from the patch. Let me know if I missed something.

Yes
No
Yes

DHCSR read handling
Retry read errors
Must succeed; no retry
Retry read or write errors

I could still reset and program a 1010 EVK with this patch. CMSIS-DAP probe, SWD.
I was curious if I could removed the fixed 100ms delay overhead in the improved implementation. I was expecting a successful read after around 100ms of looping. But if I remove it, I'll see hundreds of read / write errors, zero successful reads, and an eventual time out. I haven't dug deeper to answer why 🤷 (Put another way: I'm never looping in my setup, since the first read always succeeds.)

Yeah, that table looks right.
I tried only bumping the 100ms sleep up (so without the retry logic), but even making it 5+ seconds didn't help.
Later, I'll see if I can record how many times I end up iterating in the retry loop. I wouldn't be surprised if it's twice:

The first iteration to try reading DHCSR, which fails, but then syncs the internal state of probe-rs and/or the JTAG/DAP state
The second iteration then succeeds

Pure speculation on my part, but (to me) a hypothesis worth exploring.

I was curious if I could removed the fixed 100ms delay overhead in the improved implementation. I was expecting a successful read after around 100ms of looping. But if I remove it, I'll see hundreds of read / write errors, zero successful reads, and an eventual time out.

Maybe that ties into my speculation above: perhaps the protocol failures during reset creates a sort of "queue of confusion", and the number of post-reset-reads/writes needed to sync everything back up grows to the point that it never recovers within the 500ms of retrying. I'm being super hand-wavy, but that's my rough intuition -- even if it doesn't directly improve anything, I'd be really interested in seeing if we could get to the bottom of what's happening there.

Another fun tidbit -- I was stepping through the probe-rs code via debugger in VSCode, and when I tried using the cortex_m_reset_system retry loop, I thought it didn't help at first -- and then I realized that I used up all the time allotted for retrying within the first iteration while I was stepping around, and so it never actually never looped around a second time to retry :sweat_smile:. The joys of debugging and non-determinism, ha.

Just coming back to close the loop, in case anyone ends up here from Google or doing some archeology:
Using an MCU-LINK flashed with the latest DAPLink firmware, and using my branch that adds JTAG support CMSIS-DAP probes (https://github.com/probe-rs/probe-rs/pull/1462), I can flash the teensy with a similar "hello world" type program in just under 3 seconds. Huge improvement over J-Link.
It still fails every now and then, due to the reset issue not being resolved (I think I'll open a PR to fix that today).


Question: Usage through External Project

How might I get player info in an external project? (By which I mean it doesn't have any Bukkit or Spigot related stuff on it and it's just a java project with nothing about Minecraft on it)
Can I just enter the url to an already made dynmap and access player names and live coordinates?

May I assume that you are asking to pull information from the Dynmap into a separate Java Application?


[uart] Reduce RX FIFO depth from 128B to 64B

After more discussion with customers, it became clear that a 64B FIFO size is sufficient.

Can someone run
util/dvsim/dvsim.py -t vcs hw/top_earlgrey/dv/top_earlgrey_sim_cfgs.hjson --select-cfgs uart -i all_once

on this PR and post the results? I lost access to my VM for some reason...
If this is all-green except for uart_stress_all_with_rand_reset this can be merged (see also https://github.com/lowRISC/opentitan/pull/22026#issuecomment-1996322346).

I'm running the regression asked for above; will post the results here.

I fixed something and reran the full nightly regression.
There are some sporadic interrupt failures that should be looked at for a V2 signoff, but all tests pass with >90% of seeds except for that stress-all test that is known to fail.
I think we can move forward with this change and patch things up later for the V2 signoff.

I've now rebased this on master as I saw the same unrelated chip-level test failing repeatedly.


Added root certificates from OpenBSD as defaults

Fixes https://github.com/vapor/vapor/issues/634

Current coverage is 74.12% (diff: 100%)

Merging #31 into master will decrease coverage by 0.51%

@@             master        #31   diff @@
==========================================
  Files             6          6
  Lines           418        456    +38
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            312        338    +26
- Misses          106        118    +12
  Partials          0          0

Powered by Codecov. Last update bbb44a7...9d8e4c5


Support running steps as Kubernetes Jobs

It would be very convenient to run steps as kubernetes Job. This would enable using autoscaling (machines) based on kubernetes resource utilization, as well as sizing steps' resources for maximal cluster utilization. As it is now, you can size the agent itself, but you have to give it enough resources to run your maximally large step.

Interesting... I've not used a lot of kubernetes myself, but I've been meaning to have a play with it! Have you had any thoughts on how you'd see this working? I'd love to throw around some ideas here and see what we come up with :)

The approach I had in mind would be something like a two process model:

A master process that watches the buildkite API and creates Job objects. The master can run inside the kube cluster as a constant deployment, but it would only use a small amount of resources. It should also be able to use some config options from the step to configure the kubernetes job as necessary with resource limits and (maybe) environment variables & secrets. For failure recovery, it could use Kube annotations to get the current scheduled set of Jobs and job ids that are active.
A slave process that gets launched by the master as a Kube Job. A Job is essentially just a docker run so this would be a stripped down agent that runs a specific step and then exits. This process would include all the logic for running a step - sending back results to buildkite or running any agent plugins needed for the step. After finishing the step, the slave would exit (always successfully, so kube doesn't reschedule the job).

Getting this to work isn't terribly hard. The buildkite agent just needs a mode where it runs a specific job id and exits. The master is a bit more work, but should be pretty easy to do since it just listens for incoming jobs and schedules them - it doesn't even have to keep track of completion status, since Kube does that.
If those two are set up, just running something like https://github.com/openai/kubernetes-ec2-autoscaler will auto-scale instances as jobs come in, which would be pretty awesome :)

The buildkite agent just needs a mode where it runs a specific job id and exits.

We implemented --disconnect-after-job a while back which will disconnect after running a single job, which gets some of the way there.
We're hoping to get some time to focus on a Kubernetes stack, which will include some of this stuff. Thanks for your patience!

Any update for progress on this? is it on the roadmap at all?

No progress yet I'm afraid, have you seen https://github.com/webflow/kubekite?

It would be really nice if there were an option to combine with --disconnect-after-job providing a way to target a specific job ID. This way when launching a buildkite-agent as a job in kubernetes, you would know specifically what job it is running.
@lox is there an API that can be called from the agent that can either coerce ping to  target a specific job? Mostly getting the idea by looking at both of these which seems like a good entry point for that.
https://github.com/buildkite/agent/blob/ce69197180f2ff5b17a64259f46731d19a98c9ca/agent/agent_worker.go#L49
https://github.com/buildkite/agent/blob/ce69197180f2ff5b17a64259f46731d19a98c9ca/agent/agent_worker.go#L93
Thoughts?

@Iox what is the priority of this, while I did get kubekite to work I did have to do some manual work on it and it does feel like it should be supported officially.

Any update on this?

It would be really nice if there were an option to combine with --disconnect-after-job providing a way to target a specific job ID. This way when launching a buildkite-agent as a job in kubernetes, you would know specifically what job it is running.

Version 3.17.0 of the agent (released December 2019 added an --acquire-job flag that does exactly this.
$ buildkite-agent start --help | grep acquire
   --acquire-job value                    Start this agent and only run the specified job, disconnecting after it's finished [$BUILDKITE_AGENT_ACQUIRE_JOB]

We're not using it in any official buildkite tools yet. However anecdotally we know of a few folks using it to create one-shot agents on fargate and kubernetes. Generally there's an operator running somewhere that detects new jobs and creates a new agent pod to run the job then exit.
If you're interested in developing the ideas further, there's some occasional discussion in the #kubernetes channel on the community slack. We'd love to build and release something official for Kubernetes, but it's not on our near-term roadmap for now (too much to do, not enough time).

I think I’m going to close this with the addition of --acquire-job, the agent itself supports this nicely and anything else would be agent orchestration layered on top like the Elastic CI Stack for AWS, buildkite/helm etc 😄 :tada:


Use entity.isEntityName instead of entity.name

Currently, aliases don't work because messageParts.first is only checked against entity.name.
Using entity.isEntityName fixes this.

Thanks for contributing @WasserEsser :)

Verison with your fix was just pushed to pub @WasserEsser

Thanks!


Rename margin to glyph in the hover code

Rename margin to glyph in the hover code

Seeing a merge conflict due to recently merged PR, will fix merge conflict


Instance Segmentation on the Whole Image

@LiWentomng
In your paper, you mentioned restricting the level set to gt bounding box for segmentation and also mentioned that the training result is poor on the whole image.
How can I get the boxlevelset to run on the whole image?

Hello, @zhaoyangwei123
The gt bounding box can prevent the interference from background and other objects. We achieve this goal by the binary box-based mask (box_mask_target) as following,
           mask_scores_phi = mask_scores_concat * box_mask_target
           img_target_wbox = img_target * box_mask_target
           high_feature = torch.cat((deep_stru_feature_img, deep_stru_feature_lst), dim=1) * box_mask_target

The region outside gt box for level set  is zero, which are not participate in optimization.
You can remove the box_mask_target to run on the  whole image.


Important FIX: Local recording and Homekit Security Video recording. Cut recordings or no recordings.

Recording works here like this: when motion is detected (e.g. by Videoanalisys), it gives a signal for local or HSV recording. My corrections will make you to one and the other. But... The problem arises further. Local recording works like this: motion detection starts the recording for a predetermined time. On the other hand, HSV recordings work differently: motion detection starts the recording and each movement within couple of seconds extends the recording. While you can record both locally and HSV, the detection process itself (Videoanalisys) is one. If it is busy with one process, it will not work in the other. Hence the gaps in the recordings. The simplest and probably good solution is: set local recordings for 10 seconds and correct the code as below.
How it will work then:

Video analysis detects movement
Recording is launched and the motion detection process is blocked for 10 seconds
The local recording process is completed and the video is created and if there is no next move after the 10 seconds HSV recording ends.
If there is another move then: another local recording is created and the HSV recording is extended.

SOLUTION:

Set recording time to 10 seconds (in Camera UI Interface / settings / Recordings).

For better results enable prebuffering 4 sec.

in /homebridge-camera-ui/node_modules/camera.ui/src/controller/event/event.controller.js ,
replace:
if (!EventController.#movementHandler[cameraName] || fileBuffer)
to:
if (true)

in: /node_modules/homebridge-camera-ui/node_modules/camera.ui/src/controller/motion/motion.controller.js ,
replace:
if (camera.recordOnMovement)
to:
if (camera)

in: /homebridge-camera-ui/node_modules/camera.ui/src/controller/camera/services/videoanalysis.service.js , find a part of code similar to this one and change to this one:

// eslint-disable-next-line no-unused-vars
    pamDiff.on('diff', async (data) => {
      if (!this.finishLaunching) {
        return;
      }

      const recordingSettings = await Database.interfaceDB.chain
            .get('settings')
            .get('recordings')
            .cloneDeep()
            .value();

      const recTimer = recordingSettings.timer || 10;

      const event = data.trigger.map((data) => {
        return {
          zone: data.name,
          percent: data.percent,
          sensitivity: Math.round(100 - data.percent) + 1,
          recTimer: recTimer,
        };
      });

      if (!this.motionEventTimeout) {
        this.#triggerMotion(true, event);

        this.motionEventTimeout = setTimeout(() => {
          this.#triggerMotion(false, {
            time: new Date(),
            event: `forceClose`,
          });
        }, recTimer * 1000);
      }
    });

Restart Homebridge.

What else would I do?

Set motion detection for 15 seconds permanently - for HSV recording, local recording and for the motion sensor.
Removed from the plugin settings in homebridge: Motion Timeout and Interface Recording Timer,
Removed from the Camera UI : Recording time, and from Videoanalisys: Dwell Time and Reset Motion after.

@seydx Can You take a look, please?

@seydx Thank you very much for your reply. At the beginning I will praise Camera UI - a lot of great super work. I am looking forward to hearing about the new version.
But I know that currently in the current version many people have a problem in recording (local and HSV). I searched for a solution for a long time and found it. I tested it and it works! And even works sensationally! The whole problem is that currently in Camera UI the length of motion detection and recording is determined in advance, and in HSV dynamically. Please take a look at my PR! The code is not great but it works flawlessly! Until the release of a new plugin, maybe you would include such a fix?

@seydx I know you're extremely busy, but what is your approx timeline for the new version of Camera-UI?
I'm running into the hksv issue we're referencing above with a Raspi-V3 cam being sent in via an rtsp stream and doesn't appear to be recording :/

@mks212 How do I implement your solution steps #3-5 within Homebridge?   I cannot figure out how to get to the locations you suggest in order to edit the code.

@jondgrant
I talked with the author of the plugin - @seydx and he promised to release the correction. But I don't know when.
When it comes to editing files, you need to activate ssh and connect via ftp. How to do it you will find out on the Internet.

@seydx Thank you very much for your reply. At the beginning I will praise Camera UI - a lot of great super work. I am looking forward to hearing about the new version.
But I know that currently in the current version many people have a problem in recording (local and HSV). I searched for a solution for a long time and found it. I tested it and it works! And even works sensationally! The whole problem is that currently in Camera UI the length of recording is determined in advance, and in HSV dynamically. I described everything at the beginning of the entry. Please take a look at my PR (in camera ui, not here in homebridge camera ui) or just see code i post here above. The code is not great but it works flawlessly! Until the release of a new plugin, maybe you would include such a fix? If you release at least a beta with this amendment, I will be happy to help with the tests.

is this the PR?

🎉 A new version of camera.ui
A new version of camera.ui is currently under active development. An initial alpha/beta release and previews are coming soon. Stay tuned for exciting updates: https://github.com/seydx/camera.ui/issues/448 .
This version will no longer be developed / fixed. The new version contains many novelties and fixes (most important is for HKSV recording).


Error in installing Chrome

Hello, I came across your project while implementing deployment with dokku. I'm not clear on how dokku-apt should be used to install Chrome in my Ubuntu image, so I'd like to clarify. Any pointer would be appreciated.
Environment info:
Ubuntu 20.04.1 LTS
Dokku 0.21.4
Rails 6
The Rails app uses webdrivers and watir (a gem built on top of Selenium) to open a web page and read its content, so a browser executable needs to be installed, in this case it is expected to be Chrome.
This is what I have tried: added these files in the root folder of my Rails app (i.e. same level as app, config, etc.): apt-keys, apt-repositories, apt-packages. And here are the contents of each of the 3 files:

apt-keys: https://dl-ssl.google.com/linux/linux_signing_key.pub
apt-repositories: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
apt-packages: google-chrome-stable

But it threw the following error when I deploy (through git push dokku master):

Package google-chrome-stable is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source

Then I tried renaming the apt-repositories file to apt-sources-list, with the same content, then deployed again. This time it threw this error:

remote: W: GPG error: http://dl.google.com/linux/chrome/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 78BD65473CB3BD13
remote: E: The repository 'http://dl.google.com/linux/chrome/deb stable InRelease' is not signed.

Could you advise how dokku-apt should be used to install Chrome?
Also, as a suggestion, I think it'd be more illustrative if the README.md showed a working example with all the files needed  (e.g. install Chrome or another package) instead of / in addition to the current code snippets for the apt-* files that are independent of each other. Basically, an example that shows how the apt-* files would work together in an actual scenario rather than how each individual file should be written.
Appreciate your time. Please advise.

+1

If you're okay with using Chromium it installs without any problems since it's in Ubuntu's default repository.
apt-packages
chromium-browser


[PE-D][Tester C] Cannot add task

Labels: severity.Medium type.FeatureFlaw
original: Vanessamae23/ped#15

Feels like this should be a documentation issue.

Feels like this should be a documentation issue. To clarify in UG that tasks added to a day that typically does not exist in that calendar month will be assumed to be the last day of the month. E.g. 29th of February on a Non-Leap year, or 31st day of a month that has only 30 calendar days.

Yep, will update UG accordingly.


Article lists are incredibly laggy on mobile Firefox and overall theme performance is very low

Describe the bug
Scrolling through a list of articles is very laggy and jagged on Firefox. Overall performance of the theme is also slow.
To Reproduce
This appears to occur on pretty much every Blowfish website, including https://blowfish.page/docs/.
EDIT: For example,

The Blowfish documentation achieves 56/100 on mobile PageSpeed Insights whereas most popular Hugo themes achieve at or near 100%.
The "Welcome to Blowfish" article hits 35% on mobile and 72% on desktop.

Expected behavior
The page scrolls smoothly and overall performance is improved.
Screenshots
N/A
Desktop (please complete the following information):

OS: Android
Browser: Firefox
Version: 118.1.1 and has persisted for many months beforehand

Hugo & Blowfish versions
The scrolling issue is on most sites I have checked and the issue has persisted for months, so it should affect all recent versions.
Additional context
N/A

Importantly, this issue does not appear to be present in the upstream Congo.

Seems fine on Linux using the version 118.0.2 (64-bit).

I'll edit the issue title back to the original -- this is predominantly a mobile effect

Here, the Blowfish documentation achieves 56/100 on mobile PageSpeed Insights whereas most popular Hugo themes achieve at or near 100%.

Actually, even the "Welcome to Blowfish" article hits 35% on mobile and 72% on desktop, so this is likely a device agnostic problem.

A related issue previously observed is use of layoutBackgroundBlur lead to slowness: https://github.com/nunocoracao/blowfish/issues/907

Any suggestions on what needs to be done?

You'd probably have to profile the code to see which bits are excessively slow, but the layoutBackgroundBlur listener does appear to edit CSS style on every frame, so that would be more low-hanging fruit.

Indeed, I have this kind of problem too. Page scrolling is stuck, but when used on Firefox browser, it is better than edge browser. inPrivate mode is still stuck.

@ragibson For setups with Views/Likes that makes some sense - a list page triggers a "couple" requests to the DB. Need further investigation. Would you be able to help translate this into a set of actions that we need to fix?

It's almost certainly not a network/DB bottleneck since it's tied to scrolling for the entire lifetime of the page. On a very cursory profile from my phone it seems that Blowfish pages are ~5x more intensive on the renderer than a similar one in Congo for some reason.

I think it's due to an overzealous use of backdrop-filter in .backdrop-blur (and the -2xl, -sm, etc. variants) on many elements which is repeatedly invalidating a huge amount of the page. This, in turn, requires redrawing most of the site on every single frame of a scrolling event due to the view change. Importantly, this class is used pretty frequently even when layoutBackgroundBlur is disabled.
For example, https://blowfish.page/ requires 200-300 times as many draw calls on every frame of a scroll than other comparable sites.
For now, I've completely disabled those CSS classes on everything except the search widget and the scrolling issues are improved tremendously with effectively zero stutter.

I think I've fixed the issue in the PR above for the case where the blur features are disabled. It has the same ~200x reduction in draw calls on Firefox in that case.
Otherwise, I found a lot of documentation stating that these blur filters are inherently intensive and should be avoided, especially on mobile devices. Even after the PR, Blowfish uses them very frequently (and on multiple elements) whenever header != "basic" or layoutBackgroundBlur = true.

Use webp images and add
loading="lazy"
to _default/_markup/render-image.html
Observe the difference

@demodeveloperlab we already established this is unrelated to any network overhead or asset loading and is/was predominantly due to rendering overhead from extraneous CSS rules, but thanks for the suggestion

added @demodeveloperlab suggestion in a commit for something else and @ragibson already provided a bunch of improvements for this closing the issue


Chrome the font size is quite large than in firefox

Steps to reproduce the problem:

Open pdf viewer in chrome automatic zoom text is quite bigger than when open in firefox

What is the expected behavior? font size in chrome should be same as that in firefox
What went wrong?

As it can be seen in above image that font size is quite large

Duplicate of #16024


Split RequestParameters into Non-Identifiable and Identifiable

Changes in this Pull Request:

Split RequestParameters into Non-Identifiable and Identifiable (with and without ID path param)

Mandatory checks:

[x] latest changes were fetched from the upstream branch before creating this PR (branch is up to date)
[x] changes were tested manually
[x] unit tests were properly implemented
[x] communication about interdependent changes has been sent to the team (if applicable)
[x] respective Jenkins jobs were referenced in additional context section of this PR

OSCM Build References:
N/A
Closes #106

This change is

Codecov Report

:exclamation: No coverage uploaded for pull request head (bug/required-id-param@77b18e5). Click here to learn what that means.
The diff coverage is n/a.

Closing this PR to avoid potential conflicts with #170.
Proper solution (probably introduction of decorator pattern to request params) will be implemented in #170 for all path params.


[DRAFT] Enabling auth cookies to be shared between apps

Closing this to focus on deferring auth decisions to the ASP.NET app instead. That seems like a more robust solution. Sharing auth cookies still has some advantages and is something we may want to look into for some subset of scenarios in the future.


LCFS - Backend data table to include 'Target Carbon Intensity (TCI)' needed for calculating compliance units

Context
Backend data table(s) are needed to store the values that go in to formulas used for calculations in the compliance reporting feature of the LCFS portal. The two formulas used are:
Compliance units:

Target carbon intensity:

Reference:
Calculating compliance units PDF
Description:
This card is for adding the target carbon intensity (TCI). The TCI is the carbon intensity in which we measure the carbon intensity of the fuel supplied against. Fuel with a carbon intensity above the TCI generates negative compliance units (debits) and fuel with a carbon intensity below the TCI generates positive compliance units (credits). TCI is a product of the base fuel carbon intensity multiplied by (1-R) where R is the reduction target for that compliance period. For example, the base fuel carbon intensity of fossil-derived gasoline is 93.67 gCO2e/MJ; the reduction target in 2030 is 30%. Therefore, the TCI for the 2030 compliance period is 65.67 = 93.67 x (1-0.30).
The TCI is dependent on the fuel category (e.g., gasoline, diesel, jet), the compliance period, and the reduction target.
The inputs for the fuel categories are organized by: Compliance period | Target Carbon Intensity (gCO2e/MJ) | Reduction target %
Diesel category (CI 94.38):
2024 | 79.28 | 16%
2025 | 77.11 | 18.3%
2026 | 74.94 | 20.6%
2027 | 72.67 | 23%
2028 | 70.50 | 25.3%
2029 | 68.24 | 27.7%
2030 | 66.07 | 30%
Diesel category (CI 93.67):
2024 | 78.68 | 16%
2025 | 76.53 | 18.3%
2026 | 74.37 | 20.6%
2027 | 72.13 | 23%
2028 | 69.97 | 25.3%
2029 | 67.72 | 27.7%
2030 | 65.57 | 30%
Jet category (CI 88.83)
2024 | 88.83 | 0%
2025 | 88.83 | 0%
2026 | 87.05 | 2%
2027 | 85.28 | 4%
2028 | 83.50 | 6%
2029 | 81.72 | 8%
2030 | 79.95 | 10%
Purpose and Benefit to User:
These values are part of the intended feature that enables the calculations needed in compliance reporting. The target carbon intensity inputs shows the annual target intensity limit by fuel category (diesel, gasoline and jet) necessary to achieve a 30% reduction by 2030.
The reduction schedule for these limits by fuel category can be found in Sec. 15 of the Low Carbon Fuels (General) Regulation: https://www.bclaws.gov.bc.ca/civix/document/id/oic/oic_cur/0699_2023
Acceptance Criteria:

[ ] Given I am a , When I am , then
[ ] Given I am a , When I am , then

Development Checklist:

[ ] A
[ ] B
[ ] C

Notes:
This is setting up for a future feature that will allow IDIR access to edit the figures in these tables similar to the fuel code feature by using AG Grid.

Old act (TFRS) this is referred to as CI Limit

@Grulin There are two diesel categories in the card description. Can you please revise to include the gasoline category.


doc: user doc for CORS

This PR adds user docs for CORS.
Related: https://github.com/envoyproxy/gateway/pull/2065

/retest


CSS engineers and Customers are getting confused as articles is not clear, is this for Dynamics 365 8.2 or version  9 ?

In this article we have on the top "This topic lists the software and application requirements for this version of Dynamics 365 Server." Can we be explicit, is this for Dynamics 365 8.2 or Version 9 or both ?
If this article is for Version 9 only, please mention  "applies to 'Dynamics 365 Customer Engagement (on-premises)' "
And this article says - https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/overview  - "For on-premises customers, "Dynamics 365 Customer Engagement (on-premises)" is the official name of the product" //Version 9//

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

ID: 6bc0d3b6-63ec-daba-12b6-3f623a3215bd
Version Independent ID: a8143e0c-87e9-c2cd-60f6-3f1a1c4ecc49
Content: Software requirements for Dynamics 365 Server
Content Source: ce/customerengagement/on-premises/deploy/software-requirements-for-microsoft-dynamics-365-server.md
Product: crm-2016
GitHub Login: @Mattp123
Microsoft Alias: matp

@HinaMS and @pkunze - The top level topic has "9.x" in the title and the left hand of the article includes the version picker for either 9.0 or 9.1 (if available) versions of the topic.
Closing issue.


Do not alter the original hash in FirebaseCloudMessenger::Message.new

Fix issue #8

@freestyl3r I merged a bit prematurely, I think. Would you mind duping in FirebaseObject instead of Message? Otherwise the bug is going to be left in the other data objects that inherit from FirebaseObject.


Comma functionality with income $$

System – OS X 10.8.5
Processor 2.66 GHz Intel Core 2 Duo
Memory – 8GB 1067 MHz DDR3
Browser: Chrome Version 49.0.2623.112 (64-bit)
Went to add income and used a comma to do this.  Income calculation for salary and wages not included in total (no comma’s allowed):

Was able to apply and exit. Got email.

@Br3nda ready to be tested again.


Add a function to find densest subgraph

What is the expected enhancement?
Something that came up in the review on https://github.com/Qiskit/qiskit-terra/pull/7740 is that it would be good for retworkx to have a function to find the densest subgraph in a graph. To start we can just reuse the algorithm from the DenseLayout pass which just performs a BFS list from every node in the graph (in parallel) and takes the first n nodes from that and applies the weights and picks the most connected one with the best score from the weights. I'm not familiar with the literature on this problem space, but if there is a better algorithm that offers a faster or more complete solution we can look at implementing that too.

What is a "densest subgraph"? Take any graphs with at least one edge. Take that edgs, along with its endpoints, as a subgraph: it has density 1, the highest possible.

That's my bad it should be something like find_densest_subgraph_of_size or something like that. Specifically the function is given a graph of M nodes we want to find aubgraph of size N that has the highest degree of connectivity between the nodes. I agree if N = 2 then this is any pair of nodes with an edge but for N > 2 it's not as simple.


[Bug] Fern temporary files created as directory

Describe the bug
Somewhat related to #1998.
When running fern generate --local on Linux, the CLI generates the temporary files as directories:
drwx------ 3 user user 4096 Sep 21 23:08 fern-1350-d5GZ7wpkIfeQ

So the Java generator fails:
Exception in thread "main" java.lang.RuntimeException: Failed to read plugin configuration
	at com.fern.java.AbstractGeneratorCli.getGeneratorConfig(AbstractGeneratorCli.java:67)
	at com.fern.java.AbstractGeneratorCli.run(AbstractGeneratorCli.java:116)
	at com.fern.java.client.Cli.main(Cli.java:342)
Caused by: java.io.FileNotFoundException: /fern/config.json (Is a directory)
	at java.base/java.io.FileInputStream.open0(Native Method)
	at java.base/java.io.FileInputStream.open(FileInputStream.java:219)
	at java.base/java.io.FileInputStream.<init>(FileInputStream.java:157)
	at com.fasterxml.jackson.core.JsonFactory.createParser(JsonFactory.java:1029)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3495)
	at com.fern.java.AbstractGeneratorCli.getGeneratorConfig(AbstractGeneratorCli.java:65)

I thought the issue was related to the docker mounts, but the host files are marked as directories, so maybe the issue comes from the CLI and not the Java generator.
Expected behavior
fern-api should generate the IR and other config files as files and not directories.
CLI Version
0.42.12
Java Generator: 2.1.0
Additional context

improvements to --local are not being prioritized right now as we encourage users to go through our cloud generation service. closing but open to re-engaging down the line.


Create 黑(KataGo CUDA)_vs_白(SAI)_黑(KataGo CUDA)胜_20240727210050.sgf

Might need to take a pause with that

DOn't think it's possiable

might not working with SAI or have more time


Add DisableGridEditing to set-pnplist cmd

Type

[ ] New Feature

What is in this Pull Request ?
Add DisableGridEditing parameter to set-pnplist cmd

Thanks @reshmee011 !


Will Aleph support permessage-deflate for WebSocket ?

See: Compression Extensions for WebSocket draft-ietf-hybi-permessage-compression-28

When talking about protocol-level support, generally Aleph will support whatever Netty does.  Based on a quick look, it appears this is supported (https://netty.io/4.1/api/io/netty/handler/codec/http/websocketx/extensions/package-summary.html), but I'll need to spend some time hooking it up.  I'll leave this issue open until that's complete.

Thank you.

@ztellman I think it's safe now to close this issue 🤔


Improve glide dependencies using fire

where is the :fire: ?

Raw emoji meant to be there... okay without :fire: this time?

I've removed the subpackages directive, but I will reintroduce if there is a reason to do so, but I think we can merge now anyway (see: https://github.com/Masterminds/glide/issues/424)

looks good to me


vlc: <IP_ADDRESS> -> 2.2.6

Motivation for this change
newv ersion
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[X] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

There are quite a few packages that depend on this. Please run nox-review wip to check that they are all OK.

That command doesn't do anything for me. When I run nix-shell -p nox --run "nox-review pr 26084" it fails because of #24911 interfering.

I'm not sure exactly what your workflow is like, but I will recommend this (assuming your have the channels remote):
git checkout -b pr_26084 channels/nixos-unstable
git cherry-pick 6b69a6e34f43ce3e0b5d55a9b92fb27cf58002ac
nox-review wip --against 65477dcd34 # the last commit on nixos-unstable

Hope this helps!

Stock Fedora 25, with nixpkgs. The certificate thing from #24911 is superirritating.

I ran nox-review wip here and it passed with flying colors. Thanks @armijnhemel !


Elitemobs incompatible

hello , when i'm using Resource Pack Manager, where you can list, all resources by highest to lowest priority, it doesent work with magic, magic is using an own resource pack , and resourcepackmaanger combines them all together but it isnt working propertly ? , anyway i get the ressource pack to download ?

Use /getrp url for a download link. Then use /mhelp to see how to disable the resource pack functionality.


Add a common cloudprovider observer

cc @deads2k

proof that it works - https://github.com/openshift/cluster-kube-controller-manager-operator/pull/217

/lgtm


nixos/cri-o: Add RFC42 'settings' option

Motivation for this change
This migrates the virtualisation.cri-o module to use an RFC42-compliant settings option.
Previously, the only way to set CRI-O settings was to add a drop-in using environment.etc.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

cc @NixOS/podman
@ofborg test cri-o
Please squash first and third commits. Also reword the second (or drop it).

@zowoq Done!


Remove docid with scope=anchor

Example: https://github.com/ietf-ribose/relaton-data-ids/blob/99b3eadf8840bd841a0044effa87faa4d4e65fce/data/draft-3k1n-6tisch-alice0-00.yaml#L18-L20

We consider these anchors a detail only relevant for legacy xml2rfc API support, and they are not document identifiers.
We will maintain anchors separately as part of mapping metadata (or generate them dynamically), and not keep them in source data.

Just in case, I think we should first check what Robert further replies in this thread: https://github.com/ietf-ribose/bibxml-service/issues/206#issuecomment-1136058412
cc @ronaldtse

@strogonoff @ronaldtse
Should we still have anchor in BibXML output?
If yes, can we use primary docid as anchor as it is (without replacing spaces and slashes)?
If no, where should we render primary docid in BibXML output?

How does "primary docid" look like right now? Why does it have spaces and slashes?

@andrew2net  I believe we were discussing this question with Robert; i.e. ”do we need to maintain all old anchors as is, or can we generate them from docid even if this means they will sometimes differ a bit?” (see https://github.com/ietf-ribose/bibxml-service/issues/206).

If yes, can we use primary docid as anchor as it is (without replacing spaces and slashes)?

Some replacement may be needed, but this can be done by the app that generates XML.

How does "primary docid" look like right now? Why does it have spaces and slashes?

@ronaldtse, primary IDs for RFCs and RFC subseries have spaces (example 1, example 2).
Apart from that, I suspect primary (citeable) identifiers of non-IETF documents in misc often should have spaces (but don’t): for example, I feel like ISO 10646-1-AD2.1996 should actually be ISO/IEC 10646-1:1993/AMD 2:1996. (I think we are going to do something with such documents, e.g. replace them with documents from authoritative datasets.)
And, non-IETF documents in our own authoritative sources often contain slashes (example).

Should we introduce an IETF RFC-specific property that contains the anchor? Similar to how 3GPP has special release.project_end and similar keys, we could have a special bibxml.anchor key or similar. cc @ronaldtse
Currently, docid with type=anchor seems incorrect. For example, it’s RFC4 here, but it should be RFC0004 (see xml2rfc tools output as an example). Did we change it unintentionally?🤔 cc @andrew2net

@strogonoff since we started fetching documents from the https://www.rfc-editor.org/rfc-index.xml dataset, which isn't in a BibXML forma and doesn't contain anchors, we can remove anchors from the relaton-data-rfcs without any problem.
We still have a BibXML parser. I don't know who uses it, and does it need to reproduce the anchors in the Relaton's BibXML output? cc @ronaldtse

@andrew2net Interesting:

we started fetching documents from the https://www.rfc-editor.org/rfc-index.xml dataset

Maybe this is why the anchor has changed?

Maybe this is why the anchor has changed?

@strogonoff yes, it's definitely so.
BTW we still parse BibXML to create documents for relaton-data-ids, so the IDs still have anchors.

@strogonoff @ronaldtse can we close this issue?

@andrew2net I'm still hoping we can get rid of the anchors in the Relaton data. @strogonoff can we?


Added the ability to use a differently-named elm-format binary

On macOS' homebrew, elm-format is installed as two separate binaries:

elm-format-0.17
elm-format-0.18

elm-vim only ever looked for 'elm-format', but now the name of the
binary can be overridden by setting g:elm_format_binary.

From what I've seen, it's common to allow the user to set the path for the linter/formatter in these types of plugins, so maybe doing that instead of setting a name would allow more flexibility, and accomplish the same thing?

Do you mean an absolute path, as in the full path to the executable (/usr/bin/elm-format), or path as in the environment variable (PATH=/usr/bin:/usr/local/bin:/bin)?
Because the latter isn't good enough (the binary still has a different name), and the former can be achieved with the code in this pull request as-is: simply let g:elm-format_binary = '/my/custom/path/elm-format'.

I was thinking more of the former, a full path to the executable. Ah okay, cool that it can be done as-is. Maybe that could be added to the explanation?

To be pedantic, it depends on what vim thinks your shell is (see :help 'shell'). If it's a POSIX shell, and your g:elm_format_binary contains no slashes, it will search your PATH. If g:elm_format_binary contains a slash, I guess it'll be considered a relative path (though I'm not sure what would then be considered the current working directory).
Anyhow, I'm definitely open to suggestions on how to put all or some of the above information into the documentation.
Also, to be honest, I haven't actually tried putting more than a name in g:elm_format_binary. I hadn't even thought of it, and your question led me down a rabbit hole of vimdoc and POSIX specs.

Ah I guess that makes it tricky to be reliable. Honestly, the commit you pushed up is fine for me.


[TV emulator] "Unhandled exception: System.DllNotFoundException" on first launch of an app

I/ConsoleMessage(10510): FlutterApplication.cs: OnCreate(54) > switches: --enable-dart-profiling --enable-checked-mode
E/ConsoleMessage(10510): FlutterApplication.cs: Run(39) > Unhandled exception: System.DllNotFoundException: Unable to load shared library 'flutter_engine.so' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libflutter_engine.so: cannot open shared object file: No such file or directory
E/ConsoleMessage(10510):    at Tizen.Flutter.Embedding.Interop.FlutterEngineRunsAOTCompiledDartCode()
E/ConsoleMessage(10510):    at Tizen.Flutter.Embedding.FlutterApplication.OnCreate()
E/ConsoleMessage(10510):    at Runner.App.OnCreate()
E/ConsoleMessage(10510):    at Tizen.Applications.CoreBackend.UICoreBackend.OnCreateNative(IntPtr data)
E/ConsoleMessage(10510):    at Tizen.Applications.CoreBackend.UICoreBackend.Run(String[] args)
E/ConsoleMessage(10510):    at Tizen.Applications.CoreApplication.Run(String[] args)
E/ConsoleMessage(10510):    at Tizen.Applications.CoreUIApplication.Run(String[] args)
E/ConsoleMessage(10510):    at Tizen.Flutter.Embedding.FlutterApplication.Run(String[] args)
E/ConsoleMessage(10510):    at Runner.App.Main(String[] args)

The reason is still unknown but it may have something to do with the Linux kernel used by TV emulators.
A temporary solution:

Change the api-version value in tizen/tizen-manifest.xml file to something different (e.g. 4.0 → 6.0)
Launch the app (flutter-tizen run)
Change the value back to the original value (the error will not be generated on successive launches after the app launches successfully at least once)

Another workaround is just to install the same TPK twice if the package has previously not been installed on the device. I'll open a PR with the patch.


prerelease.1, updates to kafka v3.3.1

Update strimzi kafka version to 3.3.1 (Tested using odpi-egeria-lab chart)
Fix tag for jupyter notebooks to V314

One concern - an update to kafka could show up issues under load - Ideally we should run our tests with the final version.
I think the risk is low, but we should probably rerun CTS

I suggest we merge, and I'll launch the CTS. Probably the risk is extremely small


respect isatty parameter

respect isatty parameter to force enable ANSI escape sequence
fix issue #85

Coverage increased (+0.01%) to 91.558% when pulling 9c7d35de751992064d418f34ceef95d7101ef03f on sudoerChris:patch-1 into<PHONE_NUMBER>bc39057f824c545f2decab49c019ad on xolox:master.

DearChris,
I already made something similar :
https://github.com/xolox/python-coloredlogs/pull/95
since Peter seems to be absent, You might use that one in the meantime :
https://github.com/bitranox/bitranox_coloredlogs

Hi both and thanks for the feedback. I've just published coloredlogs release 14.1 which fixes this issue.


Updated install.sh

Added if statement to prevent re-downloading of get-pip.py if it already existed within the directory.

@routeback Can you submit this to the dev branch please? thanks


Add option --force to SDK's scan command

Closing as implemented in https://github.com/tenchi-security/zanshin-sdk-python/pull/58


docs: added container section

Fixes #3097

added the container section in technologies.md

Hi @BalaadityaPatanjali thanks fr the contribution! Please check the pipeline here to see what links are not working

Hi @BalaadityaPatanjali thanks fr the contribution! Please check the pipeline here to see what links are not working

Markdown-link-check is failing because in docs/docs/guides/otel.md , link for setup of monitoring other namespaces is not working and i am not familiar with that at all. So, i don't think i should replace that link. A little guidance here would be appreciated.

@BalaadityaPatanjali that dead link was apparently moved to https://prometheus-operator.dev/kube-prometheus/kube/monitoring-other-namespaces/
Could you please update it as part of this PR?

@BalaadityaPatanjali that dead link was apparently moved to https://prometheus-operator.dev/kube-prometheus/kube/monitoring-other-namespaces/ Could you please update it as part of this PR?

I have updated the link. Please have a look at it.

Thank you for the contribution! 🚀

Thank you for the merge !


Add Actions to publish data to storage

Creates Github Actions to automatically publish the model data checked in to github to Azure Storage. This can be leveraged by forthcoming powerbi dashboards to display the data.
As a prerequisite for these actions to work, you will need to navigate to the Settings>Secrets tab of this repo and add the following secret

https://github.com/ImperialCollegeLondon/covid19model/settings/secrets
The secret value to set can be found under the shared Azure subscription > imperialcollegecoviddata > Access keys, then copy and paste the connection string under key1

this has been done in the required repo now


Add filter suggestions under the search box on the search results page

Merge after #1428
These are deliberately only on the search results page as the most common use of these filters will be to narrow down search results. The filters work from everywhere, of course, but for education, I'd say this is the best place.

This obviously looks awful on mobile. I could tweak it slightly but it's never going to be great and I wonder if we should make this a desktop-only feature. There is one thing I considered that might help here, and which I'd love an opinion on. I added the suggestions with JavaScript as they rely on JavaScript to work, but the "Add filters to narrow search results (Learn more)." text doesn't. That could be added server-side, and also display on mobile as it'd fit nicely below the smaller search field, and just have the interactive suggestions appear on desktop only. What do you think?

This obviously looks awful on mobile. I could tweak it slightly but it's never going to be great and I wonder if we should make this a desktop-only feature. There is one thing I considered that might help here, and which I'd love an opinion on. I added the suggestions with JavaScript as they rely on JavaScript to work, but the "Add filters to narrow search results (Learn more)." text doesn't. That could be added server-side, and also display on mobile as it'd fit nicely below the smaller search field, and just have the interactive suggestions appear on desktop only. What do you think?

I made a decision on this and implemented it. 😬
The "Add filters to narrow search results (Learn more)." is now inserted server-side and so will always be visible with or without JavaScript and on all browser sizes. Then, the suggestions are appended but are hidden on mobile.

It's trivial to make these display on mobile, if that's what we decide we want.

One thing that strikes me is that these filters in the snapshot tests are going to break them whenever time moves forward, and it has a habit of doing that... 😬

I think it'd be nice to have the tappable link on mobile because typing the _ in particular is a bit annoying on a mobile keyboard. But I think it's fine to leave it out as well. People probably aren't triaging dependencies for their next big project on the phone :)
In a native app you'd probably put those as custom suggestions above the keyboard but I'm pretty sure there's no API for that for web text fields.

Regarding the snapshots: what if we use Current.date() on the Swift side to inject a
<!-- searchFilterStartDate: 2021-11-08 -->

(or some other DOM construct) into the page that JS can read and use? That way we could fully control it without having to come up with JS dependency injection setup.

In a native app you'd probably put those as custom suggestions above the keyboard but I'm pretty sure there's no API for that for web text fields.

You are correct

Final tweaking. Fixes the snapshots issue and re-works the sentence so the Learn more link is at the end:

Also, no longer hidden on mobile:


Merge arbitrary metadata via all Sibyl.Handlers.attach_* functions.

It would be very useful to be able to attach arbitrary metadata which gets passed into all our handlers when attached, for custom metadata overrides such as setting a custom debug_user: :vereis or env: :staging.

Something like Sibyl.Handlers.attach_all_events(Sibyl.Handlers.OpenTelemetry, metadata: %{user<EMAIL_ADDRESS>reason: "debugging weird bug"})
Doing this would attach the above to all OpenTelemetry traces which could then be used for additional filtering on whatever OpenTelemetry compatible UI you use.


fix(amplify-graphql-types-generator): underscore support in swift

Swift codegen did not handle underscores field names. The generated code used undescore name for map
but getters/setters used camelCase name similar to the name of the property. Udated code to use
underscore name for gettters and setters
fix #643
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

From https://github.com/aws-amplify/amplify-cli/pull/846


split in multiple cells leaves the remaining cells as blank

I have a simple table like this :
     id | name
     -------------------
     1 | Jack, Jeff, Win
     -------------------
     2 | Jonhy, chin

I want to split the cell name by "," and want to preserve the id, so after the split, the table
should look like this :
     id | name
     -------------------
     1 | Jack
     -------------------
     1 | Jeff
     -------------------
     1 | Win
     -------------------
     2 | Jonhy
     -------------------
     2 | chin

HOWEVER, if I click on edit cell > split multiple-values  the cell will be separated but the id will be blank (in the case that the cell was separated). Below I gave an example that shows you how it looks like after clicking on it
       id | name
     -------------------
        1 | Jack
     -------------------
     null | Jeff
     -------------------
     null | Win
     -------------------
        2 | Jonhy
     -------------------
     null | chin

http://stackoverflow.com/questions/39317899/open-refine-split-in-multiple-cells

Filling down the cells solved the issue

Glad you figured it out!

@tfmorris Is there a way to fill dow all the columns with one click? Instead of clicking in each columns and filling down?


Fix: Compare Action route

Subject
This fixes the issue where a revision could not be viewing via the CompareAction route.
I am targeting the 1.x branch because it's a bug fix which is backwards compatible.
Closes #405.
Changelog
### Fixed

- The CompareAction route is now working.

Lint errors were found. A patch is also available.
Please see the report: https://flintci.io/repositories/8593/analyses/63517
This comment was posted by FlintCI. It can be disabled in the repository settings.

@BurningDog Can you do the same for others actions like in PR https://github.com/sonata-project/EntityAuditBundle/pull/331/files ?

@VincentLanglet ok, done - I searched for all calls to the find() and findRevisions() functions to ensure that the passed $id is either an int or a string.

Are these changes disallowing the possibility of using entities with composite ids?
If yes, I think we must add validations to prevent these entities to be marked as auditable from the beginning.

Composite ids can be used if you call directly the method of the AuditReader, but cannot be used with these actions.
I dont think it's specifically new since you cannot pass composite ids in a url. Can u ?
Imho if something should be added it would be better to create an issue about, in order to not delay this bugfix

I dont think it's specifically new since you cannot pass composite ids in a url. Can u ?

Yes, by instance you can use this approach for the ORM manager: "/app/entity/1~42/show".

Imho if something should be added it would be better to create an issue about, in order to not delay this bugfix

I agree.


Search Bar based on Tags in field Tasg of Metadata

We will add more tags into the metadata based on the PLG posts. Main tags will be this ones:

just do it
immersion
high frequency, low stakes
iterate
serve using software
immediate disintermediation
open meritocracy
your users, your teammates
everyone does projects
trade risk for velocity
closed loop
value pipeline
dare to be wrong, take pride in being humble
happy, live, and fast
code settles arguments

I want to have a bar above the blogs where one can select one or more tags to get the right blog posts.
Additionally, the search should give results based on what search is fining in the metadata Tags.

will be "fixed" by #20


Allows rosetta to be built with pax+praxis

Allows rosetta to be built with pax+praxis as a base
CI will build rosetta with pax and t5x
Allows local directories to be provided as build-context to let the user specify custom source

@ashors1 for viz

@nluehr for viz


RegRipper Tool

Hi Team,
Is there a possibility to do registry analysis for .reg format files. If yes, please let me know how to do it.
Note: I am new to SIFT workstation.
Thanks,
Guru

Hi @gurumt05 this isn't really the best forum for these sorts of questions/conversations, it just doesn't get much attention from individuals who can answer these. You are better off emailing the dfir email list with questions like this. Issues here are mainly reserved for installation and distro management.
That being said, SIFT does come with a regripper.pl tool that can be used. You should be able to access it via CLI by typing rip.pl

Hi @ekristen
thanks for the information, could you please let me know the email id of DFIR team as i was checking i couldn't get it. please help me

https://lists.sans.org/mailman/listinfo/dfir


WebContainers not working in chrome

Describe the bug
Stackblitz complains Incompatible Web Browser when using WebContainers in chrome. Projects work completely fine in Firefox.
Link to the blitz that caused the error
https://stackblitz.com/edit/vitejs-vite-byctbg?file=src%2FApp.jsx
Steps to reproduce

Create new project using WebContainers
Attempt to start project
Preview window shows incompatible error

Expected behavior
I expect the project to boot up correctly and display the preview as the projects not using WebContainers.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots

Platform
Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 103
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 142275950,
  "usedJSHeapSize": 117023946,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 872be04de15f32da2f6e3973878bcc22a4a17b5d

Additional context
No response

I also have that same issue in microsoft edge.

I found that this issue only happended when creating a Node.js project.
When I created fron-end only projects, it worked fine.

Same issue for me!
This showed up today for node projects, even tho worked fine before on the same chrome browser.

Thanks for reporting. This should now be resolved. Sorry for the inconvenience.


Is this library still alive?

Looks like no :(

Someone with a good alternative to this library ?

any alternative to this library? i need custom search functionality like in this library.

This library is still working, it just doesn't seem have active maintenance anymore. I'm still using it in my project.  Works good so far so good (not perfect) with angular 4.

Any alternative to angular 5?

@diandsonc  Have you tried this library with Angular 5? I'm thinking to using angular 5 too, but not sure if it will work since it's depends on Angular 2.

@sh977218 Yes. It's working with Angular 5 without bug.

this could be an alternate
https://valor-software.com/ng2-select/
Not to sure, mark some time and experiment, seems like it has good traction though!

This one is a great alternative: https://basvandenberg.github.io/ng-select/#/home
I'm not a big fan of valor-software's components because some of them have huge performance issues (ng2-select included) with medium data sets (=> 200 items)

this could be an alternate
https://valor-software.com/ng2-select/
Not to sure, mark some time and experiment, seems like it has good traction though!

It's was reborn in the fork: https://github.com/optimistex/ngx-select-ex


:sparkles: restructure deps command with package-lock.yml

resolves #6643

Description
this PR restructures the dbt deps command, aiming to add a few new key features:

[x] create a new package-lock.yml file that will keep record of all packages installed during the last dbt deps run
[x] use newly created package-lock.yml as the default file to install packages from, which helps reduce install time
[x] adds 2 new dbt deps subcommands: dbt deps lock and dbt deps add
[x] refresh dbt_packages/ directory each time dbt deps is run (no more persisting old packages left in the directory)

the below will provide an overview of the changes, what they accomplish, and some a lot of detail on implementation and examples. sorry in advance for the length! 😅

dbt deps lock

the new lock command will take the packages in packages.yml and list them and their transitive dependencies in a new package-lock.yml file.
package versions should be resolved for each dependency, else, error thrown.
package-lock.yml will get written to the project_root alongside packages.yml.

example command:
dbt deps lock

dbt deps add

allows a user to add a package to their packages.yml file with configurable version and location of a given package.
added a --dry-run flag to the dbt deps add sub-command that, when False, will re-create the lock file after a new package is added to the packages.yml file. (this is setup as False by default in argparse, a user can use the flag and set to True to not persist changes down to the package-lock.yml
overwrite package info in packages.yml if a package name already exists (either explicit or fuzzy name matching)
added a quality check to ensure a version is passed in whenever the source != "local"

example command:
# add package from hub (--source arg defaults to "hub")
dbt deps add --package dbt-labs/dbt_utils --version 1.0.0

# add package from hub with semantic version
dbt deps add --package dbt-labs/snowplow --version ">=0.7.0,<0.8.0"

# add package from git
dbt deps add --package https://github.com/fivetran/dbt_amplitude --version v0.3.0 --source git

# add package from local (--version not required for local)
dbt deps add --package /opt/dbt/redshift --source local

# add package to packages.yml WITHOUT updating package-lock.yml
dbt deps add --package dbt-labs/dbt_utils --version 1.0.0 --dry-run True

dbt deps 🚩(this is now changed as of 2/10/2023, changes noted in strikethrough) 🚩
1. largely remains unchanged in order to stay backward compatible

given the recent changes to migrate away from argparse -> click, i had to make changes to the dbt deps command. when working with click, i couldn't get dbt deps to be a @cli.group(), while also allowing it to run as an isolated command. i tried using invoke_without_command=True in the @cli.group() decorator, but still didn't get it to work. so for now, i changed dbt deps to be an isolated @cli.group() and added a new @deps.command("install") to handle the old dbt deps functionality (this mimics how dbt docs and dbt source are setup.

key takeaway: dbt deps has been changed to dbt deps install and should be treated as a breaking change. happy    to discuss this further!

when a user runs dbt deps dbt deps install, it will check immediately to see if a package-lock.yml file exists in the project root directory. if not, it will create one based on the packages.yml in the project root directory.
package-lock.yml now becomes the default for installing packages.

example command:
# install packages
dbt deps install

# shows help page for dbt deps sub-commands
dbt deps

Examples:
example packages.yml:
packages:
  - package: dbt-labs/dbt_utils
    version: 0.9.2
  - git: "https://github.com/google/fhir-dbt-analytics"
    revision: 386e8430a4b9735466c90c3313ae67c31dbef58f
  - git: "https://github.com/elementary-data/dbt-data-reliability"
    revision: 0.6.11

example package-lock.yml
packages:
- package: dbt-labs/dbt_utils
  version: 0.9.2
- git: https://github.com/google/fhir-dbt-analytics
  revision: 386e8430a4b9735466c90c3313ae67c31dbef58f
- git: https://github.com/elementary-data/dbt-data-reliability
  revision: 0.6.11
- package: calogica/dbt_expectations
  version: 0.7.0
- package: yu-iskw/dbt_unittest
  version: 0.3.1
- package: calogica/dbt_date
  version: 0.6.3

⚠ Some advice/clarification needed:
first, i believe the breaking change from dbt deps to dbt deps install should warrant discussion on this PR. notes are in the above section titled dbt deps
additionally, there were 2 notable strange yaml formatting issues i ran into with this when outputting data to yaml files:
number 1:
using yaml.dump() or yaml.safe_dump() when writing package/lock results formatted slightly differently than what's in a packages.yml and advertised on the dbt website. i tried indent formatting but nothing I tried seemed to be able to replicate like what's above in the packages.yml vs. package-lock.yml examples.
number 2:
another strange one that i couldn't figure out with yaml formatting was how to get the semantic versioning to display like it's advertised on the dbt website. for example:
online:
packages:
  - package: dbt-labs/dbt_utils
    version: 0.9.2
  - package: dbt-labs/snowplow
    version: [">=0.7.0", "<0.8.0"]

dbt deps add
packages:
- package: dbt-labs/dbt_utils
  version: 0.9.2
- package: dbt-labs/snowplow
  version:
  - '>=0.7.0'
  - <0.8.0

if i use the default_flow_style=None argument in yaml.safe_dump(), we can fix how lists are displayed in the yaml file, but it then messes up how dicts are displayed....
packages:
- {package: dbt-labs/dbt_utils, version: 0.9.2}
- package: dbt-labs/snowplow
  version: ['>=0.7.0', <0.8.0]

functionally, neither of these should impact programmatic reading of the yaml data, but it does make things a touch different than what's in the examples online/the expectations you hope for with file formatting.
Conclusion:
I think that covers nearly everything! please don't hesitate to ask me any questions on this. i'm really looking forward to your review and working on any changes that may be needed. thank you!
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

In terms of the yaml write I found this answer works.

@justbldwn are you still interested in working on this feature? Otherwise we can help bring it across the finish line.

@justbldwn are you still interested in working on this feature? Otherwise we can help bring it across the finish line.

so sorry for the delay in responding! i may be able to help in the coming weeks, if you have someone that takes over and you need my assistance, too, i'm happy to help where possible.

This PR was continued in https://github.com/dbt-labs/dbt-core/pull/8408 and ultimately merged.


bump isort to v5.12.0

Closes #80

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.481%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
247

Relevant Lines:
270

💛  - Coveralls

Merging without review as all checks are passing