Skip to content

Conversation

cmaglie
Copy link
Member

@cmaglie cmaglie commented Nov 11, 2022

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)

What kind of change does this PR introduce?

This is a tentative fix for #1970

What is the current behavior?

See #1970

What is the new behavior?

Should solve the nil pointer exception reported here: #1970 (comment)
BTW I found no way to reproduce it, so testing is needed.

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

No

Copy link
Contributor

@per1234 per1234 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also was unable to reproduce #1970 but feedback from users who tested unanimously indicates that it does provide the fix and also no regressions were reported:

Thanks for investigating the reports and preparing this fix Cristian!

@cmaglie cmaglie merged commit ca39297 into arduino:master Nov 14, 2022
@cmaglie cmaglie deleted the fix_concurrency_on_board_buildoptions branch November 14, 2022 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
criticality: high Of high impact priority: high Resolution is a high priority 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.

Sometimes it will not compile after switching development version
2 participants