'diagnostics' 검색 결과

Manage LangBot bots and processing workflows through MCP, a standard for connecting agents to tools. Configure authenticated access, inspect resources, update supported settings, and investigate execution histories, logs, and model request diagnostics.

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

• Connect an MCP client to LangBot
• Create or update bots and processing workflows
• Investigate execution logs and errors

Run clang-tidy static analysis, which checks code without executing it, on added or modified BE and Cloud C++ files. Focus diagnostics on changed lines, investigate bug, performance, and readability warnings, and verify fixes with another check.

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

• Check changed C++ code before committing
• Investigate clang-tidy warnings reported by CI
• Review changes against a specific branch

Find relevant passages in an Obsidian vault using a local word-based search index. Optionally reorder results by meaning with a multilingual Nomic model, returning note paths and snippets while leaving the original notes unchanged.

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

• Find relevant passages across vault notes
• Rerank search results by semantic similarity
• Rebuild search data after note changes

Track machine learning experiments with Trackio by recording training measurements, viewing live dashboards, and flagging diagnostic events. Retrieve metrics and alerts through command-line queries, with JSON output for automated monitoring and experiment review.

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

• Recording training loss and accuracy
• Flagging loss spikes or stalled training
• Monitoring cloud training through a Space dashboard

Audit advertising accounts across twelve platforms using account data and documented sources. Identify measurement, budget, creative, and policy issues, then produce prioritized actions with evidence coverage, confidence, and missing information clearly recorded.

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

• Reviewing account health across advertising platforms
• Investigating advertising spend and tracking issues
• Prioritizing improvements to creative and landing pages

Guide CI work for Worktrunk, a Rust tool for managing Git worktrees. Adds project rules for running tests, checking Codecov coverage, diagnosing failures, reviewing pull requests, and maintaining toolchain and CI versions.

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

• Investigating failed CI checks and coverage gaps
• Reviewing pull requests against project rules
• Updating Rust toolchain and CI version pins

Build Native SDK app logic in TypeScript using explicit state, messages, and update functions. Explains the supported language subset, compiler diagnostics, module organization, and tests for logic that compiles directly into native code.

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

• Designing state and messages for a new app
• Fixing unsupported TypeScript constructs
• Splitting app logic into modules

Work around file-writing failures involving quotes, backticks, or template literals by using a Python helper script. Then run TypeScript directly through Node.js and filter diagnostic output to focus on errors reported in newly written files.

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

• Write files containing template literals
• Create several files through one Python helper
• Focus TypeScript diagnostics on newly written files

Recover from PDF and DOCX generation errors by checking the workspace, capturing error details, and trying alternative conversion engines or Python libraries. Verify that the resulting files exist and can be read.

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

• Recovering from PDF conversion errors
• Creating reports in DOCX and PDF
• Investigating garbled symbols in PDFs

Build browser-based 3D games with Three.js, TypeScript, and Vite. Structure scene and camera control, model loading, physics, and interface overlays separately from game rules, with guidance for WebGL rendering diagnostics and performance.

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

• Build a browser-based 3D exploration demo
• Prototype vehicle movement or character traversal
• Load GLB models and integrate Rapier physics

Turn business and product metrics into KPI updates for weekly, monthly, or quarterly reviews. Compares actual results with targets and prior periods, includes verified explanations for changes, and states what the findings mean for operations.

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

• Prepare a weekly or monthly KPI review
• Check progress toward a time-bound target
• Summarize verified reasons for metric changes

Guide Expo SDK upgrades through dependency updates, diagnostics, configuration cleanup, and migration of deprecated packages. Includes checks for native project changes and guidance for moving audio and video code to replacement APIs.

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

• Upgrade Expo SDK and resolve dependency issues
• Migrate from expo-av to expo-audio and expo-video
• Review native project changes during an upgrade

Investigate why a business metric changed or missed expectations. Checks definitions and data sources, measures the change, and breaks it down by relevant groups, separating verified findings from likely explanations and unresolved questions.

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

• Investigate changes in sales or usage rates
• Locate affected groups during a sudden spike or decline
• Reconcile differences between dashboards

Inspect CircleCI runs, identify failing steps, and validate configuration locally using the CircleCI CLI, its command-line tool. It also guides targeted reruns and pipeline launches, reporting results, permission gaps, and next steps.

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

• Investigating failed CircleCI runs
• Validating configuration before committing changes
• Rerunning a specific workflow or job

Design a dark monochrome interface around an exploded 3D wireframe, an outline view of separated parts. Coordinate annotations, connector lines, typography, and small metric displays to explain product structures or system states.

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

• Designing a product teardown interface
• Creating a system diagnostics dashboard
• Presenting structural specifications with annotations

Use the new Process APIs in .NET 11 applications to run external commands, capture output and errors, and manage child processes. Guidance covers waiting for completion, reading output, and controlling whether processes survive their parent.

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

• Capturing output and errors from external commands
• Stopping child processes when the parent exits
• Reading process output one line at a time

Choose and optionally run .NET test commands that match the project's SDK, test platform, and framework. Target specific tests, collect reports or diagnostics, and report execution results using syntax appropriate to the repository.

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

• Getting an exact test command for a repository
• Running a specific class, category, or target framework
• Collecting TRX reports, coverage, or diagnostic logs

Correct and improve existing MSTest tests using APIs supported by the installed version. Refine assertions and failure messages, update data-driven tests, fix setup and cleanup, and address MSTest diagnostics while preserving the project's established conventions.

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

• Making assertion failures easier to understand
• Correcting expected and actual argument order
• Improving existing data-driven tests

Diagnose slow MSBuild startup by measuring project evaluation, the work done before compilation. Inspect logs for costly file searches, imported configuration, and repeated evaluations, then identify targeted changes supported by timing evidence.

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

• Investigating delays before compilation starts
• Checking file searches across large directories
• Analyzing deep import chains

Analyze MSBuild binary logs and timing summaries to find why builds are slow. Identify costly reference resolution, code analysis, file copying, restore work, or serialized tasks, then prioritize improvements by their share of total build time.

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

• Investigate unexplained MSBuild slowness
• Measure code analysis and source generator overhead
• Find expensive reference resolution or file copying

Choose diagnostic tools and collect performance traces for production .NET problems such as high CPU usage, memory growth, or slow requests. Get environment-specific collection commands and guidance on which tools to use for later analysis.

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

• Collecting traces during high CPU usage or slow requests
• Choosing diagnostic tools for Windows or Linux
• Collecting diagnostics from containers or Kubernetes

Create readable GitHub Actions step summaries that put key results first. Organize headings, format code and review findings, and place lengthy logs or diagnostics in expandable sections for easier scanning.

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

• Making workflow results easier to scan
• Placing lengthy logs in expandable sections
• Organizing review findings by severity and action

Fit regression and time series models in Python, then examine coefficients, uncertainty, and predictions. Check model assumptions, investigate unusual observations, and compare alternatives using detailed statistical summaries and diagnostic tests.

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

• Interpret regression coefficients and confidence intervals
• Model binary outcomes or event counts
• Forecast time series with uncertainty intervals

Compare current and previous Google and Meta campaign data to investigate rising cost per acquisition, the cost of each conversion. Receive contributing factors ranked by impact, affected campaigns or audiences, and prioritized fixes.

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

• Investigating a sudden rise in acquisition costs
• Explaining performance declines to clients
• Checking for campaign issues after the weekend