microsoft / microsoft/aspire

CLI log file names are long. Do they need to be?

Open
#17,298 2 comments 0 reactions 0 assignees View on GitHub
area-cli triage:bot-seen
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

Current file name: `cli_20260519T074805_55c1dd46.log`
Or
Detached file name: `cli_20260519T074339775_detach-child_cc824ac77a9f4100a42bb5ec0c1bb223.log`

Can these be shorter? The long name can cause wrapping when displayed in UIs.

For example, just have date and then append number to avoid conflicts: `cli_20260519_1.log`, `cli_20260519_2.log`. It would require looking on disk to see what already exists, and we'd need to handle two CLIs launching at the same time.

Contributor guide

Open the contributing guide

Research direction

Start by locating the CLI code that generates the log filenames and inspect how attached and detached examples are produced. Compare the proposed date-and-counter naming with existing collision behavior, including simultaneous CLI launches; done means shorter names without conflicts and with coverage for both naming cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.