I'm currently facing an issue where uploading proceeds via piping unless an error is encountered. While this behavior is expected in many command-line utilities, I'm concerned about how errors are being handled during the upload process. I want to ensure that if any error occurs—such as connection timeouts, incomplete data, or permission issues—it is detected immediately and the process halts appropriately. Right now, it seems errors may go unnoticed until the upload is complete. I would appreciate expert advice on implementing better error handling or logging mechanisms to catch and respond to such failures during a piped upload process.
Is this automating (a) the upload of the Arduino IDE to a PC or number of PCs or (b) the compilation and upload of a program to an Arduino based microcontroller or (c) something else ?
I have no clue as to what you are asking or what you are talking about. Put it in a simpler electronics language. I run water through piping, my bride sews it on skirts.
If you are talking about an Arduino, which one, when I upload it indicates an upload error when it happens. It has no clue if the code is good or bad.