Anyone else get this when upgrading to 1.3? Any ideas?

dagster._core.errors.DagsterInvalidDefinitionError: Conflicting versions of resource with key 'airbyte' were provided to different assets. When constructing a job, all resource definitions provided to assets must match by reference equality for a given key.

Hi Guy, could you try updating to 1.3.1? This looks like a bug we identified in the initial 1.3 release

Looks like the same issue on 1.3.1. For reference: Assets are defined:

foo_assets = load_assets_from_airbyte_instance(
    airbyte,
    connection_to_group_fn=lambda group_name: "foo",
    key_prefix="foo",
    connection_filter=lambda meta: "foo" in meta.name,
)

where

airbyte=airbyte_resource.configured(AIRBYTE_CONFIG)

Jobs:

foo_replication = define_asset_job(
    "foo_replication",
    selection=AssetSelection.groups("foo"),
)

Schedules:

foo_schedule = ScheduleDefinition(
    job=foo_replication,
    cron_schedule="*/15 * * * *",
    default_status=DefaultScheduleStatus.RUNNING,
)

We are using the definitions approach instead of a

@repository

. LMK if you need to know any more

I'm experiencing the same issue here. Also willing to provide assistance if necessary

Sorry to hear this is still an issue in 1.3.1 - let me try to replicate, I think this is a slightly more complex case of what we patched so it may not have been fixed

@Guy McCombe A change I made that was just released in 1.3.4 fixes this issue if you use the

AirbyteResource

constructor instead of

airbyte_resource.configured()

Thanks, @Joel Olazagasti - I’ll give it a try