Fix misleading LogPoller logging
This was logging a critical error when any error other than an rpc error happened (eg networking issue, or context timeout) when batch_size was = 1. Should have only been logging at that level for rpc error "Limit Exceeded". Same issue for batch_size > 1, we should only be reducing the batch size if the error was specifically "Limit Exceeded", otherwise just retry again next time with the same size.
I see that you haven't updated any README files. Would it make sense to do so?
This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This got closed due to being stale, but someone noticed it again recently so I'll pick it back up again soon.
Quality Gate passed
Issues
0 New issues
0 Fixed issues
0 Accepted issues
Measures
0 Security Hotspots
54.8% Coverage on New Code
0.0% Duplication on New Code







