Creates the error reported for a subscription bound to another topic.
The existing subscription name
The topic the service reports it is bound to
('(unknown)' when the service reported none)
The topic the caller subscribed to
ReadonlyboundThe topic the existing subscription is bound to, as the service reports it.
OptionalcauseReadonlyrequestedThe topic this subscribe call asked for.
OptionalstackReadonlysubscriptionThe subscription name that already exists.
StaticstackThe Error.stackTraceLimit property specifies the number of stack frames
collected by a stack trace (whether generated by new Error().stack or
Error.captureStackTrace(obj)).
The default value is 10 but may be set to any valid JavaScript number. Changes
will affect any stack trace captured after the value has been changed.
If set to a non-number value, or set to a negative number, stack traces will not capture any frames.
StaticcaptureCreates a .stack property on targetObject, which when accessed returns
a string representing the location in the code at which
Error.captureStackTrace() was called.
const myObject = {};
Error.captureStackTrace(myObject);
myObject.stack; // Similar to `new Error().stack`
The first line of the trace will be prefixed with
${myObject.name}: ${myObject.message}.
The optional constructorOpt argument accepts a function. If given, all frames
above constructorOpt, including constructorOpt, will be omitted from the
generated stack trace.
The constructorOpt argument is useful for hiding implementation
details of error generation from the user. For instance:
function a() {
b();
}
function b() {
c();
}
function c() {
// Create an error without stack trace to avoid calculating the stack trace twice.
const { stackTraceLimit } = Error;
Error.stackTraceLimit = 0;
const error = new Error();
Error.stackTraceLimit = stackTraceLimit;
// Capture the stack trace above function b
Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace
throw error;
}
a();
OptionalconstructorOpt: FunctionStaticprepare
Thrown when a GCP Pub/Sub subscription the broker would attach to already exists but is bound to a DIFFERENT topic (M101b, V8-2).
Pub/Sub subscription names are project-global. Before this check the broker swallowed
ALREADY_EXISTSand attached to whatever topic the existing subscription was bound to, so a second topic's handler silently consumed the first topic's messages. The broker now reads the existing subscription's topic and refuses a mismatch.Remedies: pass a distinct
SubscribeOptions.queuefor this topic, or delete the existing subscription.Since
0.9.0