Kevin Otte

02/06/2023, 1:53 AM
Trying to import my own repo and receiving this error:
dagster._core.errors.DagsterInvariantViolationError: No repositories, jobs, pipelines, graphs, asset groups, or asset definitions found in "data".
  File "/usr/local/lib/python3.8/site-packages/dagster/_grpc/", line 256, in __init__
    self._loaded_repositories: Optional[LoadedRepositories] = LoadedRepositories(
  File "/usr/local/lib/python3.8/site-packages/dagster/_grpc/", line 114, in __init__
    loadable_targets = get_loadable_targets(
  File "/usr/local/lib/python3.8/site-packages/dagster/_grpc/", line 57, in get_loadable_targets
    else loadable_targets_from_python_package(package_name, working_directory)
  File "/usr/local/lib/python3.8/site-packages/dagster/_core/workspace/", line 52, in loadable_targets_from_python_package
    return loadable_targets_from_loaded_module(module)
  File "/usr/local/lib/python3.8/site-packages/dagster/_core/workspace/", line 133, in loadable_targets_from_loaded_module
    raise DagsterInvariantViolationError(
but I do have assets in this repo and this message looks cutoff... any ideas on how to debug?
:dagster-bot-resolve: 1
Here are the logs from the serverless deployment


02/06/2023, 3:41 AM
Hi Kevin - do you see the same error if you checkout your github repo and run "dagster dev" locally? (That can be a bit faster than waiting for serverless to deploy your code)
One common cause of this - the init file of your package (
in this case) needs to actually import your assets. It doesn't automatically scan them just because they exist somewhere in the package. For example if you look in the init file in the quickstart package, it actually imports the assets there:

Kevin Otte

02/06/2023, 12:41 PM
ah it was the file