-
Notifications
You must be signed in to change notification settings - Fork 7
[CLI] Make per-run log files unique by appending timestamp + open with mode="w" (fixes #984) #83
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
abhisheksingh-esp
wants to merge
1
commit into
project-chip:v2.15-cli-develop
Choose a base branch
from
abhisheksingh-esp:fix/984_unique_log_file_per_run
base: v2.15-cli-develop
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.
+13
−3
Open
Changes from all commits
Commits
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
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 we use the .isoformat() for the timestamp?
It will have the appropriate format (YYYY-MM-DDTHH:MM:SS.ffffff) and we would use a standard approach.
Let me know what you think and if that works.
Uh oh!
There was an error while loading. Please reload this page.
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.
Agreed — using .isoformat() makes sense here. It already provides the correct standardized format (YYYY-MM-DDTHH:MM:SS.ffffff) and keeps the implementation cleaner and more consistent.
Only one catch: isoformat() produces timestamps containing :, which makes the filename invalid on Windows (and some network/USB filesystems). This could create issues if the log file is copied to or opened on a Windows machine.
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.
Good catch about Windows systems.
Maybe that's not the best option.
Or maybe we could replace all
:for-from the isoformat's output.In that case, please feel free to continue with your solution if that would be a pain in Windows machines. Since my team is not using, sometimes those details may slip.
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.
Let me know which approach do you think would be better for all systems in this case
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.
Thanks. Let's go with isoformat(timespec="seconds").replace(":", "-") — gives us 2026-05-19T12-47-33. It keeps the ISO-style format we wanted, drops the noisy microseconds, and is safe on Windows, FAT/exFAT, and SMB shares (so users copying logs to a Windows machine for triage won't hit "invalid filename" errors).