Skip to content

Integrate color-eyre for better error and stacktrace reporting - #3

Merged
mzruya merged 2 commits into
mainfrom
mz.anyhow_errors
Apr 1, 2023
Merged

Integrate color-eyre for better error and stacktrace reporting#3
mzruya merged 2 commits into
mainfrom
mz.anyhow_errors

Conversation

@mzruya

@mzruya mzruya commented Apr 1, 2023

Copy link
Copy Markdown
Contributor

Simpler alternative to #2. color-eyre is an older Rust error reporting library that's meant to reduce boilerplate. It's not as fancy as error-stack, but gives an easy ability to attach context with minimal boilerplate.

For example:
image

Or:
image

@mzruya mzruya changed the title [Experiment] Integrate anyhow for better error and stacktrace reporting [Experiment] Integrate color-eyre for better error and stacktrace reporting Apr 1, 2023
@mzruya mzruya changed the title [Experiment] Integrate color-eyre for better error and stacktrace reporting Integrate color-eyre for better error and stacktrace reporting Apr 1, 2023
@mzruya
mzruya merged commit 76b7343 into main Apr 1, 2023
@mzruya
mzruya deleted the mz.anyhow_errors branch April 10, 2024 19:10
dduugg added a commit that referenced this pull request Aug 17, 2026
Resolves the eight open `actions/missing-workflow-permissions` CodeQL
alerts (#1, #3, #4, #5, #6, #7, #8, #9). Every job now has an effective
`permissions:` block scoped to what it actually does.

ci.yml
  Workflow-level `contents: read` covers `check`, `test` and `lints`,
  which only check out the repo and run cargo check/test/fmt/clippy.

  Four jobs override to `contents: write` because they mutate releases:
  - `release` runs `gh release create --generate-notes`
  - `upload-mac-universal-bin` and `upload-linux-bin` run
    `gh release upload` to attach the built tarballs
  - `generate-dotslash-files` uses facebook/dotslash-publish-release,
    which also publishes via `gh release upload`

audit.yml
  `rustsec/audit-check` needs `checks: write` to publish the advisory
  status check on push/pull_request runs and `issues: write` to open an
  issue per new advisory on the weekly scheduled run (both documented in
  the action's README). `contents: read` covers actions/checkout. It
  does not upload SARIF, so no `security-events: write`.

codeql.yml already declares permissions and is untouched.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant