Louis Auneau
03/30/2023, 2:30 PMpipelines
with:
• one asset (define as decorated function),
• one job (defined through define_asset_job
),
• one sensor triggering the asset (defined as decorated function),
• and an __init__.py
at the module root containing the following code:
from dagster import Definitions
from pipelines.core.resources.my_resource import my_resource
from pipelines.my_folder.job import my_job
from pipelines.my_folder.sensors import my_sensor
from pipelines.my_folder.assets import my_asset
defs = Definitions(
assets=[my_asset],
schedules=[],
jobs=[my_job],
sensors=[my_sensor],
resources={'my_resource': my_resource}
)
I then start dagster dev -m my_module
Everything works correctly and seeing the log I can say that my sensor and job are being triggered. But there are numerous pages inside dagit that contains errors looking like the ones attached.
Do you know what could I have done wrong ? Is it a known bug (I have seen another person mention the same a month ago) ?
Thank you by advance and have a nice day!pipelines
, there’s an error in the front end.
Dagit URLs look like this
<http://127.0.0.1:3000/locations/><module_name>/jobs/<job_name>
If your module is named pipelines
, legacy code here, will try to find a “pipeline” called “jobs” which probably doesn’t exists, which gives you this error.
Just rename your package 🙂sean
03/30/2023, 4:11 PM