'error' 검색 결과

ソフトウェアにおける非正常状態（Error, Defect, Fault, Failure）の分類と定義を提供する。 JIS規格・JSTQB・Bertrand Meyer等の複数の標準に基づき、各概念の違いを明確化し、 適切なエラー設計・障害対策の判断を支援する。エラー設計、障害分析、コードレビュー、 テスト設計時に用語の混乱を防ぎ、正確な分類に基づく対処戦略の選択に使用。 対象言語: 言語非依存。 トリガー：「ErrorとFaultの違い」「DefectとBugの関係」「障害と故障の区別」 「エラーの分類」「Failureとは何か」「非正常状態の設計」「エラー用語の定義」 「エラーと欠陥の違い」「faultとfailureの違い」 といったエラー分類・用語定義関連リクエストで起動。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fix intermittent `{:no_translation, :unicode, :latin1}` crashes in Elixir escript daemons that use length-prefixed framed IPC on stdin/stdout. Use when: (1) daemon worker crashes only on some input files, usually ones with non-ASCII bytes (kanji, cyrillic, emoji); (2) error surfaces as `Protocol error` from daemon's error branch or as garbled frame-length bytes seen by the orchestrator/client side; (3) standalone one-shot mode works fine on the same input but multi-request daemon mode fails; (4) `IO.binread(:stdio, N)` returns `{:error, {:no_translation, :unicode, :latin1}}` despite the "bin" prefix suggesting it should be encoding-agnostic. Root cause is the escript default `:standard_io` encoding — it's `:unicode`, and `IO.binread` still routes through the io_server, which translates bytes to codepoints and errors when raw binary frames contain invalid UTF-8 sequences.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Error boundary patterns, fallback UI, reset/retry, react-error-boundary library, React 19 createRoot error hooks

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use @vercel/error to design, implement, migrate, audit, or review structured TypeScript errors. Trigger when a project uses or adopts the package, or when work involves its codes, fields, factories, HTTP APIs, telemetry, or terminal output. Use native Error for local failures that need no stable identity, recovery guidance, observability, or transport.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fix a specific bug or problem in a {{engine_name}} project. Supports two modes — immediate fix or plan-first. Without arguments executes existing .unikit/code/FIX_PLAN.md. Checks {{engine_name}} compilation, suggests test coverage, and creates self-improvement patches. Use when user says "fix bug", "debug this", "something is broken", "fix the tests", "fix the errors in the tests", "read the errors in the {{engine_name}} console logs and fix the problems", or pastes an error message or {{engine_name}} console log. Also trigger when user shares a NullReferenceException, MissingReferenceException, compilation error, or any {{engine_name}}-specific error.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Patterns for robust error handling across TypeScript, Python, and Go. Covers typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnoses and fixes bugs, type errors, lint failures, CI/CD issues, and runtime errors via root-cause-first investigation. Use for defect remediation. NOT for investigation without a fix (see mk:investigate); NOT for build-only compilation errors (see mk:build-fix).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging,

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging, and ensure teams can quickly identify and resolve production issues.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Consolidate PostHog error tracking issues that are the same actual error reported under different fingerprints. Use when the user asks "why do I have so many TypeError issues that look the same?", "merge these duplicates", "stop splitting this error into new issues", or wants to clean up fingerprint sprawl. Decides between a one-shot merge of existing issues and a durable grouping rule that keeps future events from creating new fingerprints. Does NOT group conceptually similar bugs across different runtimes, SDKs, or call sites.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides Rust error handling strategy. Use when choosing between Result/Option/panic, using anyhow vs thiserror, propagating errors with ?, or designing custom error types.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DEBUGGING SKILL — Read and analyze Cocos Creator project.log for runtime errors, warnings, and stack traces. USE FOR: any bug report, crash, UI glitch, TypeError, null reference, missing asset, CompositePanel mount fail, ChildPanel route fail, or screen spec wiring error. Load this skill FIRST before any runtime debugging session. DO NOT USE FOR: compile errors (use get_errors tool instead).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scheduled patrol that finds real persistence and error bugs and fixes them. Use when running the system-error repair patrol automation, or when stuck rows, SLA breaches, the system_errors queue, or app_log ERROR rows need a repair rather than a report.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

코드, 변경 이력, 재현 절차로 오류와 예상 밖 동작의 원인을 조사합니다. 가설 검증 후 최소한으로 수정하고 회귀 테스트와 증거를 담은 보고서까지 남깁니다.

• 오류와 스택 추적의 원인 조사
• 최근 변경으로 생긴 버그 추적
• 수정 검증과 회귀 테스트 기록

Create integration tests for syncable metadata entities in Twenty itself. Cover invalid inputs, validation errors, and successful data operations, using reusable GraphQL request helpers, error snapshots, and cleanup routines to organize the test suite.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add integration tests for a new syncable entity
• Test required fields, duplicates, and invalid references
• Verify successful creation, updates, and deletion

Investigate errors and unexpected behavior by finding related code, following function calls, and checking source files. GitNexus helps trace execution paths, while the diagnosis identifies the repository and reports how current its code index is.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding where an error originates
• Investigating an endpoint that returns 500
• Tracing calls between two functions

Define service reliability measurements and targets, then turn them into Prometheus monitoring rules and alerts. Calculate error budgets, the amount of failure allowed, and outline Grafana dashboards for tracking reliability and deciding when to prioritize fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting availability and response time targets
• Calculating and tracking error budgets
• Creating alerts for rapid error budget consumption

Check a Rust project for compilation errors with cargo check, examine errors and warnings, and fix the issues found. An included command example also covers checking all project targets.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking for compilation errors after code changes
• Reviewing and fixing compiler warnings
• Checking all project targets

Investigate failed Power Automate cloud flows through FlowStudio MCP. Inspect each action’s inputs and outputs, trace incorrect data upstream, fix expression or data issues, and replay a previous run to check the repair.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate why a cloud flow failed
• Find null values or incorrect field paths in expressions
• Inspect HTTP error response details

Organize Node.js, Express, and TypeScript APIs into layers with clear responsibilities. This guide covers request handling, business logic, database access, input validation, error tracking, configuration, and testing to support consistent implementation and refactoring across services.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding an API endpoint with clearly separated responsibilities
• Organizing database access through Prisma
• Adding input validation and error tracking

Set up users, organizations, roles, and dataset sharing in cognee. The skill explains SDK and HTTP authentication, helps investigate permission errors or missing datasets, and clarifies how access settings separate each user’s stored data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Share datasets with specific users or roles
• Organize data access across teams and organizations
• Configure SDK identities and HTTP authentication

Write and review interface text, including button labels, error messages, empty screens, and onboarding instructions. Get recommended wording, alternatives, and explanations tailored to the user's situation, tone, and character limits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing clear button labels
• Rewriting error messages with recovery steps
• Guiding users through empty screens

Inspect production errors recorded in Sentry using read-only queries. The skill summarizes recent issues, retrieves details of individual error occurrences, and accesses AI-generated cause analysis or fix plans through the command-line tool.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing unresolved production issues from the last 24 hours
• Inspecting an issue by its short ID
• Checking individual error occurrences and release details

Write and troubleshoot n8n expressions, the formulas that pass and transform data between workflow steps. Covers field references, webhook inputs, dates, strings, and choosing between expressions and Code nodes for data transformations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fixing expression syntax errors
• Using webhook data in downstream steps
• Formatting dates and strings