-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Enable staticcheck and fix all issues #144
Conversation
Staticcheck is being killed for some strange reasons. Was this what you were seeing before you turned off staticcheck? @andydotxyz |
Yes |
@dominikh Do you have any idea as to why this would be happening to staticcheck? |
It's being killed because of an out of memory situation. This is probably dominikh/go-tools#825. It's likely that some package in Fyne is triggering bad behavior in Staticcheck and causes way higher memory usage than is normal. Diagnosing this is still on my todo list. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think one or two of my previous comments should have been "request changes" so applying that now
I think that if this was rebased the checks would start running again |
It should now be updated against latest develop again. Going to see if I can fix these comments. |
Looks like we are still seeing |
So #148 would fix this maybe? |
Hopefully. Lets rebase on it when that one lands 🙂 |
This PR makes sure to get all the issues reported by staticcheck fixed and marks the ones that can't be fixed to be ignored for now (waiting for Fyne 2.0.0 mostly). It should now be possible to set the GitHub action to be required 👍