Update minidump-processor requirement from 0.21 to 0.22

[dependabot[bot]]

Updates the requirements on minidump-processor to permit the latest version.

Release notes

Sourced from minidump-processor's releases.

Version 0.22.0 (2024-07-03)

Release Notes

Nothing Yet!

• Added a count of mapped memory regions to the output for Linux minidumps
• Added native thread IDs to the output both in JSON and human-readable form
• Fixed parsing .sym files with several adjacent empty lines
• Updated a number of crucial dependencies (framehop, wholesym) and removed duplications where possible

Install minidump-stackwalk 0.22.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/rust-minidump/rust-minidump/releases/download/v0.22.0/minidump-stackwalk-installer.sh | sh

Download minidump-stackwalk 0.22.0

File	Platform	Checksum
minidump-stackwalk-aarch64-apple-darwin.tar.xz	Apple Silicon macOS	checksum
minidump-stackwalk-x86_64-apple-darwin.tar.xz	Intel macOS	checksum
minidump-stackwalk-x86_64-pc-windows-msvc.zip	x64 Windows	checksum
minidump-stackwalk-x86_64-unknown-linux-gnu.tar.xz	x64 Linux	checksum
minidump-stackwalk-x86_64-unknown-linux-musl.tar.xz	x64 MUSL Linux	checksum

Changelog

Sourced from minidump-processor's changelog.

Version 0.22.0 (2024-07-03)

Nothing Yet!

• Added a count of mapped memory regions to the output for Linux minidumps
• Added native thread IDs to the output both in JSON and human-readable form
• Fixed parsing .sym files with several adjacent empty lines
• Updated a number of crucial dependencies (framehop, wholesym) and removed duplications where possible

Version 0.21.2 (2024-06-03)

• Updated the wholesym and framehop crates and reduced their dependencies

Version 0.21.1 (2024-03-01)

• Fixed a small regression in the stack walker when dealing with malformed minidumps

Version 0.21.0 (2024-02-28)

• Native debug information is now read via framehop and wholesym instead of symbolic, this provides significant speedups, reduced memory usage and more flexibility (the stack walker can be built with unwinding support while omitting symbolication for example)
• Added support for the MINIDUMP_THREAD_INFO_LIST stream
• Version numbers are now printed out for ELF files if available
• Symbol files can be passed directly instead of relying on the Breakpad directory structure, assuming they have the correct debug ID and file name
• Removed the dependency on the chrono crate
• Various cleanups and speed-ups to the stack walker

Version 0.20.0 (2024-01-31)

• Fixed several issues when printing error codes on Windows, Linux and macOS
• Fixed the debug id of modules looked up via code info, these now report the correct debug id for the module
• The dump_syms option was removed, support for stack-walking and symbolication using native debug information is mature enough that we don't need it anymore
• The minidump crate doesn't force its dependents to use the same version of memmap2 that it's using
• Updated several dependencies to remove old crates and duplications

Version 0.19.1 (2023-11-02)

• Fixed an issue that prevent the GitHub integration from automatically generating a new release.
• Updated all dependencies to address some mild security issues in some of the dependent crates.

... (truncated)

Commits

• ec48da2 chore: Release
• 67d92f1 Updated cargo-dist configuration using version 0.17.0
• a013416 Updated the release notes for the next version
• d1e2010 Update to wholesym 0.7.
• b047771 Get memory_map_count directly from stream and rename to be Linux specific
• cdd45b5 Rewrite for clippy and revert human snap changes
• db21a92 Limit memory_map_count to Linux only
• 8a75e07 Address feedback from cmartin
• ff6ee49 Add reporting of memory map count
• a4304d0 Update for json-pretty-unloaded.snap file
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changelog-app[bot]]

Generate changelog in changelog-dir>`changelog/@unreleased`</changelog-dir

What do the change types mean?

- `feature`: A new feature of the service. - `improvement`: An incremental improvement in the functionality or operation of the service. - `fix`: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way. - `break`: Has the potential to break consumers of this service's API, inclusive of both Palantir services and external consumers of the service's API (e.g. customer-written software or integrations). - `deprecation`: Advertises the intention to remove service functionality without any change to the operation of the service itself. - `manualTask`: Requires the possibility of manual intervention (running a script, eyeballing configuration, performing database surgery, ...) at the time of upgrade for it to succeed. - `migration`: A fully automatic upgrade migration task with no engineer input required. _Note: only one type should be chosen._

How are new versions calculated?

- ❗The `break` and `manual task` changelog types will result in a major release! - 🐛 The `fix` changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease. - ✨ All others will result in a minor version release.

Type

- [ ] Feature - [ ] Improvement - [ ] Fix - [ ] Break - [ ] Deprecation - [ ] Manual task - [ ] Migration

Description

Update minidump-processor requirement from 0.21 to 0.22 **Check the box to generate changelog(s)** - [ ] Generate changelog entry

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.