Improve --sysinfo command to show version data and env variables

[karthik282707]

corrected

---

Important

Enhances --sysinfo command to display version data and masked environment variables for improved debugging.

• Behavior:
  • Enhances --sysinfo command in main.py to display version data and environment variables.
  • Masks sensitive environment variables like keys, tokens, and passwords.
• Functions:
  • Adds mask_sensitive_value() in main.py to mask sensitive data.
  • Introduces get_version_info() in version_info.py to retrieve version and installation type.
• Misc:
  • Updates get_system_info() in main.py to include version and environment variables.

^{This description was created by for a97619a. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to a97619a in 1 minute and 43 seconds. Click for details.

• Reviewed 76 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 4 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. gpt_engineer/applications/cli/main.py:243

• Draft comment:
  mask_sensitive_value: Document edge-case behavior and consider more robust handling for short values.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. gpt_engineer/applications/cli/main.py:257

• Draft comment:
  Environment variable filtering: Using 'in' may capture unintended keys; consider stricter matching (e.g., startswith).
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% The comment has a valid point - using 'in' could match these prefixes anywhere in the string, not just at the start. For example, 'MY_OPENAI_KEY' would match even though it doesn't start with 'OPENAI_'. However, in this specific context, the impact is minimal since we're dealing with environment variables which typically follow standard naming conventions. The current code works fine for the intended use case of filtering relevant environment variables. While technically correct, this suggestion may be overly pedantic. The current code is working as intended for environment variables, and the risk of false matches is very low in practice. The theoretical improvement in precision doesn't justify the change given the real-world usage patterns of environment variable names. Delete the comment. While technically valid, the suggested change is not important enough to warrant a code change given the specific context of environment variable naming patterns.

3. gpt_engineer/core/version_info.py:16

• Draft comment:
  Development mode check: Directory traversal via file.parent.parent.parent may be fragile if structure changes.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

4. gpt_engineer/core/version_info.py:24

• Draft comment:
  Add a newline at the end of the file for POSIX compliance.
• Reason this comment was not posted:
  Confidence changes required: 10% <= threshold 50% None

Workflow ID: wflow_eJQeHPQsYHqMV4NC

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}