'restart' 검색 결과

Rebuild modified packages in the Storybook monorepo and restart its internal UI after code changes. The workflow provides the running URL and can optionally create a UI review of stories related to the changes.

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

• Rebuilding after changes to Storybook internals
• Restarting the internal Storybook UI
• Reviewing stories related to UI changes

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

Pause and restart Estuary connectors by disabling and re-enabling shards via flowctl. Use when temporarily stopping a connector, performing source/destination maintenance, or forcing a fresh restart to clear transient errors or load updated configs immediately. Use when user says "pause connector", "stop connector", "restart connector", "disable connector", "enable connector", "re-enable task", "disable shards", "stop my capture", "stop my materialization", "disable my materialization", "force restart connector", "connector maintenance", "temporarily stop processing", "shards disable true", "enable shards", "resume connector", or "unpause connector".

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

Plan and review fluid simulations with FluidSim, from solver selection and resource estimates to output analysis and restart checks. Examine numerical accuracy through grid and time-step comparisons, conservation checks, and explicit limits on computing resources.

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

• Selecting a solver and reviewing simulation parameters
• Estimating memory, disk space, and runtime needs
• Inspecting spectra and conservation budgets

Launch and supervise gator agents for specific GitHub issues or pull requests in OpenShell. Check isolated execution environments, inspect logs, restart stalled agents, and test model or image overrides without changing default settings.

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

• Launch gator to review and monitor a specific pull request
• Inspect sandbox status and runtime logs
• Restart a stalled or outdated gator agent

Start and manage long-running background services such as development servers. Check their status and output logs, verify listening ports, retrieve local URLs, and restart services while keeping the same service ID.

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

• Starting a development server in the background
• Checking service status and output logs
• Restarting a service while keeping its ID

Manage embedded services such as 9Router and CLIProxyAPI through local service APIs. Install, start, stop, restart, or update services, then check their status, retrieve logs, and configure automatic startup.

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

• Installing and starting embedded services
• Stopping or restarting services
• Checking service status and logs

Start, stop, and restart the OmniRoute server from the command line. Configure its port, background operation, automatic recovery, and system tray integration, or open the dashboard to manage the running server.

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

• Starting the server on a chosen port
• Running the server in the background with automatic recovery
• Stopping or restarting the server

Manage Node.js processes through PM2 from the command line. List running processes, start or restart applications, inspect logs and metrics, and save the process list, with structured JSON output for agent workflows.

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

• Inspect running processes and their metrics
• Start, stop, or restart an application
• Review recent application logs

Manage Codewhale fleet runs by inspecting workers, the agents carrying out tasks, and reviewing logs and artifacts. Classify failures, choose a supported recovery action or draft a request for human review, and summarize evidence and follow-up ownership.

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

• Checking workers in a Codewhale fleet run
• Assessing whether a temporary failure warrants a restart
• Resuming a run after a manager restart

Check a gbrain installation after a restart or when services seem broken. It tests key components, repairs some local problems, checks OpenClaw when installed, and records results, with support for custom test scripts.

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

• Check services after a machine or container restart
• Investigate problems with a gbrain installation
• Check OpenClaw services when installed

Add a NanoClaw status icon to the macOS menu bar. Check whether the service is running through a green or red dot, then start, stop, restart, or open its logs from the menu.

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

• Checking NanoClaw's running status
• Starting or stopping the service from the menu bar
• Restarting after code changes

Write Apache Cassandra distributed tests that simulate multiple nodes within one JVM, the Java runtime. The guide covers cluster setup, queries, node restarts, message dropping for failure scenarios, and troubleshooting problems caused by isolated class loading.

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

• Writing read and write tests across multiple nodes
• Testing timeouts by dropping messages between nodes
• Verifying node replacement and restarts

Plan how agents retain active work across conversation compaction, context loss, and restarts. Organize restoration packets that preserve purpose, progress, ownership, and constraints, distinguish resume from fork or rebuild, and check whether work actually resumes correctly.

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

• Prepare restoration materials before conversation compaction
• Preserve task purpose and ownership across a restart
• Distinguish native resume, fork, and artifact-based rebuild

Build workflows with Vercel's Workflow DevKit that preserve progress and resume after restarts. Structure operations as persistent steps, wait for external events, retry temporary failures, and inspect runs to understand how a process is progressing.

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

• Building processes that resume after restarts
• Pausing a workflow until an external event arrives
• Retrying temporary failures in individual steps

Set up a persistent Microsoft Testing Platform console host that applies code edits and automatically reruns tests. It covers package setup, test selection, and restarting the host when an edit cannot be applied while running.

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

• Setting up MTP console hot reload
• Automatically rerunning selected tests after edits
• Restarting after unsupported code changes

Manage Python and R packages for notebook work. Resolve missing-package errors, check installed versions, install into the selected runtime, and restart the kernel when needed, with guidance on using separate environments for different dependency requirements.

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

• Resolve missing-package errors in a notebook
• Check installed package versions
• Separate project dependencies into a named environment

Start (or restart) a local Temps control plane built from this checkout, and the web dev server (`bun dev`) in `<checkout>/web`. Invoke when the user says "start temps", "restart temps", "launch the server", "kill and restart temps", or asks to bring the local server up after backend changes. Ports, database and data dir are allocated PER CHECKOUT (a "slot") so several worktrees/branches run side by side without killing each other or corrupting each other's schema — the first checkout you start in claims slot 0 (the familiar `:8080` / `:3000`); every other worktree gets its own slot and its own `temps_s<N>` database. Uses the `fast` cargo profile (release semantics, no debug symbols, parallel codegen) for quick rebuilds. Pass `split` (e.g. "start temps split", "/start-temps split") to launch the two-process proxy/console topology for testing that feature.

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

기존 OpenClaw Gateway를 설치 환경의 관리 절차에 따라 업데이트하고, 재시작 후 세션 복구와 목표 버전의 실행 여부, 연결 및 화면 상태를 확인합니다.

• 로컬 Gateway 업데이트
• 관리 서버의 업데이트 절차 선택
• 재시작 후 세션 복구 확인

Hermes Docker 이미지의 s6 서비스 감독 구성을 파악합니다. 상주 서비스를 추가하고 프로필별 gateway의 시작·재시작 오류와 파일 소유권 문제를 조사합니다.

• Docker 이미지에 상주 서비스 추가
• gateway가 시작되지 않는 원인 조사
• 재시작 후 gateway 복원 실패 조사

실행 중인 Jupyter에서 변수와 불러온 데이터를 유지하며 Python 코드를 시험하고 객체와 셀을 확인·편집합니다. 재시작 후 전체 셀의 순차 실행도 검증합니다.

• 변수를 유지하며 데이터를 탐색합니다
• DataFrame과 Python 객체를 확인합니다
• API와 복잡한 코드를 시험하고 수정합니다

Check and control OmniRoute’s MCP server, which connects agents to tools. Inspect tool permission scopes, enable or restart the server, and invoke tools with JSON arguments from the command line.

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

• Check the MCP server’s operating status
• Enable, disable, or restart the server
• Inspect permission scopes for a tool

Validate particle data and run RELION refinement for single-particle cryo-electron microscopy. Check independently refined half maps, calculate diagnostic map correlations, and perform soft-mask postprocessing while preserving execution logs and restart information.

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

• Check particle metadata and image-stack consistency
• Run refinement on a selected particle population
• Inspect agreement between independent half maps

Build, run, and troubleshoot data processing pipelines with Nextflow and nf-core. The skill guides modular workflow development, input preparation, testing, cached restarts, and configuration for local computers, computing clusters, or cloud environments.

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

• Run an nf-core workflow with a samplesheet
• Build and test reusable DSL2 modules
• Investigate failed runs and restart with cached results