[Pyamqp GA] Stress Testing Bugs

[l0lawrence]

• [ ] Potential Bug: failing to decode empty frames - which would be intermittent. That should be repro-able by polling an otherwise idle connection for a number of minutes. And we should definitely test that - I doubt the empty frame decode logic was ever actually tested.

• [ ] we received a SASL frame outside of the SASL negotiation loop, so it showed up in the main frame processing loop and was then ignored. Though this is just a log statement, so not sure how it would have caused issues itself. It also looks like the contents of the frame aren't valid with all those zeros.

  • EventHubError('index out of bounds on dimension 1\nindex out of bounds on dimension 1)
  • Look for instances of where memoryview could be throwing the above error
  • To repro: Catch an IndexError on decode and log the incoming frame

• [ ] Sync Websocket -- CPU ConsumerClient is 0, Memory ProducerClient is linearly increasing, logs do not show

  • FlowFrame(next_incoming_id=2, incoming_window=65535, next_outgoing_id=1, outgoing_window=65535, handle=3, delivery_count=0, link_credit=3000, available=None, drain=None, echo=None, properties=None) repeats

• [ ] self._shutdown bug with ValueError not allowing for iteration via retries

[azure-sdk]

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.50518394,Storage:0.23801424,Event Hubs:0.06323718'