Skip to content
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

Doghouse server is broken after Github API changes #184

Closed
josephbergevin opened this issue Aug 29, 2018 · 10 comments
Closed

Doghouse server is broken after Github API changes #184

josephbergevin opened this issue Aug 29, 2018 · 10 comments

Comments

@josephbergevin
Copy link

I am trying to run golint on a subdirectory in my repo using this command:

golint -set_exit_status ./pkg/... | reviewdog -f=golint -diff="git diff origin/master" -reporter=github-pr-check

But it is giving me a 422 Invalid request error - along with the message: "annotation_level", "path" weren't supplied. []

I can get this to run successfully by changing my command to this:

cd pkg && golint -set_exit_status ./... | reviewdog -f=golint -diff="git diff origin/master" -reporter=github-pr-check

But then the links referenced in the errors don't include the pkg folder, so they don't work.

I there a reviewdog flag I need to include to be able to make one of the above run commands work properly?

@cupakromer
Copy link

Started getting this today too for Ruby / Rails projects. Looks like it's an issue with a change in the github API.

@josephbergevin
Copy link
Author

Oh, interesting. Is there a specific issue filed?

@cupakromer
Copy link

Well I think this may be it for reviewdog. Otherwise, digging around I see that the current GitHub v3 API for checks lists annotation_level and path as required fields for an annotation object.

Looks like changes were announced via the GitHub blog on 2018-08-16 and stated to take effect just the other day on the 27th (2018-08-27).

I think these are the change which caused the issue:

  • filename is being renamed to path
  • warning_level is being renamed to annotation_level

@josephbergevin
Copy link
Author

I wonder why those are not being renamed when the linter is run on the project directory...

@josephbergevin
Copy link
Author

@haya14busa wondering if I can get your take on this 422 Invalid request error popping up...

@ruudk
Copy link
Contributor

ruudk commented Sep 27, 2018

Getting the same issue today. When the checks report issues that are filtered (outside git diff) it does work. But when they are part of the git diff, it breaks.

@ruudk
Copy link
Contributor

ruudk commented Sep 27, 2018

@josephbergevin Can you change the title of this issue? Something like "Doghouse server is broken after Github API changes"

@ruudk
Copy link
Contributor

ruudk commented Sep 27, 2018

Btw, if the server code of Doghouse were to be open source, we could fix this issue 💪 ;)

@josephbergevin josephbergevin changed the title Error when running golint on subdirectory Doghouse server is broken after Github API changes Sep 30, 2018
@josephbergevin
Copy link
Author

Yeah I came to the same roadblock. The fix definitely needs to happen in the doghouse server code.

@haya14busa
Copy link
Member

I'm sincerely sorry for the very late response. I fixed it today so it should work fine now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants