Skip to content
This repository has been archived by the owner on Apr 5, 2024. It is now read-only.

Failed uploads fail to save as succeeded #107

Closed
eivindveg opened this issue Feb 25, 2016 · 6 comments
Closed

Failed uploads fail to save as succeeded #107

eivindveg opened this issue Feb 25, 2016 · 6 comments
Assignees
Labels
Milestone

Comments

@eivindveg
Copy link
Owner

HotSLogs recently had some maintenance resulting in a bunch of failed uploads. When the service came back up, the replays were uploaded successfully, but their local status is unchanged upon application restart. As they're removed from the list on retry, this indicates an issue with their persistence to the database.

@eivindveg eivindveg added the bug label Feb 25, 2016
@eivindveg eivindveg self-assigned this Feb 25, 2016
@zhedar
Copy link
Collaborator

zhedar commented Feb 26, 2016

So what could we do about that? We can't always check the whole DB for non-present uploads.
We would need some feedback from hotslogs with the timeframe of such an action, which probably isn't that easy and straightforward to implement for @barrett777 .

@barrett777
Copy link

I think there's some confusion here. HOTS Logs shouldn't ever give a false 'Success' message

If HOTS Logs is down (planned or unplanned), all replay uploads will return 'Maintenance.'

If you get a 'Maintenance' message, I think the best action would be to tell the user and close the program.

@zhedar
Copy link
Collaborator

zhedar commented Feb 26, 2016

I think what happened here was that you removed some games (for example with LI Ming at her release) and these games were not reuploaded after the removal, since they were already marked as uploaded.

@barrett777
Copy link

Ooh yeah. If I ever have to delete messages, I put a note on the home page, and usually give a time frame guiding users on what replays to reupload.

@eivindveg
Copy link
Owner Author

Will push a test verifying this behaviour on the Spring branch. I've also gotten a mislocation of a Windows folder that @barrett777's app couldn't handle as well. Once these two are solved and backed with tests, we might need to release 2.0.3, albeit without the tests, as they're part of the 2.1 branch.

@eivindveg eivindveg added this to the 2.0.3 milestone Mar 5, 2016
eivindveg added a commit that referenced this issue Mar 5, 2016
eivindveg added a commit that referenced this issue Mar 5, 2016
@eivindveg
Copy link
Owner Author

Got a working test for this with no major effort on the hotfix branch. However, the test behaviour is really wonky - there's really no wonder this is broken.

eivindveg added a commit that referenced this issue Mar 6, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants