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

Fixed a bug in the subscription cache #1716

Merged
merged 1 commit into from
Dec 4, 2024
Merged

Fixed a bug in the subscription cache #1716

merged 1 commit into from
Dec 4, 2024

Conversation

kzangeli
Copy link
Collaborator

@kzangeli kzangeli commented Dec 4, 2024

Partial fix for issue #1715
The issue also talks about a crash. I've seen no such thing, unfortunately :(

When the broker starts up and there are "old" subscriptions in the database, the subscription cache needs to be populated with those subscriptions.
This issue fixes a bug for the entity projection (the field 'notification::attributes' of a subscription payload).
The attributes were compacted when added to the subscription cache.
This makes zero sense and the bug has been fixed.

Amazing how a bug this important has survived for so long ...

So, when restarting the broker, as the projection attributes were erroneous (wrong names), all notifications are sent without any attributes (that is if projection attributes were part of the subscription).

Copy link

github-actions bot commented Dec 4, 2024

CLA Assistant Lite bot All contributors have signed the CLA ✍️

@kzangeli kzangeli merged commit 7ed7ff2 into develop Dec 4, 2024
9 checks passed
@kzangeli kzangeli deleted the issue/1715 branch December 4, 2024 17:54
@github-actions github-actions bot locked and limited conversation to collaborators Dec 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant