Latest AI Performance Verification List in Coding | Orivel | Claude Haiku 4.5 (Anthropic)

Benchmark Genres

View all 664 Discussions 254 Creative Writing 26 Coding 26 System Design 25 Education Q&A 24 Explanation 27 Summarization 28 Idea Generation 24 Roleplay 27 Business Writing 24 Planning 23 Analysis 26 Brainstorming 26 Persuasion 27 Humor 24 Empathy 25 Counseling 28

Model Directory

View all GPT-5.6 (OpenAI) GPT-5.5 (OpenAI) GPT-5.2 (OpenAI) GPT-5 mini (OpenAI) GPT-5.4 (OpenAI) Claude Opus 4.6 (Anthropic) Claude Fable 5 (Anthropic) Claude Opus 5 (Anthropic) Claude Sonnet 5 (Anthropic) Claude Opus 4.8 (Anthropic) Claude Sonnet 4.6 (Anthropic) Claude Opus 4.7 (Anthropic) Claude Haiku 4.5 (Anthropic) Gemini 2.5 Pro (Google) Gemini 2.5 Flash (Google) Gemini 2.5 Flash-Lite (Google)

Coding

Anthropic Claude Haiku 4.5 VS OpenAI GPT-5.4

Command-Line File Synchronization Tool

Write a Python script for a command-line file synchronization tool. The script must accept three command-line arguments: source_path: The path to the source directory. replica_path: The path to the replica directory that will be synchronized. log_file_path: The path to a file where all operations will be logged. Core Functionality: One-Way Sync: The tool must perform a one-way synchronization, making the replica_path directory an exact copy of the source_path directory. Files and directories present in the source but not in the replica must be copied to the replica. Files and directories present in the replica but not in the source must be removed from the replica. Files present in both locations but with different content must be updated in the replica (the source version overwrites the replica version). Change Detection: Use the MD5 hash of file contents to determine if a file needs to be updated. Do not rely on modification timestamps. Logging: Log all file operations (e.g., "COPY file.txt", "REMOVE old_dir", "UPDATE changed.log") to both the console and the specified log file. Each log entry should be timestamped. Execution: The script should perform the synchronization operation exactly once and then exit. It should not run in a loop. Requirements: Use Python 3. Use the argparse library for command-line argument parsing. The solution must correctly handle nested directories, empty directories, and files of various sizes. The script should be a single, self-contained file.

573

Apr 9, 2026 09:38

Coding

Anthropic Claude Haiku 4.5 VS OpenAI GPT-5.2

Advanced Log File Parser for a Custom Format

Write a Python function parse_log(log_content: str) -> list that parses a log file with a custom format. The function should take the log content as a single multiline string and return a list of dictionaries, where each dictionary represents a successfully completed transaction. Log Format Rules: START <transaction_id> <timestamp>: Marks the beginning of a transaction. transaction_id is a string without spaces. timestamp is an ISO 8601 formatted string. END <transaction_id> <status> <timestamp>: Marks the end of a transaction. The transaction_id must match an open transaction. status is a single word (e.g., SUCCESS, FAIL). EVENT <key1>=<value1> <key2>="<value with spaces>" ...: Represents an event within the current active transaction. It consists of one or more key-value pairs. Values containing spaces must be enclosed in double quotes. COMMENT # <any text>: A comment line that should be ignored. Processing Logic: The function should process lines sequentially. An EVENT line is associated with the most recently started transaction that has not yet ended. A transaction is only considered complete and valid if it has a matching START and END line with the same transaction_id. The output should be a list of dictionaries. Each dictionary represents one completed transaction and must have the following keys: transaction_id (string) start_time (string) end_time (string) status (string) events (a list of dictionaries, where each inner dictionary represents the key-value pairs of an EVENT line). Error Handling and Edge Cases: Ignore any COMMENT lines, blank lines, or lines that are malformed and do not match the specified formats. Ignore any EVENT that occurs outside of an active transaction (i.e., before the first START or after a transaction has been closed). If a new START line appears before the previous transaction has been closed with an END, the previous transaction is considered "abandoned" and should be discarded. The new START line begins a new transaction. Any transaction that is still open at the end of the log file is also considered "abandoned" and should not be included in the final output.

571

Mar 23, 2026 08:42

Coding

OpenAI GPT-5.4 VS Anthropic Claude Haiku 4.5

Log File Analyzer for User Activity

Write a Python function analyze_logs(log_data) that takes a single multi-line string log_data as input. Each line in the string represents a log entry in the format [TIMESTAMP] LEVEL: MESSAGE. The function should parse these logs and return a dictionary summarizing the data. The summary dictionary should have three keys: counts_by_level: A dictionary where keys are log levels (e.g., 'INFO', 'WARN', 'ERROR') and values are the count of logs for that level. successful_logins: A list of unique usernames (strings) who successfully logged in. A successful login is indicated by a message like "User 'username' logged in...". failed_login_ips: A dictionary where keys are IP addresses (strings) and values are the count of failed login attempts from that IP. A failed login is indicated by a message like "Failed login attempt for user 'username' from IP 'ip_address'". Your function should be robust and handle malformed or irrelevant log lines gracefully by ignoring them. The parsing of log levels should be case-insensitive (e.g., 'info' and 'INFO' should both count towards the total, which should be stored under the uppercase key 'INFO').

645

Mar 15, 2026 08:13

Coding

OpenAI GPT-5 mini VS Anthropic Claude Haiku 4.5

Implement a Dependency Resolver with Semantic Versioning

Your task is to write a function that simulates a package manager's dependency resolver. The function should take a list of all available packages, a target package to install, and its version requirement. It must return a flat list of packages (name and specific version) that need to be installed, in a valid topological order (dependencies before dependents). The resolver must handle semantic versioning (SemVer) constraints. For this task, you only need to support exact versions, caret (^), and tilde (~) specifiers. 1.2.3: Must be exactly version 1.2.3. ^1.2.3: Allows versions from 1.2.3 up to, but not including, 2.0.0 (i.e., >=1.2.3 <2.0.0). ~1.2.3: Allows versions from 1.2.3 up to, but not including, 1.3.0 (i.e., >=1.2.3 <1.3.0). Your implementation must: Select the highest possible version of each package that satisfies all constraints placed upon it by other packages in the dependency tree. Produce a topologically sorted list of packages for installation. Gracefully handle and report errors for: Unresolvable version conflicts (e.g., one dependency requires ^1.0.0 and another requires ^2.0.0 of the same package). Circular dependencies (e.g., package A depends on B, and B depends on A). A required package or version not being available. You can choose any programming language for your implementation. Define the function signature and data structures as you see fit, but make them clear.

603

Mar 15, 2026 06:11

Latest Tasks & Discussions

Command-Line File Synchronization Tool

Advanced Log File Parser for a Custom Format

Log File Analyzer for User Activity

Implement a Dependency Resolver with Semantic Versioning

Related Links