Sheridan C Rawlins
Sheridan C Rawlins
Ok - so in reality my responses will have ~400 entries in them, but for testing I put 10; the default bufferSize is 128 so… well… it looked like it...
```scala val processor = PublishProcessor.create[IdVisitResponse]().toSerialized logger.info("making request {}", uri) SingleFutureCallback.execute(httpClient, req) .toFlowable .map[IdVisitResponse](IdVisitResponse.apply) .concatWith(processor) .concatMap { resp => val ret = Flowable.just(resp) resp.continuation match { case None => processor.onComplete() ret...
That "feedback loop" style kind of reminds me of a "goto" statement… not too shabby and more likely to be understandable by reviewers/maintainers; thanks for the idea. I still think...
buildx can't push to artifactory or other repos that don't have /oauth/token as their token endpoint
Hmm… well that's strange… I'll try to do some more debugging when I get a chance and wireshark if possible to see what's being sent returned… unless you have some...
Does #29 fix this?
> Thank you for this PR. I'd appreciate if you could provide a guide for manually testing this change. Well… I did put a unit test in there, which describes...
Hi - we started using the s3+dynamo solution for a few needs so this lost urgency for me. But... I thought I had added a test to show the use...
FWIW, I had to force push to make the license appear signed (I recall reading that commits made prior to adding a user address don't get tied to your account)...
> Thank you for this PR. I'd appreciate if you could provide a guide for manually testing this change. The test should now serve as the guide - I grew...
I'm not quite sure how to get Vercel to ✅ - if anyone can authorize that, please do, or if that's an ignorable check, please let me know.