RTOS port for NRF51 targets

This patch allows NRF51 based targets to use the RTX kernel.
The RTOS port of NRF51 is not totally straightforward because the NRF51  doesn't provide a SysTick. Therefore the port should provide an alternative timer which generate the OS tick.
In the case of NRF51, the alternative timer is generated via the channel 1 of RTC1.
More information about alternative timer as RTX Kernel Timer:
https://www.keil.com/pack/doc/CMSIS/RTX/html/_timer_tick.html
All tests builds (GCC, ARMCC) and runs on MKIT (NRF51822) and NRF51_DK targets.

I've removed setbuf from rtos tests.
All tests are still passing on nrf51_DK
+--------+----------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| Result | Target         | Toolchain | Test ID     | Test Description                      | Elapsed Time (sec) | Timeout (sec) | Loops |
+--------+----------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| OK     | NRF51_DK[DFD8] | ARM       | DTCT_1      | Simple detect test                    |        0.88        |       10      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | EXAMPLE_1   | /dev/null                             |        3.87        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_10     | Hello World                           |        0.75        |       5       |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_11     | Ticker Int                            |       11.72        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_12     | C++                                   |        1.73        |       10      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_2      | stdio                                 |        1.13        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_23     | Ticker Int us                         |       11.74        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_24     | Timeout Int us                        |       12.82        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_25     | Time us                               |       11.81        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_26     | Integer constant division             |        1.75        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_34     | Ticker Two callbacks                  |       11.73        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_37     | Serial NC RX                          |       11.41        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_38     | Serial NC TX                          |       15.98        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_A1     | Basic                                 |        1.73        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_A21    | Call function before main (mbed_main) |        1.8         |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_A9     | Serial Echo at 115200                 |        6.67        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | MBED_BUSOUT | BusOut                                |        2.66        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | RTOS_1      | Basic thread                          |       11.71        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | RTOS_2      | Mutex resource lock                   |       11.89        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | RTOS_3      | Semaphore resource lock               |        8.86        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | RTOS_4      | Signals messaging                     |        6.82        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | RTOS_5      | Queue messaging                       |        2.75        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | RTOS_6      | Mail messaging                        |        2.74        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | RTOS_7      | Timer                                 |       11.73        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | ARM       | RTOS_8      | ISR (Queue)                           |        5.82        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | DTCT_1      | Simple detect test                    |        0.89        |       10      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | EXAMPLE_1   | /dev/null                             |        3.87        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_10     | Hello World                           |        0.74        |       5       |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_11     | Ticker Int                            |       11.73        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_12     | C++                                   |        1.75        |       10      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_2      | stdio                                 |        1.11        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_23     | Ticker Int us                         |       11.76        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_24     | Timeout Int us                        |       12.83        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_25     | Time us                               |       11.82        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_26     | Integer constant division             |        1.75        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_34     | Ticker Two callbacks                  |       11.76        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_37     | Serial NC RX                          |        11.4        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_38     | Serial NC TX                          |       15.98        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_A1     | Basic                                 |        1.74        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_A21    | Call function before main (mbed_main) |        1.81        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_A9     | Serial Echo at 115200                 |        6.7         |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | MBED_BUSOUT | BusOut                                |        2.66        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | RTOS_1      | Basic thread                          |       11.72        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | RTOS_2      | Mutex resource lock                   |       11.89        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | RTOS_3      | Semaphore resource lock               |        8.86        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | RTOS_4      | Signals messaging                     |        6.82        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | RTOS_5      | Queue messaging                       |        2.77        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | RTOS_6      | Mail messaging                        |        2.74        |       20      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | RTOS_7      | Timer                                 |       11.72        |       15      |  1/1  |
| OK     | NRF51_DK[DFD8] | GCC_ARM   | RTOS_8      | ISR (Queue)                           |        6.81        |       20      |  1/1  |
+--------+----------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+

Some tests fail on NRF51822 target because there is not enough memory in the system (stdout eat 1024 bytes...):
+---------+----------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| Result  | Target         | Toolchain | Test ID     | Test Description                      | Elapsed Time (sec) | Timeout (sec) | Loops |
+---------+----------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| OK      | NRF51822[DFA8] | ARM       | DTCT_1      | Simple detect test                    |        0.85        |       10      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | EXAMPLE_1   | /dev/null                             |        3.86        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_10     | Hello World                           |        0.74        |       5       |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_11     | Ticker Int                            |       11.72        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_12     | C++                                   |        1.74        |       10      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_2      | stdio                                 |        1.11        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_23     | Ticker Int us                         |       11.74        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_24     | Timeout Int us                        |       12.82        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_25     | Time us                               |        11.8        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_26     | Integer constant division             |        1.74        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_34     | Ticker Two callbacks                  |       11.77        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_37     | Serial NC RX                          |       11.41        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_38     | Serial NC TX                          |       15.95        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_A1     | Basic                                 |        1.72        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_A21    | Call function before main (mbed_main) |        1.81        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_A9     | Serial Echo at 115200                 |        6.66        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | MBED_BUSOUT | BusOut                                |        2.64        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | RTOS_1      | Basic thread                          |       11.72        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | RTOS_2      | Mutex resource lock                   |       11.88        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | RTOS_3      | Semaphore resource lock               |        8.84        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | RTOS_4      | Signals messaging                     |        6.82        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | RTOS_5      | Queue messaging                       |        2.76        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | RTOS_6      | Mail messaging                        |        2.73        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | RTOS_7      | Timer                                 |       11.73        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | ARM       | RTOS_8      | ISR (Queue)                           |        5.77        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | DTCT_1      | Simple detect test                    |        0.85        |       10      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | EXAMPLE_1   | /dev/null                             |        3.87        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_10     | Hello World                           |        0.73        |       5       |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_11     | Ticker Int                            |       11.72        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_12     | C++                                   |        1.74        |       10      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_2      | stdio                                 |        1.12        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_23     | Ticker Int us                         |       11.72        |       15      |  1/1  |
| FAIL    | NRF51822[DFA8] | GCC_ARM   | MBED_24     | Timeout Int us                        |       16.13        |       15      |  0/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_25     | Time us                               |       11.81        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_26     | Integer constant division             |        1.74        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_34     | Ticker Two callbacks                  |       11.81        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_37     | Serial NC RX                          |       11.37        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_38     | Serial NC TX                          |       15.97        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_A1     | Basic                                 |        1.71        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_A21    | Call function before main (mbed_main) |        1.81        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_A9     | Serial Echo at 115200                 |        6.65        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | MBED_BUSOUT | BusOut                                |        2.67        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | RTOS_1      | Basic thread                          |       11.73        |       15      |  1/1  |
| TIMEOUT | NRF51822[DFA8] | GCC_ARM   | RTOS_2      | Mutex resource lock                   |       40.24        |       20      |  0/1  |
| TIMEOUT | NRF51822[DFA8] | GCC_ARM   | RTOS_3      | Semaphore resource lock               |       40.25        |       20      |  0/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | RTOS_4      | Signals messaging                     |        6.81        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | RTOS_5      | Queue messaging                       |        2.76        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | RTOS_6      | Mail messaging                        |        2.75        |       20      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | RTOS_7      | Timer                                 |       11.72        |       15      |  1/1  |
| OK      | NRF51822[DFA8] | GCC_ARM   | RTOS_8      | ISR (Queue)                           |        6.81        |       20      |  1/1  |
+---------+----------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+

The test MBED_24 failed on this run for an unknown reason, I've rerun it on NRF51822 and it work:
+--------+----------------+-----------+---------+------------------+--------------------+---------------+-------+
| Result | Target         | Toolchain | Test ID | Test Description | Elapsed Time (sec) | Timeout (sec) | Loops |
+--------+----------------+-----------+---------+------------------+--------------------+---------------+-------+
| OK     | NRF51822[DFA8] | ARM       | MBED_24 | Timeout Int us   |       12.87        |       15      |  1/1  |
| OK     | NRF51822[DFA8] | GCC_ARM   | MBED_24 | Timeout Int us   |       12.86        |       15      |  1/1  |
+--------+----------------+-----------+---------+------------------+--------------------+---------------+-------+

@0xc0170 Could you review this ?

@mbed-bot: TEST
HOST_OSES=ALL
BUILD_TOOLCHAINS=ALL
TARGETS=NRF51822,NRF51_DK

Funnily enough, MBED_24 passed in the CI!

After some investigation, MBED_24 tries to ensure that us ticker work correctly.
It setup a callback every 500us and count for the time a callback has been set.
Every time the callback has been set 2000 times, a trace is printed on the serial line.
The Host side of the test verify that a trace is emitted every second.
Unfortunately, the precision of the RTC on nrf51 is 30.5us.
That mean that the callback will not always be scheduled after 500us but scheduled after 500us + [0:30.5]us.
Another cause of drift is the time required to setup a new callback, the nrf51 runs at 16Mhz by default. There is just 16 cycles occurring by us, it is easy to get a significant drift in that area if a program set a callback every 500us.
Failling tests results:
HOST: Property 'host_test_name' = 'wait_us_auto'
HOST: Property 'description' = 'Timeout Int us'
HOST: Property 'test_id' = 'MBED_24'
HOST: Start test...
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.11 sec (0.11) [FAIL]
* in 1.09 sec (0.09) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]

Successful tests results:
HOST: Property 'description' = 'Timeout Int us'
HOST: Property 'test_id' = 'MBED_24'
HOST: Start test...
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
* in 1.10 sec (0.10) [OK]
Consecutive OK timer reads: 10

Ah I see, thanks for clarifying @pan-. Did you have a chance to test with IAR?

@bridadan No, IAR is not supported on nrf51 if I recall correctly, it will be, later.

@pan- my mistake, thanks for clarifying.
Test results looks good, so +1 from me.

LGTM


Update Kubernetes version to 1.20.6

Kubernetes Version to 1.20.6 and Golang Version to 1.15
Docker image for testing:
docker.io/swisstxt/cloudstack-kubernetes-provider:v1.20.6-ae73327f

Any update on this - can this be merged?

@rhtyd @joschi36 Can this be merged after 1.0 is released? Since there only exist isos for 1.16. Post release isos for 1.18, 1.20 can be created and tested

@rhtyd @davidjumani I also vote to move this out of v1.0, so we finally can get the first release done. Never intended to be in 1.0

Okay removing from 1.0 milestone

This PR can be closed (already merged as part of #44 )


python311Packages.aiohomekit: 3.0.3 -> 3.0.4

Diff: https://github.com/Jc2k/aiohomekit/compare/refs/tags/3.0.3...3.0.4
Changelog: https://github.com/Jc2k/aiohomekit/releases/tag/3.0.4
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release 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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 257279 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.homekit_controller
python310Packages.aiohomekit
python310Packages.aiohomekit.dist
python311Packages.aiohomekit
python311Packages.aiohomekit.dist


Upgrading Heroku "One Click Install" Helpy

Hi,
If I've installed using your "One click installer" on Heroku what is the upgrade process? I wasn't able to find any documentation available on this procedure.
Thanks!

You will have to clone the heroku repo, pull and merge from github and then push it back to Heroku.  Visit your app's homepage on Heroku and navigate to the Deploy section. Follow the instructions under Heroku Git - Use Heroku Toolbelt. In particular:
heroku login
heroku git:clone -a <your app name>
cd <your app name>

Once you have this set up, you can update your app with changes from the repository with the following:
git remote add upstream https://github.com/helpyio/helpy
git pull upstream master
git push heroku master

@scott Thanks. Appreciate it.

is there any need for migration?

Yes I think you do have to explicitly tell Heroku to migrate on version upgrades using heroku run rake db:migrate if the update requires a migration.


Create README for developing grpc storage plugins

@chvck would you mind adding a simple README.md to plugin/storage/grpc about developing a new storage plugin?  Not the end user documentation (it would go to docs), but developer documentation.

Yes sure thing.


Add icons to user group index pages

Re-uses the icons created so far to illustrate https://snoopycrimecop.github.io/www.openmicroscopy.org/products/omero/scientists/index.html
https://snoopycrimecop.github.io/www.openmicroscopy.org/products/omero/developers/index.html
https://snoopycrimecop.github.io/www.openmicroscopy.org/products/omero/institution/index.html
Also removed OMERO.mail from institutional key features as not a priority feature and gives us a round 8 features like the other pages.
Still icons to add to the dev index page

@lunson if you could confirm you're happy with the staging pages for this once you're around, I'll get this merged for you and then you can carry on with a fresh branch.

@hflynn Looks good to merge!


Fog shifts slightly on token movement

This was an issue present in previous versions of Foundry, but now I can only replicate with Perfect Vision module active.  Tests were done with only the Perfect Vision Module Active version 1.9.6 on Foundry 0.87 Hotfix 1, and is reproducible.  Seemingly each adjustment of a token that causes a fog of war update shifts the existing fog up and to the left slightly.  After many movements it becomes very noticeable and causes issues.
For reference, scene dimensions are 6001x6001, Gridless, but with grid of 100px, 5ft.  Underlying image is 4096x4096.

Thanks for the report. I haven't tested it extensively. I assume it is fixed in v1.9.7. Let me know if it isn't.


Bad hash table

Hi,
i get the message "Bad hash table - repair ASAP /home/xxx/go/bin/onionscandb/relationships/Onion/0" after scanning an onion site with onionscan.
my system:
uname -a
Linux user 4.10.0-28-generic #32~16.04.2-Ubuntu SMP Thu Jul 20 10:19:48 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.3 LTS
Release:	16.04
Codename:	xenial
any ideas?

Hello!
A broken hash table can be resulted from sudden system shutdown. Please make a backup of the entire database directory, and then run Scrub() function on the collection, here is an example:
https://github.com/HouzuoGuo/tiedot/blob/master/example.go#L58


feat: Improve message_bus.py _process_message performance with a pxd file

Nov 11 14:14:54 homeassistant homeassistant[471]: 2022-11-11 08:14:54.221 DEBUG (MainThread) [aiohomekit.controller.ble.pairing] Qingping Temp RH H [D3:2C:5A:5B:53:13] (id=CA:CC:78:DE:9D:4D): Subscribing to gatt notify for iid: 60
Nov 11 14:14:54 homeassistant homeassistant[471]: 2022-11-11 08:14:54.321 DEBUG (MainThread) [aiohomekit.controller.ble.pairing] Qingping Temp RH H [D3:2C:5A:5B:53:13] (id=CA:CC:78:DE:9D:4D): Subscribing to gatt notify for iid: 59
Nov 11 14:14:54 homeassistant homeassistant[471]: 2022-11-11 08:14:54.421 DEBUG (MainThread) [aiohomekit.controller.ble.pairing] Qingping Temp RH H [D3:2C:5A:5B:53:13] (id=CA:CC:78:DE:9D:4D): Subscribing to gatt notify for iid: 145
Nov 11 14:14:54 homeassistant homeassistant[471]: 2022-11-11 08:14:54.521 DEBUG (MainThread) [aiohomekit.controller.ble.pairing] Qingping Temp RH H [D3:2C:5A:5B:53:13] (id=CA:CC:78:DE:9D:4D): Subscribing to gatt notify for iid: 257

We are able to keep up with the 100ms buffer on the CSRs now almost every time


⚠ Bofrost.at has degraded performance

In fcc6e65, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1331 ms

Resolved: Bofrost.at performance has improved in d12682a after 6 minutes.


Upgrade/deprecate weave

Do we still use it?

I have no idea who is using weave right now...
Also the last commit https://github.com/weaveworks/weave was in August... It looks like that Weave is not under active development

We don't recommend it to anyone for quite some time now.


Connection knots are not removed when a connection is disconnected.

Describe the bug
When deleting a node that has a connection with knots, while the knots stop being rendered, when the graph is reloaded after an editor restart, the knots are added even though the connection they're based on no longer exists.
Expected behavior
Connection knots are dropped when a connection is broken.
Actual behavior
No response
How to Reproduce?
No response
Godot full version
4.2.2-stable
Orchestrator version
2.1.dev2
Additional information
No response

Can no longer reproduce, likely fixed with the Orchestration refactor/split.


README: Include Resolved Issue Reporters as Contributors

For those that submitted an issue that was resolved (ex. #26 and #28 ), shouldn't they be included in the contributor list as well?

@all-contributors
Please add @bontebok for bugs.
Please add @SectOLT for bugs.

ThaNKS!


drag and swipe not work on touch screen

I try to make an action sheet using vueuse gestur. On the desktop it worked fine but on the touch screen, the drag does not trigger.
pls see in demo
here is my source code

may i know what is your solution?


how to use 'KEYS *'

I want to get all keys in redis cluster，and i use "(redisReply *)redisClusterCommand(g_redis_cluster_conn, "KEYS *")",  but , this returns NULL
please help me, much THX

the "nodeIterator ni"  don't need to release ?

the "nodeIterator ni"  don't need to release ?

Only if you malloc it. In the example above, it is stack allocated. initNodeIterator() doesn't allocate anything.

the "nodeIterator ni"  don't need to release ?

Only if you malloc it. In the example above, it is stack allocated. initNodeIterator() doesn't allocate anything.

Got it, thanks a lot.


moved validation to docker validator

Issue #, if available:
https://github.com/aws/eks-anywhere/pull/3409#discussion_r976956447
Description of changes:
Moved provider specific docker endpoint validation from cluster level to provider level.
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve

/approve


Fix warn logs in BeanPostProcessorChecker

Description
Fixes #38631
Fix warn logs: Mark the bean post processor related beans as internal to avoid the log 'Bean xxx of type xxx is not eligible for getting processed by all BeanPostProcessors'
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

/check-enforcer override

For pipeline failures will be fixed in later PR.

/check-enforcer override


Autonomous Worlds on Substrate

Project Abstract
SpellCrafter is a "spell-crafting" card game where players discover ingredients, unlock recipes, and craft new spells in a challenge to be the most powerful mage. Players encounter offchain challenges (puzzles) that must be solved in order to unlock new recipes that can be used to craft spells on-chain. This game is a re-imagining of Arcane Assembly, a game developed with Dojo (on Starknet), as a Substrate-native game. Even though a game in it's own right, SpellCrafter is intended to be a used as a source of magic spells for other games that need them for their players. In the game, players must search the web, offchain, in order to learn knowledge that they can use to unlock recipes, such as by solving a puzzle or a riddle.
To enable SpellCrafter on Substrate, we introduce publicly verifiable on-chain randomness, timelock encryption, verifiable computation (zkSNARKs) and practical witness encryption capabilities to web3 gaming on Polkadot/Substrate. In collaboration with ChainSafe Gaming, Ideal Labs aims to enhance web3 gaming on Polkadot by leveraging the Ideal Network's post-finality gadget, an MPC solution that enables a randomness beacon, to develop a practical witness encryption mechanism. That is, it enables the usage of verifiable randomness on-chain (and across chains), allows for messages to be locked for future blocks, and provides secret sharing capabilities, wherein the network acts as a distributed key generator and constructs keys for 'authorized' users (where authorization is gated behind valid proofs). This approach ensures fair play, enables asynchronous player coordination, and introduces proof-of-knowledge gating for in-game assets, events, or anything. This would not only allow for games like zkHunt or dark forest to be implemented on Substrate, but would allow for new on-chain conditional data access mechanisms to be created, such as requiring a zkSNARK of some in-game knowledge in order to proceed to the next level.
Application Checklist
[x] The application template or delivery template has been copied and aptly renamed for an application (project_name.md) and a delivery (project_name_m1.md).
[x] I have read the games bounty guidelines.
[ ] Payment details have been provided (Polkadot address in the application). (will add shortly)
[x] The initial PR contains only one commit (squash and force-push if needed).

Hey @driemworks
Thank you for the application, is this ready for an initial review?

Hey @driemworks
Thank you for the application, is this ready for an initial review?

@darkfriend77 yes, this is ready for review

🤞🏼 ...

💪

Dear Application Team,
I hope this message finds you well. I would like to provide some feedback on the game’s bounty application:
Game Design Document (GDD):
The current GDD does not seem to reflect aspects related to the spelling and the powerful mage game loop. It still appears to be centered around the concept of "Fragments." Additionally, there are no visuals provided for the spell narrative. And how you will be distinct from the Arcane Assembly Game (https://github.com/ArcaneAssemblers/spellcrafter)
Similar Games:
In the section discussing similar games, Xaya and Mud are mentioned. These are game engine frameworks/projects rather than actual games. Please provide examples of playable games that are similar to the proposed project.
Interaction Time and Time lock Randomness:
Clarification is needed on the interaction time for time lock randomness and execution. Specifically, how long does a player need to wait for these interactions? What is the minimum time required for such interactions?
Randomness Mechanism:
Instead of using a very expensive randomness function for this, wouldn't a traditional coin flip randomness mechanism be sufficient for this game? Considering the typical value of game assets, a simpler method might be much more practical and more efficient. High-stakes games, such as those in the casino and gambling sectors, would benefit probably more from tech-intensive solutions.
GDD and Spell Crafting Details:
There seems to be a focus on the spells being usable in other games, but what is the incentive for another game to use spells from SpellCrafter, as opposed to minting and selling their own NFTs that they have full control of? Additionally, how easy would it be for you to use the spell system in another game? Will there be any APIs/libraries/plugins/etc. that simplify the interaction with the system, or will game developers be expected to implement blockchain interaction themselves?
The lack of a comprehensive GDD detailing the spell-crafting process makes it difficult to understand the core mechanics of the game. It appears that the game is designed more around a technical use case rather than utilizing technology to enhance a game feature.
Bounty and Grant Structure:
It may be more appropriate to split the bounty into a traditional Web3 Foundation grant for Milestones 1 and 2, as they are very technical. As a suggestion only Milestone 3 should be included in the game's bounty, accompanied by a proper GDD.
Thank you for considering this feedback. I look forward to seeing the improvements and clarifications in the revised application.
Best regards,
The Games Bounty Team

@HopeClary thanks a lot for this helpful feedback. We are currently working on the required changes based on your feedback. I will ping you back once we have it ready for a new review. Thanks again.

Subject: Important Update on Games Bounty – Transition to DOT Play Bounty
Dear Team,
We hope this message finds you well. We are writing to inform you of an important update regarding the Games Bounty you expressed interest in.
As you may be aware, the Games Bounty has recently undergone a significant transformation and has now been rebranded as the DOT Play Bounty. As part of this transition, the curators of the original Games Bounty no longer have access to the associated funds, nor do we have any authority over the allocation or spending of the 100k DOT that was initially set aside for this initiative.
We would like to take this opportunity to sincerely thank you for your interest and the time you have invested in the Games Bounty. Your enthusiasm and dedication to contributing to the Polkadot ecosystem are greatly appreciated.
While the Games Bounty has been discontinued in its previous form, we encourage you to explore the following avenues to continue your involvement:

Contact DOT Play: If you are interested in participating in the newly formed DOT Play Bounty, we recommend you contact the DOT Play team for further details and potential opportunities.

Create a Treasury Proposal: Consider submitting a proposal through the Polkadot governance system. This is an excellent way to secure funding for innovative projects that align with the broader Polkadot ecosystem.

Web3 Foundation Grants: You may also explore opportunities through the Web3 Foundation by applying for a grant. The foundation continues to support promising projects that contribute to the growth and development of the Web3 ecosystem.

We are confident that your talents and ideas will find the right platform for success, and we encourage you to continue your journey within the Polkadot and Web3 communities.
Thank you once again for your understanding and continued contributions.
Best regards,
Cedric
Former Games Bounty Curator


Added Mole details

I added details of Mole injection tool and it's web sites for find it's documentation and it's open source code.

@all-contributors please add @Dilshan1997 for doc tutorial


Update managing-accessibility-settings.md

Why:
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[ ] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[ ] For content changes, I have completed the self-review checklist.

Thanks for your interest in the Docs—
These changes appear to be based around personal preference, and don't meet our style guide (that's also partly why the tests are failing). I'd recommend that you raise an issue first in future, so that we can discuss changes before you spend time writing them up. That way everybody—most importantly, you as the contributor—has a better overall experience.
You can also feel free to check out one of our issues marked help wanted.


Merge pull request #1 from docker/master

update from origin

- What I did
- How I did it
- How to verify it
- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:azhong/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


When I execute "make" ,an error will be reported

I guess the version of my "cmake" is inconsistent with yours. Can you tell me your version of cmake

The version of mine is 3.10.2

The version of my ubuntu is 18.04

you need to replace all std::nan() with std::nan()

you need to replace all std::nan<>() with std::nan

you need to replace all std::nan<>() with std::nan()

ok，thanks a lot

You mean NAN with std::nan() ? There is no std::nan in the code?

@cpsoymilk which compiler version are you using? I can't reproduce.

I changed the version from master to 0.2.0, and then it works normally

@cpsoymilk Which compiler version and OS were you using? This is an error that should be fixed.

Do you mean the version of "make"? Besides, I don't know what OS you mean. I'll show you tomorrow. It's in my office computer.

I mean which Operating System (OS), like Ubuntu 18.04, 20.04, Windows 10..? And wich compiler? (What do you get when you execute c++ --version) ?

Okay, I'll get back to you later

Experiencing the same compilation errors when using CentOS 7 and GCC 8.3.1. Replacing std::isnan<double>() with std::isnan() fixes the problems.

should be fixed with https://github.com/grepthat/libOpenDRIVE/pull/52, feel free to reopen if it's still broken


Link to 'Network Readiness Assessment' is pointing to the old SoF portal

Link to 'Network Readiness Assessment' is pointing to the old SoF portal, should be updated to live documentation

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

ID: 8e8b2651-40bb-0d26-6126-d88689047f23
Version Independent ID: 5be83c7d-ef7f-5582-4a6c-f0709fb2ec7b
Content: Prepare your network for Microsoft Teams - Microsoft Teams
Content Source: Teams/upgrade-prepare-environment-prepare-network.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@DrLippert Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @scanum
Good Day!
Could you please let the document owner know that the link to "Network Readiness Assessment"(https://go.microsoft.com/fwlink/?linkid=855800) doesn't work.
Thank you!

hello colleagues, same query here - the link to Network Readiness Assessment does not work (https://www.skypeoperationsframework.com/Offers?pageState=NetworkReadiness). I have seen that it was under the investigation a month ago, is there any ETA yet? Thank you

@LanaChin Hi Lana! The link to "Network Readiness Assessment"(https://go.microsoft.com/fwlink/?linkid=855800) doesn't work. Could you please aid with next steps? Thanks!

Hi @DrLippert, @sowjanya365, and @algalakt  - The topic is deprecated and replaced by https://docs.microsoft.com/microsoftteams/prepare-network. Thank you.


Method to set the Dragdealer to initial state

I need to set new Dragdealer options on window resize. Is there a method to set everything back to initial state?

There is the init()-method. I don't think it's documented but at least for us it seems to be working fine to reset the number of steps:
// [...]
var dragDealer = new Dragdealer(someDomElem,someConfig);
// [...]
function reset(newNumberOfSteps) {
  dragDealer.options.steps = newNumberOfSteps
  dragDealer.init();
}
// [...]


Seminars as events

It seems that our template allows specifying "events" (see https://research-group.netlify.app/event/ and https://github.com/wowchemy/starter-hugo-research-group/tree/main/content/event). This might be more flexible than a table (e.g., I think it would be better to show the latest and upcoming talks first, and we could automatically sort the talks by using events)? cc @bajinsheng

The event tab requires too much information, a large portion of it is not necessary I think. And also it would take a longer time to maintain it. Also, the events cannot be sorted. Have not found a solution about how to customize it.
I am not sure it is worth spending so much time maintaining the seminar information.

Merged #44.

Great, thanks! I think we could still leave the "seminar" name, which is more specific than "events". It seems also your update in https://github.com/nus-test/nus-test.github.io/pull/42 got lost?

Completed by #46


Content for blog post - Orchestrate Spark Applications using AWS Step Functions & Apache Livy

Sample codes which are used for blog post - Orchestrate Spark Applications using AWS Step Functions & Apache Livy

Can somebody merge this please?


glTF PBR volume shader

First attempt to add a volume shader for KHR_materials_volume.
Does not work yet, it fails with the error "No renderable elements found in gltf_pbr_default.mtlx". Not sure what I am doing wrong...
My idea was to create a nodegraph consisting of surface and volume shader. The nodegraph has a single output node of type material. Is this the correct way of structuring it?

As explained in a comment in #1 (link), support for combining surface and volume shaders is not yet complete. It requires a BSDF-over-VDF layer operator which is worked on at the moment.

Volume support is now supported using a BSDF-over-VDF layering operator as part of a surface shader. Closing this.


Support for Windows Server Containers

Feature Description

One-line feature description (can be used as a release note): Support for Windows Server Containers
Primary contact (assignee): @michmike
Responsible SIGs: sig-windows
Design proposal link (community repo): TBD
Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @brendandburns, @JiangtianLi, @alinbalutoiu
Approver (likely from SIG/area to which feature belongs): @michmike
Feature target (which target equals to which milestone):

Beta release target 1.9

How is this different from https://github.com/kubernetes/features/issues/116?

@luxas my bad. i thought i was supposed to create a new issue versus updating the existing one. closing this item now.


Missing documentation for breaking changes

There are two undocumented breaking changes when migrating from v3 to v4 bindings.

In v3, not found resources (via PK/ID bindings) returned null to the handler, now they throw an exception before the handler is invoked. This required us to pause a migration effort.

Multi-level bindings no longer work. E.g., partitionKey={a.b} throws an exception saying b cannot be found. This additionally required us to pause our migration effort.

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

ID: 85e586ec-9cc0-d6b2-d64a-085dcb1b32c2
Version Independent ID: 032d523f-4af0-b219-7f14-425f8ef131e2
Content: Migrate Azure Cosmos DB extension for Azure Functions to version 4.x
Content Source: articles/azure-functions/migrate-cosmos-db-version-3-version-4.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@oadrian2
Thanks for your feedback! We will investigate and update as appropriate.

@ealsur can you help out with this and see if updates are needed? Thanks!

@oadrian2 Can you please describe a bit more what you mean with examples? At least number 2 seems related to Expression Resolution in Bindings which is something that the Cosmos DB Extension does not do (it's the Functions Runtime). Did you also upgrade the Functions Runtime?

Are you using .NET or other languages? Number 1 seems a bug that was already fixed: https://github.com/Azure/azure-webjobs-sdk-extensions/pull/878

Thanks @oadrian2. Then the bugfix applies. The migration document should not be updated as this was considered a regression. The bundles should have an updated version that contains this fix. Bundle releases are handled by the team at https://github.com/Azure/azure-functions-extension-bundles (in case there is no bundle release that contains this existing fix, they should handle it there).

I've updated our code back to v4 and it does seem to be working now. Thank you for the update.


Multiple instances uses same options

Hello I have an form in which you can add as many select2 single select boxes as you want. It is done by cloning it, before cloning I do $(".select.custom-select.select2-selection--single").select2('destroy'); and after cloning $("select2.control").select2(). Problem is that if I select option A in select1 I cannot select it in select3 or select5.. It's disabled option. It seems that all those instances are linked between.. :/ Any workaround or something I have missed?

Hello,
I tried to duplicate your issue but did not manage to.
Maybe if you use the destroy method on your original <select> and not on the <span> created by the select2 it would work better?
We will be able to help you more if you provide a snippet of you code.

It sounds like you are calling .select2("destroy") on the selection element (generated by Select2) instead of on the original <select>. That would explain why things may not be getting cleaned up correctly.

This appears to be more of a usage question than a bug report or common feature request.  As we continue to keep the Select2 issue tracker geared towards these two areas, bug reports and common feature requests, we are redirecting usage questions to other communities such as the mailing list, IRC, or Stack Overflow.

Necroing to include some additional info.
The problem is related to the attribute data-select2-id given to the options of the select, even if I use the destroy method both the select and the options keep all of the select2 data bind to them.
If different options in different select have the same data-select2-id it's impossible to select the same value, the fastest way to solve this for me was to remove the attribute manually.
I'm currently using the 4.0.8v


Summary overwrite earlier models

Summary writer overwrites the previous version of models. For example, when I save any model that has (step + 1) % 100 == 0, then when saving model-1299 model-299 is deleted.
Environment info
Operating System: Ubuntu 14.04
Installed version of CUDA and cuDNN:
(please attach the output of ls -l /path/to/cuda/lib/libcud*):
-rw-r--r-- 1 root root 189170 Sep 23  2015 /usr/local/cuda-7.5/lib/libcudadevrt.a
lrwxrwxrwx 1 root root     16 Sep 23  2015 /usr/local/cuda-7.5/lib/libcudart.so -> libcudart.so.7.5
lrwxrwxrwx 1 root root     19 Sep 23  2015 /usr/local/cuda-7.5/lib/libcudart.so.7.5 -> libcudart.so.7.5.18
-rwxr-xr-x 1 root root 311596 Sep 23  2015 /usr/local/cuda-7.5/lib/libcudart.so.7.5.18
-rw-r--r-- 1 root root 558020 Sep 23  2015 /usr/local/cuda-7.5/lib/libcudart_static.a
If installed from binary pip package, provide:

A link to the pip package you installed:
The output from python -c "import tensorflow; print(tensorflow.__version__)".
0.11.0rc0

If installed from source, provide

The commit hash (git rev-parse HEAD)
The output of bazel version

If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
if (step + 1) % 100 == 0:
saver.save(sess, 'model', global_step = step)

The Saver class has options that control deleting previous checkpoints.  Please see the documentation for details: https://www.tensorflow.org/versions/r0.11/api_docs/python/state_ops.html#Saver


Set x-windows urgent on bell

I'm not really an expert on how this is implemented (and especially have on idea what the Mac/growl/whatever equivalents are), but I use the X urgent-on-bell feature of my current terminal to flash the window title in i3wm when long-running commands (compiles/etc.) are complete.
E.g. a short command to run as a test to see if it works is:
sleep 2 && echo -e "\a"

The sleep is because if you're already looking at the terminal window, i3wm will ignore/reset the urgent flag right away, so "sleep 2" gives me time to switch to another window/desktop to see if, when echo \a runs, the window it's in is highlighted. I don't know how other window managers handle/display the urgent flag.
Understood if this is considered bloat, but hopefully it wouldn't be too hard to add; I currently have it working even through tmux sessions, so a bell in a terminal session on a remote host gets percolated through tmux back to my local terminal window, and it's very nice/important for my workflow, to get me back on task.

Sounds reasonable. Adding it to the list!


Compare manually drawing a rectangular ROI with the results derived from SC segmentation?

From Kyle's comment here:
https://docs.google.com/document/d/1NFWOPu-yP1u0O62YUX4w5IrzwaRwaMozwdJPhJ32XLA/edit?disco=AAABF6huiJ0
To do a proper comparison, I would need to draw an angled rectangle for the mask, and I don't know how to do that using SCT.
But as a quick and dirty comparison, I did the following: The current pipeline uses a spinal cord segmentation as input for the shimming coefficient calulation in ST, but the ROI is a failry narrow cylinder around it. I merely modified so that we now calculate in a rectangle drawn around the SC segmentation, then adjusted the rectangle to be as wide in A-P and R-L as the B1+ shim box was for Volume Specific shimming. So the ROI still followed the curve of the spine (as opposed to merely being an oblique box), but it was much closer to the one used by the scanner.
I can only compare the CoV calculation that ST itself does (it combined the measured B1+ maps using the new, calculated shim values, and then takes a CoV within the ROI), which is not a like-for-like with out experiment, but still, for sub 04, using the COV reduction RF shimming approach, I see 22.1% using the spinal cord+cylinder mask, and 27.5% using the rectangular mask. So this might be worth exploring further and putting into an appendix.
Moving discussion here @jcohenadad
Pls ping me if this is of interest (and if I have not explained it wll, it is late here)

amazing-- that's exactly what we need. If you can take a screenshot of both masks, we report the numbers, and that's all we need

I've put together the numbers and the two masks (overlaid) in a figure for Sub04 here: https://docs.google.com/presentation/d/1SY4UtXNas9o-S4GYaqGDehS0KoUiwA-ISRyhL6LHxAA/edit#slide=id.g2b9660979b0_1_0


Gradients?

I have not been able to get gradients to work? Any advice? Has anyone been able to get this to work?

@harman7: gradients are not supported yet.

I'd love to see gradients too. @JohnCoates i wrote you an email with some code that might help with the implementation


Use upstream product-profunctors

I also had to update the lts version, as there was a dependency problem with lts 6.22 and product-profunctors-<IP_ADDRESS>.
It compiles fine, haven't run it.
This should be the only remaining bit blocking https://github.com/folsen/opaleye-gen/issues/8 .

@phile314 Thanks for contributing!


Fixed isExclusiveDevDependency and covered it with test

Current dependencies on/for this PR:

main

PR #14   👈

This comment was auto-generated by Graphite.


Creating a icon pack 1

Creating an icon pack like this either by using the SVG icons for these and storing them in  the libraries for example
https://libraries.excalidraw.com/

If you mean that we need to add svg icons in our sketch page... like we are doing with arrow-icons (which are svgs too)...then I would like to work on this

I will create a button that says "add icon" in the sketch page....after clicking that button a white screen appear which tells the user to select an icon. after the user selects one icon... the user gets to use that icon in the sketch page!
If you like the "separate white screen for showing icons idea" then I want to work on this
working on this idea would require to put a HOLD on those other "create icon pack" issues coz this white page needs to be created first

I will create a button that says "add icon" in the sketch page....after clicking that button a white screen appear which tells the user to select an icon. after the user selects one icon... the user gets to use that icon in the sketch page!
If you like the "separate white screen for showing icons idea" then I want to work on this
working on this idea would require to put a HOLD on those other "create icon pack" issues coz this white page needs to be created first

This is what we require not individual icons

If you mean that we need to add svg icons in our sketch page... like we are doing with arrow-icons (which are svgs too)...then I would like to work on this

This is the requirement!

Hello, Can I work on this? @smaranjitghose

progress 85%. will submit PR for this one and other iconsPack issues today

Hello, Can I work on this? @smaranjitghose

After 3 days. Once @ashuvssut has submitted his initial PR


GraphBuilder - verify node name is not reserved method of nn.module

Pull Request Description:
Checklist before requesting a review:

[ ] I set the appropriate labels on the pull request.
[ ] I have added/updated the release note draft (if necessary).
[ ] I have updated the documentation to reflect my changes (if necessary).
[ ] All function and files are well documented.
[ ] All function and classes have type hints.
[ ] There is a licenses in all file.
[ ] The function and variable names are informative.
[ ] I have checked for code duplications.
[ ] I have added new unittest (if necessary).

This PR intends to rename reserved name of node on the Graph such as "to" in order to avoid confusion between node of the output model and the PyTorch operation "to".
We still consider if the operation "to" as part of input model is valid MCT input, therefore, setting this PR to draft.


Support Flink 1.15

Signed-off-by: mzareba<EMAIL_ADDRESS>
Problem & solution
We want to make sure OpenLineage's Flink integration supports several major Flink versions, namely at least 1 behind current release (1.14 and 1.15 as of today).

[x] Make sure Flink integration builds and executes tests in proper manner.
[x] Append CircleCI parameters' matrix with 1.15 version.

Checklist

[ ] You've signed-off your work
[ ] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[ ] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] You've updated the CHANGELOG.md with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

Relevant issue: https://github.com/OpenLineage/OpenLineage/issues/979


Move HOMEBREW_CACHE to ~/Library/Caches

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

Thanks to @dlitz for the initial PR, the security checks and sorry for the massive delay in getting this to a 🚢able state.
I decided on ~/Library/Caches as it's a user-specific cache directory that OS X already knows how to handle sensibly and avoids any permission issues. For people who already had that directory around it'll also be a no-op for them and for those who wish to keep using /Library/Caches they can set the HOMEBREW_CACHE environment variable.

Is the migration really worth it? Seems like starting over with fresh caches might be less prone to support problems.

By moving cache folder in a per-user paths, we will need a new place for Formula lock files. Otherwise, it will be broken for multiple user cases.

This looks like it's going to trigger migration of ancient cache directories if the user has an old /Library/Caches lying around because he switched to ~/Library/Caches/Homebrew a long time ago but never blew away the old /Library/Caches/Homebrew.

The migration will also be totally random on a multi-user system based on a race of who sits down and uses brew first.

I agree with @ilovezfs, starting with fresh seems to be the most simple and robust way.

I agree with @ilovezfs, starting with fresh seems to be the most simple and robust way.

@xu-cheng and the way that shows 0⃣ consideration to people with slow internet connections.

The migration will also be totally random on a multi-user system based on a race of who sits down and uses brew first.

Maybe a crazy idea, but we could symlink stuff from the legacy cache directory to the new per-user cache directory to address this. (This will raise many other questions I probably don't have answers to.)

@MikeMcQuaid I only thought that robust should be more important than usability here. But point taken.
Also what's your thought on lock file directory, as I mentioned in https://github.com/Homebrew/brew/pull/292#issuecomment-222321153

@UniqMartin Another option might be hardlinks.

I've updated this to move instead of copy, not rerun every time on failure but instead print a warning telling users to manually migrate. I've tested this with various combinations of bad permissions and it behaves as expected as the FileUtils methods do not fails on being unable to touch or rm_rf.

Just want to remind that formula lock directory should be addressed in this or future PR. (TL;DR by moving cache to a per user dir, lock will fail on multiuser machines)

Just want to remind that formula lock directory should be addressed in this or future PR. (TL;DR by moving cache to a per user dir, lock will fail on multiuser machines)

👍 That's already the case with the legacy ~/Library/LaunchAgents so I think it's a future PR thing.

Any objections to 🚢ing the current code and iterating on any issues? Happy to wait for folks here to do more review or testing but just want to be sure I'm waiting on the right people 😀

I still think this is a bad idea, but I don't intend to stand in front of the :train:

@ilovezfs The migration or the move?

I think switching to ~/Library/Caches/Homebrew is the best thing since sliced bread. The migration, not so much.

Pushing with the migration. If there's issues it should be easy to disable (particularly as brew update means the master version of update-report is always run now).

Fun:
iMac-TMP:homebrew-core joe$ brew update
Updated 1 tap (homebrew/core).
==> Cleaning up /Library/Caches/Homebrew...
==> Migrating /Library/Caches/Homebrew to /Users/joe/Library/Caches/Homebrew...
==> Deleting /Library/Caches/Homebrew...
==> Updated Formulae
bfg
iMac-TMP:homebrew-core joe$ git reset --hard HEAD^
HEAD is now at b8f2c4a emojify 1.0.0 (new formula) (#1607)
iMac-TMP:homebrew-core joe$ brew update
Updated 1 tap (homebrew/core).
==> Cleaning up /Library/Caches/Homebrew...
==> Migrating /Library/Caches/Homebrew to /Users/joe/Library/Caches/Homebrew...
==> Deleting /Library/Caches/Homebrew...
==> Updated Formulae
bfg

Rinse, lather, repeat.

@ilovezfs Can you confirm why the check is failing in your case?

Where's the fun in that? But sure.

It's creating the .migration_attempted and then deleting it.

@ilovezfs but, presumably, failing to delete the actual cache?

@ilovezfs should be fixed as-of 8108106; let me know.

Right. The FileUtils.rm_rf  leaves behind /Library/Caches/Homebrew and /Library/Caches/Homebrew/Formula/[a bunch of .brewing files] because /Library/Caches/Homebrew/Formula isn't owned by me. That commit should "fix" it.

Yup:
1
.
..
.migration_attempted
Formula
==> Deleting /Library/Caches/Homebrew...
2
.
..
Formula
No changes to formulae.
iMac-TMP:homebrew-core joe$ brew update
Already up-to-date.
iMac-TMP:homebrew-core joe$

Of course that also potentially leaves behind who-knows-how-much-stuff that will now never be removed or attempted to be removed, since the .migration_attempted isn't per user, which it probably should be (like .migration_attempted.501).

@ilovezfs Glad it works.

Of course that also potentially leaves behind who-knows-how-much-stuff that will now never be removed or attempted to be removed

Tweaked messaging for this case in 4a8fcae.

Better notice the warning the first time!


comment about SBT in Example.scala should be more explicit

at ScalaBridge Montreal right now, don't have time to do a PR, so opening a ticket: @ironfish noticed that the Example.scala file says "open the SBT console", but this is ambiguous, when I run sbt I think of that as the "SBT console", but actually I have to run the (itself poorly named) console command to get to the Scala REPL. this was confusing for a student, suggest being more explicit.

👍


Debug the driver script for execute_deeptools_bamcompare.sh

On 2024-1201, created normalization.md (uncommitted) to run parameterized tests of execute_deeptools_bamcompare.sh. Many of these tests failed for reasons that are currently unclear. The script and its behavior need debugging to identify the root causes of these failures.

[ ] Investigate failed tests.

Review the command logs to identify parameter combinations that failed.
Document which parameters failed and why, providing as much detail as possible (e.g., invalid arguments, missing inputs, unexpected outputs).
Report findings here, specifying failure cases and whether they are reproducible.

[ ] Refactor the script.

Based on the identified issues, refactor the code in execute_deeptools_bamcompare.sh.
Where appropriate, write additional error handling and logging to improve debugging for future users/me.
Review parameter handling to ensure compatibility with deepTools and edge cases.
Put together a list of edge cases (e.g., empty inputs, mismatched chromosomes in BAM files, etc.)

[ ] Develop and validate tests.

Extend normalization.md with integration tests covering valid and edge case parameters.
Validate that outputs (e.g., bigWig or bedGraph files) match expected results, considering proper scaling, input-output consistency, and handling of missing or malformed data.
If integration testing reveals issues with upstream workflow scripts, create separate issues.

[ ] Improve the documentation.

Update script documentation to clarify expected inputs, valid parameter ranges, and potential failure points.
Add examples of successful test cases to the repo.

Document which parameters failed and why, providing as much detail as possible (e.g., invalid arguments, missing inputs, unexpected outputs).
Report findings here, specifying failure cases and whether they are reproducible.

Somehow, when execute_deeptools_bamcompare.sh is supplied with parameter
--scl_fct "0.50:0.50,0.50:0.50,0.50:0.50,0.50:0.50,0.50:0.50,0.50:0.50"

the expected assignment to --fil_stm is not preserved, resulting in "Error: --fil_stm is required." errors, e.g.
❯ cat ./scl_fct.50:50__norm.none__scl_pre.ses/tracks/logs/execute_deeptools_compare.3.stderr.txt
Error: --fil_stm is required.

❯ cat ./scl_fct.50:50__norm.none__scl_pre.ses/tracks/logs/execute_deeptools_compare.3.stdout.txt
Error: --fil_stm is required.

Document which parameters failed and why, providing as much detail as possible (e.g., invalid arguments, missing inputs, unexpected outputs).
Report findings here, specifying failure cases and whether they are reproducible.

When execute_deeptools_bamcompare.sh is supplied with parameter
--scl_fct "none"

the script fails with the error "Error: --scl_fct_num was assigned 'none' but must be a positive float.", e.g.
❯ cat ./scl_fct.none__norm.blank__scl_pre.blank/tracks/logs/execute_deeptools_compare.2.stderr.txt
Error: --scl_fct_num was assigned 'none' but must be a positive float.

❯ cat ./scl_fct.none__norm.blank__scl_pre.blank/tracks/logs/execute_deeptools_compare.2.stdout.txt
##############################
## Resolved argument states ##
##############################

- Comparison operation: log2
- Scaling factor source: '--scl_fct <str>'
- Normalization method: User-supplied scaling via '--scl_fct none'

##############################
## Resolved argument states ##
##############################

- Comparison operation: log2
- Scaling factor source: --scl_fct
- Normalization method: User-supplied scaling via --scl_fct 'none'

Error: --scl_fct_num was assigned 'none' but must be a positive float.

When execute_deeptools_bamcompare.sh is supplied with parameters
--scl_fct "none"
--norm <str != "none">

the script fails with the error described above as well as a warning, e.g.
❯ cat ./scl_fct.none__norm.bpm__scl_pre.blank/tracks/logs/execute_deeptools_compare.2.stderr.txt
Warning: Using '--scl_fct <str>' with '--norm <str>' (when '--norm' is not 'none') is not recommended. Options associated with '--norm' are designed to adjust for differences in sequenced read alignment counts (i.e., sequencing depth after alignment and processing), while values supplied to '--scl_fct <str>' typically account for compositional differences between libraries, such as those derived from exogenous spike-in DNA or scaling factors computed by tools like DESeq2 or edgeR. Combining these options can skew y-axis values, leading to misleading or unreliable relative or semiquantitative results.
Error: --scl_fct_num was assigned 'none' but must be a positive float.

❯ cat ./scl_fct.none__norm.bpm__scl_pre.blank/tracks/logs/execute_deeptools_compare.2.stdout.txt
Warning: Using '--scl_fct <str>' with '--norm <str>' (when '--norm' is not 'none') is not recommended. Options associated with '--norm' are designed to adjust for differences in sequenced read alignment counts (i.e., sequencing depth after alignment and processing), while values supplied to '--scl_fct <str>' typically account for compositional differences between libraries, such as those derived from exogenous spike-in DNA or scaling factors computed by tools like DESeq2 or edgeR. Combining these options can skew y-axis values, leading to misleading or unreliable relative or semiquantitative results.
##############################
## Resolved argument states ##
##############################

- Comparison operation: log2
- Scaling factor source: '--scl_fct <str>' and '--norm <str>'
- Normalization method: User-supplied scaling via '--scl_fct none' combined with coverage normalization via '--norm BPM'

##############################
## Resolved argument states ##
##############################

- Comparison operation: log2
- Scaling factor source: --norm
- Normalization method: Coverage normalization via --norm 'BPM'

Error: --scl_fct_num was assigned 'none' but must be a positive float.

When execute_deeptools_bamcompare.sh is supplied with parameters
--scl_fct "none"
--norm "none"
--scl_pre "none"

we again get the error "Error: --scl_fct_num was assigned 'none' but must be a positive float." and the following warning:
❯ cat ./scl_fct.none__norm.none__scl_pre.none/tracks/logs/execute_deeptools_compare.2.stderr.txt
Warning: Argument '--scl_fct none' and argument '--norm none' were both specified. The 'bamCompare' operation ('--oper log2') will proceed without scaling, allowing sequencing depth to affect the result.
Error: --scl_fct_num was assigned 'none' but must be a positive float.

❯ cat ./scl_fct.none__norm.none__scl_pre.none/tracks/logs/execute_deeptools_compare.2.stdout.txt
Warning: Argument '--scl_fct none' and argument '--norm none' were both specified. The 'bamCompare' operation ('--oper log2') will proceed without scaling, allowing sequencing depth to affect the result.
##############################
## Resolved argument states ##
##############################

- Comparison operation: log2
- Scaling factor source: '--scl_fct <str>'
- Normalization method: User-supplied scaling via '--scl_fct none'

##############################
## Resolved argument states ##
##############################

- Comparison operation: log2
- Scaling factor source: --norm
- Normalization method: Coverage normalization via --norm 'None'

Error: --scl_fct_num was assigned 'none' but must be a positive float.

#QUESTION: Why is ## Resolved argument states ## printed twice?

Regarding Issue comment #2, argument --scl_fct is not designed to accept "none" as a value.

Correct Usage:

The argument can either be...

omitted entirely
or assigned a comma-separated string of scaling factor pairs.

Each scaling factor pair must follow the format:
first:second  # numerator:denominator

Examples:

Single pair: --scl_fct "1.0:0.5"
Multiple pairs: --scl_fct "1.0:0.5,0.75:0.25"

Note:
Ensure that the scaling factors provided correspond to the respective files (e.g., numerator and denominator) in the comparison.


fix bug introduced by this commit https://github.com/jstrachan/ipaas-…

…quickstarts/commit/2db7a07ffe959a950c85179a7ffdb74fbce1db8f so we can do a release again

[merge]


An Exception found in the tutorial jupyter notebook.

Bug Description
The ImportError: IntProgress not found was triggered when ran a cell in https://github.com/fastnlp/fastNLP/blob/master/tutorials/fastnlp_1_minute_tutorial.ipynb
Reproduction
1.Use the jupyter to lauch the https://github.com/fastnlp/fastNLP/blob/master/tutorials/fastnlp_1_minute_tutorial.ipynb, then run each cell from top to buttom.
2.When reach the cell[8]:
from fastNLP import Trainer, CrossEntropyLoss, AccuracyMetric
trainer = Trainer(model=model,
                  train_data=train_data,
                  dev_data=dev_data,
                  loss=CrossEntropyLoss(),
                  metrics=AccuracyMetric()
                  )
trainer.train()
print('Train finished!')

It produced:
~/anaconda3/envs/fastnlp/lib/python3.6/site-packages/tqdm/_tqdm_notebook.py in status_printer(_, total, desc, ncols)
    102             if total:
--> 103                 pbar = IntProgress(min=0, max=total)
    104             else:  # No total? Show info style bar with no progress tqdm status

NameError: name 'IntProgress' is not defined

During handling of the above exception, another exception occurred:

ImportError                               Traceback (most recent call last)
<ipython-input-8-4b34d005949c> in <module>
      6                   metrics=AccuracyMetric()
      7                   )
----> 8 trainer.train()
      9 print('Train finished!')

~/anaconda3/envs/fastnlp/lib/python3.6/site-packages/fastNLP/core/trainer.py in train(self)
    163                 self._summary_writer = SummaryWriter(path)
    164             if self.use_tqdm:
--> 165                 self._tqdm_train()
    166             else:
    167                 self._print_train()

~/anaconda3/envs/fastnlp/lib/python3.6/site-packages/fastNLP/core/trainer.py in _tqdm_train(self)
    177         total_steps = data_iterator.num_batches*self.n_epochs
    178         epoch = 1
--> 179         with tqdm(total=total_steps, postfix='loss:{0:<6.5f}', leave=False, dynamic_ncols=True) as pbar:
    180             ava_loss = 0
    181             for epoch in range(1, self.n_epochs+1):

~/anaconda3/envs/fastnlp/lib/python3.6/site-packages/tqdm/_tqdm_notebook.py in __init__(self, *args, **kwargs)
    210         # Replace with IPython progress bar display (with correct total)
    211         self.sp = self.status_printer(
--> 212             self.fp, self.total, self.desc, self.ncols)
    213         self.desc = None  # trick to place description before the bar
    214

~/anaconda3/envs/fastnlp/lib/python3.6/site-packages/tqdm/_tqdm_notebook.py in status_printer(_, total, desc, ncols)
    109             # #187 #451 #558
    110             raise ImportError(
--> 111                 "IntProgress not found. Please update jupyter and ipywidgets."
    112                 " See https://ipywidgets.readthedocs.io/en/stable"
    113                 "/user_install.html")

ImportError: IntProgress not found. Please update jupyter and ipywidgets. See https://ipywidgets.readthedocs.io/en/stable/user_install.html

Speculation
The library ipywidgets is missed, when use "pip install ipywidgets", the bug got fixed. (Since the travis CI is not related to jupyter notebook, the exception would not be deteceted by CI)
Proposal
Add the lib ipywidgets in https://github.com/fastnlp/fastNLP/blob/master/requirements.txt
Environment
Desktop (please complete the following information):

OS: Mac OSX 10.14
python env: pure virtual env with new lib described in https://github.com/fastnlp/fastNLP/blob/master/requirements.txt

A huge thanks to @hazelnutsgz .
This is probably caused by tqdm. It cannot work well with jupyter notebook sometimes. We had noticed this bug before, so we design an parameter called use_tqdm for trainer.  If use_tqdm=False, the progress bar of training epochs would not be shown in jupyter cells.
We will investigate this bug later. Thanks again for your detailed report 👍


Bump FontAwesome version to 5.14.0

@thii I'll need you to approve this since I don't have write permissions to master

Closing because did not include fonts. An error occurred updating them with libswift.dylib. Investigating further as ref #259

Oops. It was because of GitHub branch protection. I just removed the requirement of reviews--you should be able to self-merge your PRs now.


[BUG] ADD HACKTOBERFEST AND GSSOC BANNER ON THE README FILE

Description
To foster community engagement and encourage contributions, we proudly display the Hacktoberfest and GirlScript Summer of Code (GSSoC) banners in our README. Hacktoberfest is an annual event that celebrates open-source contributions, inviting developers of all levels to participate and make their mark in the open-source community. By promoting this event, we aim to inspire contributors to enhance their skills while supporting our project. Similarly, featuring the GSSoC banner highlights our commitment to nurturing young talent and providing a platform for aspiring developers to learn and grow. Together, these banners represent our dedication to inclusivity and collaboration in the tech community, encouraging developers to join us in making a difference through code.
Steps to Reproduce
Clone the Repository: Begin by cloning the repository that contains the project. This can be done using the Git command line interface, which allows users to create a local copy of the project on their machines.
Install Dependencies: Once the repository is cloned, the next step is to navigate into the project directory and install the necessary dependencies. This is often done using a package manager like npm, which retrieves and installs the libraries and tools required for the application to run.
Start the Application: After all dependencies are installed, users should start the application to verify its functionality. This usually involves executing a command that launches the app on a local server.
Navigate to the Buggy Feature: Users should then access the specific feature or page of the application where the bug is believed to exist. This helps in isolating the problem area.
Perform the Trigger Action: To recreate the bug, users need to perform the action that causes the issue. This might involve clicking buttons, entering data, or navigating through different pages.
Document Behavior: It’s essential to note what the expected behavior of the application is versus what actually happens when the action is performed. This documentation can provide insights into what went wrong.
Capture Error Messages: If any error messages or logs are generated during the process, these should be recorded. Error messages are often vital clues for developers in diagnosing issues.
Expected Behavior
The expected behavior is for the Hacktoberfest and GSSoC banners to be prominently displayed at the top of the README file, showing support for these open-source events and encouraging contributions.
Actual Behavior
The current README file does not include the Hacktoberfest and GSSoC banners. Adding these banners would help in promoting the events and attracting more developers to participate and contribute to the project.
Solution:
To add these banners, include the following Markdown code at the beginning of the README file:
Screenshots (if applicable)
N/A

ADD LABELS HACKTOBERFEST AND GSSOC EXT 24
ASSIGN ME THE TASK
TANK YOU @ombhojane !


(maint) Remove lucid from build targets

Ubuntu 10.04 (Lucid Lynx) goes EoL 2015-04-30, and as such, we no longer
want to be building packages for this platform.
https://lists.ubuntu.com/archives/ubuntu-announce/2015-March/000193.html

CLA signed by all contributors.


OpenCE 1.9 CVE list

[ ] CVE-2024-5187 against onnx 1.16, fixed in 1.17.
[ ] CVE-2024-49767 against werkzeug. For upcoming releases that include this package, please update from current 3.0.3 to 3.0.6 or later.

Please backport the fix for CVE-2024-3568 to transformers 4.17.0.
internal reference: https://github.ibm.com/ax/planning/issues/14594

Tensorflow
CVE-2023-33976 .  It looks like it is addressed in Tensorflow 2.12.1
https://github.ibm.com/NGP-TWC/ml-planning/issues/42641

ONNX
CVE-2024-27319
CVE-2024-27318
https://github.ibm.com/NGP-TWC/ml-planning/issues/42636

Please allow for latest black.

Package Updates in 1.9.6, compared to OpenCE 1.9.5

CVE
Package
1.9.6
1.9.5

CVE-2024-49767
werkzeug
3.0.3
3.0.6

GHSA-h4gh-qq45-vh27
cryptography
43.0.0
43.0.3

pytorch-lightning
2.0.1
2.3.3

Backports of CVEs in 1.11.5 (as compared to 1.11.3)

CVE-2024-5187 - backported to onnx 1.16
CVE-2024-3568 - backported to transformers v4.17
CVE-2024-31580 and CVE-2024-31583 - backported to torch v2.1.2


PR comment formatted badly when sarif has two tool entries

Here is my sarif content
{
  "$schema": "https://schemastore.azurewebsites.net/schemas/json/sarif-2.1.0-rtm.5.json",
  "version": "2.1.0",
  "runs": [
    {
      "tool": {
        "driver": {
          "fullName": "Trivy Vulnerability Scanner",
          "informationUri": "https://github.com/aquasecurity/trivy",
          "name": "Trivy",
          "rules": [
            {
              "id": "DS002",
              "name": "Misconfiguration",
              "shortDescription": {
                "text": "Image user should not be 'root'"
              },
              "fullDescription": {
                "text": "Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile."
              },
              "defaultConfiguration": {
                "level": "error"
              },
              "helpUri": "https://avd.aquasec.com/misconfig/ds002",
              "help": {
                "text": "Misconfiguration DS002\nType: Dockerfile Security Check\nSeverity: HIGH\nCheck: Image user should not be 'root'\nMessage: Specify at least 1 USER command in Dockerfile with non-root user as argument\nLink: [DS002](https://avd.aquasec.com/misconfig/ds002)\nRunning containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.",
                "markdown": "**Misconfiguration DS002**\n| Type | Severity | Check | Message | Link |\n| --- | --- | --- | --- | --- |\n|Dockerfile Security Check|HIGH|Image user should not be 'root'|Specify at least 1 USER command in Dockerfile with non-root user as argument|[DS002](https://avd.aquasec.com/misconfig/ds002)|\n\nRunning containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile."
              },
              "properties": {
                "precision": "very-high",
                "security-severity": "8.0",
                "tags": [
                  "misconfiguration",
                  "security",
                  "HIGH"
                ]
              }
            },
            {
              "id": "DS026",
              "name": "Misconfiguration",
              "shortDescription": {
                "text": "No HEALTHCHECK defined"
              },
              "fullDescription": {
                "text": "You should add HEALTHCHECK instruction in your docker container images to perform the health check on running containers."
              },
              "defaultConfiguration": {
                "level": "note"
              },
              "helpUri": "https://avd.aquasec.com/misconfig/ds026",
              "help": {
                "text": "Misconfiguration DS026\nType: Dockerfile Security Check\nSeverity: LOW\nCheck: No HEALTHCHECK defined\nMessage: Add HEALTHCHECK instruction in your Dockerfile\nLink: [DS026](https://avd.aquasec.com/misconfig/ds026)\nYou should add HEALTHCHECK instruction in your docker container images to perform the health check on running containers.",
                "markdown": "**Misconfiguration DS026**\n| Type | Severity | Check | Message | Link |\n| --- | --- | --- | --- | --- |\n|Dockerfile Security Check|LOW|No HEALTHCHECK defined|Add HEALTHCHECK instruction in your Dockerfile|[DS026](https://avd.aquasec.com/misconfig/ds026)|\n\nYou should add HEALTHCHECK instruction in your docker container images to perform the health check on running containers."
              },
              "properties": {
                "precision": "very-high",
                "security-severity": "2.0",
                "tags": [
                  "misconfiguration",
                  "security",
                  "LOW"
                ]
              }
            }
          ],
          "version": "0.38.1"
        }
      },
      "results": [
        {
          "ruleId": "DS002",
          "ruleIndex": 0,
          "level": "error",
          "message": {
            "text": "Artifact: Dockerfile\nType: dockerfile\nVulnerability DS002\nSeverity: HIGH\nMessage: Specify at least 1 USER command in Dockerfile with non-root user as argument\nLink: [DS002](https://avd.aquasec.com/misconfig/ds002)"
          },
          "locations": [
            {
              "physicalLocation": {
                "artifactLocation": {
                  "uri": "Dockerfile",
                  "uriBaseId": "ROOTPATH"
                },
                "region": {
                  "startLine": 1,
                  "startColumn": 1,
                  "endLine": 1,
                  "endColumn": 1
                }
              },
              "message": {
                "text": "Dockerfile"
              }
            }
          ]
        },
        {
          "ruleId": "DS026",
          "ruleIndex": 1,
          "level": "note",
          "message": {
            "text": "Artifact: Dockerfile\nType: dockerfile\nVulnerability DS026\nSeverity: LOW\nMessage: Add HEALTHCHECK instruction in your Dockerfile\nLink: [DS026](https://avd.aquasec.com/misconfig/ds026)"
          },
          "locations": [
            {
              "physicalLocation": {
                "artifactLocation": {
                  "uri": "Dockerfile",
                  "uriBaseId": "ROOTPATH"
                },
                "region": {
                  "startLine": 1,
                  "startColumn": 1,
                  "endLine": 1,
                  "endColumn": 1
                }
              },
              "message": {
                "text": "Dockerfile"
              }
            }
          ]
        }
      ],
      "columnKind": "utf16CodeUnits",
      "originalUriBaseIds": {
        "ROOTPATH": {
          "uri": "file:///"
        }
      },
      "conversion": {
        "tool": {
          "driver": {
            "name": "sarif-tools",
            "fullName": "sarif-tools https://github.com/microsoft/sarif-tools/",
            "version": "1.0.0",
            "properties": {
              "file": "/home/runner/work/lee-test-dte-reusable-workflow-python/lee-test-dte-reusable-workflow-python/reports/trivy-iac-results.sarif",
              "modified": "2023-04-05T16:55:57.719925",
              "processed": "2023-04-05T16:56:29.319849"
            }
          }
        },
        "invocation": "/opt/hostedtoolcache/Python/3.10.10/x64/bin/sarif copy --output /home/runner/work/lee-test-dte-reusable-workflow-python/lee-test-dte-reusable-workflow-python/reports/trivy-combined-results.sarif /home/runner/work/lee-test-dte-reusable-workflow-python/lee-test-dte-reusable-workflow-python/reports/trivy-iac-results.sarif /home/runner/work/lee-test-dte-reusable-workflow-python/lee-test-dte-reusable-workflow-python/reports/trivy-image-results.sarif"
      }
    },
    {
      "tool": {
        "driver": {
          "fullName": "Trivy Vulnerability Scanner",
          "informationUri": "https://github.com/aquasecurity/trivy",
          "name": "Trivy",
          "rules": [
            {
              "id": "CVE-2022-40897",
              "name": "LanguageSpecificPackageVulnerability",
              "shortDescription": {
                "text": "pypa-setuptools: Regular Expression Denial of Service (ReDoS) in package_index.py"
              },
              "fullDescription": {
                "text": "Python Packaging Authority (PyPA) setuptools before 65.5.1 allows remote attackers to cause a denial of service via HTML in a crafted package or custom PackageIndex page. There is a Regular Expression Denial of Service (ReDoS) in package_index.py."
              },
              "defaultConfiguration": {
                "level": "error"
              },
              "helpUri": "https://avd.aquasec.com/nvd/cve-2022-40897",
              "help": {
                "text": "Vulnerability CVE-2022-40897\nSeverity: HIGH\nPackage: setuptools\nFixed Version: 65.5.1\nLink: [CVE-2022-40897](https://avd.aquasec.com/nvd/cve-2022-40897)\nPython Packaging Authority (PyPA) setuptools before 65.5.1 allows remote attackers to cause a denial of service via HTML in a crafted package or custom PackageIndex page. There is a Regular Expression Denial of Service (ReDoS) in package_index.py.",
                "markdown": "**Vulnerability CVE-2022-40897**\n| Severity | Package | Fixed Version | Link |\n| --- | --- | --- | --- |\n|HIGH|setuptools|65.5.1|[CVE-2022-40897](https://avd.aquasec.com/nvd/cve-2022-40897)|\n\nPython Packaging Authority (PyPA) setuptools before 65.5.1 allows remote attackers to cause a denial of service via HTML in a crafted package or custom PackageIndex page. There is a Regular Expression Denial of Service (ReDoS) in package_index.py."
              },
              "properties": {
                "precision": "very-high",
                "security-severity": "7.5",
                "tags": [
                  "vulnerability",
                  "security",
                  "HIGH"
                ]
              }
            }
          ],
          "version": "0.38.1"
        }
      },
      "results": [
        {
          "ruleId": "CVE-2022-40897",
          "ruleIndex": 0,
          "level": "error",
          "message": {
            "text": "Package: setuptools\nInstalled Version: 65.5.0\nVulnerability CVE-2022-40897\nSeverity: HIGH\nFixed Version: 65.5.1\nLink: [CVE-2022-40897](https://avd.aquasec.com/nvd/cve-2022-40897)"
          },
          "locations": [
            {
              "physicalLocation": {
                "artifactLocation": {
                  "uri": "venv/lib/python3.10/site-packages/setuptools-65.5.0.dist-info/METADATA",
                  "uriBaseId": "ROOTPATH"
                },
                "region": {
                  "startLine": 1,
                  "startColumn": 1,
                  "endLine": 1,
                  "endColumn": 1
                }
              },
              "message": {
                "text": "venv/lib/python3.10/site-packages/setuptools-65.5.0.dist-info/METADATA<EMAIL_ADDRESS>              }
            }
          ]
        }
      ],
      "columnKind": "utf16CodeUnits",
      "originalUriBaseIds": {
        "ROOTPATH": {
          "uri": "file:///"
        }
      },
      "conversion": {
        "tool": {
          "driver": {
            "name": "sarif-tools",
            "fullName": "sarif-tools https://github.com/microsoft/sarif-tools/",
            "version": "1.0.0",
            "properties": {
              "file": "/home/runner/work/lee-test-dte-reusable-workflow-python/lee-test-dte-reusable-workflow-python/reports/trivy-image-results.sarif",
              "modified": "2023-04-05T16:56:16.972127",
              "processed": "2023-04-05T16:56:29.319849"
            }
          }
        },
        "invocation": "/opt/hostedtoolcache/Python/3.10.10/x64/bin/sarif copy --output /home/runner/work/lee-test-dte-reusable-workflow-python/lee-test-dte-reusable-workflow-python/reports/trivy-combined-results.sarif /home/runner/work/lee-test-dte-reusable-workflow-python/lee-test-dte-reusable-workflow-python/reports/trivy-iac-results.sarif /home/runner/work/lee-test-dte-reusable-workflow-python/lee-test-dte-reusable-workflow-python/reports/trivy-image-results.sarif"
      }
    }
  ]
}

Docker Image Scan Result (From the sarif above)
Results

[ERROR] [DS002] [HELP LINK] Artifact: Dockerfile Type: dockerfile Vulnerability DS002 Severity: HIGH Message: Specify at least 1 USER command in Dockerfile with non-root user as argument Link: \[DS002\]\(https:\/\/avd.aquasec.com\/misconfig\/ds002\)

https://github.com/AAInternal/lee-test-dte-reusable-workflow-python/blob/python-test-command/Dockerfile#L1-L1

[NOTE] [DS026] [HELP LINK] Artifact: Dockerfile Type: dockerfile Vulnerability DS026 Severity: LOW Message: Add HEALTHCHECK instruction in your Dockerfile Link: \[DS026\]\(https:\/\/avd.aquasec.com\/misconfig\/ds026\)

https://github.com/AAInternal/lee-test-dte-reusable-workflow-python/blob/python-test-command/Dockerfile#L1-L1

Suppressed Results
Nothing here.
Rules information

Rules details
- DS002 [undefined]

> Image user should not be 'root'

,
- DS026 [undefined]

> No HEALTHCHECK defined

Tool information

Name: Trivy
Organization: undefined
Version: undefined

Docker Image Scan Result
Results

[ERROR] [CVE-2022-40897] [HELP LINK] Package: setuptools Installed Version: 65.5.0 Vulnerability CVE-2022-40897 Severity: HIGH Fixed Version: 65.5.1 Link: \[CVE-2022-40897\]\(https:\/\/avd.aquasec.com\/nvd\/cve-2022-40897\)

https://github.com/AAInternal/lee-test-dte-reusable-workflow-python/blob/python-test-command/venv/lib/python3.10/site-packages/setuptools-65.5.0.dist-info/METADATA#L1-L1

Suppressed Results
Nothing here.
Rules information

Rules details
- CVE-2022-40897 [undefined]

> pypa-setuptools: Regular Expression Denial of Service (ReDoS) in package_index.py

Tool information

Name: Trivy
Organization: undefined
Version: undefined