ワンクリックでManusで任意のスキルを実行

bullmq-queue-debug

スター0

フォーク0

更新日2026年1月9日 17:40

BullMQ job queue debugging for Volatio, redis-cli inspection patterns, checking stuck/failed/completed jobs, avoiding bun --eval hangs with queue connections. Use when jobs stuck, queue inspection needed, or debugging background workers.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

adam-s

adam-s/volatio

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

bullmq-queue-debug

When to Use

Jobs appear stuck or not processing
Need to inspect queue state (waiting, completed, failed)
Debugging background job workers
Checking if jobs are being added correctly

Golden Path: Check Queue via Redis Directly

Never use bun --eval with BullMQ imports - it hangs because Redis connections don't close.

# Check waiting jobs
docker exec volatio-redis-1 redis-cli LLEN bull:news.yahoo-sync:wait

# Check completed jobs
docker exec volatio-redis-1 redis-cli ZCARD bull:news.yahoo-sync:completed

# Check failed jobs
docker exec volatio-redis-1 redis-cli ZCARD bull:news.yahoo-sync:failed

Common Queue Names

Queue	Pattern
Yahoo News Sync	`bull:news.yahoo-sync:*`
Economic Calendar	`bull:calendar.sync:*`

Redis Queue Key Patterns

# List all BullMQ keys
docker exec volatio-redis-1 redis-cli KEYS 'bull:*'

# Check specific queue lengths
docker exec volatio-redis-1 redis-cli LLEN bull:<queue-name>:wait
docker exec volatio-redis-1 redis-cli ZCARD bull:<queue-name>:completed
docker exec volatio-redis-1 redis-cli ZCARD bull:<queue-name>:failed
docker exec volatio-redis-1 redis-cli ZCARD bull:<queue-name>:delayed

Inspecting Job Data

# Get waiting job IDs
docker exec volatio-redis-1 redis-cli LRANGE bull:news.yahoo-sync:wait 0 10

# Get job data (replace <job-id>)
docker exec volatio-redis-1 redis-cli HGETALL bull:news.yahoo-sync:<job-id>

If You MUST Use TypeScript to Check Queues

Create a dedicated script file that explicitly closes connections:

// packages/jobs/src/scripts/check-queue-status.ts
import { yahooNewsSyncQueue } from '../domains/news/yahoo-sync.job';

async function main() {
  const job = await yahooNewsSyncQueue.getJob('yahoo-sync-2025-01-15');
  console.log('Status:', await job?.getState());
  console.log('Result:', job?.returnvalue);
  
  // CRITICAL: Close queue connection explicitly
  await yahooNewsSyncQueue.close();
}

main();

Then run:

bun run --env-file ../../.env packages/jobs/src/scripts/check-queue-status.ts 2>&1

Don'ts

Never Use bun --eval with BullMQ

# ❌ BAD: Hangs indefinitely
bun --eval "
import { yahooNewsSyncQueue } from './src/domains/news/yahoo-sync.job';
const job = await yahooNewsSyncQueue.getJob('job-id');
console.log(job?.returnvalue);
process.exit(0);  // Still hangs!
"

Why it hangs:

BullMQ maintains persistent Redis connections
process.exit(0) doesn't cleanly close connections
Multiple connections from eval scripts conflict with workers

Clearing Stuck Queues

# Remove all waiting jobs
docker exec volatio-redis-1 redis-cli DEL bull:news.yahoo-sync:wait

# Remove all failed jobs
docker exec volatio-redis-1 redis-cli DEL bull:news.yahoo-sync:failed

# Clear entire queue (nuclear option)
docker exec volatio-redis-1 redis-cli KEYS 'bull:news.yahoo-sync:*' | xargs docker exec volatio-redis-1 redis-cli DEL

Verify Redis is Running

docker compose ps | grep redis
docker exec volatio-redis-1 redis-cli PING  # Should return PONG

このリポジトリの他の Skills

同じリポジトリ

market-data-integrity

adam-s/volatio

Market data integrity rules — gap filling, look-forward bias prevention, and stock split handling. Use when writing or reviewing code that loads prices, fills missing data, computes returns, backtests strategies, or makes trading decisions. Applies across Python, TypeScript, SQL, and TimescaleDB.

2026-02-120

debug-logs

adam-s/volatio

Analyze Volatio debug logs from /tmp/volatio-debug/. Use when the user asks to check debug logs, analyze problems, or diagnose simulation issues.

2026-02-070

systematic-testing

adam-s/volatio

Apply bottom-up systematic testing to a multi-layer system. Use when asked to test, debug, or verify a pipeline that spans multiple layers (e.g., Python worker → bridge → processor → API → UI).

2026-02-070

drizzle-migrations

adam-s/volatio

Drizzle Kit workflow for Volatio using idempotent migrations (generate + edit + migrate), never use push. Idempotent patterns prevent partial failure issues, enable safe re-runs, and work cleanly in CI. Use when schema changes, migration errors, or database sync issues occur.

2026-01-290

experiment-creation

adam-s/volatio

Template for creating Volatio research experiments with Optuna optimization and portfolio backtesting. Includes proper train/test splits, lookahead bias prevention, results saving, and validated patterns from Exp 051-053.

2026-01-200

lookahead-bias-checklist

adam-s/volatio

Financial research look-ahead bias verification for Volatio ML pipelines, mandatory baseline comparisons, timezone handling, feature leakage detection. Use when model accuracy seems too good or validating prediction experiments.

2026-01-140

name	bullmq-queue-debug
description	BullMQ job queue debugging for Volatio, redis-cli inspection patterns, checking stuck/failed/completed jobs, avoiding bun --eval hangs with queue connections. Use when jobs stuck, queue inspection needed, or debugging background workers.

bullmq-queue-debug

When to Use

Jobs appear stuck or not processing
Need to inspect queue state (waiting, completed, failed)
Debugging background job workers
Checking if jobs are being added correctly

Golden Path: Check Queue via Redis Directly

Never use bun --eval with BullMQ imports - it hangs because Redis connections don't close.

# Check waiting jobs
docker exec volatio-redis-1 redis-cli LLEN bull:news.yahoo-sync:wait

# Check completed jobs
docker exec volatio-redis-1 redis-cli ZCARD bull:news.yahoo-sync:completed

# Check failed jobs
docker exec volatio-redis-1 redis-cli ZCARD bull:news.yahoo-sync:failed

Common Queue Names

Queue	Pattern
Yahoo News Sync	`bull:news.yahoo-sync:*`
Economic Calendar	`bull:calendar.sync:*`

Redis Queue Key Patterns

# List all BullMQ keys
docker exec volatio-redis-1 redis-cli KEYS 'bull:*'

# Check specific queue lengths
docker exec volatio-redis-1 redis-cli LLEN bull:<queue-name>:wait
docker exec volatio-redis-1 redis-cli ZCARD bull:<queue-name>:completed
docker exec volatio-redis-1 redis-cli ZCARD bull:<queue-name>:failed
docker exec volatio-redis-1 redis-cli ZCARD bull:<queue-name>:delayed

Inspecting Job Data

# Get waiting job IDs
docker exec volatio-redis-1 redis-cli LRANGE bull:news.yahoo-sync:wait 0 10

# Get job data (replace <job-id>)
docker exec volatio-redis-1 redis-cli HGETALL bull:news.yahoo-sync:<job-id>

If You MUST Use TypeScript to Check Queues

Create a dedicated script file that explicitly closes connections:

// packages/jobs/src/scripts/check-queue-status.ts
import { yahooNewsSyncQueue } from '../domains/news/yahoo-sync.job';

async function main() {
  const job = await yahooNewsSyncQueue.getJob('yahoo-sync-2025-01-15');
  console.log('Status:', await job?.getState());
  console.log('Result:', job?.returnvalue);
  
  // CRITICAL: Close queue connection explicitly
  await yahooNewsSyncQueue.close();
}

main();

Then run:

bun run --env-file ../../.env packages/jobs/src/scripts/check-queue-status.ts 2>&1

Don'ts

Never Use bun --eval with BullMQ

# ❌ BAD: Hangs indefinitely
bun --eval "
import { yahooNewsSyncQueue } from './src/domains/news/yahoo-sync.job';
const job = await yahooNewsSyncQueue.getJob('job-id');
console.log(job?.returnvalue);
process.exit(0);  // Still hangs!
"

Why it hangs:

BullMQ maintains persistent Redis connections
process.exit(0) doesn't cleanly close connections
Multiple connections from eval scripts conflict with workers

Clearing Stuck Queues

# Remove all waiting jobs
docker exec volatio-redis-1 redis-cli DEL bull:news.yahoo-sync:wait

# Remove all failed jobs
docker exec volatio-redis-1 redis-cli DEL bull:news.yahoo-sync:failed

# Clear entire queue (nuclear option)
docker exec volatio-redis-1 redis-cli KEYS 'bull:news.yahoo-sync:*' | xargs docker exec volatio-redis-1 redis-cli DEL

Verify Redis is Running

docker compose ps | grep redis
docker exec volatio-redis-1 redis-cli PING  # Should return PONG