'runtime' 검색 결과

Manage Fluid in KubeSphere with configuration files and commands for installation, data connections, caching, status checks, and troubleshooting. Prepare Dataset and runtime resources, preload data into cache, and adjust runtime replica counts.

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

• Install or upgrade Fluid in KubeSphere
• Configure data connections and caching
• Preload data into cache with DataLoad

Guide test design for SGLang's scripted runtime by deciding when a test harness API adds real value. Favor direct reads, meaningful outcome checks, and the engine's actual execution loop over unnecessary wrappers.

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

• Decide whether a test harness needs a new API
• Review wrappers around directly accessible test state
• Test timeout behavior through the real engine loop

Guide changes to SGLang runtime configuration and shared process state. Identify where resolved settings, runtime flags, resources, and per-forward state belong, and use the documented access patterns and checks when developing or testing.

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

• Review how server settings are read and updated
• Choose where shared and per-forward state should live
• Check configuration publication order in worker processes

Use when configuring OmniStudio at the org level: enabling Standard Runtime, selecting the Runtime Namespace, assigning Permission Set Licenses, toggling feature settings, and granting Experience Cloud community access. Trigger keywords: OmniStudio Settings, Standard OmniStudio Runtime, managed package runtime, runtime namespace, OmniStudio Permission Set, OmniStudio PSL. NOT for moving an org off the vlocity namespace — use omnistudio/vlocity-to-native-omnistudio-migration. NOT for deciding whether to adopt OmniStudio — use architect/omnistudio-vs-standard-decision.

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

Analyze custom virtual machines written in JavaScript by extracting instruction tables, examining constants, and capturing runtime state. Use the findings to reconstruct how obfuscated code executes, including custom runtimes used in risk-control engines.

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

• Identify a custom virtual machine in obfuscated JavaScript
• Extract and classify virtual machine instructions
• Trace exported functions and their execution flow

Identify runtime signs of attackers breaking out of Docker or Kubernetes containers. Review namespace changes, privilege abuse, sensitive host access, and unusual system calls to guide incident investigations and compare monitoring coverage across security tools.

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

• Investigating a suspected Docker or Kubernetes container escape
• Choosing runtime behaviors to monitor for escape attempts
• Comparing escape detection coverage across security sensors

[omh] Unsure whether Codex or Claude Code is ready: executor runtime readiness - compare Codex, Claude Code, Hermes coding, and oh-my runtimes by tools and handoff mode; use external-connector-readiness for a named plugin or API, and toolbelt-readiness for the whole capability inventory. Use when the user says: executor-runtime-readiness, executor readiness, runtime readiness, codex readiness, claude code readiness, hermes coding readiness, executor tools, missing tools.

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

Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first content changes, validation, cleanup proof, or durable workflow rules. Best when agents must prove the actual folder/module/scene/prefab/runtime owner before editing, especially runtime UI, generated assets, code graphs, tutorial/state flows, guided selection/action flows, overlay/dim source-bound mistakes, coordinate conversions, focus/highlight/marker/HUD alignment, predictive lead aiming, ballistic trajectories, spatial IoU verification, or repeated "fix still not visible" failures.

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

Wire the Prisma Next runtime — `db.ts` setup using `postgres<Contract>(...)` from `@prisma-next/postgres/runtime`, `sqlite<Contract>(...)` from `@prisma-next/sqlite/runtime`, or `mongo<Contract>(...)` from `@prisma-next/mongo/runtime`; middleware composition (telemetry from `@prisma-next/middleware-telemetry`; lints and budgets), `DATABASE_URL` config, per-environment branching, switching between Postgres, SQLite, and Mongo façades. Use for db.ts, postgres(), sqlite(), mongo(), middleware, telemetry, lints, budgets, DATABASE_URL, .env, connection pool, poolOptions, dev vs prod config, transactions, db.transaction, read replicas, multi-database, script won't exit, hangs, close connection, db.end, db.close, pool.end, [Symbol.asyncDispose], await using.

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

Build and review HyperFrames animations using motion recipes, scene templates, and transitions. Find guidance for seven animation runtimes, including GSAP and Three.js, and inspect existing scenes for timing gaps and inconsistent motion.

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

• Combine motion recipes for text and shapes
• Build scenes with several animation phases
• Choose an animation runtime

Trace software artifacts from source and dependencies through builds, publishing, and runtime use in CTF sandboxes. Compare intended versions with shipped files to identify the earliest divergence and document the evidence linking each stage.

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

• Comparing declared, resolved, and shipped dependency versions
• Tracing package or build tampering through CI/CD
• Identifying the artifact actually used at runtime

Analyze running containers in a CTF sandbox by comparing declared configuration with live processes, mounts, and routes. Trace how secrets and helper containers affect behavior, then document the earliest mismatch and a minimal evidence chain.

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

• Comparing container manifests with live runtime behavior
• Identifying which process consumes a mounted secret
• Tracing changes made by sidecars or init containers

Update GitHub Actions when workflow logs warn about deprecated runtimes. The skill guides compatible version selection, pins actions to exact commits, preserves existing workflow behavior, and checks execution results and outputs after the upgrade.

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

• Addressing deprecated runtime warnings
• Upgrading actions while preserving workflow behavior
• Pinning action versions to exact commits

Connect a local CopilotKit agent to Slack through a managed Intelligence Channel. The skill guides dedicated Slack app creation, credential setup, runtime configuration, and checks that a human mention receives an actual reply.

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

• Setting up a dedicated Slack bot for a local agent
• Investigating a Channel stuck waiting for its runtime
• Diagnosing mentions that receive no reply

Detect unexpected changes in running containers by comparing them with their original images and monitoring execution and file activity. Use Falco or Microsoft Defender for Containers to investigate changes and guide isolation, replacement, and preventive configuration.

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

• Finding unexpected binaries executed inside running containers
• Investigating package installations and file changes at runtime
• Checking whether containers still match their approved images

Add checks to LLM prompts and responses using Llama Guard 3, NeMo Guardrails, and LLM Guard. Configure content screening, conversation boundaries, and sensitive-data filtering, then measure blocking and false-positive rates with labeled test prompts.

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

• Adding runtime safety checks to LLM, RAG, or agent apps
• Screening prompts for injection and jailbreak attempts
• Filtering sensitive or toxic model responses

Retrieve locally stored Chinese A-share prices, financial statements, and valuation context through the project's shared interfaces. Look up technical indicators, inspect available data fields, and check data dates when results disagree.

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

• Checking a stock's prices and valuation context
• Retrieving financial data across reporting periods
• Looking up technical indicators and their data dates

Implement or review a managed runtime provider for NemoClaw. Check its required interfaces, activation requirements, saved provider identity, and lifecycle behavior, then report validation evidence and any remaining qualification requirements.

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

• Plan a new managed runtime provider
• Review provider activation requirements
• Check saved state across lifecycle operations

Debug json-render interfaces with an inspector panel that shows screen specifications, editable runtime state, action history, and streamed updates. Select a rendered page element to locate its definition and investigate display or interaction problems.

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

• Investigate missing or incorrectly displayed elements
• Inspect and edit application state at runtime
• Review action results and errors

Deploy and configure LangBot with Docker Compose or Kubernetes. Set up application settings, plugin execution, the Box sandbox for isolated commands, and API authentication, with guidance on hosting choices and common deployment problems.

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

• Deploy LangBot on a self-hosted server
• Configure Box and the plugin runtime
• Enable API authentication for agent access

Assess Docker, containerd, and Podman environments for weaknesses that could expose the host system. The skill organizes checks for excessive permissions, exposed runtime sockets, and known vulnerabilities, alongside indicators defenders can monitor.

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

• Assessing container isolation
• Reviewing permissions and exposed runtime sockets
• Checking known runtime vulnerabilities

Use this skill when the user is deploying or operating the DOCA Argus Service — the packaged BlueField-side runtime-security container that watches the BlueField and attached host for suspicious activity, integrity violations, and operational anomalies, and forwards findings to a SIEM (Splunk / ELK / Sentinel / syslog). Covers the four-axis config (detection policy, forwarding, sampling, host coverage), running the NGC container on BlueField Arm, and wiring the forwarder. Trigger even without "DOCA Argus" by name — typical implicit phrasings: "container green but no findings arrive", "false-positive flood in Splunk", or "runtime security on a fleet of BlueField-3s". Refuse and route elsewhere for installing DOCA, SIEM-side ingest stanzas, pre-baked detection-rule packs, and metrics observability (DOCA Telemetry). Argus is NVIDIA's currently- promoted runtime-security framework, superseding the older App Shield library; name it first for new runtime-security work.

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

Bun — fast all-in-one JavaScript runtime, bundler, test runner, and package manager. Use when speeding up Node.js projects, using Bun as a drop-in Node replacement, bundling with Bun, or running tests faster. Covers runtime APIs, package management, bundling, and Bun-specific features like Bun.serve, Bun.file, and Bun.sqlite.

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

Assists with using Bun as an all-in-one JavaScript/TypeScript runtime, package manager, bundler, and test runner. Use when building HTTP servers, managing packages, running tests, or migrating from Node.js. Trigger words: bun, bun serve, bun install, bun test, bun build, javascript runtime, bun runtime.

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