Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I can't actually decide if this is a bug or just me doing something wrong....
What version of Go are you using (
We are seeing something that seems very likely to be related since it is a nested package in dcrd. However, rather than not being able to find the module, instead the dependency solver believes the nested module is provided by the parent module despite the parent module not including it as evidenced by looking in
This can currently be reproduced as of dcrd commit be318f5a by navigate to the
The following are the results:
We can verify the
For some extra data, here are the relevant tags:
@IngCr3at1on, the first problem is that the go.mod files checked into the repo are empty. They need to have a module line, like
I will make this issue track having a good diagnosis of this condition.
Once those go.mod files are updated (and new tags added), then I think you'll be up against #26250. Watch for that issue to be closed.