'runtime' 검색 결과

Review existing tests and CI, the automated checks run during development, for redundant coverage, misplaced tests, and opportunities to reduce runtime or cost. Receive file-specific recommendations based on documented improvement patterns, with uncertain findings separated.

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

• Investigating a slow test suite
• Finding redundant or misplaced tests
• Reviewing CI runtime and cost

Investigate excessive privileges inside Kubernetes pods by reviewing security settings, runtime events, and audit logs. Use admission policies to restrict risky configurations and Falco monitoring to detect suspicious privilege changes and container activity.

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

• Finding pods running as root or in privileged mode
• Reviewing host filesystem access and dangerous Linux permissions
• Detecting privilege changes while containers are running

Assess serverless functions, primarily AWS Lambda, for unsafe execution of external input and unauthorized changes to code or added libraries. Combine source inspection, activity logs, and permission reviews to identify injection risks and recommend detection and prevention measures.

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

• Reviewing Lambda event handlers for injection vulnerabilities
• Investigating unauthorized function or layer changes
• Checking privilege escalation through Lambda execution roles

Set up and operate Amazon GuardDuty to detect threats in AWS. Configure protection features, centralize findings across accounts, investigate suspicious activity, and build automated responses with EventBridge and Lambda, including containment of potentially compromised resources.

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

• Setting up threat detection for AWS accounts
• Investigating credential abuse and compromised instances
• Automating responses to high-severity findings

Detect unauthorized cryptocurrency mining in cloud workloads by combining billing changes, CPU usage, mining pool connections, and process alerts. Follow workflows to preserve evidence, isolate affected resources, and trace how attackers gained access.

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

• Investigating sudden cloud billing increases
• Responding to GuardDuty cryptocurrency alerts
• Checking containers for unauthorized mining processes

Create and tune Falco rules to detect possible container escapes, where a container gains access to its host. Define detection conditions, alert priorities, and output fields, then refine exceptions to reduce false positives.

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

• Writing rules for suspicious host filesystem access
• Investigating noisy container escape alerts
• Reusing detection conditions through macros and lists

Investigate compromised Docker containers by preserving evidence and examining image layers, logs, file changes, and host settings. Summarize suspicious activity, security configuration issues, and vulnerability findings to support incident response.

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

• Investigating a compromised application container
• Examining a suspicious image from a registry
• Checking evidence of a container escape attempt

Forward tasks from Claude Code's rescue subagent to Codex through a helper script. This internal skill handles model and effort options, fresh or resumed runs, and write access, then returns the helper's output unchanged.

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

• Hand off diagnosis or implementation work to Codex
• Resume a previous Codex request
• Start a fresh Codex run

Diagnose oh-my-codex installation and skill discovery problems by checking configuration, hooks, plugin caches, and optional Team runtime checks. Produce an evidence-based report and carry out confirmed repairs with user approval, then verify the results.

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

• Investigate installation or skill discovery failures
• Check for duplicate hooks and legacy settings
• Inspect plugin cache version conflicts

Configure safety checks for LLM applications with NeMo Guardrails. Covers attempts to bypass safety rules, input and output validation, masking personal information, and checking factual claims through programmable rules and integrations.

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

• Detecting instructions that try to bypass safety rules
• Masking personal information before processing
• Adding factual checks to generated answers

Investigate and fix agent behavior in TradingAgentsCN by checking active database prompt templates, prompt assembly code, and output processing. Apply targeted changes and verify them with focused tests, template checks, and workflow logs.

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

• Investigating prompt changes that do not affect runtime behavior
• Synchronizing database templates with prompt assembly code
• Tracing incorrect dates or price references in position analysis

Run context-mode diagnostics to check runtimes, hooks, full-text search support, plugin registration, and npm and marketplace versions. Results appear directly in the conversation with clear status labels, with a CLI fallback if the MCP call fails.

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

• Checking the environment after installation
• Checking hooks and full-text search support
• Reviewing plugin registration status

Choose and run checks for TypeScript SDK changes, including type checks, linting, builds, Vitest suites, and tests of complete runtime flows. Also guides writing or adapting CLI tests for Effect v4.

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

• Validate changes to TypeScript packages
• Choose focused checks for a change
• Investigate failing TypeScript CI checks

Reproduce Mastra Code bugs with a real model and compare timestamped logs across network, streaming, execution, and terminal interface layers. Use the evidence to locate timing problems, incorrect token rates, flicker, or stuck status displays.

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

• Investigating incorrect token rate displays
• Reproducing intermittent bugs with a real model
• Tracing flicker or stuck status displays

Build and review Kubernetes Operators, controllers that keep custom resources in their desired state. Included tools check resource definitions and Go reconciliation code, then assess operational capabilities and suggest improvements.

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

• Designing custom resource definitions for a new Operator
• Reviewing Go reconciliation code for common mistakes
• Assessing Operator capabilities and planning improvements

Set up a Windows sandbox in Daytona to test OpenWork with a simulated corporate certificate authority. Check successful and broken HTTPS connections, the desktop app’s use of Windows trust, and certificate handling in runtimes it launches.

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

• Reproducing corporate certificate failures on Windows
• Checking OpenWork’s use of trusted Windows certificates
• Comparing valid and broken HTTPS certificate chains

Investigate opaque errors in shipped OpenWork builds using local logs and Sentry exception reports. Identify the change that caused the failure, reproduce it on the affected runtime, file a Linear issue, and reply to the original report.

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

• Investigating unexplained errors in shipped OpenWork builds
• Identifying the PR that introduced a failure
• Reproducing errors on the affected runtime

Run Openwork end-to-end tests, which verify complete user journeys, locally or on Daytona. Check the exact commit and runtime, investigate failures or skipped tests, and report results with commands, counts, and an explicit overall verdict.

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

• Running a single end-to-end test
• Verifying the exact commit intended for a PR
• Investigating skipped tests and missing prerequisites

Reconcile project documentation, agent rules, authorized memory, and workspace leftovers with current code and runtime behavior. Prepare a clear handoff by correcting stale information, identifying authoritative explanations, and reporting what is verified, pending, or awaiting cleanup approval.

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

• Synchronizing documentation after development
• Resolving stale or conflicting agent rule files
• Preparing a handoff to another person or a fresh session

Helps address Google Cloud Security Command Center findings by planning targeted fixes for permissions, misconfigurations, vulnerabilities, and combined attack paths. It includes impact checks, verification, rollback steps, and execution after user approval.

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

• Fix excessive permissions flagged by Security Command Center
• Plan fixes for exposed buckets or firewall rules
• Address attack paths involving multiple security issues

Plan and configure security across Google Kubernetes Engine clusters. Review access permissions, enable Secret Manager integration, and configure protections such as Shielded Nodes and Binary Authorization to strengthen the platform supporting your applications.

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

• Review cluster access permissions
• Enable Secret Manager integration
• Configure Shielded Nodes and GKE Sandbox

Explore how coordinating agents can pass relevant working state to workers through KV cache, a model's internal attention memory. Covers task-specific selection, runtime requirements, and comparisons of accuracy, token use, and processing overhead.

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

• Reducing repeated history sent to worker agents
• Comparing internal memory sharing with text summaries
• Assessing runtime support for KV cache compaction

Diagnose errors and incorrect inference results in MNN's QNN backend for Qualcomm HTP processors. Compare intermediate calculation data against CPU results to locate the first faulty operator, distinguish bugs from precision limits, and guide operator support and performance fixes.

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

• Investigate QNN runtime and model conversion errors
• Find the first operator producing incorrect results
• Distinguish implementation bugs from numerical precision limits

Prepare a clean Doris package and run Docker regression tests, which check whether changes break existing behavior. Restore configuration and startup files from Git, build the test image, and investigate failures using configuration checks and runtime logs.

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

• Run Docker regression tests before submitting Doris changes
• Test without local configuration changes affecting results
• Investigate missing test suites or startup failures