ripe-gigabyte-88964
04/17/2023, 7:58 PMFilesystem changed during run: retrying
when trying to call workspace.write_digest
from a goal rule. Looking through .pants.d/pants.log
but nothing is popping out at me as the issue. The digest I am trying to write is just an empty directory:
dagster_home_path = dist_dir.relpath / "dagster_home"
dagster_home_digest = await Get(Digest, CreateDigest([Directory(str(dagster_home_path))]))
logger.debug(f"Creating dagster home directory at {dagster_home_path}")
workspace.write_digest(dagster_home_digest)
ripe-gigabyte-88964
04/17/2023, 7:59 PMhappy-kitchen-89482
04/17/2023, 7:59 PMhappy-kitchen-89482
04/17/2023, 8:00 PMdagster_home_path
end up evaluating to?ripe-gigabyte-88964
04/17/2023, 8:00 PMdist/dagster_home
- /Users/nick.dellosa/Projects/data-platform/dist/dagster_home
is the absolute pathhappy-kitchen-89482
04/17/2023, 8:01 PMripe-gigabyte-88964
04/17/2023, 8:02 PMhappy-kitchen-89482
04/17/2023, 8:02 PMhappy-kitchen-89482
04/17/2023, 8:02 PMripe-gigabyte-88964
04/17/2023, 8:03 PMripe-gigabyte-88964
04/17/2023, 8:05 PM15:39:19.05 [INFO] pantsd 2.16.0rc0 running with PID: 8365
15:39:19.15 [INFO] handling request: `--print-stacktrace dagster ::`
15:39:33.76 [INFO] request completed: `--print-stacktrace dagster ::`
15:40:21.79 [INFO] notify invalidation: cleared 0 and dirtied 0 nodes for: {"pants-plugins/plugins/dagster/goals.py"}
15:40:21.79 [INFO] notify invalidation: cleared 1 and dirtied 2 nodes for: {"pants-plugins/plugins/dagster/goals.py"}
15:40:21.79 [ERROR] saw filesystem changes covered by invalidation globs: content changed (Digest('9b61bab483e5f51b9e1b551b38c18b6107fc67c36ef076955bca0bd855d60795', 258) fs Digest('7f68cd243874fee0d32a5ffe1850bfc5f3307f0a42efa7dcc779948ef995f40d', 258)). terminating the daemon.
15:40:22.67 [ERROR] service failure for <pants.pantsd.service.scheduler_service.SchedulerService object at 0x442574a910>.
ripe-gigabyte-88964
04/17/2023, 8:23 PMdagster_home_path = dist_dir.relpath / "dagster_home"
dagster_home_digest = await Get(Digest, CreateDigest([Directory(str(dagster_home_path))]))
logger.debug(f"Creating dagster home directory at {dagster_home_path}")
workspace.write_digest(dagster_home_digest)
logger.debug("dir created")
dagster_process = await Get(
Process,
VenvPexProcess(
dagster_pex,
argv=("dev", *process_opts),
input_digest=await Get(Digest, MergeDigests([sources_digest, dagster_home_digest])),
extra_env=FrozenDict({"DAGSTER_HOME": dagster_home_path.absolute()}),
description="Run dagit",
),
)
logger.debug("dagster process")
result = await Effect(
InteractiveProcessResult, InteractiveProcess, InteractiveProcess.from_process(dagster_process)
)
witty-crayon-22786
04/17/2023, 10:49 PM--no-pantsd
?ripe-gigabyte-88964
04/18/2023, 12:14 PMripe-gigabyte-88964
04/18/2023, 12:17 PMripe-gigabyte-88964
04/18/2023, 12:19 PMdist
directory?ripe-gigabyte-88964
04/18/2023, 12:29 PMripe-gigabyte-88964
04/18/2023, 12:57 PMhappy-kitchen-89482
04/18/2023, 2:21 PMhappy-kitchen-89482
04/18/2023, 2:22 PMripe-gigabyte-88964
04/18/2023, 3:15 PMhappy-kitchen-89482
04/18/2023, 3:27 PMFilesystem changed during run
issue, or just the input digest issue?ripe-gigabyte-88964
04/18/2023, 3:30 PMripe-gigabyte-88964
04/18/2023, 8:00 PMPYTHONPATH
when I run the pex shim. However, providing PYTHONPATH
as an extra_env
variable to VenvPexProcess
doesn't seem to work. I also see that there is a PEX_EXTRA_SYS_PATH
option for building the pex, but I don't see a good way to use that in a PexRequest
.happy-kitchen-89482
04/18/2023, 10:38 PMripe-gigabyte-88964
04/19/2023, 12:49 PMdist
.ripe-gigabyte-88964
04/19/2023, 1:14 PM./pex_shim dagster dev -m module_name
) -m module_name
and for whatever reason, that was causing it to recognize the module name as ' module_name' instead of just 'module_name'.happy-kitchen-89482
04/19/2023, 3:38 PMpants run path/to/file.py
works like that - it builds a reusable third-party only pex, but takes sources directly from the source tree.happy-kitchen-89482
04/19/2023, 3:38 PM-mmodule_name
?ripe-gigabyte-88964
04/19/2023, 3:40 PM--module-name=mymodule
worked, but -m mymodule
did not due to added whitespace. -m
is shorthand for --module-name
.happy-kitchen-89482
04/19/2023, 10:06 PM-mmodule_name
would also workhappy-kitchen-89482
04/19/2023, 10:06 PMhappy-kitchen-89482
04/19/2023, 10:06 PMhappy-kitchen-89482
04/19/2023, 10:06 PM--module-name
seems better anywayhappy-kitchen-89482
04/19/2023, 10:06 PM