-
Notifications
You must be signed in to change notification settings - Fork 5
fix: accept namespaced TII param refs #51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
LorenzoRD2003
wants to merge
1
commit into
txpipe:main
Choose a base branch
from
LorenzoRD2003:fix/namespaced-tii-refs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+151
−7
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
Does anyhow Error Display (to_string) include source/context chain or only the top-level message, and what does the alternate {:#} format print?💡 Result:
When using the anyhow crate, the standard Display format (typically triggered by the {} format specifier or to_string) displays only the outermost error message or context [1][2][3]. It does not include the lower-level source or cause chain, behaving identically to the Display implementation of the underlying error type from which the anyhow::Error was constructed [1][3][4]. The alternate format specifier {:#} is used to print the error along with its full cause chain [5][3][4]. This format utilizes anyhow's built-in formatting logic to display the entire chain of underlying errors [6][5]. If you need to access or manually render the source chain without using the {:#} format, you can use the Error::chain method, which provides an iterator over the full sequence of source errors [3][4][7].
Citations:
Fix the error assertion to check anyhow’s full cause chain
anyhow’s
to_string()/ default{error}formatting prints only the outermost context message (e.g.,"parsing tii file"), not the inner"invalid param type"from the source error chain. Use alternate formatting ({error:#}) or iterateerror.chain().🐛 Proposed fix
📝 Committable suggestion
🤖 Prompt for AI Agents