ExponentialBackOff | The ExponentialBackOff algorithm ported to Swift | Learning library

I am trying to call a method until list.size !=0 in a exponential fashion. How to achieve it? I tried with the below but no luck.

I'm trying to write RetryAdvice for Kafka handler; and fall back to saving to MongoDB as RecoveryCallback.

I have three fragments on an activity. On one I am loading a default view which is to be populated by data from Google Calendar but asynchronously -syncwholeCalendar(). While the app has loaded the default view, the app crashes when, Calendar data is being loaded and the user is on another fragment in the activity - saying the recyclerview cannot be null. Same is the issue, when I logout without waiting for the sync to complete... The issue is getEvents(), when the recyclerview is called to inflate it on sync... no issue when I am active on the fragment...

Is there a step I am missing or approach that I am taking incorrect?

Context:

The docs in "stateful retry" (https://docs.spring.io/spring-kafka/reference/html/#stateful-retry) and "seek to current" (https://docs.spring.io/spring-kafka/reference/html/#seek-to-current) make it sound like that as a user, I should migrate away from a RetryTemplate to using the BackOff function in SeekToCurrentErrorHandler.

I currently have a mix of RetryTemplate with an infinite loop for certain exceptions + SeekToCurrentErrorHandler with a fixed retry of 3 times that works for all other exceptions.

Now I am looking to replace this attempt with handler.setBackOffFunction((record, ex) -> { ... });, but I have been facing following issue

But I am not sure if this intended, I am misconfiguring or if this is a bug.

• Spring Boot 2.4.0
• spring-kafka 2.6.3

Question:

When I am using the SeekToCurrentErrorHandler with large intervals, the error-message for "hey your listener threw an exception" appear to log AFTER a interval was done. Is this intentional? My code is throwing an exception and a log-entry may appear much after.

Here we line 1 executed at 22:59:14. An exception is thrown shortly after, but appears in the logs 10s later at 22:59:24. When using ExponentialBackOff, that timeframe becames larger and larger.

I work mostly on offline machines and really want to begin to migrate from Python to Julia. Currently the biggest problem I face is how can I setup a package server on my own network that does not have access to the internet. I can copy files to the offline computer/network and want to be able to just cache a good percentage of the Julia Package Ecosystem and copy it to my network, so that I and others can install packages as needed.

I have experimented with PkgSever.jl by using the deployment docker-compose script they have, then just installing a long list of packages so that the PkgServer instance would cache everything. Next took the PkgServer machine offline and attempted to install packages from it. This worked well, however when I restarted the docker container the server was running in, everything fell apart quickly.

It seems that maybe the PkgServer needs to be able to talk to the Storage Server at least once before being able to serve packages. I tried setting: JULIA_PKG_SERVER_STORAGE_SERVERS from: "https://us-east.storage.juliahub.com,https://kr.storage.juliahub.com" to: "" but that failed miserably.

Can someone please point me in the right direction.

TIA

It looks like the PkgServer is actually trying to contact the Registry before it starts. I don't know enough about the registry stuff enough to know if there is a way to hack this to look locally or just ignore this..

I decided to make the transition from the Realtime database to Firestore however I'm running into some unexpected issues. It's very simple: the browser console logs out extremely unexpected results but the methods like exist still work as expected.

I want to use PyJulia to speed up some part of the code

Describe the bug

DeviceClient SetMethodDefaultHandlerAsync handler is not triggered on internet disconnection instantly. It triggers after 15 to 20 minutes. Below are the logs

IoT Hub connection status Changed Status: Connected Reason: Connection_Ok Time: 3:09:15 PM +02 IoT Hub connection status Changed Status: Disconnected_Retrying Reason: Communication_Error Time: 3:26:29 PM +02

I disconnected the internet at 3:10:00 PM +02 and communication error was thrown after 16 minutes. I have created a sample code which reproduces the issue

Steps to reproduce

The cloud.google.com/go/pubsub library recently released (in v1.5.0, cf. https://github.com/googleapis/google-cloud-go/releases/tag/pubsub%2Fv1.5.0) support for a new RetryPolicy server-side feature. The documentation (https://godoc.org/cloud.google.com/go/pubsub#RetryPolicy) for this currently reads

I've read the Wikipedia article, and although it describes exponential backoff in discrete time, I don't see how the article relates to the MinimumBackoff and MaximumBackoff parameters specifically. For guidance on this, I referred to the documentation for github.com/cenkalti/backoff, https://pkg.go.dev/github.com/cenkalti/backoff/v4?tab=doc#ExponentialBackOff. That library defines an ExponentialBackoff as