ruvnet/ruflo · error

[GUPP] Pull not implemented - stub adapter

Error message

[GUPP] Pull not implemented - stub adapter

What it means

Stub notice in GuppAdapterStub.pull(): the adapter is enabled and configured but pull was never implemented, so it warns and returns an empty bead list. Callers silently receive no data — this is a placeholder, not a real sync.

Source

Thrown at v3/plugins/gastown-bridge/src/index.ts:391

class GuppAdapterStub implements IGuppAdapter {
  private enabled: boolean;
  private endpoint?: string;

  constructor(config?: GasTownBridgeConfig['gupp']) {
    this.enabled = config?.enabled ?? false;
    this.endpoint = config?.endpoint;
  }

  isAvailable(): boolean {
    return this.enabled && !!this.endpoint;
  }

  async pull(_options?: { rig?: string; since?: Date }): Promise<Bead[]> {
    if (!this.isAvailable()) {
      return [];
    }
    // Stub: Would connect to GUPP endpoint
    console.warn('[GUPP] Pull not implemented - stub adapter');
    return [];
  }

  async push(_beads: Bead[]): Promise<{ pushed: number; errors: string[] }> {
    if (!this.isAvailable()) {
      return { pushed: 0, errors: ['GUPP not configured'] };
    }
    // Stub: Would connect to GUPP endpoint
    console.warn('[GUPP] Push not implemented - stub adapter');
    return { pushed: 0, errors: ['Not implemented'] };
  }

  async sync(): Promise<{ pulled: number; pushed: number; conflicts: string[] }> {
    if (!this.isAvailable()) {
      return { pulled: 0, pushed: 0, conflicts: [] };
    }
    // Stub: Would connect to GUPP endpoint
    console.warn('[GUPP] Sync not implemented - stub adapter');

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Implement the pull operation in the gupp adapter, or route pull through the real backend instead of the stub.
2. Guard callers so pull is only invoked when a supporting adapter is configured.
3. Return a clear unsupported-operation result to callers rather than only logging.

When it happens

Trigger: Caller invokes pull() on the GUPP stub adapter before the real pull implementation lands; operation is a logged no-op so dependent flows do not hard-fail.

Common situations: See trigger scenarios.

AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18). Data as JSON: /api/errors/4586b1345b630df7. Report an issue: GitHub.