Skip to content
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

bug: duplicate events received when using multiple namespaces #1644

Open
awrichar opened this issue Feb 25, 2025 · 1 comment
Open

bug: duplicate events received when using multiple namespaces #1644

awrichar opened this issue Feb 25, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@awrichar
Copy link
Contributor

awrichar commented Feb 25, 2025

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).

Image

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
@awrichar awrichar added the bug Something isn't working label Feb 25, 2025
@EnriqueL8
Copy link
Contributor

Thanks @awrichar - this one is linked to #1614 and is related to reliable receipts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants