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

Catch thrown errors in parEvalMap, parEvalMapUnordered #2826

Merged
merged 3 commits into from
Feb 19, 2022

Conversation

armanbilge
Copy link
Member

Fixes #2825.

.compile
.drain
.attempt
.void
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe some .timeout(2.seconds)?

Copy link
Contributor

@nikiforo nikiforo Feb 17, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

like in the test to the top

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe. Munit already puts a 30 second timeout on each test, and I just followed the pattern of the test above which is checking a very similar issue 😆

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, my bad, you are right it puts a timeout. 👍

.compile
.drain
.attempt
.void
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe some .timeout(2.seconds)

@mpilquist mpilquist merged commit 017bb9b into typelevel:main Feb 19, 2022
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.

parEvalMapUnordered and friends can deadlock on exceptions in fs2 3.x, but not in fs2 2.x
3 participants