fix(gmail): use configured timezone for Date header (#472)#514
Closed
dinakars777 wants to merge 1 commit intoopenclaw:mainfrom
Closed
fix(gmail): use configured timezone for Date header (#472)#514dinakars777 wants to merge 1 commit intoopenclaw:mainfrom
dinakars777 wants to merge 1 commit intoopenclaw:mainfrom
Conversation
Fixes openclaw#472 Instead of directly invoking time.Now().Format() using the system timezone, we now fetch the globally configured timezone through getConfiguredTimezone, ensuring the Date header format properly aligns with explicit configuration and avoids the +0900 issue.
21a541e to
05e427c
Compare
Collaborator
|
Landed manually on I kept the intended fix: outbound RFC822 I also added regression coverage in Verified locally:
Thanks @dinakars777. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #472.
Instead of directly invoking
time.Now().Format()using the system's runtime timezone, we now properly fetch the globally configured timezone throughgetConfiguredTimezone. This ensures theDateheader correctly aligns with the application-wide explicit configuration and falls back totime.Localcorrectly if not set, avoiding the+0900timezone delivery misconfiguration.