seahorse build
displays an error despite successful compilation
#9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When you create a new Seahorse project and build it for the first time, it will show that compilation has failed (
This is most likely a bug in the Seahorse compiler! [...]
)If you run it again, the error message is no longer displayed and it says the project was successfully compiled.
Since
target/deploy/program.so
exists, it was actually successfully compiled.Cause
In
src/bin/cli/build.rs
, there is a check to determine whether to show the message:The assumption was probably that Anchor only sends warnings and errors to stderr. Unfortunately, this is not the case. Everything is sent to stderr, including
Compiling
statements.This means that outputs like
Compiling thiserror v1.0.51
are matched, which causes the error message to be displayed.Solution
Create a filtered version of
stderr
where allCompiling
statements are removed and perform the check on that.Alternative
The cleanest solution would be to use
if !anchor_output.status.success()
as the only check -- but I'm not sure how reliable the exit code ofanchor build
is.