Developer catalogs 93 CJK Unicode bugs across 87 libraries, finds five root causes

·1 views

A developer who uses a Japanese keyboard while reviewing open-source code began logging text-handling bugs and has now compiled a public corpus of 93 bugs found across 87 libraries. The majority — 36 of 93 — stem from the same IME composition flaw, where a Japanese user's Enter keypress to confirm kanji selection accidentally triggers form submission handlers before input is complete. The fix requires a single property check, but the bug persists because it only reproduces with an IME active, a setup most maintainers don't use during testing. Beyond the IME issue, the remaining bugs cluster into four patterns: missing locale translations, broken surrogate-pair and grapheme-cluster handling, date parsing failures for non-Latin calendar formats, and similar edge cases invisible in standard English-language testing. The catalogued bugs are publicly available in a caniuse-style reference that links each entry to a real pull request or issue.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Five design rules that keep AI agents running reliably despite constant interruptions

Building long-running AI agents requires solving a core challenge: preserving meaningful state across frequent interruptions, reboots, or scheduled restarts that wipe working memory. The author recommends maintaining a single source-of-truth file, updated after every step, written as if the next reader has total amnesia. Before taking any action, the agent should re-verify real-world conditions rather than rely on remembered assumptions, since stale beliefs can corrupt ongoing work. Every action must also be designed to be safely repeatable, so an interruption mid-task results in a harmless retry rather than a broken state. Finally, work should be chunked into units small enough to complete within a single run, with outcomes persisted at each boundary so that being killed between steps carries no cost.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

NetZero Tool Auto-Generates Kubernetes Network Policies Using Go and eBPF

A developer has open-sourced NetZero, a zero-configuration tool written in Go and C that automates the creation of Kubernetes NetworkPolicy files for zero-trust environments. The tool addresses a common pain point where manually writing network policies often leads to missed dependencies and production outages. NetZero uses eBPF to hook into the Linux kernel at the socket-connection level, capturing outbound traffic metadata such as PID, destination IP, and port with minimal overhead. A Go-based user-space layer then enriches this raw data by querying the host's /proc filesystem and performing reverse DNS lookups to map IPs to stable domain names. After a test run completes, the tool aggregates the observed traffic and exports a ready-to-use Kubernetes YAML manifest reflecting actual runtime behavior.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

5 Python list behaviors that trip up developers in coding interviews

Python lists are among the first data structures developers learn, yet they remain a common source of errors in technical interviews and real-world coding. Key pitfalls include shallow copies sharing references to inner objects, the multiplication operator creating duplicate references rather than independent lists, and list.sort() returning None instead of a sorted list. Modifying a list while iterating over it can also cause elements to be silently skipped due to index shifting. Safer alternatives such as copy.deepcopy(), list comprehensions, and the built-in sorted() function help avoid these subtle bugs.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Implement Google Sign-In in Flutter Using google_sign_in 7.2.0 Without Firebase

Developers building Flutter apps can now implement Google OAuth authentication directly without relying on Firebase, using the updated google_sign_in package version 7.2.0. The latest version introduces breaking changes from older implementations, requiring explicit initialization and a new authenticate() method, which renders most existing online tutorials outdated. The approach involves obtaining a Google ID token on the client side and sending it to a custom backend, where it must be verified against Google's servers using a library such as google-auth-library for Node.js. Setting up OAuth credentials correctly in the Google Cloud Console — including the right package name, SHA-1 fingerprint, and client IDs for Android, iOS, and web — is critical, as misconfigurations cause silent sign-in failures. This method is particularly suited for projects that already have their own user management and session systems, where adding Firebase would introduce unnecessary complexity.

0 comments Read more at DEV Community