deepseek-ai/deepseek-harness · error · Error

typert: host-context "${key}" resolver is already configured

Error message

typert: host-context "${key}" resolver is already configured

What it means

Error "typert: host-context "${key}" resolver is already configured" thrown in deepseek-ai/deepseek-harness.

Source

Thrown at packages/typert/registry/src/service.ts:384

  private getHost(key: string): TypertHostContextProvider | undefined {
    const provider = this.hosts.get(key)?.provider
    if (provider === undefined) return undefined
    const resolver = this.hostResolvers.get(key)?.provider
    if (resolver === undefined) return provider
    return {
      wire: provider.wire,
      wireTypeSymbol: provider.wireTypeSymbol,
      resolve: id => resolver.resolve(id),
    }
  }

  private configureHost<Wire>(
    ctx: Context,
    key: string,
    resolver: TypertHostContextResolver<Wire>,
  ): TypertDisposer {
    validateSegment('Context key', key)
    if (this.hostResolvers.has(key)) throw new Error(`typert: host-context "${key}" resolver is already configured`)
    const entry: ProviderEntry<HostContextResolverEntry> = {
      provider: { resolve: async id => resolver(id as Wire) },
      owner: {},
    }
    const { hostResolvers, changes } = this
    return ctx.effect(function* () {
      hostResolvers.set(key, entry)
      changes.emit({ kind: 'host-context', key })
      yield () => {
        /* v8 ignore next -- duplicate configuration is rejected, so this effect remains the key's unique owner. */
        if (hostResolvers.get(key) !== entry) return
        hostResolvers.delete(key)
        changes.emit({ kind: 'host-context', key })
      }
    }, `typert.contexts.configureHost(${JSON.stringify(key)})`)
  }

  private registerHost<Wire>(ctx: Context, key: string, provider: TypertHostContextProvider<Wire>): TypertDisposer {

View on GitHub (pinned to b150a551b8)

Solutions

1. Configure the host-context resolver once per key.

When it happens

Trigger: Thrown at packages/typert/registry/src/service.ts:384 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/b9bc82966f9af364. Report an issue: GitHub.