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

Errors after recent outage #119

Open
kule opened this issue Jan 9, 2014 · 3 comments
Open

Errors after recent outage #119

kule opened this issue Jan 9, 2014 · 3 comments

Comments

@kule
Copy link

kule commented Jan 9, 2014

Not sure if this is something that needs to be looked into but my app stopped working after the last hn outage. It kept giving the Error Loading message even after quitting via the tasks list. I deleted and re-downloaded and it works correctly again now.

@newsyc
Copy link
Contributor

newsyc commented Jan 9, 2014

Unfortunately when Hacker News recovered from the outage, it re-used post
identifiers that news:yc had already cached. As the posts are now different
that can lead to a corrupted cache.

This also affected the official HNSearch.com as well as many other related
websites. In general, re-using IDs is not supposed to happen when
maintaining a website, and I'm surprised the operators of Hacker News
didn't fix the issue.

Sent from my iPhone

On Jan 9, 2014, at 4:52 AM, Luke pearce [email protected] wrote:

Not sure if this is something that needs to be looked into but my app
stopped working after the last hn outage. It kept giving the Error Loading
message even after quitting via the tasks list. I deleted and re-downloaded
and it works correctly again now.


Reply to this email directly or view it on
GitHubhttps://github.com//issues/119
.

@kule
Copy link
Author

kule commented Jan 9, 2014

Ah makes sense, thanks for the reply.

@shedd
Copy link

shedd commented Jan 10, 2014

Thanks for this - I was also having the same issue where the app seemed to be broken after the outage. Deleting the app and reinstalling it fixed the issue. Perhaps the app needs an automated cache clear after multiple failed attempts to load data?

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

No branches or pull requests

3 participants