Turbo Operations

goldsky-io/goldsky-agent/skills/turbo-operations

作者 goldsky-ioaa52f88312de无许可证12 个星标收录于 2026年10月9日更新于 2026年10月9日仓库今天更新

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. Triggers on: 'how do I pause/restart/delete', 'will deleting lose my data', 'what does this error mean', 'inspect TUI shortcuts'. For interactive diagnosis of a broken pipeline, use /turbo-doctor.

包含脚本DevOps & Cloud
AI 生成的概览

Turbo 管道生命周期命令、监控、检查点与常见错误模式的参考手册。

功能
该技能是操作 Turbo 管道的查询参考。它记录了管道状态、流式与作业模式的生命周期差异、暂停、恢复、重启和删除等生命周期命令、检查点行为,以及包括 inspect 和 logs 在内的监控命令。它还提供错误模式表和一个辅助脚本,用于分析管道日志中的常见错误并给出发现与建议。
适用场景
当你需要查询如何暂停、恢复、重启或删除 Turbo 管道,了解删除是否会丢失数据,解读管道错误信息,或查找 inspect 与 TUI 快捷键时使用。它是参考手册,而非交互式诊断工具。
运行要求
需要 Goldsky CLI 来执行文档中的命令,并需要访问 Turbo 项目。它附带可执行 shell 脚本 scripts/analyze-logs.sh 和 JSON 错误模式数据文件;运行脚本需要 shell 环境和管道日志访问权限。

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-pipelinegoldsky 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

来源与署名

来源:goldsky-io/goldsky-agent位于skills/turbo-operations提交aa52f88

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架