-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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/cmd/gorename: panics when displaying diff #14009
Comments
After trying to patch locally, I noticed that stdout is actually nil. I may be missing something when running gorename, but I'm not sure what. |
Adding logic to set stdout to os.Stdout fixed the issue. The test used inside knowledge of the files to set the stdout variable to os.Stdout when running tests. To not break the tests, I've not restructured the files but added some logic to the flag parsing to set stdout properly. I'm working on getting gerrit set up to submit a patch. |
CC @alandonovan |
I have a change ready for review, but the CLA is taking a while to show up in gerrit. Just waiting on that before |
Gerrit is not picking up the CLA I had already signed before signing up with Gerrit. Trying again doens't work, since I already signed once. Any chance of an assist here? |
@ScottMansfield, email me details (which email you're trying, whether it's your gmail, what Gerrit says, etc). My github username at golang.org. |
Submitted CL: https://go-review.googlesource.com/#/c/18813/ |
This is for the golang/tools repository, but can't open an issue there.
Running gorename with the diff display option panics when diff returns no data. Because err is not checked (because of the diff return codes) before display, the display part can panic when the diff output is nil.
My run on my local machine gave me a panic:
I will be submitting a small patch to prevent this panic and provide some output.
The text was updated successfully, but these errors were encountered: