Error Checking/Reporting When Fetching F/W Signatures

[Martinski4GitHub]

• Improved error checking and reporting when downloading F/W image signatures from RMerlin's website. This allows users to see when the failure to download the checksum signatures may be due to their IP address currently being banned from accessing the website server [HTTP error code 403].

• Miscellaneous improvements.

Sample check and report of HTTP error:

[ExtremeFiretop]

Merged, approved all looking good!

[Martinski4GitHub]

@ExtremeFiretop,

Whenever you get a chance, please review and test the changes in this PR.
As I mentioned, the idea is to explicitly check and report error codes from the curl command, including HTTP error codes.
This way, users can become aware in cases when their IP address has been banned from accessing RMerlin's website.

Talk to you later this evening or tomorrow evening.

[ExtremeFiretop]

@ExtremeFiretop,

Whenever you get a chance, please review and test the changes in this PR. As I mentioned, the idea is to explicitly check and report error codes from the curl command, including HTTP error codes. This way, users can become aware in cases when their IP address has been banned from accessing RMerlin's website.

Talk to you later this evening or tomorrow evening.

I was doing it live as you were typing that clearly ! 🤣
I was on it as soon as you submitted it !

[Martinski4GitHub]

Merged, approved all looking good!

That was FAST!!!! LOL!!
I'm going offline right now to do some work (WFH) for my day job.

I'll be doing some more testing and validation later this evening, just in case I missed something.
Also, I'll run the latest code through the Linter tool.

Take care, bud!!

[Martinski4GitHub]

@ExtremeFiretop,

I ran a few more tests using the latest code in the develop branch, and so far it's working well.
The Linter tool didn't report any errors or new warnings - we have good "clean" code!!!

When/If you get feedback from the OP (@Razor221) confirming that the latest code addresses the issue they reported, feel free to release the next production version. At this point, I have nothing else to add or modify.

Over the weekend, I'll take a look at your YazFi PR.

Have a good one, bud!!

[ExtremeFiretop]

@ExtremeFiretop,

I ran a few more tests using the latest code in the develop branch, and so far it's working well. The Linter tool didn't report any errors or new warnings - we have good "clean" code!!!

When/If you get feedback from the OP (@Razor221) confirming that the latest code addresses the issue they reported, feel free to release the next production version. At this point, I have nothing else to add or modify.

Over the weekend, I'll take a look at your YazFi PR.

Have a good one, bud!!

I'm sending it out even without the formal agreement we discussed in SNBforums.
I'll just use your previous message as a form of agreement ;)

Thanks for your review buddy! I much prefer your wording on this