Comment 3 for bug 788590

I believe this is related to an issue we were discussing a while back on
duplication of users was happening in the datastore, when lookup calls were
made too quickly after an object was created. I don't think we ever found a
way around this and just made sure calls weren't being made too quickly on
our end.

The only way I can really see around this at the moment, is if you look up a
UGP by Game/User and the results list has more than 1 element, delete the
rest. This will only happen the second time a lookup is made after
sufficient time has passed since the creation.

On Thu, May 26, 2011 at 11:20 PM, Matt Giuca <email address hidden>wrote:

> OK so fixing bug #788592 fixes the lots of blank UGPs problem. But there
> is still a problem where if a game makes lots of requests as it is
> starting up, there will be lots of concurrent UGPs created for the same
> game/user pair. This is an extremely bad situation -- it shouldn't
> matter much in the long run because once a game is reloaded, it will
> always choose the same UGP and ignore the others, but it could introduce
> random bugs into games that are being played for the first time.
>
> ** Summary changed:
>
> - Lots of blank UserGameProfiles
> + Lots of UserGameProfiles created simultaneously
>
> ** Changed in: mugle
> Importance: Undecided => High
>
> ** Changed in: mugle
> Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to MUGLE.
> https://bugs.launchpad.net/bugs/788590
>
> Title:
> Lots of UserGameProfiles created simultaneously
>
> Status in Mars Programming Language:
> Invalid
> Status in Melbourne University Game-based Learning Environment:
> Triaged
>
> Bug description:
> For every "real" user game profile created, there are about 10
> completely blank ones, without even a user.
>