garethbrickman
commented
1 hour ago Is this reproducible when running dagster dev locally? My first though is in your setup.py or requirements.txt is you should ensure you pin dagster and dagster-webserver to use the same versions.
(If you don't explicitly pin all dagster dependencies to the same version, then there will be version mismatches that can cause incompatibilities).
What's the issue?
Dagster reported an Unexpected GraphQL error,I want to know if this issue is a bug or a problem with my dagster settings?
error info: Operation name: {RunRootQuery}
Message: 'NoneType' object has no attribute 'lineage_snapshot'
Path: ["pipelineRunOrError","parentPipelineSnapshotId"]
Locations: [{"line":14,"column":3}]
Stack Trace: File "/usr/local/lib/python3.10/site-packages/graphql/execution/execute.py", line 523, in execute_field result = resolve_fn(source, info, **args) File "/usr/local/lib/python3.10/site-packages/dagster_graphql/schema/pipelines/pipeline.py", line 476, in resolve_parentPipelineSnapshotId if snapshot.lineage_snapshot is not None:
What did you expect to happen?
No response
How to reproduce?
No response
Dagster version
1.8.7
Deployment type
Docker Compose
Deployment details
Package an image using Docker, upload it to AWS ECR, deploy grpc, daemon, and web server on AWS ECS, and use Fargate's startup type
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization. By submitting this issue, you agree to follow Dagster's Code of Conduct.