Hey, currently certain AWS errors cause a segfault instead of returning the err :(
For example, if your stream gets recreated outside of your app, your stored sharditerator is no longer valid and you'll get an AWS error when you try to use it.
EDIT: I've also changed listShards error handling - because we no longer panic, the "loop forever even if you error" behaviour of listShards is now quite problematic. I think it should return error - if client wants to loop and try again forever they are free to do so.
Hey, currently certain AWS errors cause a segfault instead of returning the err :(
For example, if your stream gets recreated outside of your app, your stored sharditerator is no longer valid and you'll get an AWS error when you try to use it.
EDIT: I've also changed listShards error handling - because we no longer panic, the "loop forever even if you error" behaviour of listShards is now quite problematic. I think it should return
error
- if client wants to loop and try again forever they are free to do so.