-
Notifications
You must be signed in to change notification settings - Fork 424
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
GRIP (possible regression) giving me an error for some reason #382
Comments
Same here, feels like a regression in the REST API. |
Yeah, I just used it on my work computer and it bunked too, and for that I'm on python 3.11. Same error. Thanks @alexander-roemer for the validation. |
I've got a ticket open with GH support, will report back if I find out anything useful. |
Just discovered this project, and thought it was an error on my part. Hope GH maintainers get in touch soon |
I'm experiencing the same here. I tried modifying the headers in
but get the same error. Unfortunately, I'm not familiar enough with the api interactions to be more useful than that. |
I have kind of a hacky workaround using directly the github api with
Then open readme.html locally.
|
Same for me.
|
The error page body is: {"message":"Invalid request media type (expecting 'text/plain')","documentation_url":"https://docs.github.com/rest/markdown/markdown#render-a-markdown-document-in-raw-mode"} But setting Content-Type to In the mean time, |
Same here! |
If the |
Same error here. # if self.user_content:
url = '{0}/markdown'.format(self.api_url)
data = {'text': text, 'mode': 'gfm'}
if self.context:
data['context'] = self.context
data = json.dumps(data, ensure_ascii=False).encode('utf-8')
headers = {'content-type': 'application/json; charset=UTF-8'}
# else:
# url = '{0}/markdown/raw'.format(self.api_url)
# data = text.encode('utf-8')
# headers = {'content-type': 'text/x-markdown; charset=UTF-8'} |
Update from GitHub support: they confirmed this issue exists and I am waiting on an update from engineering. |
This is a valid workaround. Works also for me when using the empty personal token via |
Just ran into this, thank you for the feedback and support, all! I can confirm that
indeed is a workaround at the moment. |
Let's one-up that, for my mac (with z-shell), I ran this and now I just type echo "export GRIPUSER='asdfasdf'" >> ~/.zshrc && echo "export GRIPPASS=''" >> ~/.zshrc && echo "alias grip=\"grip --user=\$GRIPUSER --pass=\$GRIPPASS\"" >> ~/.zshrc && source ~/.zshrc |
Or, more easily, you could set username and password in |
As is
where my github personal token is stored in /path/to/github_token |
Hi folks, GitHub employee here. Just wanted to report that the API issue is now resolved, and unauthenticated requests to the Thanks for bringing this to our attention, and apologies for the trouble! |
Getting an error and I don't know why. I thought it was because I had a circular link (like a link from A --> B and from B --> A) but then I removed it and it still didn't work. Details below
The text was updated successfully, but these errors were encountered: