Incorrect / persistent new data version flag

[BeigeOne]

Dagster version

1.6.4

What's the issue?

I made some changes to my project which involved changing an asset (call it X) to an observable source asset and removing some other assets. The issue I have is that the asset downstream of X is now persistently reporting in the UI that "Changes since last materialization: X has a new data version"

What did you expect to happen?

I expected the process to be:
observe asset X -> materialize ds_asset -> expected the 'X has a new data version' flag on ds_asset to disappear
and for this to be true independent of former incarnations of X

How to reproduce?

# first set up using X as asset
@asset()
def X():
    pass

@asset(deps=["X"])
def ds_asset():
    pass

UI: deployment-reload
UI: materialize X
UI: materialize ds_asset
UI: materialize X
->ds_asset now flagged with 'Changes since last materialization: X has a new materialization'
UI: materialize ds_asset
->ds_asset flag disappears

# first set up using X as asset
#@asset()
#def X():
#    pass

# subsequently change X to observable_source_asset
@observable_source_asset() 
def X():
     return DataVersion('dummy-version-id')

@asset(deps=["X"])
def ds_asset():
    pass

UI: deployment-reload
UI: observe X
->ds_asset now flagged with 'Changes since last materialization: X has a new materialization'
UI: materialize ds_asset
->ds_asset flag remains

Deployment type

Local

Deployment details

windows-local

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

[BeigeOne]

Is there a workaround? Some way I can easily clear the history of X?

[BeigeOne]

I have been using a workaround:

• use UI asset catalog to 'wipe materializations'
• remove X from code
• redeploy code
• materialise first downstream asset
• reinstate code
• observe X
• materialise first downstream asset