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

Set IncludeEmptyEntriesInMessagePayload capability to true by default #2701

Merged
merged 3 commits into from
Sep 13, 2024

Conversation

liliankasem
Copy link
Member

@liliankasem liliankasem commented Sep 10, 2024

Issue describing the changes in this PR

resolves #1096

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • I have added all required tests (Unit tests, E2E tests)

Additional information

This makes a change so that the worker will by default send the IncludeEmptyEntriesInPayload capability to the host. This means that empty entries will always be included in the message payload. This was initially created as a flag to avoid breaking users but there is no reason not to make this the permanent behaviour now as it's what would normally be expected.

Original bug: #876

@liliankasem liliankasem force-pushed the liliankasem/1096/always-send-empty-entries branch 2 times, most recently from 6216a84 to 7b57069 Compare September 11, 2024 16:43
@liliankasem liliankasem requested a review from kshyju September 11, 2024 18:50
@liliankasem liliankasem force-pushed the liliankasem/1096/always-send-empty-entries branch from 7b57069 to 13a9990 Compare September 12, 2024 20:37
@liliankasem liliankasem changed the title IncludeEmptyEntriesInMessagePayload capability is always enabled Set IncludeEmptyEntriesInMessagePayload capability is true by default Sep 12, 2024
@liliankasem liliankasem changed the title Set IncludeEmptyEntriesInMessagePayload capability is true by default Set IncludeEmptyEntriesInMessagePayload capability to true by default Sep 12, 2024
Copy link
Member

@kshyju kshyju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's also capture this change in the release notes.

@liliankasem liliankasem merged commit 06574fc into feature/2.x Sep 13, 2024
27 checks passed
@liliankasem liliankasem deleted the liliankasem/1096/always-send-empty-entries branch September 13, 2024 17:26
fabiocav pushed a commit that referenced this pull request Oct 11, 2024
…#2701)

* Set IncludeEmptyEntriesInMessagePayload to true by default

* Update release notes
brettsam pushed a commit that referenced this pull request Oct 21, 2024
…#2701)

* Set IncludeEmptyEntriesInMessagePayload to true by default

* Update release notes
fabiocav pushed a commit that referenced this pull request Oct 21, 2024
…#2701)

* Set IncludeEmptyEntriesInMessagePayload to true by default

* Update release notes
fabiocav pushed a commit that referenced this pull request Oct 21, 2024
…#2701)

* Set IncludeEmptyEntriesInMessagePayload to true by default

* Update release notes
fabiocav pushed a commit that referenced this pull request Nov 11, 2024
…#2701)

* Set IncludeEmptyEntriesInMessagePayload to true by default

* Update release notes
fabiocav pushed a commit that referenced this pull request Nov 13, 2024
…#2701)

* Set IncludeEmptyEntriesInMessagePayload to true by default

* Update release notes
fabiocav pushed a commit that referenced this pull request Nov 13, 2024
…#2701)

* Set IncludeEmptyEntriesInMessagePayload to true by default

* Update release notes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants