CLI not using system time - displays incorrect dates for builds and versions

[ssfdre38]

Describe the bug

The GitHub Copilot CLI appears to be using incorrect dates for build timestamps and version information instead of using the system time. This results in displaying random or incorrect dates that don't match the actual system clock.

Affected version

0.0.337

Steps to reproduce the behavior

1. Run the copilot CLI
2. Observe the version information and build dates displayed
3. Compare with actual system time

Expected behavior

The CLI should use the system time for all timestamps, including:

• Build dates
• Version timestamps
• Any other time-related information displayed to users

This ensures consistency and accuracy in version tracking and debugging.

Additional context

This issue affects the ability to accurately track when builds were created and can cause confusion when debugging or reporting issues.

[RyanHecht]

Hi @ssfdre38 - Can you show an example of exact commands you're running so I can better understand your scenario?

Also, could you tell me what operating system and shell you're using?

[ssfdre38]

Sure. Look at https://github.com/ssfdre38/match-mania and it's a game that I've been having copilot-cli make for me. This was all last week. It keeps saying build date is January not October even after correcting it and telling it to look at system time

[RyanHecht]

Can you show me some screenshots from copilot that show the commands that Copilot is running, and their outputs that have the incorrect dates? Also, what operating system and shell are you running copilot from?

[ssfdre38]

date_test.txt

I posted a second comment that should have had this file on it and I'm using the latest build
Version 0.0.337 · Commit 905260d
Ubuntu 24.04 and standard shell and using termius on my phone and desktop

[marcinkubica]

hmm, works on my machine 🤷 0.0.338 tho

2nd session

[ssfdre38]

That was after you told it to add it. This is raw output. Also I've told it numerous times to use system time for date and it kept reverting back even after saving chat history and telling it to load to memory after loading chat history