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

Don't upload replays twice #93

Merged
merged 3 commits into from
Dec 7, 2015
Merged

Don't upload replays twice #93

merged 3 commits into from
Dec 7, 2015

Conversation

zhedar
Copy link
Collaborator

@zhedar zhedar commented Dec 7, 2015

This is a workaround for issue #91.
I could isolate, why that happens:
Uploaded files didn't get persisted correctly on a first run. A second run was needed. So that meant, that every file had to be uploaded / parsed twice.

This was fixed by:

  • Writing all new replay files to the db and thus updating them again, when uploaded.
  • Creating a new ReplayFile entity, when the WatchHandler registers a new entry.
  • Refresh after an update or create (needed for the watchhandler)

- writes new replays to the db
- refreshes after an update
@zhedar zhedar changed the title Dont Don't upload replays twice Dec 7, 2015
@eivindveg
Copy link
Owner

This will do for 2.0.1. For next release we may want to invent an async unique entry queue system that the initial pass and the uploaderservice push to.

@zhedar
Copy link
Collaborator Author

zhedar commented Dec 7, 2015

I'm currently trying a more efficient version for the create all on startup, so maybe we get the best out of 2.0.1 though.

@zhedar zhedar added this to the 2.0.1 milestone Dec 7, 2015
@zhedar zhedar added the bug label Dec 7, 2015
eivindveg added a commit that referenced this pull request Dec 7, 2015
@eivindveg eivindveg merged commit 688b67d into hotfix/2.0.1 Dec 7, 2015
This was referenced Dec 7, 2015
@zhedar zhedar deleted the bugfix/upload-twice branch January 31, 2016 01:39
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants