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

fix: Using IO.delay to defer evaluating the logging call #1089

Merged
merged 1 commit into from
Sep 15, 2022

Conversation

eikek
Copy link
Member

@eikek eikek commented Sep 15, 2022

When using pure the effect is evaluated exactly once when creating the IO, but not when evaluating it.

When using `pure` the effect is evaluated exactly once when creating
the IO, but not when evaluating it.
@eikek eikek requested a review from a team as a code owner September 15, 2022 13:07
Copy link
Contributor

@jachro jachro left a comment

Choose a reason for hiding this comment

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

Thanks Eike for spotting this!

@eikek eikek merged commit 5796151 into development Sep 15, 2022
@eikek eikek deleted the fix-iologger branch September 15, 2022 15:54
@jachro jachro mentioned this pull request Sep 22, 2022
jachro added a commit that referenced this pull request Sep 22, 2022
* fix: adding --skip-template-update to renku migrate

* feat: Adding `visibility` to dataset detail response (#1092)

* refactor: Better GitLab stub (#1088)

* fix: Using IO.delay to defer evaluating the logging call (#1089)

* refactor: add generic JSON encoder for all TinyTypes (#1087)

* chore: KG processes documentation
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