Skip to content

Converted startup runtime collision into a warning#2202

Merged
vasilmkd merged 3 commits into
typelevel:series/3.xfrom
djspiewak:bug/ioapp-init
Aug 6, 2021
Merged

Converted startup runtime collision into a warning#2202
vasilmkd merged 3 commits into
typelevel:series/3.xfrom
djspiewak:bug/ioapp-init

Conversation

@djspiewak

Copy link
Copy Markdown
Member

Fixes #1918

When the global runtime is already initialized by the time main runs, we now treat this as a warning (which prints to stderr) rather than a fatal error (which is what we did previously). The warning is still important because the user really needs to know that we're ignoring their custom configurations.

We can probably do better than the text on this warning and give the user some actionable steps to track down why the warning is appearing.

@vasilmkd vasilmkd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Bummer, it looks like you forgot the mima filters.

Comment thread core/js/src/main/scala/cats/effect/IOApp.scala
@vasilmkd vasilmkd merged commit b079480 into typelevel:series/3.x Aug 6, 2021
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.

Initialization error when using unsafe.implicits.global within IOApp

2 participants