Skip to content

chore(security): Improve logging for settings discovery failures #22

@mathe00

Description

@mathe00

Enhance the console log messages when settings discovery fails for a script to provide clearer feedback to the user about the potential cause and risks.

  • Review discoverScriptSettings and updateScriptSettingsCache in src/python_executor.ts.
  • When discovery fails (timeout, non-zero exit, parse error, missing marker - if implemented), ensure plugin.logWarn or plugin.logError messages clearly state:
    • The script path.
    • The specific reason for failure (timeout, exit code, parse error).
    • A warning about potential unintended code execution if the script didn't handle --get-settings-json.
    • A recommendation to use the define_settings/_handle_cli_args structure.
  • (Optional) Consider adding a non-persistent Notice after a manual "Refresh Definitions" if any scripts failed discovery.

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions