Rubén Lopez Lozoya
04/07/2021, 3:49 PMRubén Lopez Lozoya
04/07/2021, 6:07 PMOperation name: PartitionSetLoaderQuery
Message: Unknown fragment "PartitionGraphFragment".
Path:
Locations: [{"line":69,"column":6}]
I am able to run the backfill with no problems but my screen is full of GraphQL error notifications, anyone knows why does this happen?Peter B
04/07/2021, 8:58 PMArun Kumar
04/07/2021, 11:49 PMK8RunLauncher
to execute a pipeline run in a separate K8s job?Avri Naamani
04/08/2021, 7:11 AMError: There are no sensors defined for repository...
while running dagster sensor list -d path_to_working_dir/ -f /path_to_pipeline_file.py
I tried to put the sensor function and decorator in a separate file and also in the same file as the pipeline.
When i try to run the same command on the sensor file i get dagster.core.errors.DagsterUserCodeProcessError: dagster.core.errors.DagsterInvariantViolationError: No pipelines or repositories found in "address_enrichment_sensor".
What am i missing here?Josh Taylor
04/08/2021, 8:18 AMAlessandro Marrella
04/08/2021, 8:24 AMdagster_celery_k8s
:
An exception was thrown during execution that is likely a framework error, rather than an error in user code.
dagster.check.CheckError: Invariant failed. Description: Pipeline run dev_volumeclass_pipeline (0329a1a3-4013-4dfc-8f84-d9ee13492b9e) in state PipelineRunStatus.STARTED, expected NOT_STARTED or STARTING
any idea why this happens? (dagster 0.11.3)Marco
04/08/2021, 8:37 AMcvb
04/08/2021, 11:13 AMdagster.reconstructable(mypipeline)
. It works fine, except now I can't reload my pipeline without restarting python, somehow reconstructable
always returns the same pipeline, any ideas how to force it to reload?
Here is what I mean with examples in ipython:
In [1]: import tst_pipe
In [2]: import dagster
In [4]: orig_solids = [s.name for s in tst_pipe.pipe.solids]
...: recons = [s.name for s in dagster.reconstructable(tst_pipe.pipe).get_definition().solids]
...: print('original', orig_solids)
...: print('recons', recons)
original ['c', 'b', 'a']
recons ['c', 'b', 'a']
looks fine, now I add new step to my file and relaunch the same code:
In [5]: orig_solids = [s.name for s in tst_pipe.pipe.solids]
...: recons = [s.name for s in dagster.reconstructable(tst_pipe.pipe).get_definition().solids]
...: print('original', orig_solids)
...: print('recons', recons)
original ['c', 'b', 'd', 'a']
recons ['c', 'b', 'a']
Marco
04/08/2021, 1:43 PMMarco
04/08/2021, 1:47 PMRubén Lopez Lozoya
04/08/2021, 3:12 PMclient.ts:557 WebSocket connection to '<wss://mydoman.com/graphql>' failed:
This never happened to me, but my Dagster status indicator turns grey and if I refresh the page it turns green again but any action shows a loading spinner that stays forever and I keep getting this errorsandy
04/08/2021, 3:25 PMPythonObjectDagsterType
and bye bye (mostly) to make_python_type_usable_as_dagster_type
I wanted to highlight a recent change that makes Dagster easier to use with PEP 484 type annotations.
Previously, @solid
-decorated functions would only accept type annotations for a limited subset of types. E.g. the following code would fail with a `DagsterInvalidDefinitionError`:
class MyClass:
pass
@solid
def my_solid(_, input1: MyClass):
pass
As of 0.11.0, this is a valid definition. Dagster will automatically construct a DagsterType
for MyClass
, which means it will automatically show up in Dagit as well.
This change should significantly reduce boilerplate in some situations. You should never need to instantiate a PythonObjectDagsterType
, and you should only need to use the usable_as_dagster_type
and make_python_type_usable_as_dagster_type
APIs in situations where you want to apply a custom type check function to every instance of a particular Python type.
Happy typing!David Smit
04/08/2021, 4:00 PMMatt Bereiter
04/08/2021, 4:46 PMAlex Despotakis
04/08/2021, 4:50 PMSolidExecutionContext
object called context
for some solid in composite pipeline COMP
, made up of pipelines A
, B
, and C
. If I call context.pipeline_name
the property will return COMP
. Let's say the context is from a solid that exists in A
, is there an EASY way to trace the solid back to the originating pipeline? In this case, each solid in COMP
is unique. Alternatively, if we know the pipeline's name in advance, is there a way to get all of the solids in that pipeline? That might be easier than the garbage I came up with.Ben Torvaney
04/08/2021, 8:16 PMJamie
04/08/2021, 10:32 PMMark Kudryk
04/08/2021, 10:38 PMuser
04/08/2021, 11:29 PMchris
04/08/2021, 11:41 PMArun Kumar
04/09/2021, 10:12 AMDaniil
04/09/2021, 1:32 PMdagster.yaml
or complete example with all possible fields somewhere. Didn't find it in the docs. By now my dagster.yaml
is as follows (mostly copied it from https://github.com/dagster-io/dagster/blob/master/examples/deploy_docker/dagster.yaml ), db is up and being populated with some data. But still it keeps to create local directory storage
and write logs to it. Probably need to another storage to yaml but not sure what.Ronak Jain
04/09/2021, 1:47 PMdagster-scheduler/dagster-scheduler/schedules/scripts/fe95d72f20754d7eaec30af5bf8fb1ad7f75a24b.sh: Operation not permitted
while running scheduler...?Ronak Jain
04/09/2021, 2:34 PMRonak Jain
04/09/2021, 2:42 PMRonak Jain
04/09/2021, 2:44 PMEduardo Santizo
04/09/2021, 3:35 PMcvb
04/09/2021, 5:09 PMadamd
04/09/2021, 7:27 PMadamd
04/09/2021, 7:27 PM