Serial Monitor auto reconnects after build failure.

[Llaves]

If the serial monitor was active when the build/upload command is invoked, the monitor is restored when the operation is complete, even if it failed. This occurs at arduino.ts line 722 (I think). The problem is that this immediately hides the build output window and the user may not notice that the build failed, no upload occurred, and they are still running the result of the previous successful upload and left wondering why the new code had no effect.

This conflicts to some degree with issues 1060 and 1061. 1060 points out that if you don't restore the monitor in this case, then the next successful compile will not open the monitor as the recorded state at the start of the compile. This would require some sort of persistent state var rather than just testing to see if the monitor is open at the invocation of the compile. 1061 seems to want the serial monitor to remain open and connected to the device in the event of a failed compile, though I don't understand what the use case for that would be.

[StefanKellerAC]

Yes, that would be fine!
An acoustic signal would be fine for me:
#1518 (comment)

[gcampbell-msft]

@Llaves We have recently updated the Arduino extension to depend on a new standalone Serial Monitor extension, please upgrade your arduino extension and try out this new feature!

Let us know if it solves your issue or if the issue still persists!

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 30 days. To reactivate the issue, simply post a comment with the requested information to help us diagnose this issue. If this issue remains inactive for another 7 days, it will be automatically closed.

[github-actions]

This issue has been automatically closed due to inactivity. If you are still experiencing problems, please open a new issue.