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
Copy file name to clipboardExpand all lines: qos/noop/context.go
+6-14Lines changed: 6 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -11,14 +11,6 @@ import (
11
11
"github.com/buildwithgrove/path/protocol"
12
12
)
13
13
14
-
// clientRespMsgNoProtocolEndpoints is the error message sent to clients when
15
-
// the underlying protocol fails to register any endpoint responses with the NoOp QoS service.
16
-
// This can occur due to:
17
-
// - User error: invalid service ID in the request's HTTP header
18
-
// - Protocol error: selected endpoint failed to provide a valid response
19
-
// - System timeout: no endpoints responded within the allowed time window
20
-
constclientRespMsgNoProtocolEndpoints="NoOp QoS service error: No responses received from any service endpoints. Please verify your service ID and retry."
21
-
22
14
// requestContext implements all the functionality required by gateway.RequestQoSContext interface.
23
15
var_ gateway.RequestQoSContext=&requestContext{}
24
16
@@ -45,7 +37,7 @@ type requestContext struct {
45
37
46
38
// presetFailureResponse, if set, is used to return a preconstructed response to the user.
47
39
// This is used by the conductor of the requestContext instance, e.g. if reading the HTTP request's body fails.
48
-
presetFailureResponse*HTTPResponse
40
+
presetFailureResponsepathhttp.HTTPResponse
49
41
}
50
42
51
43
// GetServicePayload returns the payload to be sent to a service endpoint.
0 commit comments