1 views collected around this technical thread.
This article details a MySQL 8.0.35 crash caused by an InnoDB assertion that a VARCHAR length exceeds 65,535 bytes, explains the error‑log and core‑dump analysis, shows how to reproduce the bug, and notes its resolution in MySQL 8.0.35.
The article recounts the history of the 1969 text‑based Lunar Lander game, explains how its creator used the rocket equation and Taylor series for physics simulation, and reveals a long‑standing bug—a missing factor in the square‑root denominator—that causes the optimal fuel‑burn strategy to fail, prompting a modern analysis of the error.
This collection provides a curated list of technical articles covering performance testing strategies, bug case studies, web crawling implementations, UI automation techniques, UiAutomator usage, Selenium best practices, and mobile app performance monitoring, each with its original title and publication date.
This article examines why many testing teams skip bug root‑cause analysis, outlines typical scenarios where such analysis is needed, and presents a practical four‑step method—including recording, cause marking, role attribution, and improvement planning—to enhance software quality and team efficiency.
This article shares practical insights on QA versus QC, essential skills for becoming a qualified QA, demand analysis, test case creation, test‑left and test‑right shifts, bug analysis using the 5‑Why method, automation tools, and a personal tool‑development case, all aimed at improving game testing professionalism.
A bug in ByteDance's iOS client caused 1080p videos to become unplayable after 1 hour 53 minutes due to a downloader component truncating files beyond the int type limit, which was resolved by upgrading to a longlong type.
This article investigates why Sentinel’s QPS threshold of 20 is triggered at 15, analyzing metric logs, the underlying MetricNode and MetricTimerListener code, and revealing a timing discrepancy between second‑level and minute‑level counters that can cause premature flow‑control blocking.
This collection provides a curated set of links to articles covering performance testing strategies, notable bug analyses, and practical web crawling implementations, offering valuable insights for software testers and engineers seeking to improve testing practices and data extraction techniques.
This article examines the MySQL C API option MYSQL_OPT_READ_TIMEOUT, comparing official documentation that claims a three‑times timeout with empirical tests and source‑code analysis across MySQL 5.7.20, 5.0.96, and later versions, revealing outdated documentation and a historic bug.
This article presents a collection of classic interview questions and answers on interface automation testing, covering topics such as Python coding, testing methodologies, and tools like Jenkins.
This article provides a curated collection of links covering performance testing of message queues, stress testing password interfaces, probabilistic algorithm testing, notable bug analyses, and various web crawling implementations using httpclient and Groovy, offering valuable resources for backend developers and testers.
The article explains the importance of bug analysis for improving product quality, outlines the information that can be analyzed, describes common bug resolution categories, discusses bug severity levels, and shows how various stakeholders can use bug metrics to drive process optimization and predict future issues.
The article analyzes why MySQL tables upgraded from 5.6 to 5.7 began generating duplicate‑key errors during inserts, examines related InnoDB auto‑increment mechanisms, reproduces the issue, discusses known bugs (including replace‑into replication problems), and proposes both operational and kernel‑level solutions.
The article shares a tester's three‑year journey, detailing real‑world problems such as session synchronization failures, configuration migration oversights, missing identifiers, and process compliance lapses, while offering analysis, root‑cause explanations, and practical lessons learned for improving software testing and operations.
A recent study of five major open‑source distributed systems reveals that most failures can be triggered and reproduced with simple, multi‑event tests, highlighting the importance of systematic testing, deterministic error handling, and concise logging for reliable system operation.