'values' 검색 결과

Merges, appends, joins, and deduplicates multiple CSV, TSV, and Excel files (including multi-sheet workbooks) with pandas - mapping mismatched column names to one schema, normalizing keys, resolving conflicting values, tracking which file each row came from, and verifying the row math. Use when the user wants to combine spreadsheets or exports, stack monthly files, consolidate contact or lead lists, VLOOKUP-style join two sheets on an ID or email, or dedupe records across sources, even if they only say "put these together" or "clean up these lists into one".

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

Process construction payment applications. Validate schedule of values, calculate retainage, track billing status, and generate G702/G703 forms.

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

Generate AIA-style payment applications. Track schedule of values, calculate retention, and produce payment documentation.

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

Use when a tabular dataset (CSV, Excel, Parquet, Stata, SAS) needs a data dictionary. Profiles every variable (type, levels, range, missingness) into codebook.md and codebook.json and flags coded values of unknown meaning as [NEEDS DICTIONARY] instead of guessing.

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

Use when a clinical CSV/Excel dataset needs profiling and cleaning before analysis (missing values, outliers, duplicates, type mismatches). Profiles, flags and generates cleaning code in three stages, each gated on the researcher's approval. Never auto-cleans.

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

Read huge, dense, read-only text as rendered PNG pages instead of raw text — image tokens scale with pixels, not characters, so token-dense bulk (big files, vendored code, diffs, logs) costs ~60–75% less as an image. Use when you must skim or reason over thousands of lines you will NOT edit or byte-copy. Lossy on exact strings: never for files you'll Edit, secrets, hashes, or byte-exact values. Fable-class readers only.

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

Business-logic flaw hunting - workflow/state bypass, price/quantity tampering, negative/overflow values, coupon/refund abuse, mass assignment, and logic races. The top-paying bug class with no scanner coverage. Wiki-first, FIND schema output.

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

Create, scaffold, or generate Helm charts, Chart.yaml, values.yaml, templates, helpers.

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

Validate, lint, audit, check Helm charts — Chart.yaml, templates, values.yaml, CRDs, schemas.

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

Apify integration. Manage Actors, Datasets, KeyValueStores, RequestQueues, Tasks. Use when the user wants to interact with Apify data.

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

Use when implementing select values from a range.

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

Use when implementing enter and format monetary values.

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

Fix misleading Flutter/Dart test failures where expected data is empty ([]) or default values instead of the mocked response, caused by stale Mockito generated mocks or missing stubs being silently swallowed by try/catch in provider/repository code. Use when: (1) Test expects non-empty data but gets [], (2) Mock stubs for a method are set up but the code under test returns fallback/empty results, (3) A PR added new methods to a service class and tests that previously passed now fail with misleading "expected X, actual: empty" assertions, (4) "Generated files are out of date" CI error alongside test failures. The root cause is MissingStubError thrown by unstubbed mock methods, caught by production try/catch blocks, causing silent fallback to empty state.

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

Optimize slow PostgreSQL inserts in Python using psycopg2. Use when: (1) Row-by-row inserts are taking too long over network, (2) executemany() isn't providing speedup, (3) Migrating large datasets to PostgreSQL, (4) Network latency making individual INSERT statements impractical. The key is using execute_values() from psycopg2.extras instead of executemany() or individual execute() calls.

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

Use database cache when external APIs aren't reliably idempotent. Use when: (1) External API claims idempotency but returns different values for same input, (2) Re-running a script creates duplicate resources, (3) Need stable identifiers across runs but external service generates new ones. Pattern: check database cache first, only call external API for genuinely new items, cache the result.

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

Fix incorrect priority ordering when using denormalized aggregate columns. Use when: (1) Records are processed in wrong order despite ORDER BY on count/sum columns, (2) Top items by some metric aren't being selected first, (3) Aggregate columns show 0 or NULL for records that should have high values, (4) Priority queue processes low-value items before high-value ones. The root cause is often that denormalized columns (vine_count, loop_count, total_orders, etc.) weren't backfilled or maintained properly. Solution: JOIN with source tables to compute actual aggregates at query time.

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

Fix LRU-bounded Flutter/bloc state classes that silently lose insertion-order updates. Use when: (1) a state class uses `Equatable` with a `LinkedHashMap<K, V>` field to preserve insertion order (LRU, MRU, recent-items caches), (2) `Cubit.emit` appears to drop emissions when an existing key is re-inserted or moved to most-recent, (3) LRU eviction evicts the "wrong" entry after a refresh, (4) a test that reports the same key twice and then overflows the cap sees the refreshed entry evicted instead of the oldest. Root cause: Equatable's default map comparison is structural (unordered), so reordering without changing keys/values produces an "equal" state that `Cubit.emit` suppresses.

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

Fix ClickHouse query errors when querying AggregatingMergeTree tables that use state functions. Use when: (1) Query fails with type mismatch on AggregateFunction columns, (2) Using sum/count on columns created with sumState/countState/uniqState, (3) Creating views that JOIN with materialized views using AggregatingMergeTree, (4) Getting unexpected results from aggregate columns that show as AggregateFunction(sum, ...) type. The *State() functions store intermediate aggregate states, not final values - you must use *Merge() functions to finalize them.

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

Fix ClickHouse query errors in Rust when using clickhouse-rs crate. Use when: (1) "string is not valid utf8" errors - typically FixedString columns need CAST to String, (2) "tag for enum is not valid" errors - typically Option<T> fields receiving non-NULL values, (3) Sum/count aggregations returning Float64 but Rust expects u64, (4) LEFT JOIN results with empty strings where Rust expects Option::None, (5) "not enough data, probably a row type mismatches a database schema" - query SELECT returns fewer columns than the Rust Row struct expects (common when multiple query functions share the same struct but one function is missing columns added later), (6) Garbled/corrupted data when INSERTing to FixedString(N) columns using String Rust type - silently corrupts data (no error!) because String adds a length prefix but FixedString expects exactly N raw bytes. Fix: use [u8; N] with #[serde(with = "BigArray")] from serde-big-array, (7) "the trait bound `[u8; 64]: serde::Serialize` is not satisfied" when using [u8; N] arrays in Row structs - need #[serde(with = "BigArray")] annotation from serde-big-array crate.

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

ACTIVATE when drafting all-hands speeches, investor updates, quarterly letters to stakeholders, press statements, CEO announcements, crisis communications, customer updates, or any mission-critical communication to employees, investors, customers, or media. Executive communications require persuasion, clarity, emotional intelligence, and alignment with company values and strategy.

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

Generates automated test oracles to verify correct software behavior. Creates assertion-based oracles (expected values), property-based oracles (invariants), differential oracles (comparing implementations), and metamorphic oracles (input transformations). Use when you need to generate assertions for test cases, identify invariants that should always hold, compare new vs legacy implementations, create metamorphic test relationships, validate function correctness, or improve test coverage with better verification strategies. Supports Python (pytest, unittest, hypothesis) and Java (JUnit, property testing).

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

Selectively instruments code to capture runtime data for debugging failures and bugs. Use when investigating crashes, exceptions, unexpected behavior, test failures, or performance issues. Analyzes stack traces and error messages to identify suspicious code regions, then adds targeted logging, tracing, and assertions to capture variable values, execution paths, timing, and conditional branches. Supports Python, JavaScript/TypeScript, Java, and C/C++.

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

Identify and report code smells indicating poor design or maintainability issues in Python code, including duplicate code, magic numbers, hardcoded values, God classes, feature envy, inappropriate intimacy, data clumps, primitive obsession, and long parameter lists. Use when conducting code quality audits, preparing for refactoring, improving codebase maintainability, or performing design reviews. Produces markdown reports with severity ratings, locations, descriptions, and specific refactoring recommendations with before/after examples. Triggers when users ask to find code smells, identify design issues, suggest refactorings, improve code quality, or detect maintainability problems.

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

Automatically analyzes configuration files to detect inconsistencies, conflicts, missing keys, and divergent values across environments, versions, or modules. Use when managing multi-environment configurations, detecting config drift, validating configuration changes, or ensuring consistency across microservices. Supports JSON, YAML, TOML, INI, XML, .env, and properties files. Identifies security issues like hardcoded secrets and provides actionable resolution guidance.

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