Skip to content
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

Remove multierror to fix error in error handling #832

Closed
wants to merge 1 commit into from

Conversation

serprex
Copy link
Contributor

@serprex serprex commented Dec 16, 2023

multierror struct has a formatting closure, making it unserializable
Thus, multierror cannot be stored in temporal state

Replace with jsonerr, with fallback logic for non serializable errors

@serprex serprex requested a review from iskakaushik December 16, 2023 15:07
@serprex serprex force-pushed the no-errors-in-json branch 2 times, most recently from 19b18e5 to b41d6fe Compare December 16, 2023 15:19
multierror struct has a formatting closure, making it unserializable
Thus, multierror cannot be stored in temporal state

Replace with jsonerr, with fallback logic for non serializable errors
@serprex
Copy link
Contributor Author

serprex commented Dec 16, 2023

This is probably overkill, simpler would be to store errors as []string

Rendered: #833

@serprex
Copy link
Contributor Author

serprex commented Dec 16, 2023

Closing in favor of #833

@serprex serprex closed this Dec 16, 2023
@serprex serprex deleted the no-errors-in-json branch December 19, 2023 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants