'exceptions' 검색 결과

Spring Boot와 Quarkus의 Java 코드를 명명, 불변 데이터, 예외 처리, 프로젝트 구조와 테스트 규약에 따라 작성하고 검토합니다. 빌드 파일로 프레임워크를 판별합니다.

• Java 코드의 규약 준수 검토
• Optional과 streams 사용 확인
• 패키지와 프로젝트 구조 정리

C++ 코드 구현·검토·리팩터링에서 타입 사용, 메모리 관리, 예외 처리와 동시성을 점검합니다. 표준 지침에 따라 안전성과 코딩 방식의 일관성을 정리합니다.

• 모던 C++ 코드 작성
• 메모리 소유권과 자원 해제 검토
• 기존 C++ 코드 리팩터링

Review multi-step forms to find information users must enter more than once. Suggest automatic filling, reuse options, and preserving data between steps, while explaining relevant accessibility requirements and exceptions for security or validity.

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

• Checking repeated fields during checkout
• Reviewing signup and onboarding forms
• Reusing information in support flows

Review forms for autofocus that moves users past introductory content when a page loads. Suggest removing it or moving focus after user interaction, while considering exceptions for login pages and pages dedicated to search.

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

• Reviewing forms with introductory content
• Investigating unexpected scrolling on page load
• Moving focus after a user action

Create integration tests for syncable metadata entities in Twenty itself. Cover invalid inputs, validation errors, and successful data operations, using reusable GraphQL request helpers, error snapshots, and cleanup routines to organize the test suite.

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

• Add integration tests for a new syncable entity
• Test required fields, duplicates, and invalid references
• Verify successful creation, updates, and deletion

Implement validation and migration action builders for syncable entities, data types handled by Twenty's synchronization system. This skill covers required fields, uniqueness, reference checks, and orchestration wiring, with validators that return errors without throwing exceptions or changing data.

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

• Add required-field and duplicate checks
• Validate references to parent entities
• Build create, update, and delete migration actions

Turn past classrooms and chat history into a reusable personal skill for course creation. It examines varied examples, checks recurring patterns and exceptions, and asks for corrections before saving instructions that reflect the user's workflow and quality expectations.

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

• Reviewing patterns across past course creation
• Turning preferred workflows into reusable instructions
• Checking inferred preferences against examples

Write and refine Javadoc comments for Java types and members. Apply consistent summaries and tags for parameters, return values, exceptions, inherited behavior, code examples, version information, and deprecated members with suggested alternatives.

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

• Adding documentation to public Java APIs
• Standardizing parameter and exception descriptions
• Documenting generics and inherited behavior

Write focused Java unit tests with JUnit 5, including tests that repeat checks across different inputs. Covers clear test structure, exception checks, mock objects that replace dependencies, and ways to organize test suites.

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

• Writing a unit test for a Java method
• Checking the same behavior with multiple input values
• Testing exceptions and related assertions

Review punctuation in code, comments, and text files using a policy that favors the plain hyphen over em and en dashes, while accounting for exceptions involving existing data and explicitly requested literary or news text.

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

• Replacing em and en dashes in code comments
• Reviewing punctuation in generated code
• Checking how existing dashes in data should be handled

Write consistent XML documentation comments for C# types and public members. Follow specific rules for summaries, parameters, return values, properties, exceptions, examples, and inherited documentation so API behavior and usage are clearly described alongside the code.

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

• Adding documentation to public APIs
• Standardizing parameter and return value descriptions
• Documenting exception conditions and usage examples

Write focused C# unit tests with XUnit, including tests that run against multiple input datasets. Apply consistent naming, setup, assertions, shared fixtures, and mock dependencies to keep tests readable, independent, and organized.

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

• Set up an XUnit test project for C#
• Test multiple input cases with Theory and data attributes
• Check exceptions and isolate dependencies with mocks

Write C# unit tests with NUnit using clear naming, focused assertions, and independent test cases. Covers project setup, testing with multiple input values, exception checks, and replacing dependencies with mocks to test components in isolation.

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

• Setting up an NUnit test project
• Testing the same behavior with multiple inputs
• Checking exceptions and collection contents

Keeps customer-facing CopilotKit Intelligence documentation consistent by applying an approved vocabulary to prose, navigation, buttons, and image descriptions. Checks disallowed alternatives and exceptions while preserving code identifiers and the labels users actually see in product controls.

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

• Standardizing terminology in customer documentation
• Reviewing navigation and button labels
• Checking terminology in image descriptions

Rewrite lengthy prompts, tool descriptions, and agent instructions into compact text while preserving requirements, exceptions, and exact values. The process records removed content and compares token counts, the units models use to measure text length.

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

• Shortening system prompts
• Compressing tool documentation and skill bodies
• Reducing text length for model input

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

Build a repeatable process for Microsoft monthly security updates, from reviewing advisories and ranking vulnerabilities to testing, staged deployment, and verification. Helps teams set response deadlines based on risk and report remaining unpatched systems.

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

• Establishing a monthly Microsoft security update workflow
• Prioritizing vulnerabilities by exploitation risk
• Planning pilot and production deployment stages

Build a tracking system for vulnerabilities that cannot be fixed on time. Define exception requests, approval workflows, alternative protective measures, expiration checks, and audit records so teams can track accepted risks and support compliance reviews.

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

• Standardizing exception requests for delayed vulnerability fixes
• Recording alternative protections and risk acceptance
• Checking expired exceptions and producing monthly reports

Troubleshoot WxJava failures using logs, exceptions, and request details. The skill helps isolate configuration, access token, signature, payment certificate, callback, and network issues, then proposes a minimal fix with steps to verify the result.

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

• Investigating failed WxJava API calls
• Diagnosing access token and storage issues
• Checking payment callbacks and signature verification

Screens incoming nondisclosure agreements against an organization's criteria or stated defaults. Classifies each agreement into three review levels and produces a report covering flagged clauses, risks, suggested fixes, and recommended next steps.

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

• Screen an NDA received by sales or business development
• Check for non-compete and non-solicitation clauses
• Identify missing exceptions to confidentiality obligations

Review SOC 2 Type II audit readiness through six questions about controls, the organizational safeguards assessed over an observation period. Identify evidence gaps, control changes, and exceptions, then organize readiness findings and three concrete next actions.

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

• Check readiness before the observation period begins
• Review control operation midway through the period
• Check evidence coverage before audit fieldwork

Find repeated tasks in recorded activity or starred examples, then describe their steps, exceptions, and human decisions. Assess a small automation candidate using captured evidence, available tools, permissions, and clear completion criteria.

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

• Finding recurring tasks in activity records
• Reviewing starred examples for workflow patterns
• Assessing a small automation candidate

Investigate slow or failing requests in Google Cloud using Cloud Trace. Filter traces by duration or error status, inspect spans representing individual operations, and retrieve related Cloud Logging entries to investigate bottlenecks and exceptions.

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

• Find requests exceeding a latency threshold
• Inspect operation hierarchies within a trace
• Investigate failures using related application logs

Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.

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

• Update billing logic and its specification together
• Review how trials and enterprise contracts are handled
• Find the code that defines prices and allowances