Skip to content

Conversation

@junghoon-vans
Copy link
Member

Summary

Fix gas report parser incorrectly matching commented stdout lines.

Problem

The gas report parser was matching lines like # stdout 'GAS USED: 123' because it only checked if the line contained the pattern, not if it started with it.

Changes

  • Add isValidStdoutLine function to validate lines start with known prefixes
  • Add STORAGE FEE: to defaultStdoutPrefixes for consistency
  • Use prefix validation in parseGasOutput to filter commented lines

The gas report parser was incorrectly matching commented lines like
"# stdout 'GAS USED: 123'" because it only checked if the line
contained the pattern, not if it started with it.

Changes:
- Add isValidStdoutLine function to check line starts with known prefix
- Add STORAGE FEE to defaultStdoutPrefixes for consistency
- Use isValidStdoutLine in parseGasOutput to filter commented lines
@junghoon-vans junghoon-vans self-assigned this Nov 28, 2025
@sonarqubecloud
Copy link

@notJoon notJoon merged commit d193177 into main Nov 28, 2025
85 of 87 checks passed
@notJoon notJoon deleted the fix-bless-parsing-commented-stdout branch November 28, 2025 09:46
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.

4 participants