-
Notifications
You must be signed in to change notification settings - Fork 186
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
liliankasem
merged 3 commits into
feature/2.x
from
liliankasem/1096/always-send-empty-entries
Sep 13, 2024
Merged
Set IncludeEmptyEntriesInMessagePayload capability to true by default #2701
liliankasem
merged 3 commits into
feature/2.x
from
liliankasem/1096/always-send-empty-entries
Sep 13, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
liliankasem
force-pushed
the
liliankasem/1096/always-send-empty-entries
branch
2 times, most recently
from
September 11, 2024 16:43
6216a84
to
7b57069
Compare
kshyju
reviewed
Sep 12, 2024
liliankasem
force-pushed
the
liliankasem/1096/always-send-empty-entries
branch
from
September 12, 2024 20:37
7b57069
to
13a9990
Compare
liliankasem
changed the title
IncludeEmptyEntriesInMessagePayload capability is always enabled
Set IncludeEmptyEntriesInMessagePayload capability is true by default
Sep 12, 2024
liliankasem
changed the title
Set IncludeEmptyEntriesInMessagePayload capability is true by default
Set IncludeEmptyEntriesInMessagePayload capability to true by default
Sep 12, 2024
kshyju
approved these changes
Sep 13, 2024
There was a problem hiding this 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.
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue describing the changes in this PR
resolves #1096
Pull request checklist
release_notes.md
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