Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Return an EvalResult alongside the redeemer #1101

Merged
merged 7 commits into from
Feb 18, 2025
Merged

Return an EvalResult alongside the redeemer #1101

merged 7 commits into from
Feb 18, 2025

Conversation

Quantumplation
Copy link
Contributor

This refactors things so that eval_phase_two can expose logs even when the script succeeds.

It also enriches traces to be either Logs or Labels, so that we can tell the difference between the two when inspecting the traces.

I was kind of changing things mechanistically, so let me know if you'd prefer anything changed!

I'm also not familiar with the changelog convention, so if someone could help me write a good changelog entry that would be helpful!

This refactors things so that eval_phase_two can expose logs even when the script succeeds.

It also enriches traces to be either Logs or Labels, so that we can tell the difference between the two when inspecting the traces.
@Quantumplation Quantumplation requested a review from a team as a code owner February 17, 2025 20:39
The clones are cheap enough here that we likely don't need to worry about the cost of cloning; and this removes a significant foot-gun where you can wipe out the logs/labels by accessing the other field.
@rvcas rvcas merged commit cc729a7 into main Feb 18, 2025
13 checks passed
@rvcas rvcas deleted the pi/eval-result branch February 18, 2025 00:58
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
Status: ✅ In Next Release
Development

Successfully merging this pull request may close these issues.

2 participants