Weird Error: Creating gist failed: 422 Unprocessable Entity #79

Closed
cordoval opened this Issue Mar 16, 2012 · 34 comments

Comments

Projects
None yet

all of a sudden gist Creating gist failed: 422 Unprocessable Entity

stopped working

draper7 commented Mar 16, 2012

Same here...

$export GITHUB_USER=draper7
$export GITHUB_TOKEN=xxxxxxxxxxxxxxxxxxxxxx
$gist file.txt
Creating gist failed: 422 Unprocessable Entity
$gist -v
2.0.4

I installed 2.0.0 and see this error:

$gist ls.txt
SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
...

Thanks,

Dusty

+1 :(

+1

I mean where is @defunkt :D, is it his fault or is it github's fault?

anyone knowledgeable enough to troubleshoot and blame one or the other? anyone have rebased their install or can point to a solution?

https://gist.github.com/2048076

That shoes that gisty seems to be having the same problem.

On Fri, Mar 16, 2012 at 4:10 PM, Luis Cordova <
reply@reply.github.com

wrote:

I mean where is @defunkt :D, is it his fault or is it github's fault?

anyone knowledgeable enough to troubleshoot and blame one or the other?
anyone have rebased their install or can point to a solution?


Reply to this email directly or view it on GitHub:
#79 (comment)

what is gisty? is that another gem? do they rely on the same communication with github? somebody please draw attention to this

tomasky commented Mar 18, 2012

I have the some error with vim-gist.

yes i think it is using some common component which is failing can someone check please?

It's a CSRF error, use the API.

canoon commented Mar 18, 2012

Looks like github is finally auditing their code.

this is on gist gem, @technoweenie what do you suggest when you say use the API? you mean the web? so this gist gem is useless now? How easy is it to change to API the current code?

sanemat commented Mar 19, 2012

I have same error ;(
https://gist.github.com/2048076

How to get more verbose error?

locojay commented Mar 19, 2012

same here with or without setting GITHUB_USER, GITHUB_TOKEN

@defunkt I think you are the only one that can help a non rubyist to switch the code on your gist gem to support the new changes on the API

Here's the problem:

http://develop.github.com/p/gist.html

Create a New Gist

Coming soon.

Github must have flipped the switch to require using the API, yet there is
no documentation on how to create a gist using the api.

On Sun, Mar 18, 2012 at 10:33 PM, Luis Cordova <
reply@reply.github.com

wrote:

@defunkt I think you are the only one that can help a non rubyist to
switch the code on your gist gem to support the new changes on the API


Reply to this email directly or view it on GitHub:
#79 (comment)

my bad... that one was deprecated...

http://developer.github.com/v3/gists/

On Sun, Mar 18, 2012 at 10:40 PM, Peter Hamilton
peterghamilton@gmail.comwrote:

Here's the problem:

http://develop.github.com/p/gist.html

Create a New Gist

Coming soon.

Github must have flipped the switch to require using the API, yet there is
no documentation on how to create a gist using the api.

On Sun, Mar 18, 2012 at 10:33 PM, Luis Cordova <
reply@reply.github.com

wrote:

@defunkt I think you are the only one that can help a non rubyist to
switch the code on your gist gem to support the new changes on the API


Reply to this email directly or view it on GitHub:
#79 (comment)

Can we close the issue? Defunkt already provided an alternate path until the gem gets fixed. This issue isn't doing anyone any good, he's spamming it on IRC.

Just tracking and logging some guidance, hope someone is able to PR, thanks guys

quoting @Ryanf

the gem isn't posting to /gists within the api, it's posting to gist.github.com/gists
which belongs to the web app
so the reason it isn't working is that the web app won't accept the post without a token that proves you're coming from a page rendered by the rails app
which you aren't
so the whole thing would need to be redone to use the API   
just managed to use the API via curl, so in principle there's no reason the gem can't work
the things that need to change are

CREATE_URL = 'https://api.github.com/gists'
and the data method needs to be rewritten to generate json

+1 Please fix

@ghost

ghost commented Mar 19, 2012

+1 please fix

+1

+1

matheo commented Mar 19, 2012

+1

w0ng commented Mar 19, 2012

@Spaceghost can you share what was discussed on IRC as the alternative?

+1
Please fix this.

+1

Owner

defunkt commented Mar 20, 2012

Fixed. (thanks @boucher!)

I just pushed version 3.0.0 to RubyGems. Updating homebrew now.

Important: No more GITHUB_TOKEN or github.token. Just use your password instead.

See the README for keychain integration help.

@defunkt defunkt closed this Mar 20, 2012

yes thanks so much @defunkt, I could not have done it myself, thanks really

Why remove the Token? Having my password set as an env variable isn't optimal.

I agree with @ampledata, what gives with not using tokens anymore?

I wrote a post here about using Git's include feature for private configuration info like your GitHub token and password you guys may be interested in: http://travisjeffery.com/b/2012/03/using-gits-include-for-private-information-like-github-tokens/

@sanemat sanemat referenced this issue in swdyh/gisty Feb 2, 2013

Open

Error 422 Unprocessable Entity #6

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