Skip to content

fix: spell malformed correctly in the config parse error - #6166

Open
yottanami wants to merge 1 commit into
Unitech:developmentfrom
yottanami:agent/282-malformed-typo
Open

yottanami wants to merge 1 commit into
Unitech:developmentfrom
yottanami:agent/282-malformed-typo

Conversation

@yottanami

Copy link
Copy Markdown
Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes (unit; e2e same as development locally)
Fixed tickets #1440
License MIT
Doc PR N/A, no documentation change

When a process file fails to parse, pm2 start and pm2 stop|restart|delete <file> print File <name> malformated. This changes both messages in lib/API.js to malformed, as noted in #1440.

Checked by running pm2 start and pm2 stop against an invalid JSON config before and after (the message now reads malformed). bash test/unit.sh passes; e2e scripts give the same results as development locally, and process-file/yaml-configuration.sh, which goes through this code path, passes.

Written with an AI coding assistant (Claude Code).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@CLAassistant

CLAassistant commented Oct 3, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@yottanami
yottanami marked this pull request as ready for review October 3, 2026 15:43
@yottanami

Copy link
Copy Markdown
Author

Signed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants