Jan Brennenstuhl
Jan Brennenstuhl
### Email Provider web.de ### What happened? According to the docs `It might happen on rare occasions that the email provider doesn't allow real-time verification of emails. In this case,...
### Email Provider mailbox.org ### What happened? According to the docs `It might happen on rare occasions that the email provider doesn't allow real-time verification of emails. In this case,...
I would like to be able to configure timeouts on a per request basis similar to what OkHttp calls `Call Timeout` ([link](https://square.github.io/okhttp/4.x/okhttp/okhttp3/-ok-http-client/-builder/call-timeout/)). ## Detailed Description My current understanding is, that...
The current OAuth2-related code in `oauth.py` expects a [scope parameter](https://github.com/zalando/PGObserver/blob/master/frontend/src/oauth.py#L43) to be present in the authorization response. Otherwise it won't identify the authorization response as such. This is not in...
I am currently in the mood of spreading some love and some experience with setting up multi-region clusters. However, with Planb-Cassandra being currently dependent on Stups-tooling this becomes fairly difficult...
Currently when extending an existing ring, all user-data gets copied to new instances, including erase_on_boot set to false. this needs to mounting issues during taupage boot, as the new volumes...
## Description The Content Security Policy (CSP) prevents cross-site scripting attacks by blocking inline execution of scripts. However, the Doks-custom email shortcode leverages unsafe inline JS which renders the shortcode...
Make sure, also Leetspeak possibilities (e.g. using '3' instead of 'e') are recognized.
Currently, `@CircuitBreaker` always wraps failures into into an `ExhaustedRetryException`. This hides the true nature of the failure and makes it furthermore impossible to figure out whether the circuit breaker is...
I want to achieve following behaviour: Specific execution failures are first retried according to e.g. a `SimpleRetryPolicy`, then if the policy is exceeded the failure is recorded by the CircuitBreaker....