OwenKephart

This is a cool idea. I think the code you've written should actually work here, even if it's a bit of a pain to have to have to return a...

Hi @jmccartin! Thanks for digging into this -- I think your suggested fix would work, and this would definitely be valuable, as it can be quite tricky to debug these...

Stems from: https://sourcegraph.com/github.com/dagster-io/dagster/-/blob/js_modules/dagit/packages/core/src/assets/LaunchAssetChoosePartitionsDialog.tsx?L229 using op names (which get translated to step names).

@sryza isn't that the case w/ non_argument_deps as well? If the user needs that info, they can always supply it via a SourceAsset

Hi @swaroopch ! Thanks for the contribution. This implementation seems totally reasonable to me. It looks like you'll need to update some tests to mock out that API call: ```...

Hi @erinov1 ! Thanks for the report, this is related to the issue here: https://github.com/dagster-io/dagster/issues/9076. I believe this issue can be fixed with a smaller change than the prior issue,...

Hi @danielgafni! I see what you're saying on the Asset Catalog side of things, but do you mind elaborating on what you would like to see in the structured logs?...

@erinkcochran87 it's a bit more general than the vars property -- basically, you can supply whatever config key you want to the dbt_cli_resource (for example "blah", which doesn't exist in...

Hi @PadenZach ! Thanks for the detailed writeup, this definitely seems like a promising direction. We don't currently have plans of implementing this behavior, but if you're interested in taking...

For an example of the current workaround, see: https://github.com/dagster-io/dagster/discussions/9772