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
If this function call returns an error (I accidentally added a newline character to the end of the escalation policy id when called from GetEscalationPolicy), the call in the following line may result in a crash as req.Header may be nil.
However, if nil would be returned in case of an error to GetEscalationPolicy, thisdefer results in a crash as res.Body will be nil as well.
Expected behaviour
Erroneous input shouldn't result in a crash but the error being returned to the user.
The text was updated successfully, but these errors were encountered:
Bug description
If this function call returns an error (I accidentally added a newline character to the end of the escalation policy id when called from GetEscalationPolicy), the call in the following line may result in a crash as
req.Header
may benil
.However, if
nil
would be returned in case of an error to GetEscalationPolicy, thisdefer
results in a crash asres.Body
will be nil as well.Expected behaviour
Erroneous input shouldn't result in a crash but the error being returned to the user.
The text was updated successfully, but these errors were encountered: