https://dagster.io/ logo
#ask-community
Title
# ask-community
r

Ronak Jain

03/28/2022, 1:09 PM
Guys, which version is stable Dagster 13.0 or 14.0 ? And, Please let me know reason as well, then I can migrate accordingly ? Thanks..
d

daniel

03/28/2022, 4:58 PM
Hi Ronak - the latest version is stable, that's what we recommend upgrading to. Any APIs that are more experimental will be clearly marked as such and log a warning when they're used.
r

Ronak Jain

03/31/2022, 7:39 AM
Hi @daniel Thanks for the your reply. But I am getting issue when, I am doing migrate here.
ERROR : No Modules named : dagster.core.definition.repository.
I migrated till 0.13.4, it's working fine but when I am moving into 14.5, I am getting issue from there
ERROR : No Modules named : dagster.core.definition.repository.
d

daniel

03/31/2022, 12:58 PM
Can you post the full stack trace of the error that you're seeing?
r

Ronak Jain

03/31/2022, 1:00 PM
@daniel Please look:
d

daniel

03/31/2022, 1:02 PM
Can you paste the text?
r

Ronak Jain

03/31/2022, 1:02 PM
ok
Copy code
2022-03-31 13:02:46 +0000 - dagster.daemon.SensorDaemon - INFO - Not checking for any runs since no sensors have been started.
2022-03-31 13:02:46 +0000 - dagster.daemon.SchedulerDaemon - WARNING - Could not load location udpsystem to check for schedules due to the following error: dagster.core.errors.DagsterImportError: Encountered ImportError: `No module named 'dagster.core.definitions.repository'` while importing module udpsystem from file /home/orchestrator/domains/udpsystem/udpsystem.py. Local modules were resolved using the working directory `/home/orchestrator`. If another working directory should be used, please explicitly specify the appropriate path using the `-d` or `--working-directory` for CLI based targets or the `working_directory` configuration option for `python_file`-based workspace targets.

Stack Trace:
  File "/usr/local/lib/python3.9/site-packages/dagster/grpc/server.py", line 212, in __init__
    self._loaded_repositories = LoadedRepositories(
  File "/usr/local/lib/python3.9/site-packages/dagster/grpc/server.py", line 97, in __init__
    loadable_targets = get_loadable_targets(
  File "/usr/local/lib/python3.9/site-packages/dagster/grpc/utils.py", line 27, in get_loadable_targets
    else loadable_targets_from_python_file(python_file, working_directory)
  File "/usr/local/lib/python3.9/site-packages/dagster/core/workspace/autodiscovery.py", line 18, in loadable_targets_from_python_file
    loaded_module = load_python_file(python_file, working_directory)
  File "/usr/local/lib/python3.9/site-packages/dagster/core/code_pointer.py", line 93, in load_python_file
    raise DagsterImportError(

The above exception was caused by the following exception:
ModuleNotFoundError: No module named 'dagster.core.definitions.repository'

Stack Trace:
  File "/usr/local/lib/python3.9/site-packages/dagster/core/code_pointer.py", line 79, in load_python_file
    return import_module_from_path(module_name, python_file)
  File "/usr/local/lib/python3.9/site-packages/dagster/seven/__init__.py", line 47, in import_module_from_path
    spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/home/orchestrator/domains/udpsystem/udpsystem.py", line 1, in <module>
    from services.utils.pipeline_facilitator import repository_creator
  File "/home/orchestrator/services/utils/pipeline_facilitator.py", line 4, in <module>
    from services.utils.domain_factory import DomainFactory
  File "/home/orchestrator/services/utils/domain_factory.py", line 16, in <module>
    from dagster.core.definitions.repository import CachingRepositoryData
cc: @daniel
d

daniel

03/31/2022, 2:23 PM
try changing that line to
Copy code
from dagster.core.definitions.repository_definition import CachingRepositoryData
imports that aren't from the top-level dagster module are technically not considered part of the public API and are more likely to change between versions
r

Ronak Jain

03/31/2022, 2:37 PM
Copy code
Stack Trace:
  File "/usr/local/lib/python3.9/site-packages/dagster/grpc/server.py", line 212, in __init__
    self._loaded_repositories = LoadedRepositories(
  File "/usr/local/lib/python3.9/site-packages/dagster/grpc/server.py", line 97, in __init__
    loadable_targets = get_loadable_targets(
  File "/usr/local/lib/python3.9/site-packages/dagster/grpc/utils.py", line 27, in get_loadable_targets
    else loadable_targets_from_python_file(python_file, working_directory)
  File "/usr/local/lib/python3.9/site-packages/dagster/core/workspace/autodiscovery.py", line 18, in loadable_targets_from_python_file
    loaded_module = load_python_file(python_file, working_directory)
  File "/usr/local/lib/python3.9/site-packages/dagster/core/code_pointer.py", line 93, in load_python_file
    raise DagsterImportError(

The above exception was caused by the following exception:
  File "/home/orchestrator/domains/udpsystem/udpsystem.py", line 1, in <module>
    from services.utils.pipeline_facilitator import repository_creator
  File "/home/orchestrator/services/utils/pipeline_facilitator.py", line 4, in <module>
    from services.utils.domain_factory import DomainFactory
  File "/home/orchestrator/services/utils/domain_factory.py", line 19, in <module>
    from services.openlineage_sensor.sensor import openlineage_sensor
  File "/home/orchestrator/services/openlineage_sensor/sensor.py", line 12, in <module>
    from dagster.core.definitions.sensor import DEFAULT_SENSOR_DAEMON_INTERVAL
@daniel Error still we have but different, do we have any alternative , I can move directly without HELM.
d

daniel

03/31/2022, 2:38 PM
try changing that to
from dagster.core.definitions.sensor_definition
. Try to avoid importing from dagster other than the top-level module to avoid similar issues in the future
r

Ronak Jain

03/31/2022, 2:45 PM
ok
d

daniel

03/31/2022, 2:46 PM
r

Ronak Jain

03/31/2022, 2:47 PM
ok, Thanks let me check 🙂
2 Views