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

Certain emotesets return error 500 when retreiving emote images #50

Closed
jjlucsy opened this issue Feb 3, 2020 · 8 comments
Closed

Certain emotesets return error 500 when retreiving emote images #50

jjlucsy opened this issue Feb 3, 2020 · 8 comments
Labels
product: v5 API endpoints in the "v5" namespace ticketed Has been given an internal tracking ticket

Comments

@jjlucsy
Copy link

jjlucsy commented Feb 3, 2020

The chat message USERSTATE will contain all the emotesets that a user has. I've found two sets that will produce an error 500 when trying to retrieve the emote images for them.

How to reproduce
curl -H "Accept: application/vnd.twitchtv.v5+json" -H "Client-ID: 046ape8hh5j3y3vx13ta1hdpliu4s2" -X GET "https://api.twitch.tv/kraken/chat/emoticon_images?emotesets=1115262924"
curl -H "Accept: application/vnd.twitchtv.v5+json" -H "Client-ID: 046ape8hh5j3y3vx13ta1hdpliu4s2" -X GET "https://api.twitch.tv/kraken/chat/emoticon_images?emotesets=1500636590"

@jjlucsy jjlucsy added the product: v5 API endpoints in the "v5" namespace label Feb 3, 2020
@jbulava
Copy link
Member

jbulava commented Feb 12, 2020

Ticketed internally as GQL-915. Investigating if this is a bug that needs further attention.

@jbulava jbulava added the ticketed Has been given an internal tracking ticket label Feb 12, 2020
@mccxiv
Copy link

mccxiv commented Mar 25, 2020

Another one for your investigation: 950319492

curl -X GET \
  'https://api.twitch.tv/kraken/chat/emoticon_images?emotesets=950319492' \
  -H 'Accept: application/vnd.twitchtv.v5+json' \
  -H 'Cache-Control: no-cache' \
  -H 'Client-ID: 1pr5dzvymq1unqa2xiavdkvslsn4ebe'
{
    "error": "Internal Server Error",
    "status": 500,
    "message": ""
}

@DaGaffer
Copy link

DaGaffer commented Apr 22, 2020

Linking more information from a thread I created today on the dev forums:

https://discuss.dev.twitch.tv/t/retrieving-emotesets-occasionally-fails-with-error-500-internal-server-error/25101/3

I am seeing EmoteSets (even EmoteSet 0) randomly not be delivered with the HTTP 500 error.

This appears to be because some of the servers are failing to deliver emote sets, rather than an issue with particular emotesets in general (unless I am seeing a different issue than the above of course).

The relevant bit from that thread:

When EmoteSets are successfully delivered, the emote sets are pre-cached on one of the two servers that are attempting to serve the request.

The unsuccessful responses are always MISS, MISS when it comes to being cached.

As a side note, I have not yet seen any seattle server which has the emotes cached.

Example of a success header:
GV_TwitchLog: EmoteSet response header: X-Served-By: cache-sea4480-SEA, cache-bur17534-BUR
GV_TwitchLog: EmoteSet response header: X-Cache: MISS, HIT

Example of a fail header:
GV_TwitchLog: EmoteSet response header: X-Served-By: cache-sea4480-SEA, cache-bur17561-BUR
GV_TwitchLog: EmoteSet response header: X-Cache: MISS, MISS

Full header (success):
GV_TwitchLog: EmoteSet response header: Connection: keep-alive
GV_TwitchLog: EmoteSet response header: Content-Length: 2719
GV_TwitchLog: EmoteSet response header: Content-Type: application/json; charset=utf-8
GV_TwitchLog: EmoteSet response header: Access-Control-Allow-Origin: *
GV_TwitchLog: EmoteSet response header: Cache-Control: no-cache, no-store, must-revalidate, private
GV_TwitchLog: EmoteSet response header: Content-Encoding: gzip
GV_TwitchLog: EmoteSet response header: Expires: 0
GV_TwitchLog: EmoteSet response header: Pragma: no-cache
GV_TwitchLog: EmoteSet response header: Timing-Allow-Origin: https://www.twitch.tv
GV_TwitchLog: EmoteSet response header: Date: Tue, 21 Apr 2020 20:32:15 GMT
GV_TwitchLog: EmoteSet response header: X-Served-By: cache-sea4480-SEA, cache-bur17534-BUR
GV_TwitchLog: EmoteSet response header: X-Cache: MISS, HIT
GV_TwitchLog: EmoteSet response header: X-Cache-Hits: 0, 1
GV_TwitchLog: EmoteSet response header: X-Timer: S1587501135.495488,VS0,VS0,VE1
GV_TwitchLog: EmoteSet response header: Vary: Accept-Encoding
GV_TwitchLog: EmoteSet response header: Strict-Transport-Security: max-age=300

Full Failure header:
GV_TwitchLog: EmoteSet response header: Connection: keep-alive
GV_TwitchLog: EmoteSet response header: Content-Type: application/json; charset=utf-8
GV_TwitchLog: EmoteSet response header: Access-Control-Allow-Origin: *
GV_TwitchLog: EmoteSet response header: Cache-Control: no-cache, no-store, must-revalidate, private
GV_TwitchLog: EmoteSet response header: Content-Encoding: gzip
GV_TwitchLog: EmoteSet response header: Expires: 0
GV_TwitchLog: EmoteSet response header: Pragma: no-cache
GV_TwitchLog: EmoteSet response header: Timing-Allow-Origin: https://www.twitch.tv
GV_TwitchLog: EmoteSet response header: Date: Tue, 21 Apr 2020 20:31:25 GMT
GV_TwitchLog: EmoteSet response header: X-Served-By: cache-sea4480-SEA, cache-bur17561-BUR
GV_TwitchLog: EmoteSet response header: X-Cache: MISS, MISS
GV_TwitchLog: EmoteSet response header: X-Cache-Hits: 0, 0
GV_TwitchLog: EmoteSet response header: X-Timer: S1587501086.909211,VS0,VS0,VE39
GV_TwitchLog: EmoteSet response header: Vary: Accept-Encoding
GV_TwitchLog: EmoteSet response header: Strict-Transport-Security: max-age=300
GV_TwitchLog: EmoteSet response header: transfer-encoding: chunked

For around 20 successes and 20 failures, this has held. FYI if useful.

@tduva
Copy link

tduva commented Apr 26, 2020

My users (and myself) are having this issue as well. In addition to some emotesets always causing error 500 (others posted examples above), it lately seems to be returning error 500 on and off for any request.

@remixer-dec
Copy link

I have 100% error rate in the last 4 days with emotesets=0

@DaGaffer
Copy link

@remixer-dec Same here.

@RAnders00
Copy link
Contributor

RAnders00 commented May 11, 2020

I think this issue is a bit more severe than "Investigating if this is a bug that needs further attention." if it affects emote set 0 (global emotes). I reckon a large number of integrations are relying on global emotes in some way.

@Xemdo
Copy link

Xemdo commented Jul 27, 2023

Closing due to the deprecation of the Kraken API as of February 2023.

@Xemdo Xemdo closed this as completed Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product: v5 API endpoints in the "v5" namespace ticketed Has been given an internal tracking ticket
Projects
None yet
Development

No branches or pull requests

8 participants