palantir / witchcraft-rust-server

A highly opinionated Rust embedded application server for RESTy APIs
Apache License 2.0
4 stars 7 forks source link

Update minidump-processor requirement from 0.19 to 0.20 #165

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 9 months ago

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

Release notes

Sourced from minidump-processor's releases.

Version 0.20.0 (2024-01-31)

Release Notes

  • 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

Install minidump-stackwalk 0.20.0

Install prebuilt binaries via shell script

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

Download minidump-stackwalk 0.20.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.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.

Version 0.19.0 (2023-11-02)

  • The stackwalker can now lookup symbols using a module's code identifier if the debug identifier is missing. This is useful with Windows minidumps lacking debug identifiers (a condition that happens rather frequently when Windows is running out of memory at the time of minidump generation).
  • Added a custom MozLinuxLimits stream that captures the contents of the /proc/<pid>/limits file of the affected process.
  • Add support for the HandleDataStream stream type. This includes all public types that can appear in the stream.
  • Remove support for the ThreadIdNameMapping annotation which is unused since we added support for the thread names stream.

Version 0.18.0 (2023-09-18)

  • Add support for the MozMacosBootargsStream minidump stream which captures information holding macOS kernel boot arguments.
  • Always use the code file for unwinding on Windows when using native debug information. Previously the stack walker could use the PDB file which does not contain unwinding information in 64-bit builds.
  • Populate the process ID field on Linux, this displays the PID of the crashed process.
  • Expose the MINIDUMP_MEMORY_INFO fields in the public API.
  • Disable bit-flip detection on 64-bit ARM minidumps since it's prone to false positives.

Version 0.17.0 (2023-05-17)

  • Stack-walking using native debug information was somewhat buggy, after more thorough testing it should be now on-par with breakpad symbol file-based stack-walking.

... (truncated)

Commits
  • 3581196 chore: Release
  • 852af14 Updated cargo-dist configuration
  • 0b3aff9 Updated the release notes for the next version
  • 8e2dae5 Updated ctor to version 0.2
  • 7da12de Updated all the dependencies, this removes a few duplications and picks up so...
  • e6b5c2a fix: restore the idx field on thread spans
  • dd377d1 Remove the dependency on dump_syms
  • 35651c5 Make MmapMinidump static
  • 8d69037 Avoid requiring a dependency on memmap2 to use Minidump<'_, Mmap>
  • 7f38b36 bug-1873529: fix debug id for modules found by code-info lookup
  • 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] commented 9 months ago

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.19 to 0.20 **Check the box to generate changelog(s)** - [ ] Generate changelog entry
dependabot[bot] commented 8 months ago

Superseded by #171.