sidefuzz
sidefuzz copied to clipboard
Update color-backtrace requirement from 0.4.2 to 0.5.1
Updates the requirements on color-backtrace to permit the latest version.
Changelog
Sourced from color-backtrace's changelog.
[v0.5.1] (2021-04-25)
- Add the ability to print module_name:offset, or address of frame
- Contributed by [
@s1341], thanks![v0.5.0] (2020-11-21)
- Add
__rust_begin_short_backtracefilter- Remove experimental failure support
[v0.4.2] (2020-05-19)
Added
CloneandDebugimpls forBacktracePrinterCOLORBT_SHOW_HIDDENenv variable, disabling frame filtering[v0.4.1] (2020-05-08)
Fixed
- Use correct verbosity level for string formatting
- Fix off-by-one in frame hiding code
- Hides one additional post-panic frame
- Slightly improved doc
[v0.4.0] (2020-05-06)
Added
BacktracePrinter::format_trace_to_string- Ability to add custom frame filter callbacks
BacktracePrinter::add_frame_filterBacktracePrinter::clear_frame_filtersdefault_frame_filter- Thanks to [
@yaahc] for helping out with this!- Prefer
RUST_LIB_BACKTRACEenv var when determining the default verbosity to print non-panic backtraces
- Also contributed by [
@yaahc]Changed
- Rename
Settings→BacktracePrinter- Move
print_backtrace→BacktracePrinter::print_trace- Move
print_panic_info→BacktracePrinter::print_panic_info- Move
color_backtrace::failure::print_backtrace→BacktracePrinter::print_failure_trace- The majority of old APIs have deprecated shims that forward calls to their new place to ease porting
- The
outsetting is no longer part of theBacktracePrinterand instead supplied as an argument to all functions that need it
- The previous design forced
Sync + Send + 'staticconstraints on any output stream since they are required when registering
... (truncated)
Commits
f8dbec3Update CHANGELOG, bump versiond25c611Add the ability to print module_name:offset, or address of frame (#44)dc53c08Bump version to v0.5a7240e7Remove experimental failure supportc68832aAdd badge for Apache license390e22bAdd__rust_begin_short_backtracefilter- See full diff 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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language -
@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)