-
Notifications
You must be signed in to change notification settings - Fork 8.9k
bugfix: ensure environment is fully loaded before ConfigurationFactory initialization #7705
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
Open
WangzJi
wants to merge
5
commits into
apache:2.x
Choose a base branch
from
WangzJi:fix/7641
base: 2.x
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
5757b07
bugfix: ensure environment is fully loaded before ConfigurationFactor…
WangzJi 12b34ea
Merge branch '2.x' into fix/7641
WangzJi d356804
bugfix: ensure environment is fully loaded before ConfigurationFactor…
WangzJi 34e4cdb
Merge branch '2.x' into fix/7641
WangzJi 324e83f
Merge branch '2.x' into fix/7641
WangzJi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
Can you explain why this change was made?
What's the difference between setting the environment only when it's empty and setting it unconditionally (without checking for emptiness)?
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.
@funky-eyes Thanks for the review!
The key point: Line 64 triggers
ConfigurationFactorystatic initialization, which needs a complete environment.With the old null check:
EnvironmentPostProcessorsets environment (without application.properties in Spring Cloud)ApplicationContextInitializerskips updating (due to null check)ConfigurationFactorygets incomplete environment → can't readseata.config.typefrom application.propertiesUnconditional update ensures:
ApplicationContextInitializer's environment (which has all property sources loaded)EnvironmentPostProcessor'sThis explains why bootstrap.yml workaround works - it's loaded early enough.
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.
So, in Spring Cloud there can be multiple Environment instances, which is why the environment may be incomplete. Otherwise, as I understand it, the same instance shouldn't have this problem, right?
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.
In Spring Cloud, it's the same Environment instance throughout, but its PropertySources content evolves over time.
Timeline:
SeataClientEnvironmentPostProcessor runs (Order: HIGHEST_PRECEDENCE)
ConfigDataEnvironmentPostProcessor runs (Order: HIGHEST_PRECEDENCE + 10)