#I have a module that has a dependency on
frail locust
Ultimately I'm not even sure what should happen in this case, since the versions may be incompatible. Maybe we name the dependency something unique?
vestal yacht
I ran into this also... I think it's a regression, since all modules are scoped, there's no reason for dependencies to conflict in this way
cc @untold stone @mint sage @wet crypt maybe a theseus regression?
vestal yacht
Ultimately I'm not even sure what should happen in this case, since the versions...
I'll let the experts weigh in on that particular error, but the overall design is that dependencies are fully namespaced, so you can have any number of instances of the same module, loaded in different places in the dependency tree, at different versions, and they will not conflict. (which is why I think this error is a regression)
@frail locust would you mind opening a github issue? 🙏 So that we can track it properly
wet crypt
offhand I'm not sure if it's theseus-related or not, https://github.com/dagger/dagger/blob/4e44fdb7eaf2e5545a7a5650a58db22b4c0f2ca0/engine/server/session.go#L1251 looks to be the error? I think a github issue would help. But maybe the other experts would have a better idea 😅
frail locust
This looks exactly like the error I was getting. Workaround was to prepend the project name to the dependency name.
mint sage
does anyone have a reproducer here?
it is an error to load the same module twice into a session (would be nice to fix, but not sure on desired behavior)
there's a possible way of getting this with https://github.com/dagger/dagger/issues/10669#issuecomment-3031752234
vestal yacht
there's a possible way of getting this with https://github.com/dagger/dagger/iss...
Ah yup that's how I hit it - was in the shell