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

[BUG] bot:peek image upload fails (403 response code imgur) #1124

Closed
1 task done
amacado opened this issue Mar 31, 2022 · 8 comments
Closed
1 task done

[BUG] bot:peek image upload fails (403 response code imgur) #1124

amacado opened this issue Mar 31, 2022 · 8 comments
Assignees
Labels
bug Use this label for pointing out bugs

Comments

@amacado
Copy link
Member

amacado commented Mar 31, 2022

I have searched through the issues and didn't find my problem.

  • Confirm

Bug description

Sometimes the upload to imgur seems to fail, not sure about the reasons yet:

image
https://github.com/devicons/devicon/runs/5771824897?check_suite_focus=true

The result is that bot:peek posts "env.MESSAGE" instead the images (see for example #1123 (comment)).

Possible fixes or solutions

Revisit the https://github.com/devicons/public-upload-to-imgur project and see what's the problem

Additional information

No response

@amacado amacado added the bug Use this label for pointing out bugs label Mar 31, 2022
@amacado amacado changed the title [BUG] bot:peek image upload failes (403 response code imgur) [BUG] bot:peek: image upload fails (403 response code imgur) Mar 31, 2022
@amacado amacado changed the title [BUG] bot:peek: image upload fails (403 response code imgur) [BUG] bot:peek image upload fails (403 response code imgur) Mar 31, 2022
@Thomas-Boi
Copy link
Member

Sure, I'll take a look at the issue. Might need 2 weeks before I can do that though.

@Thomas-Boi
Copy link
Member

Brief research shows that there's a new Bearer token in the docs.
image

Since our request is failing with a 403 error (forbidden access), it seems like we might need a new token. I'll look more into this issue after 2 weeks.

@Panquesito7
Copy link
Member

Has this been addressed?

@Snailedlt
Copy link
Collaborator

@Panquesito7 I'm not sure, but I haven't seen the issue pop up again in quite some time. @Thomas-Boi Did you ever fix this? If not, maybe it was fixed by another API update?

@Thomas-Boi
Copy link
Member

Thomas-Boi commented Jan 14, 2023

I don't think we ever saw the problem again but I'm not sure. I can't really remember sorry.
If the action is working fine, then that means the problem is no longer present and this can be closed.

@Snailedlt
Copy link
Collaborator

Okey, no worries 😊

@Panquesito7
Copy link
Member

Well, I haven't seen this issue happening anymore.
Should we close it or keep it open just in case?

@Snailedlt
Copy link
Collaborator

Let's close it. We can re-open if it happens again :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Use this label for pointing out bugs
Projects
None yet
Development

No branches or pull requests

4 participants