This repository has been archived by the owner on Sep 12, 2022. It is now read-only.
Problem: Duplicate user_allocation_source Events
#350
Comments
julianpistorius
added a commit
to julianpistorius/atmosphere
that referenced
this issue
Apr 30, 2017
… Events Solution: Added behave scenario to ensure that we don't create duplicate events when checking the TAS API multiple times.
6 tasks
julianpistorius
added a commit
to julianpistorius/atmosphere
that referenced
this issue
Apr 30, 2017
julianpistorius
added a commit
to julianpistorius/atmosphere
that referenced
this issue
Apr 30, 2017
steve-gregory
pushed a commit
that referenced
this issue
May 1, 2017
* Problem : Duplicate user_allocation_source Events * Problem: Can't freeze time more than once Solution: If `context.freezer` already exists, set `context.freezer.time_to_freeze` to `context.frozen_current_time`. * Problem: No test for #350 - Duplicate `user_allocation_source` Events Solution: Added behave scenario to ensure that we don't create duplicate events when checking the TAS API multiple times. * Problem: No migration to remove existing duplicate events re #350 Solution: Added migration to remove duplicate events with name `user_allocation_source_created`. * Added an entry to the CHANGELOG.md file for #350 * Renamed the projects.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Duplicate user_allocation_source events were created every time update_snapshot periodic task ran
Fixed by: #351
The text was updated successfully, but these errors were encountered: