moby-engine: Fix CVE-2024-36620, CVE-2024-36621, CVE-2024-36623 for 3.0

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Add patches for CVE-2024-36621 and  CVE-2024-36620 and CVE-2024-36623
Change Log

CVE-2024-36620
CVE-2024-36621
CVE-2024-36623

Does this affect the toolchain?

NO
Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2024-36620
https://nvd.nist.gov/vuln/detail/CVE-2024-36621
https://nvd.nist.gov/vuln/detail/CVE-2024-36623

Test Methodology

Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=689282&view=results

Auto cherry-pick results:

3.0-dev :white_check_mark: -> https://github.com/microsoft/azurelinux/pull/11375

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=691407&view=results


Getting started: picking the same theme should also be accepted as done criteria

Otherwise I can only see the step completed if a pick a different theme, but maybe I like the one that is active?

@JacksonKearl if I manually uncheck the box, and then re-select the theme, and then repeat the process, the box doesn't re-check. At that point, I'm also unable to manually check it.

Haven't been able to repro the cannot-check bug listed above, this was verified last iteration so will close out and reassign the milestone as no new work has been done.


Please add this functionality

Hi please add these functions and options

add an option to open the destroy window automatically when bags are opened, (for easy access adding items to inclusions)
left click in sell and destroy window should sell or destroy the specific item (I never used the "sell all/destroy all" buttons in the previous version)
Left click on the merchant button should open the options, not start selling. (there is already a sell button in the dejunk sell window and it's muscle memory to press a red blizzard-style button for options. Seriously, don't mess with muscle memory.)

the new design is nice and compact, but i'd like to see the functionality restored to where is was in the past an improved even,
thanks

Hey

I like this, and I think it would make sense to add this functionality as part of the "Auto Junk Frame" option
Already on the todo list, but there's some other things I have to find the time to fix first
Fair enough. I've been wanting to synchronize the functionality between the merchant and minimap buttons for a while, so this might be a good excuse to do it now

Also, I will (slowly) restore some of Dejunk's old functionality, but definitely not everything. There are quite a few features that I left out when I built the new version of the addon, and that's mostly because the old code had become so bloated and confusing that I found it too difficult/time-consuming to maintain. The goal for now is to avoid reaching that point again.

If I may add another flaggable option -- can auto-destroy run when talking to a merchant? That is, after selling everything that can be vendored, everything with no sell price is automatically destroyed.

If I may add another flaggable option -- can auto-destroy run when talking to a merchant? That is, after selling everything that can be vendored, everything with no sell price is automatically destroyed.

Unfortunately not. Blizzard has made it so that items can only be destroyed one at a time in response to a hardware event (e.g. executing a chat command, clicking a button, or pressing a key).


How can we show the images like whatsApp when Android style is Messaging, I am attaching the images for reference.

Thanks. if you want to show a plain notification without messaging style, you need to implement the following:

for the image after expanding, that is the big picture style

for the image before expansion, that is the large icon .

If you need Messaging style, there's some more info over on the docs here.

large icon is not showing with messaging


fix: updated .toml and lock file dependencies

Checklist

[X] Added tests for changed code.
[X] Updated documentation for changed code.
[X] I've added a news fragment of my changes with the name,
"{ISSUE_NUM}.{feature|bugfix|doc|removal|misc}""

Related Issue

Fixes #306, updates certifi and pytz to more recent versions.
Description

Versions of certifi and pytz within pyrh were outdated by a few years. These packages follow date structure versioning instead of semantic versioning. Packages using updated versions (eg: 2022's version instead of 2020's version) signals incompatibility within Poetry's dependency resolver when combined with pyrh, so I updated them within pyrh's pyproject.toml and re-wrote the lock file.

seems like a ci error--I'll fix it when I have some time, otherwise feel free to take a stab at it

seems like a ci error--I'll fix it when I have some time, otherwise feel free to take a stab at it

Pre-commit Action was failing to build isort environment. Throwing the error below, so I updated isort to 5.12 in pyproject.toml and the pre-commit-config and it worked locally.
[INFO] Installing environment for https://github.com/pycqa/isort.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
An unexpected error has occurred: CalledProcessError: command: ('/home/runner/.cache/pre-commit/repog4yvbyy7/py_env-python3/bin/python', '-mpip', 'install', '.', 'toml')
return code: 1
...
RuntimeError: The Poetry configuration is invalid:
            - [extras.pipfile_deprecated_finder.2] 'pip-shims<=0.3.4' does not match '^[a-zA-Z-_.0-9]+$'```

Merged, thanks for the contribution--until I cut a release, feel free to install from mainline

@adithyabsk I'm happy to cut the release and save you the time, but not sure I have credentials for that

@jhirschibar no worries, I cut a new release, we had a couple of other minor tweaks that needed to get in either way: https://github.com/robinhood-unofficial/pyrh/releases/tag/v2.1.2


Resolve a bug in the diffing algorithm.

(the diff method wasn't removing attributes)

bors merge


feat: updated enterprise db crn

Description
Updated CRN
Types of changes in this PR
Changes that affect the core Terraform module or submodules

[ ] Bug fix
[ ] New feature
[ ] Dependency update

Changes that don't affect the core Terraform module or submodules

[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[x] CI-related update (pipeline, etc.)
[ ] Other

Release required?
Identify the type of release. For information about the changes in a semantic versioning release, see Release versioning.

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
If a release is required, replace this text with information that users need to know about the release. Write the release notes to help users understand the changes, and include information about how to update from the previous version.
Your notes help the merger write the commit message for the PR that is published in the release notes for the module.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
Merge by using "Squash and merge".

@imprateeksh All permanent instance need to be provisioned using https://github.ibm.com/GoldenEye/ge-dev-account-management
Please delete this instance and recreate using terraform

Sure @ocofaigh. I have deleted this instance. Will recreate as suggested.


[BugFix] fix close shared conjuncts in ES DataSource

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：
Fixes #10368
Problem Summary(Required) ：
conjuncts in DataSource are shared by Multi DataSource.
If one of our operators has more than one scan range,
it will lead to an use-after-free error
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_admit_test

run starrocks_be_unittest

run starrocks_clang-format

need the test cases

https://github.com/Mergifyio backport branch-2.3

https://github.com/Mergifyio backport branch-2.4