Fridolin Glatter

Thanks, and did you try giving `def fixture2(requests, service1, service2)` for example? Just guessing here based on the links above.

Alright then, sorry I can't be of more help right now.

There might be one more thing you can do: show the pytest devs in their [existing issue](https://github.com/pytest-dev/pytest/issues/11532) to integrate pytest-lazy-fixture in core pytest that you're interested in that :)

Hi @SongminYu and thanks for your extensive report! There are a few things that jump out to me here: 1. Your output of `message-ix show-versions` shows that you're using v3.8.0...

> the user has written their own code including classes with similar names to Scenario that somehow wrap the actual message_ix.Scenario class. I see, that makes more sense :)

Thanks for this PR, @ywpratama :) One thing to note right away: please keep the existing file structure intact. We want all tutorials to be available under `tutorial/wherever they belong`,...

Hi :) Just jumping in here to let you know: I'm looking for exactly this information right now. Is the recommended way to handle this situation still as described [here](https://community.codecov.com/t/unable-to-determine-a-parent-commit-to-compare-against-in-base-branch-after-squash-and-merge/2480/15)?...

Thanks for the quick reply! Unfortunately, this workflow doesn't seem to be very straightforward to implement at first glance, so I'll try to piece it together tomorrow. If you have...

Thanks, but I'm not sure how an empty upload is going to help me (just by the name of it). Instead, I'm now thinking that storing the report with GitHub...

Or what about this: 1. Get coverage report on PR 2. Upload to Codecov 3. Upload to Codecov again, but `override_branch` so that the commit seems to belong to `main`,...