Asset daemon breaks when downgrading to 1.7.7 about dagster HOT 2 CLOSED

Hi @somiandras -- apologies for the disruption caused here, and I appreciate you bringing this feedback.

When conceived, this set of changes was intended to be possible to safely roll back, and it was definitely an oversight that this was not the case, which we'll be more diligent about in this area moving forward.

In cases where you're working primarily with unpartitioned assets, it's possible to resolve this situation by manually updating the stored cursor value (the risk with partitioned assets is mostly that it may take a very long time to rebuild information calculated over a large number of ticks). If that's the case, and you're interested, I can help assist with reseting your cursor to a healthy state in the event that you need to roll back.

from dagster.

Hi @OwenKephart, thanks for the context. Luckily I found the solution for my other issue that popped up on 1.7.10 so as things stand now I can live with 1.7.10 and no need to downgrade anymore.

from dagster.