Skip to content

fix: a bug was introduced that was not capture in the tests, having this inside a future does not run unfortunatelly. #209

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

Merged
merged 1 commit into from
Apr 22, 2025

Conversation

goncalo-frade-iohk
Copy link
Contributor

@goncalo-frade-iohk goncalo-frade-iohk commented Apr 16, 2025

Description:

Changed to a batchUpdate to see if it handles better and does not crash

Checklist:

  • My PR follows the contribution guidelines of this project
  • My PR is free of third-party dependencies that don't comply with the Allowlist
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • I have checked the PR title to follow the conventional commit specification

@goncalo-frade-iohk goncalo-frade-iohk requested a review from a team as a code owner April 16, 2025 11:45
@goncalo-frade-iohk goncalo-frade-iohk force-pushed the fix/bug-with-saving branch 2 times, most recently from bbc457f to b308ba9 Compare April 22, 2025 14:19
…his inside a future does not run unfortunatelly.

Changed to a batchUpdate to see if it handles better and does not crash

Signed-off-by: goncalo-frade-iohk <[email protected]>
@goncalo-frade-iohk goncalo-frade-iohk merged commit 194377a into main Apr 22, 2025
4 checks passed
@goncalo-frade-iohk goncalo-frade-iohk deleted the fix/bug-with-saving branch April 22, 2025 14:35
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