[fix] Prevents long waiting times when connecting to incorrect or unresponsive addresses

[zhiyxu]

Currently, when making HTTP requests using requests.get, there is no timeout specified. This can lead to long waiting times (up to 2 minutes) during the protocol_probe process when connecting to incorrect or unresponsive addresses. This delay is due to the default TCP SYN-SENT timeout.

Add a default timeout parameter to all requests.get calls to allow for fast failure and better error handling in network operations.

[CLAassistant]

All committers have signed the CLA.

[zhiyxu]

@mihran113 @alberttorosyan @SGevorg Could you please help checking the pr, thanks in advance!

[mihran113]

Hey @zhiyxu! Thanks a lot for opening the PR. Everything looks good. Just one ask: could you please also add an entry to changelog?

[zhiyxu]

Hey @zhiyxu! Thanks a lot for opening the PR. Everything looks good. Just one ask: could you please also add an entry to changelog?

Thanks for your quick reply, changelog is updated.

BTW, what is the release cadence of the project, and when will the next version be released?

[mihran113]

Hey @zhiyxu! Thanks a lot for opening the PR. Everything looks good. Just one ask: could you please also add an entry to changelog?

Thanks for your quick reply, changelog is updated.

BTW, what is the release cadence of the project, and when will the next version be released?

We try to ship releases at least twice a month, but mainly depends on the features completed.
There's one more PR that I've asked for some changes and we'll release the next version, so tomorrow or (worst case scenario) Monday the new release will be shipped.

[zhiyxu]

Hey @zhiyxu! Thanks a lot for opening the PR. Everything looks good. Just one ask: could you please also add an entry to changelog?

Thanks for your quick reply, changelog is updated.
BTW, what is the release cadence of the project, and when will the next version be released?

We try to ship releases at least twice a month, but mainly depends on the features completed. There's one more PR that I've asked for some changes and we'll release the next version, so tomorrow or (worst case scenario) Monday the new release will be shipped.

There's still a failure in unit tests, could you please help to check and merge the commit, it would be great if this commit could be included in the next release.

[mihran113]

Hey @zhiyxu! Thanks a lot for opening the PR. Everything looks good. Just one ask: could you please also add an entry to changelog?

Thanks for your quick reply, changelog is updated.
BTW, what is the release cadence of the project, and when will the next version be released?

We try to ship releases at least twice a month, but mainly depends on the features completed. There's one more PR that I've asked for some changes and we'll release the next version, so tomorrow or (worst case scenario) Monday the new release will be shipped.

There's still a failure in unit tests, could you please help to check and merge the commit, it would be great if this commit could be included in the next release.

It's the performance tests, it's failing currently for all the commits, and none of your changes affecting those parts, so I'll merge the commit 🎉

[mihran113]

Hey @zhiyxu! The new version of aim has been shipped (3.23.0) which includes the changes made with this PR. 🎉