Don't reset upper bounds #135226
Merged
Don't reset upper bounds #135226
Conversation
This file contains hidden or 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
Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built.
rjernst
added
:Core/Infra/Core
elasticsearchmachine
added
Team:Core/Infra
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
jdconrad
approved these changes
Sep 22, 2025
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Sep 23, 2025
Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built.
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Sep 23, 2025
Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built.
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Sep 23, 2025
Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built.
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Sep 23, 2025
Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 23, 2025
Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 23, 2025
Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 23, 2025
Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 23, 2025
Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built.
pxsalehi
pushed a commit
to pxsalehi/elasticsearch
that referenced
this pull request
Sep 24, 2025
Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built.
pxsalehi
added a commit
to pxsalehi/elasticsearch
that referenced
this pull request
Sep 24, 2025
This reverts commit ddbac68.
DiannaHohensee
pushed a commit
that referenced
this pull request
Sep 24, 2025
* Revert "Move individual stats fields to AsyncRefresh (#135052)" This reverts commit 2b0153b. * Revert "Track shardStarted events for simulation in DesiredBalanceComputer (#133630)" This reverts commit f248596. * [CI] Update transport version definitions * Revert "[CI] Update transport version definitions" This reverts commit 90f38b0. * Don't reset upper bounds (#135226) Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built. * Revert "Don't reset upper bounds (#135226)" This reverts commit ddbac68. --------- Co-authored-by: elasticsearchmachine <[email protected]> Co-authored-by: Ryan Ernst <[email protected]>
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.
Transport version upper bounds are currently set to their values from upstream main whenever no new definition is detected. However, this is like a partial merge of upstream, and produces broken state files. This commit temporarily comments out resetting until a more robust solution is built.