You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got a problem where I would like to apply the same circuit breaker to different instances of the same function (a function that cannot be created as a static method to solve this problem). As it stands, a new circuit breaker is created for each instance of this function.
It would be useful to cover this case and others by making the circuit breakers uniquely identified by name and thus able to be reused in the situation as above. Since all the circuit breakers are kept track of in CircuitBreakerMonitor, a solution could just include checking if a circuit breaker by that name already exists and, if it does, returning the existing circuit breaker.
The text was updated successfully, but these errors were encountered:
I want to have different methods and classes under the same name, so on other part of my app I can query that name and temporary disable some action.
I tried to use the same name on multiple methods decorators, but it didn't worked.
e.g some endpoint is down, my UI is server rendered so I can disable some parts of the UI based on CircuitBreakerMonitor.get('circuit_breaker_group_name')._state
I've got a problem where I would like to apply the same circuit breaker to different instances of the same function (a function that cannot be created as a static method to solve this problem). As it stands, a new circuit breaker is created for each instance of this function.
It would be useful to cover this case and others by making the circuit breakers uniquely identified by name and thus able to be reused in the situation as above. Since all the circuit breakers are kept track of in CircuitBreakerMonitor, a solution could just include checking if a circuit breaker by that name already exists and, if it does, returning the existing circuit breaker.
The text was updated successfully, but these errors were encountered: