goldsky-io/goldsky-agent

turbo-operations

Turbo pipeline operations reference — lifecycle commands (pause, resume, restart, delete), pipeline states, checkpoint behavior, streaming vs job-mode differences, CLI syntax for inspect/logs, TUI shortcuts, and error pattern lookup.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/goldsky-io/goldsky-agent --skill turbo-operations

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Turbo Pipeline Operations

Lifecycle commands, monitoring, and error reference for running Turbo pipelines. This is a lookup reference — for interactive troubleshooting of a broken pipeline, use /turbo-doctor. For building new pipelines, use /turbo-builder.

Pipeline States

StateDescription
runningPipeline is actively processing data
startingPipeline is initializing
pausedPipeline is paused (replicas set to 0)
stoppedPipeline is not running (manually stopped)
errorPipeline encountered an error
completedJob-mode pipeline finished processing range

Streaming vs Job Mode Lifecycle

OperationStreaming PipelineJob-Mode Pipeline (job: true)
ListShows as running/pausedShows as running/completed
PauseSupportedNot supported
ResumeSupportedNot supported
RestartSupportedNot supported — use delete + apply
DeleteSupportedSupported (auto-cleanup ~1hr after done)
ApplyUpdates in placeMust delete first, then re-apply

Job-Mode Pipeline Lifecycle

Job-mode pipelines (job: true) are one-time batch processes:

  1. Start — process data from start_at to end_block
  2. Run — process the bounded data range
  3. Complete — automatically stop when range is processed
  4. Auto-cleanup — ~1 hour after completion, automatically removed

Cannot pause, resume, or restart. Must delete before redeploying.

Lifecycle Commands

List Pipelines

bash
goldsky turbo list

Pause a Pipeline

Temporarily stop processing without deleting. Preserves all state for later resumption.

bash
goldsky turbo pause <pipeline-name>

Resume a Pipeline

Restore a paused pipeline. Can only resume a paused pipeline.

bash
goldsky turbo resume <pipeline-name>

Restart a Pipeline

Trigger a pod restart for a running or paused pipeline.

bash
goldsky turbo restart <pipeline-name>
# To clear all checkpoints and reprocess from the beginning:
goldsky turbo restart <pipeline-name> --clear-state

Delete a Pipeline

Permanently remove a pipeline. All checkpoints are lost. Data already written to sinks is preserved.

bash
goldsky turbo delete <pipeline-name>

Delete and Recreate (Fresh Start)

bash
goldsky turbo delete my-pipeline
goldsky turbo apply my-pipeline.yaml

Checkpoint Behavior

  • Deleting a pipeline removes its checkpoints permanently
  • Recreating with the same name starts fresh (no checkpoint recovery)
  • To preserve checkpoints, use apply to update instead of delete/recreate
  • Checkpoint state is tied to source names — renaming a source resets its checkpoint
  • Checkpoint state is tied to pipeline names — renaming a pipeline resets all checkpoints

Monitoring Commands

ActionCommand
List pipelinesgoldsky turbo list
View live datagoldsky turbo inspect <name> -p
Inspect specific nodegoldsky turbo inspect <name> -n <node> -p
View logsgoldsky turbo logs <name>
Follow logsgoldsky turbo logs <name> --follow
Logs with timestampsgoldsky turbo logs <name> --timestamps
Last N linesgoldsky turbo logs <name> --tail N
Logs since N seconds agogoldsky turbo logs <name> --since N

goldsky turbo inspect Flags

FlagShortDescription
--print-pPrint records to stdout
--topology-node-keys-nComma-separated node keys to filter (e.g. a transform name)
--buffer-size-bMax records to keep in buffer (default: 10000)

Always use -p. Always include it in every inspect command you suggest.

Log Analysis Script

Use the helper script to quickly analyze pipeline logs:

bash
./scripts/analyze-logs.sh <pipeline-name>
./scripts/analyze-logs.sh <pipeline-name> --tail 100

The script checks for common error patterns and reports findings with recommendations.

Common Error Patterns

Detailed error patterns and solutions are in `data/error-patterns.json`.
Error PatternLikely CauseFix
connection refusedDatabase unreachableCheck network/firewall settings
authentication failedWrong credentialsUpdate secret with correct credentials
secret not foundMissing secretCreate secret with goldsky secret create
SQL syntax errorInvalid transform SQLFix SQL in YAML and redeploy
duplicate keyPrimary key collisionEnsure unique primary key in transform
script transform errorTypeScript runtime failureCheck script logic, null handling, return types
dynamic_table errorBackend connection issueVerify dynamic table secret/table exists
WASM execution failedScript crash in sandboxDebug script — check for undefined access
handler timeoutExternal HTTP endpoint slowIncrease timeout_ms or fix handler endpoint

Script Transform Issues

IssueFix
undefined property accessAdd null checks: input.field ?? ''
Wrong return typeEnsure returned object matches schema exactly
Missing return fieldsAll schema fields must be present in returned object
invoke is not a functionEnsure script defines function invoke(data)
BigInt errorsUse BigInt() constructor, not direct number literals

Dynamic Table Issues

IssueFix
Table not foundCreate the table in PostgreSQL before deploying
No matches from checkVerify data exists in the backing table
Stale dataFor postgres backend, verify rows are actually there
Memory pressureLarge in_memory tables → switch to postgres backend

Troubleshooting Quick Reference

SymptomLikely CauseQuick Fix
No data flowingstart_at: latestWait for new data or use earliest
Auth failedWrong credentialsUpdate secret with correct password
Connection refusedNetwork/firewallCheck host, whitelist Goldsky IPs
Storage exceededNeon free tier (512MB)Upgrade plan or clear data
SQL errorBad transform syntaxValidate YAML first
Pipeline not foundName mismatchRun goldsky turbo list to check names
Permission deniedRole insufficientVerify Editor or Admin role in the project
pipeline already existsJob-mode staleDelete first, then re-apply
Cannot pause/resume jobJob-mode limitationJob pipelines don't support pause/resume
Cannot restart jobJob-mode limitationDelete + re-apply instead
Can't connect to inspectPipeline not runningCheck status with goldsky turbo list
Logs are emptyPipeline just startedWait for data or check start_at
TUI disconnectsPipeline interruptedAuto-reconnects within 30 min; check status

Related

  • `/turbo-doctor` — Interactive diagnostic skill for pipeline issues
  • `/turbo-builder` — Build and deploy new pipelines
  • `/turbo-pipelines` — YAML configuration and architecture reference

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
goldsky-io
Comunidad

auth-setup

Set up Goldsky CLI authentication and project configuration. Use this skill when the user needs to: install the goldsky CLI (what's the official install command?), run goldsky login (including when the browser opens but 'authentication failed'), run goldsky project list and see 'not logged in' or 'unauthorized', switch between Goldsky projects, check which project they're currently authenticated to, or fix 'unauthorized' errors when running goldsky turbo commands. Also use for 'walk me through s

Instalaciones / 1h
4
GitHub Stars
12
Actualizado
2 nov
goldsky-io
Comunidad

boost

Configure and troubleshoot Goldsky Boost, the free RPC caching CDN in front of a provider the user already pays for. Use for cutting RPC bills without migrating, connecting Alchemy/QuickNode/Infura upstreams, goldsky boost, edge.goldsky.com/boost, verification, cache hit rates, ethgetLogs forwarding, and x-cache / x-edge-billable / x-edge-source headers. Boost keeps the existing provider and forwards uncached requests. To replace a provider with Goldsky's managed RPC, use /edge. Pipeline, Subgra

Instalaciones / 1h
4
GitHub Stars
12
Actualizado
2 nov
goldsky-io
Comunidad

datasets

Use this skill when the user needs to look up or verify Goldsky blockchain dataset names, chain prefixes, dataset types, or versions. Triggers on questions like 'what\\'s the dataset name for X?', 'what prefix does Goldsky use for chain Y?', 'what version should I use for Z?', or 'what datasets are available for Solana/Stellar/Arbitrum/etc?'. Also use for chain-specific dataset questions (e.g., polygon vs matic prefix, stellarnet balance datasets, solana token transfer dataset names), and to ans

Instalaciones / 1h
4
GitHub Stars
12
Actualizado
2 nov
goldsky-io
Comunidad

edge

Configure and troubleshoot Goldsky Edge, Goldsky's managed EVM RPC endpoint service. Use for Edge RPC, Goldsky RPC endpoints, edge.goldsky.com, slow ethgetLogs, rate limits, hedged requests, flashblocks, HyperEVM system transactions, x402 pay-per-request RPC, pricing, the Edge dashboard, gsedge keys, rpc-edge, and errors -32005/-32012/-32014/-32015/-32016. Covers resilient low-latency EVM endpoints and provider comparisons. For self-hosted eRPC configuration, consult docs.erpc.cloud/llms.txt. To

Instalaciones / 1h
4
GitHub Stars
12
Actualizado
2 nov