-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/tools/gopls: bad error messages when changing package names #41061
Comments
Is this a duplicate of #38866? |
Possibly, but I think there are also issues with transitioning from a regular package to an x test. |
I've got a repro based on the above testcase, and will start taking a peek soon. Is anyone else working on this, though? Don't want to step on toes. =) (if I hear nothing back I'll continue as if the answer to that is a "no") |
Go right ahead. i was going to look at #38866 but there's other things to do. |
Change https://golang.org/cl/262019 mentions this issue: |
@pjweinb After a couple fridays afternoons of 20%ing, I unfortunately didn't get enough traction. This one appears to require a lot of institutional knowledge. 🙂 📚 Per @stamblerre suggestion I've parked the test that I wrote at https://go-review.googlesource.com/c/tools/+/262019, which I believe exercises this, but I'll take the pragmatic approach of dropping off this one and trying out an easier feature. Sincere apologies if I wasted anyone's time trying to tackle this!! |
This adds a test that asserts that gopls gracefully recovers from a bad package name. It does not include the fix for the test, and so this test is skipped: I took a stab at it but it was a deep spelunk that I wasn't able to make enough progress on. Updates golang/go#41061 Change-Id: I86d817396dae5b0211e633721867e811c7d6cf40 Reviewed-on: https://go-review.googlesource.com/c/tools/+/262019 Run-TryBot: Jean de Klerk <[email protected]> gopls-CI: kokoro <[email protected]> TryBot-Result: Go Bot <[email protected]> Trust: Jean de Klerk <[email protected]> Reviewed-by: Rebecca Stambler <[email protected]>
Change https://golang.org/cl/274533 mentions this issue: |
Instead of skipping the test, insist on 1.16 or later. See golang/go#41061 Change-Id: Ie13f114039693993d65333ab9194629187a9b6b1 Reviewed-on: https://go-review.googlesource.com/c/tools/+/274533 Run-TryBot: Peter Weinberger <[email protected]> gopls-CI: kokoro <[email protected]> TryBot-Result: Go Bot <[email protected]> Trust: Peter Weinberger <[email protected]> Reviewed-by: Rebecca Stambler <[email protected]>
Let's close this now that the test has been enabled. |
Instead of skipping the test, insist on 1.16 or later. See golang/go#41061 Change-Id: Ie13f114039693993d65333ab9194629187a9b6b1 Reviewed-on: https://go-review.googlesource.com/c/tools/+/274533 Run-TryBot: Peter Weinberger <[email protected]> gopls-CI: kokoro <[email protected]> TryBot-Result: Go Bot <[email protected]> Trust: Peter Weinberger <[email protected]> Reviewed-by: Rebecca Stambler <[email protected]>
Repro case:
Modifying foo/bar_test.go to contain
package foo_test
results in bad error messages (it doesn't recover from expecting that its name isfoo_
.The text was updated successfully, but these errors were encountered: