You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue reproduce with the latest stable release?
Yes (at v0.8.2)
What did you do?
# old
env CUE_EXPERIMENT=modules=0
exec cue vet -c .
# new
env CUE_EXPERIMENT=modules
exec cue vet -c .
-- cue.mod/module.cue --
module: "github.com/foo/bar"
language: {
version: "v0.9.0"
}
-- bar.cue --
package bar
import xxx "github.com/foo/bar/abc:abc"
z: xxx.x & 123
-- abc/baz.cue --
package abc
x: 123
What did you expect to see?
A passing test
What did you see instead?
# old (0.023s)
# new (0.011s)
> env CUE_EXPERIMENT=modules
> exec cue vet -c .
[stderr]
github.com/foo/bar@v0: import failed: no dependency found for package "github.com/foo/bar/abc":
./bar.cue:3:8
[exit status 1]
FAIL: /tmp/testscript3893947838/repro.txtar/script.txtar:7: unexpected command failure
The text was updated successfully, but these errors were encountered:
Otherwise trying to load an import path with an unnecessary qualifier,
such as "mod.com/x:x", would be added to the map of known packages
under its canonical form "mod.com/x", but we would do the lookup
based on the original non-canonical import path, not finding a match.
Add reminders to the relevant places about the paths being canonical,
and use a separate variable for unqualified import paths for clarity.
The use of unqualified paths seems wrong to me too, so add a TODO.
Fixes#3162.
Signed-off-by: Daniel Martí <mvdan@mvdan.cc>
Change-Id: Ifc748ce61420f501b08216662b647e5475822593
What version of CUE are you using (
cue version
)?Does this issue reproduce with the latest stable release?
Yes (at v0.8.2)
What did you do?
What did you expect to see?
A passing test
What did you see instead?
The text was updated successfully, but these errors were encountered: