Philippe Laflamme
07/19/2023, 3:38 AMPhilippe Laflamme
07/19/2023, 3:40 AMPhilippe Laflamme
07/19/2023, 3:41 AMowen
07/19/2023, 5:25 PMPhilippe Laflamme
07/19/2023, 5:26 PMPhilippe Laflamme
07/19/2023, 5:28 PMPhilippe Laflamme
07/19/2023, 5:28 PMowen
07/19/2023, 5:29 PMPhilippe Laflamme
07/19/2023, 5:30 PMdagster instance migrate
Rolling back to 1.3.13 will "just work" ?owen
07/19/2023, 5:37 PMPhilippe Laflamme
07/19/2023, 5:39 PMowen
07/19/2023, 5:40 PMPhilippe Laflamme
07/19/2023, 5:40 PMPhilippe Laflamme
07/19/2023, 5:41 PMPhilippe Laflamme
07/19/2023, 5:41 PMowen
07/19/2023, 5:42 PMmax_materializations_per_minute
set to the default value (1) then then only the most recent partition of the downstream time partitioned asset will be materializedPhilippe Laflamme
07/19/2023, 5:42 PMowen
07/19/2023, 5:43 PMPhilippe Laflamme
07/19/2023, 5:43 PMPhilippe Laflamme
07/19/2023, 5:48 PM2023-07-19 13:47:40 -0400 - dagster.daemon.AssetDaemon - ERROR - Caught error:
dagster._check.CheckError: Invariant failed. Description: Invalid serialized cursor
Stack Trace:
File "/.venv/lib/python3.11/site-packages/dagster/_daemon/daemon.py", line 225, in core_loop
yield from self.run_iteration(workspace_process_context)
File "/.venv/lib/python3.11/site-packages/dagster/_daemon/asset_daemon.py", line 95, in run_iteration
AssetReconciliationCursor.from_serialized(raw_cursor, asset_graph)
File "/.venv/lib/python3.11/site-packages/dagster/_core/definitions/asset_reconciliation_sensor.py", line 362, in from_serialized
check.invariant(len(data) in [3, 4], "Invalid serialized cursor")
File "/.venv/lib/python3.11/site-packages/dagster/_check/__init__.py", line 1654, in invariant
raise CheckError(f"Invariant failed. Description: {desc}")
Philippe Laflamme
07/19/2023, 5:48 PM1.3.13
owen
07/19/2023, 5:50 PMPhilippe Laflamme
07/20/2023, 11:29 PMowen
07/20/2023, 11:55 PMPhilippe Laflamme
07/20/2023, 11:55 PMPhilippe Laflamme
07/20/2023, 11:58 PM.0
releases. I'm going to revert to 1.3.13 instead, can I simply set the cursor to the "empty" cursor? Will that risk kicking off any new materializations or will it instead "reset" the cursor to the latest after the first run?owen
07/21/2023, 12:03 AMinstance.daemon_cursor_storage.set_cursor_values(
{"ASSET_DAEMON_CURSOR": None}
)
if all of your assets are completely up-to-date, then it won't kick off any new materializations, but it could materialize at most one partition per partitioned asset if the most recent partition is out of datePhilippe Laflamme
07/21/2023, 12:04 AMPhilippe Laflamme
07/21/2023, 2:22 AMfrom dagster._daemon.asset_daemon import CURSOR_KEY,AssetReconciliationCursor
instance.daemon_cursor_storage.set_cursor_values({CURSOR_KEY: AssetReconciliationCursor.empty().serialize()})
thanks again for the pointers