The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

I'm seeing dbt asset materializations selecting the wrong nodes and failing because of that

```Running with dbt=1.5.2
Registered adapter: bigquery=1.5.3
Found 133 models, 2 tests, 1 snapshot, 0 analyses, 524 macros, 0 operations, 0 seed files, 410 sources, 0 exposures, 0 metrics, 0 groups
The selection criterion 'fqn:kipptaf.powerschool.kippnewark_powerschool.stg_powerschool__s_nj_stu_x' does not match any nodes
The selection criterion 'fqn:kipptaf.powerschool.kippnewark_powerschool.stg_powerschool__s_nj_ren_x' does not match any nodes
The selection criterion 'fqn:kipptaf.powerschool.kippnewark_powerschool.stg_powerschool__s_nj_crs_x' does not match any nodes

Nothing to do. Try checking your model configs and model specification args```

the correct fqn should be `kipptaf.powerschool.staging.stg_powerschool__s_nj_stu_x` for example

I have a source with a similar name to what it's selecting, but the fqn is `source.kipptaf.kippnewark_powerschool.stg_powerschool__s_nj_stu_x`

in `get_subset_selection_for_context` , `get_node_info_by_output_name` returns the source node instead of the model

that a bug or can I do something about it?

hmm looks like another instance of <https://dagster.slack.com/archives/C04CW71AGBW/p1689016255104989>

Do your sources have the same name as your models?

the basic name, yes. this model is a union of 3 similarly named sources

guessing an immediate workaround would be differentiating the model name right?

Yeah — timothee has a workaround in his thread

Hello Charlie, I created an <https://github.com/dagster-io/dagster/issues/15207|issue on github>. At least we have a quick fix until they release a bug fix.

Hey all, this should be resolved with <https://github.com/dagster-io/dagster/pull/15226> — thanks for the fix!