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 has been archived by the owner on May 3, 2023. It is now read-only.
If registering fails or if dumping fails because no trace can be found, traceloop should return HTTP error codes so that clients can react on errors (e.g., curl -f).
Currently it's always a 200 OK response even if dumping fails because there is no trace (prog with name "MYNAME" not found).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If registering fails or if dumping fails because no trace can be found, traceloop should return HTTP error codes so that clients can react on errors (e.g.,
curl -f
).Currently it's always a 200 OK response even if dumping fails because there is no trace (
prog with name "MYNAME" not found
).The text was updated successfully, but these errors were encountered: