Skip to content
This repository has been archived by the owner on Mar 24, 2022. It is now read-only.

Make lucetc and lucet-validate errors more verbose #408

Merged
merged 1 commit into from
Jan 31, 2020

Conversation

acfoltzer
Copy link
Contributor

@acfoltzer acfoltzer commented Jan 31, 2020

The full fix for these issues is tracked in #409, but this can merge first because it is already useful.

Copy link
Contributor

@iximeow iximeow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing these!

ClifWasmError(#[from] ClifWasmError),
#[error("Lucet Module error")]
#[error("Lucet Module: {0}")]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is definitely a "when we actually spec this out with tests" thought, but "Error: Lucet Module error: Unknown module for ..." ends up repeating that there's an error a bit more than we probably should 😅

@acfoltzer acfoltzer changed the title Make lucetc and lucet-validate errors more verbose [WIP] Make lucetc and lucet-validate errors more verbose Jan 31, 2020
@acfoltzer acfoltzer changed the title [WIP] Make lucetc and lucet-validate errors more verbose [WIP] Make errors more verbose, and test their output Jan 31, 2020
@acfoltzer acfoltzer changed the title [WIP] Make errors more verbose, and test their output Make lucetc and lucet-validate errors more verbose Jan 31, 2020
@acfoltzer acfoltzer merged commit 25bf287 into master Jan 31, 2020
@acfoltzer acfoltzer deleted the acf/verbose-lucetc-errors branch January 31, 2020 22:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants