Skip to content

Fix missing line break on invalid library message #3084

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Psykii22 wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix missing line break on invalid library message #3084

Psykii22 wants to merge 2 commits into from
+1 −1

Conversation

@Psykii22
Copy link

@Psykii22 Psykii22 commented Jan 21, 2026 •
edited
Loading

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)
@Psykii22
Fix missing line break on invalid library message
deafa57 
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 •
edited
Loading

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
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

3 participants

@Psykii22 @CLAassistant @per1234