'failures' 검색 결과

커밋 전 코드 변경의 기밀 정보, 보안 위험, 테스트와 정적 검사 결과를 확인합니다. 독립 에이전트가 검토하고 지적된 문제만 자동으로 수정합니다.

• 기능 추가 후 커밋 전 점검
• 추가 코드의 기밀 정보와 공격 위험 검사
• 새 테스트 실패와 기존 실패 구분

원인 불명의 버그, 간헐적 이상, 성능 저하를 코드 변경 전에 조사합니다. 관찰한 증상과 추측을 구분하고 증거로 가설을 좁혀 원인과 근거를 보고합니다.

• 원인 불명의 버그 조사
• 간헐적으로 발생하는 이상 원인 조사
• 성능 저하의 원인 파악

기준 브랜치부터 CI 실패를 조사하고 수정합니다. 영향을 받는 PR을 하나씩 검증하고 대상 커밋의 근거와 미해결 사항을 기록해 담당자에게 인계할 준비를 합니다.

• 기준 브랜치의 CI 실패 재현과 수정
• 영향을 받는 PR을 하나씩 조사
• 현재 후보 코드의 필수 검사 검증

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

Guide HyperFrames video projects from setup and component selection through checks, previews, and rendering. Use command-line tools to inspect timelines, diagnose failures, compare frames, and choose local, batch, or cloud rendering for the finished composition.

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

• Set up and preview a HyperFrames video project
• Diagnose build or rendering failures
• Render multiple videos from variable data

Investigate intermittent Remotion CI failures, record their error patterns in a tracking issue, and increment counts for repeated failures. Find failed checks even without a supplied pull request, then rerun affected GitHub Actions jobs.

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

• Investigate a CI failure that may pass on retry
• Find failed checks without a pull request number
• Record recurring failures and update their counts

Design and review API contract tests, which check agreed request and response behavior. Examine schemas, server output, and client parsing to identify compatibility problems, reproduce failures locally, and report gaps in test coverage.

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

• Checking client impact before changing an API response
• Investigating client and server disagreements at runtime
• Reproducing compatibility failures with local test data

Implement Python error handling with early input checks, appropriate exception types, and clear messages. Handle individual failures in batch jobs, preserve error context for debugging, and use Pydantic models to validate structured input.

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

• Validating user input and API parameters
• Designing exception types and clear error messages
• Continuing batch jobs after individual failures

Add retries and timeouts to Python service calls, with increasing and randomized waits between attempts. Use examples to distinguish temporary failures from permanent errors, limit retry duration, and record retries in logs.

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

• Adding retries to external API calls
• Setting timeouts for network operations
• Handling rate limits and temporary service failures

Add clear runtime reporting to Python, PowerShell, or Node.js batch scripts. Design start messages, progress counts, item failures, and final summaries while preserving existing result output, error handling, and exit codes, then verify visibility during execution.

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

• Add progress reporting to long-running batch scripts
• Report individual failures and final outcome counts
• Keep progress logs separate from machine-readable results

Investigate LLM application failures with Phoenix CLI by reviewing execution records, recording observations, and grouping mistakes into counted categories. Inspect datasets and experiments to identify which failure types deserve evaluation tests first.

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

• Investigating failures in LLM applications
• Grouping observed mistakes into failure categories
• Choosing which evaluation tests to build first

Investigate recurring SGLang automated test failures by comparing logs, commit history, and GPU environments. Narrow down code changes or machine-specific problems, optionally reproduce failures remotely, and summarize the evidence in a structured report.

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

• Finding the change behind a recurring test failure
• Checking whether failures depend on a GPU or runner
• Reproducing a test failure on a remote GPU server

Plan authentication for a Zoom integration by choosing an app type, selecting an authorization flow, and defining minimum permissions. Work through token storage, renewal, and authentication failures with a clear implementation approach.

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

• Choosing an authentication flow for a Zoom integration
• Defining minimum permissions for an app
• Planning token storage and renewal

Explore an existing Vitest 3.2 JSON test report to count results, search failed tests, and inspect file errors. Review original diagnostic details and keep tentative explanations separate from evidence, without launching tests.

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

• Check failure counts in an existing test report
• Search failures by file path or diagnostic text
• Inspect file errors separately from failed assertions

Trace failing cmux Swift package tests to the commits that introduced them by running older revisions in CI, the automated testing environment. It helps distinguish outdated expectations, code regressions, and intermittent failures, then guides focused fixes and verification.

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

• Investigating a package suite failing on main
• Finding the PR that first broke a test
• Distinguishing outdated tests from code regressions

Reproduce model connection failures and interrupted responses in the desktop app using a local fault server and test providers. Check error messages and retry behavior for refused connections, DNS failures, HTTP errors, stalled requests, and cut streams.

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

• Checking error messages for model connection failures
• Testing responses to rate limits and server errors
• Reproducing stalled requests and interrupted replies

Add error handling to n8n workflows with connected error outputs, retries, and failure notifications. Return HTTP status codes that explain what went wrong, distinguish invalid requests from service failures, and keep internal error details out of public responses.

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

• Investigating workflows that fail without notification
• Returning clear errors from webhook APIs
• Retrying temporary network failures

Continuously monitor automatic end-to-end tests on NemoClaw main, group failures by root cause, and coordinate fixes and peer reviews through GitHub. Track ownership and merge readiness while checking whether later runs confirm each repair.

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

• Continuously monitor automatic test failures on main
• Coordinate repair ownership across maintainers
• Review peer fixes and assess merge readiness

Diagnose GKE TPU slice creation failures and pending JobSets caused by unstable managed instance groups, the underlying VM groups. Read-only checks examine logs, instance status, upgrades, and repairs to identify causes and suggest user-applied fixes.

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

• Investigating TPU SliceCreationFailed errors
• Checking whether pending JobSets relate to MIG instability
• Tracing stalled node pool upgrades or repairs

Investigate failed workflows and tasks in Managed Service for Apache Airflow. The skill compares remote logs, task states, and source code to explain failures, show supporting evidence, and recommend specific code or configuration fixes.

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

• Investigating a failed DAG run
• Diagnosing task timeouts and queue delays
• Checking service errors against DAG code

Diagnose Google Cloud Filestore mount failures by checking client access rules, network firewalls, and audit logs. Distinguish permission errors from connection timeouts, then provide a structured report and remediation commands that require confirmation before execution.

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

• Investigating a Filestore mount that hangs or fails
• Diagnosing access-denied errors from a GKE workload
• Checking client permissions and VPC firewall rules

Diagnoses storage failures in GKE, Google's managed Kubernetes service, including stuck Pods, disk attachment errors, storage pressure, and missing volume expansion. It provides diagnostic commands and reviewable configuration patches for deployment through GitOps.

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

• Diagnose Pods stuck in ContainerCreating
• Investigate slow disks and node storage pressure
• Find why expanded storage is missing inside a container

Diagnose interrupted or repeatedly restarting AI training jobs managed by JobSet on GKE. Correlate restart metrics, node events, host health, and worker logs to distinguish Spot VM preemptions, infrastructure failures, and application crashes, then recommend responses.

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

• Investigating repeated JobSet restarts
• Checking whether Spot VM preemptions interrupted training
• Tracing recurring failures to a physical host

Inspect GKE TPU Dynamic Slices, diagnose provisioning failures, and validate workload configuration for single slices or JobSet workloads spanning multiple slices. Get cleanup commands, with confirmation required before destructive changes.

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

• Checking TPU slice lifecycle states
• Diagnosing TPU slice provisioning failures
• Validating single-slice and multi-slice JobSet manifests