Skip to content

Fix missing line break on invalid library message#3084

Open
Psykii22 wants to merge 4 commits intoarduino:masterfrom
Psykii22:fix-3039-missing-newline
Open

Fix missing line break on invalid library message#3084
Psykii22 wants to merge 4 commits intoarduino:masterfrom
Psykii22:fix-3039-missing-newline

Conversation

@Psykii22
Copy link

@Psykii22 Psykii22 commented Jan 21, 2026

When multiple invalid libraries were found during verbose compilation, the warning messages were printed without newlines between them.

Added newline character after status.Message() in detector.go

Fixes #3039

Please check if the PR fulfills these requirements

See how to contribute

  • The PR has no duplicates (please search among the Pull Requests
    before creating one)
  • The PR follows
    our contributing guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • UPGRADING.md has been updated with a migration guide (for breaking changes)
  • configuration.schema.json updated if new parameters are added.

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

When multiple invalid libraries (e.g., empty folders without header files) are found during verbose compilation, all warning messages are printed on the same line without newlines:

loading library from .../EmptyLib1: invalid library: no header files foundloading library from .../EmptyLib2: invalid library: no header files found

Issue: #3039

What is the new behavior?

Each warning message is now printed on its own line:

loading library from .../EmptyLib1: invalid library: no header files found
loading library from .../EmptyLib2: invalid library: no header files found

Does this PR introduce a breaking change, and is titled accordingly?

No, this is a non-breaking bug fix. It only affects the formatting of verbose output.

Other information

  • The fix adds + "\n" after status.Message() in detector.go line 630
  • Verified locally by creating two empty library folders and running verbose compile
  • The CI failures appear to be unrelated to this change (board detection tests, YAML parsing issues)

When multiple invalid libraries were found during verbose compilation, the warning messages were printed without newlines between them.

Added newline character after status.Message() in detector.go

Fixes arduino#3039
@CLAassistant
Copy link

CLAassistant commented Jan 21, 2026

CLA assistant check
All committers have signed the CLA.

@per1234 per1234 added topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project topic: build-process Related to the sketch build process labels Jan 21, 2026
@Psykii22
Copy link
Author

Psykii22 commented Feb 8, 2026

@per1234 sir as I'm first time contributing in oss so how much time it will take to merge the pr if its merge-able, and if its not then why. If you can tell me it would be very helpful.
Thank you

@codecov
Copy link

codecov bot commented Feb 12, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.57%. Comparing base (65c01ec) to head (3b84947).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3084      +/-   ##
==========================================
+ Coverage   69.56%   69.57%   +0.01%     
==========================================
  Files         253      253              
  Lines       19280    19280              
==========================================
+ Hits        13412    13414       +2     
+ Misses       4629     4628       -1     
+ Partials     1239     1238       -1     
Flag Coverage Δ
unit 69.57% <100.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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

Labels

topic: build-process Related to the sketch build process topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Missing line break on "invalid library" message

3 participants