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
When using FireFly with multiple namespaces, it seems that events of type "blockchain invoke succeeded" and "contract deploy succeeded" are always received multiple times. If I have 7 namespaces, the namespace that triggered the invoke/deploy receives the success event 7 times. Other namespaces don't receive the event at all (which is expected, as it should only be sent to the namespace that triggered it).
What did you expect to happen?
I would expect only one copy of the "blockchain invoke succeeded" or "contract deploy succeeded" event to be delivered back to the namespace that triggered the request.
How can we reproduce it (as minimally and precisely as possible)?
Create multiple namespaces and either deploy a contract or invoke a contract.
Anything else we need to know?
No response
OS version
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
The text was updated successfully, but these errors were encountered:
What happened?
When using FireFly with multiple namespaces, it seems that events of type "blockchain invoke succeeded" and "contract deploy succeeded" are always received multiple times. If I have 7 namespaces, the namespace that triggered the invoke/deploy receives the success event 7 times. Other namespaces don't receive the event at all (which is expected, as it should only be sent to the namespace that triggered it).
What did you expect to happen?
I would expect only one copy of the "blockchain invoke succeeded" or "contract deploy succeeded" event to be delivered back to the namespace that triggered the request.
How can we reproduce it (as minimally and precisely as possible)?
Create multiple namespaces and either deploy a contract or invoke a contract.
Anything else we need to know?
No response
OS version
The text was updated successfully, but these errors were encountered: