deepseek-ai/deepseek-harness · error · Error
typert-protocol: Remote method "${method}" has conflicting i
Error message
typert-protocol: Remote method "${method}" has conflicting invocation markers What it means
Error "typert-protocol: Remote method "${method}" has conflicting invocation markers" thrown in deepseek-ai/deepseek-harness.
Source
Thrown at packages/typert/protocol/src/index.ts:266
function mark(
prototype: object,
method: string,
invocation: RemoteInvocationMarker,
exportName?: string,
): void {
let table = markers.get(prototype)
if (table === undefined) {
table = new Map()
markers.set(prototype, table)
}
const marker: StoredRemoteMethodMarker = {
...(exportName === undefined || exportName === method ? {} : { exportName }),
invocation: Object.freeze(invocation),
}
const current = table.get(method)
if (current !== undefined) {
if (current.exportName === marker.exportName && sameInvocation(current.invocation, invocation)) return
throw new Error(`typert-protocol: Remote method "${method}" has conflicting invocation markers`)
}
table.set(method, Object.freeze(marker))
}
function sameInvocation(left: RemoteInvocationMarker, right: RemoteInvocationMarker): boolean {
return left.kind === right.kind
&& (left.kind === 'direct' || (right.kind === 'context' && left.context === right.context))
}
function validateName(subject: string, value: string): void {
if (!isTypertRemoteSegment(value)) {
throw new TypeError(`typert-protocol: ${subject} must contain only RPC endpoint segment characters`)
}
}
View on GitHub (pinned to b150a551b8)
Solutions
- Remove the duplicate Remote markers so the method carries exactly one invocation marker.
When it happens
Trigger: Thrown at packages/typert/protocol/src/index.ts:266 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of deepseek-ai/deepseek-harness@b150a551b8 (2026-08-24).
Data as JSON: /api/errors/87c2448c50d45b6d.
Report an issue: GitHub.