Fix timezone-dependent test failures in timestamp assertions #269
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
Co-authored-by: elpete <2583646+elpete@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update migrations and settings for consistent timestamp handling
Fix timezone-dependent test failures in timestamp assertions
Jan 28, 2026
elpete
approved these changes
Jan 28, 2026
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.
Tests asserting exact timestamp values (e.g.,
AttributeSpec#shows all the attributes in the component casing) fail on local installations with non-UTC timezones. Migration files inserted timestamps as string literals, which databases interpret according to session timezone settings.Changes
createDateTime()callsBefore:
After:
createDateTime()produces CFML datetime objects in the application timezone (UTC perApplication.cfc), ensuring consistent storage/retrieval regardless of server locale. Existing configuration (this.timezone = "UTC",serverTimezone=UTC,convertToTimezone = "UTC") already establishes UTC throughout the stack.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.