You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @PfisterFactor thanks for reporting this issue. Just for my understanding, why it's important to have one atomic call for getting all the state? Are you trying to access the state values from a shared virtual object handler, or from a regular virtual object handler? Because if you're trying to access state from a regular virtual object handler, you cannot have two concurrent handlers trying to read/write state keys at the same time, so a loop like:
for key in ctx.stateKeys():
ctx.get(key)
Should be enough.
Also did you consider storing all your virtual object state as an individual key in the K/V store?
Atomic in the sense of just one round-trip to the state is necessary. Not in the multithreaded sense as like you said the exclusivity guarantees make this safe.
I suppose more just for convenience and ease of use, as it gets annoying to have to write a loop all the time instead of just .getAll.
Nesting the state in one top level field works but is just inconvenient
Currently if I want to get the entire key value state on a virtual object - I need to
.get
each key individually.It would be nice if a
.getAll()
function existed that returned the entire state in one atomic call.The text was updated successfully, but these errors were encountered: