When trying to transition to the Definitons API with GRPC se

Question

When trying to transition to the Definitons API with GRPC servers ``` old repository CMD dagster api grpc h 0 0 0 0 p 4000 f FOO repository py attribute myrepo == gt works fine new definitions CMD dagster api grpc h 0 0 0 0 p 4000 m package name == gt fails with = gt DagsterInvariantViolationError No repositories jobs pipelines graphs asset groups or asset definitions found in package name CMD dagster api grpc h 0 0 0 0 p 4000 m package name package name == gt fails with = gt No module named package name package name ` while importing module package name package name``` Similarly to <https github com slopp dagteam blob main workspace yaml> my workspace yaml looks like ```load from grpc server host package name port 4000 location name package name ``` inside docker But outside docker during local development ```load from python package package name package name package name``` Outside docker a `pip install e ` has been executed and the modules are resolvable Inside docker it would be convenient to not first volume map copy the file and then additionally pip install e it It would be uesful I think also for speedier reloading to be able to pass a file like before f FOO repository py Is there any chance I can get this convenient behavior back when using definitions My package scaffolded from dagster cli as package name package name assets py and package name package name init py contains in the init ```from import assets defs = Definitions assets= load assets from modules assets ``` However I do not find any good way to specify the init file in the ` f` parameter There dagster also fails to resolve it due to missing modules

geoHeil · Answer

< Ben Gotow> amp < Sean Lopp> can you also look at this

geoHeil · Answer

This problem is also reproducible when including a pip install e in the dockerfile

geoHeil · Answer

I just re converted all to a repository based approach This is working much better Please can you assist me to fix it for the new definitions API

geoHeil · Answer

However I think both seem to have the same problem which I could solve by now Irrespective of Definitions or repository api Both can be supplied with the ` f` parameter as a file And for both One MUST omit relative imports in the initial file irrespective if it is the ` init ` or `repository` file With this both variants are now working for me

Sean Lopp · Answer

I don t think this behavior has anything to do with the definitions API e g if you created a file called `definitions py` you could use it similar to your `repository py` file and include in ` init py` something like `from definitions import defs` I believe what you are seeing is expected differences in how python resolves relative imports in installed packages vs un installed packages

geoHeil · Answer

< Sean Lopp> might be something similar But I am still super confused due to the XOR behavior