Claire Lin

@rexledesma saw that you added the [original diff](https://github.com/dagster-io/dagster/commit/2cedce8e7c61a588d49e397e9eb707e2df2fff82) that pinned `google-api-python-client`, mind taking a look at this?

We should document that metadata can be attached to asset materializations via: ``` yield Output(5, metadata={"my_metadata": 5}) ``` in [this section](https://docs.dagster.io/concepts/assets/asset-materializations#attaching-metadata-to-an-assetmaterialization)

Thanks @TimoFriedri for raising this feature request. We'll get back to you soon about this

Ideally nbconvert updates to a newer version of mistune, but until then making nbconvert an extra requirement sounds reasonable to me. Thoughts @alangenfeld ?

I will take on this issue

We should mention in this error message that `with_resources` call outside of a repository may be the source of this error.

IO manager page includes code samples with this error: https://docs.dagster.io/concepts/io-management/io-managers#applying-io-managers-to-assets

Side note: these code examples are all of the `OR` case (e.g. if ANY upstream partition is replaced). We don't handle the `AND` case as well--for example, materializing a partition...

@sryza @erinkcochran87 I added updates to this page per your feedback, including: - Featuring the multi-asset monitoring example at the forefront (materializing a daily asset when upstream partitions from 2...

@sryza The code example of kicking off a downstream partition when either of the corresponding upstream partitions are materialized has been updated, following the implementation added in https://github.com/dagster-io/dagster/pull/9856