Github returned error 422: Validation Failed #66

Closed
jonlong opened this Issue Feb 2, 2013 · 3 comments

Comments

Projects
None yet
2 participants
@jonlong

jonlong commented Feb 2, 2013

Have generated a token with the curl call and tried authenticating via both the OSX keychain and settings file methods, as well as removing/reinstalling via both Package Control and directly from GitHub.

All attempts to create a new gist end with the error message "Gist: GitHub returned error 422: Validation Failed"

Has anyone run into this issue before?

@jonlong

This comment has been minimized.

Show comment
Hide comment
@jonlong

jonlong Feb 7, 2013

Able to replicate when attempting to save a gist with no content. This was coming up because my workflow was such that I saved/named the gist before adding any content, so it was tossing an "unprocessable entity" error as all the necessary fields weren't filled.

Right behavior, just a vague error message—will submit a patch with a more descriptive one.

jonlong commented Feb 7, 2013

Able to replicate when attempting to save a gist with no content. This was coming up because my workflow was such that I saved/named the gist before adding any content, so it was tossing an "unprocessable entity" error as all the necessary fields weren't filled.

Right behavior, just a vague error message—will submit a patch with a more descriptive one.

@condemil

This comment has been minimized.

Show comment
Hide comment
@condemil

condemil Aug 8, 2013

Owner

Added error message about empty content of the file. GitHub API not allow to create files with empty content.

Owner

condemil commented Aug 8, 2013

Added error message about empty content of the file. GitHub API not allow to create files with empty content.

@condemil condemil closed this Aug 8, 2013

@jonlong

This comment has been minimized.

Show comment
Hide comment
@jonlong

jonlong Aug 8, 2013

@condemil Aaaaand I never submitted that patch. Thanks for the fix!

jonlong commented Aug 8, 2013

@condemil Aaaaand I never submitted that patch. Thanks for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment