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
{{ message }}
This repository was archived by the owner on Nov 19, 2023. It is now read-only.
I then attempt to delete the poison via DELETE /servers/882/routes/20e/poisons and get back a 204 No Content, but the poison is still present.
I also experience the same problem when I try to delete the specific poison, both via DELETE /servers/882/routes/20e/poisons/latency and DELETE /servers/882/routes/20e/poisons/latency:outgoing; I get a 204 No Content, but the poison is still there.
Note that I can delete any incoming poisons; the problem is exclusive to outgoing ones.
I'm experiencing that I'm unable to delete outgoing poisons after adding them via the HTTP API.
I added an outgoing
latencypoison to a route via the HTTP API, resulting in the call toGET /servers/882/routes/20e/poisonslooking like this:I then attempt to delete the poison via
DELETE /servers/882/routes/20e/poisonsand get back a 204 No Content, but the poison is still present.I also experience the same problem when I try to delete the specific poison, both via
DELETE /servers/882/routes/20e/poisons/latencyandDELETE /servers/882/routes/20e/poisons/latency:outgoing; I get a 204 No Content, but the poison is still there.Note that I can delete any incoming poisons; the problem is exclusive to outgoing ones.