Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
2.3.3
-
None
-
1
Description
During testing of stellar-nebula, I noticed it seems like the SDK does not have any sort of rate-limiting to its attempts to connect to a node whenever the node causes an issue during the initial bootstrap. I believe it was a CMD_GET_ERROR_MAP returning STATUS_UNKNOWN_COMMAND which triggered it in my case.