Commit: e97d4be296ee2dd35197b28aabb7487fc3061886 aims to resolve this. The CheckBalance
should possibly be refactored further maybe? Currently it not only loads the balance,but also the user…
could this fail if something else writes the temp value in the meantime?
It is unlikely that this would happen because there can only be one DB write operation to the temp value at a time …
This line of code is actually misplaced. The right flag would have been "flag flag_alias_set" but it is not being utilized or checked in the associated vis
file. The commit c2a0b05c84462067456…
there is no way to test this outside of live api right?
Yeah Correct.Currently the endpoints for the aliases assignment and resolution are only accessible in the staging environment.