-
Notifications
You must be signed in to change notification settings - Fork 1k
panic: shouldn't be possible unable to deduce repository and source type for: "golang.org/x/sys/unix" #581
Comments
sm.DeduceProjectRoot: unable to deduce repository and source type for: "golang.org/x/crypto/acme/autocert" |
The ultimate reason for the error is detailed in #292, but it's not great that there's a panic case that can be triggered by this. Let's treat this issue as being about covering that panic. |
Any specific error message instead of the panic? |
Looking at the source line, I see it's preceded by a note from me:
So yeah 😄 Problem is, at that specific point, there are a number of things that could cause the error. Still, for now, the best thing to do is probably just return the error out directly. |
Should it be handled somewhere else? Otherwise,
|
#561 Seems like an improvement to the errors that are returned:
|
Yes, #561 would improve the message - but it absolutely does have to return out the error, as it's not possible to continue solving if this occurs. It could be handled earlier, e.g. in |
BTW, I noticed that |
Right, we never print anything directly from within gps. There's only one single solitary exception to that rule, and it needs to be gotten rid of, too 😄 apart from the fs funcs you're working on in the other PR, gps should be considered self-contained, and import only things at or below its level in the project. Instead, follow the pattern that's in that function - return a
It is - the comments say a bit about it. It's run the second time in order to get the modified input hash for the |
solver.selectRoot() panics when solver.intersectConstraintsWithImports() returns an error. This commit returns the error instead if that error is due to inability to deduce a project repository. Solves golang#292 and golang#581 Signed-off-by: Ibrahim AshShohail <[email protected]>
@sdboyer Somehow this issue is not reproducible using I'm getting the following error instead of a panic: @bsed Could you update |
The text was updated successfully, but these errors were encountered: