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

Give Twitch API values precedence over cached values #126

Open
Camtendo opened this issue Jun 2, 2015 · 2 comments
Open

Give Twitch API values precedence over cached values #126

Camtendo opened this issue Jun 2, 2015 · 2 comments
Assignees
Labels

Comments

@Camtendo
Copy link
Member

Camtendo commented Jun 2, 2015

There are instances where certain fields of polled Twitch data will not update because the cached values are already set. We need to default to always setting from values returned from the API.

@Camtendo Camtendo added the bug label Jun 2, 2015
@Camtendo Camtendo self-assigned this Jun 2, 2015
@dguenther
Copy link
Member

I'm not sure what this is referring to. It looks like we don't poll for channel info though, so if we set the game or status from another source, I'm not sure it'll update.

I'm working on a refactor of the Twitch socket that breaks out the Twitch and Redis calls into a separate file, so hopefully this will get fixed in the process. I'm not sure it'll be ready for SoDak, though.

@Camtendo
Copy link
Member Author

Camtendo commented Aug 6, 2015

Yeah, that sounds like what the issue is. The current workaround is to clear Twitch stuff, then reset it, so we're fine for Sodak

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants