lang: Fix declare_program! messing up IDL errors generation#4126
Merged
acheroncrypto merged 3 commits intoDec 14, 2025
Conversation
|
@acheroncrypto is attempting to deploy a commit to the Solana Foundation Team on Vercel. A member of the Team first needs to authorize it. |
Otter-0x4ka5h
pushed a commit
to Otter-0x4ka5h/anchor
that referenced
this pull request
Mar 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
As mentioned in #3757 (comment), the
errorsmodule generated bydeclare_program!makes theerrorsfield of IDLs inconsistent at best and incorrect at worst.Summary of changes
declare_program!messing up IDL errors generation by skipping the generation of theerrorsmodule during IDL generationerrorsfield in their IDL because ofdeclare_program!usageNote: There is no good reason for the
errorsmodule to exist for Solana program builds, as it might result in getting stack-related error logs during build (see #4109), but that problem is outside the scope of this PR (will handle in a subsequent PR).