-
Notifications
You must be signed in to change notification settings - Fork 17
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
Race issue in bitballs #329
Comments
One solution is to simply create the new team right away as the old one is being saved. I wonder if there's a better one. Essentially, the problem is that |
as an aside, I improperly changed createTeam to:
This did not produce any errors, as it was seemingly trapped by zones and not reported. |
we might also want to look at memory leaks |
|
* install dbus * removing debug testee * upgrades to steal 2, but dev.html shows nothing * Add the main boolean attribute * Use done-autorender * Use steal-tools@pre * minor steal changes * fixing some bugs related to #329
In bitballs, there's a
<select>
two-way bound toteam
-that-is-being-created'scolor
:There's a bug where
can-connect
is adding the newly created team to the list of teams.availableColors
changes, which causes a mutation,team
-that-is-being-created'scolor
This all happens before the
team
-that-is-being-created is replaced by a new Team:This "race" condition changes because of zones. Without zones, the mutation happens after the promise is resolved. With zones, the mutation fires before the zone fires.
The text was updated successfully, but these errors were encountered: