'failures' 검색 결과

Recover from repeated sandbox execution failures by saving Python code to a script and running it through run_shell. Check output, error messages, and exit codes to confirm results or diagnose remaining execution problems.

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

• Continuing Python work after two consecutive sandbox failures
• Switching execution methods after persistent timeouts
• Diagnosing script failures through error output

Investigate Python failures in a sandbox, an isolated execution environment, by capturing partial logs, testing functions separately, and checking output files one at a time. Use the findings to identify failing steps and rebuild a working script.

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

• Investigate failures with missing or incomplete output
• Isolate a failing function in a large script
• Verify multiple generated files one at a time

Run Python code through a saved script and shell when repeated sandbox failures point to environment problems. Captures execution output and checks exit codes and expected files to verify whether the task completed.

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

• Continuing work after repeated sandbox execution failures
• Running Python scripts saved in the workspace
• Investigating failures through shell error output

Validate security patches by comparing vulnerable and patched code against exploit tests, related attack variants, and normal behavior. Produce reproducible logs showing remaining flaws, regressions, newly introduced security failures, and gaps that still need testing.

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

• Validate an AI-generated security patch before review
• Check related attack variants for incomplete fixes
• Check whether a fix breaks normal behavior

Build failure handling into n8n workflows with separate error paths, retries, alerts, and clear API responses. Use it for webhooks and unattended jobs to make failures visible and return status codes that explain what went wrong.

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

• Add error responses to a webhook API
• Receive alerts when scheduled jobs fail
• Retry temporary external service failures

Analyze CLR activation logs to explain how .NET Framework selects and loads its runtime, the software that executes managed code. Diagnose loading failures, unexpected version choices, installation dialogs, and conflicting activation paths within a process.

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

• Investigating failures to load the .NET Framework runtime
• Explaining why an unexpected CLR version was selected
• Tracing .NET 3.5 installation dialogs or their absence

Investigate MSBuild failures caused by projects or build configurations writing to the same output folders. Compare build logs, output paths, and project settings to identify collisions behind overwritten files, restore errors, or failures that disappear on retry.

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

• Investigate file access errors during parallel builds
• Find shared intermediate folders causing NuGet restore errors
• Check output paths when building for multiple frameworks

Guide agents through failures with timed retries, alternative methods, targeted fixes, and clear handoffs. It also explains when to continue with partial results, helping teams choose a recovery approach that fits the problem.

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

• Retrying temporary API and network failures
• Switching methods when a tool fails
• Diagnosing build and test errors

Investigate failed gh-aw workflows using existing logs and audit reports. Identify missing tools, authentication failures, permission issues, network restrictions, and timeout causes, then guide fixes through source review and controlled validation.

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

• Investigating a failed workflow run
• Separating authentication failures from permission errors
• Checking whether the same error recurs across runs

Investigate bugs, crashes, and intermittent failures without changing code. Multiple agents examine evidence from different angles, then produce ranked possible causes, confidence levels, and the smallest steps needed to confirm the diagnosis.

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

• Investigating the cause of a crash
• Tracing a bug introduced by recent changes
• Examining failures that occur intermittently

Diagnose failed canary ferry runs, automated checks for failures or regressions, when invoked by CI with the required context. It gathers logs, classifies the cause, and files a GitHub issue with supporting evidence.

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

• Investigate GPU or TPU canary failures triggered by CI
• Distinguish infrastructure failures from training or metric problems
• File a GitHub issue with logs and run context

Investigate crashes, hangs, incorrect responses, and other failures by testing hypotheses against observed runtime behavior. Confirm the cause, verify the fix with a reproducing test, check the real workflow, and remove temporary debugging artifacts.

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

• Investigating crashes, hangs, or incorrect responses
• Tracing intermittent failures or asynchronous behavior
• Analyzing binary behavior without source code

Diagnose NVSHMEM launch failures, crashes, hangs, and communication problems using exact commands and complete logs. Separates observations from likely causes, checks version-specific documentation, and prepares a Markdown bug report for the user to submit.

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

• Investigate launch failures, crashes, and hangs
• Distinguish NVSHMEM defects from application or environment issues
• Check whether a known issue applies to the installed version

Troubleshoot applications where NeMo Relay is installed but runtime behavior is missing or incorrect. It helps isolate loading failures, inactive execution contexts, missing events, and plugin or export configuration issues before changing application settings.

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

• Diagnose native extension or shared-library loading failures
• Investigate missing lifecycle events
• Separate execution contexts across concurrent requests

Check DOCA installation health, prepare build and runtime requirements, and investigate environment failures such as missing libraries or memory settings. Helps choose container learning or hardware deployment paths based on the available system.

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

• Check whether a DOCA installation is healthy
• Investigate library detection and runtime environment failures
• Start learning through an NGC DOCA container without hardware

Analyze MSBuild binary logs to diagnose build failures. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), binlog MCP startup or connection failures (use troubleshoot-binlog-mcp), non-MSBuild build systems.

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

Audit application source code against the OWASP Top 10 (2021) vulnerability categories — broken access control, cryptographic failures, injection, insecure design, security misconfiguration, vulnerable components, authentication failures, data integrity, logging failures, SSRF. Use when the user mentions 'OWASP,' 'OWASP Top 10,' 'security audit,' 'security review,' 'secure code review,' 'code security review,' 'vulnerability audit,' 'find vulnerabilities,' 'appsec review,' 'application security audit,' 'check for security issues,' 'broken access control,' 'IDOR,' 'SQL injection,' 'XSS,' 'SSRF,' or wants to check their codebase for common security weaknesses.

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

Use when analyzing failing test cases to determine whether failures indicate genuine bugs or test implementation issues. Activates on "analyze failing tests", "debug test failures", "investigate test errors", or when provided with specific failing test names or output. Applies balanced investigative reasoning — does not auto-fix tests without establishing root cause.

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

General workflow for auditing ML CI failures, experiment regressions, training run failures, golden metric failures, and telemetry-backed ML work-product claims from local repositories, logs, metrics, configs, and artifacts. Use when Codex needs to decide whether an ML failure is a model/convergence issue, correctness bug, data/config issue, infrastructure/runtime issue, evaluation/gating policy issue, or unsupported claim, and produce structured evidence-backed outputs.

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

Use when diagnosing frontend build failures, runtime errors, UI anomalies, API/data problems, white screens, request failures, or unexplained production exceptions; Chinese triggers include debugging, debug, troubleshooting, positioning, error reporting, exceptions, white screens, request failures.

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

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.

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

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.

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

Babysit a GitHub pull request during a user-approved monitoring window by polling review comments, CI checks/workflow runs, and mergeability state. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and report fresh review feedback. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.

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

OpenClaw 테스트의 메모리 증가와 부족 원인을 조사합니다. 측정값과 메모리 객체 기록을 비교해 실제 해제 누락과 테스트 프로세스의 모듈 보존을 구분하고 수정 결과를 검증합니다.

• Vitest 메모리 부족 원인을 조사합니다
• 같은 프로세스의 메모리 기록을 비교합니다
• 해제 누락과 모듈 보존을 구분합니다