# critical Published articles for critical. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Critical correctness bug in Lix DevFeed: [Critical correctness bug in Lix]() Original publisher: [Read original article]() Published: 2025-06-27T00:00:00Z Content type: news Language: en Sources: [News on Lix]() Topics: [bug](), [incident](), [Nix](), [Linux](), [Deployment Tools]() Tags: [bug](), [critical](), [incident](), [linux]() ### AI overview A critical regression in Lix versions 2.91.2, 2.92.2, and 2.93.1 can cause missing or silently invalidated store paths during derivation builds. The incident has been mitigated; versions 2.91.3, 2.92.3, and 2.93.2 are identified as unaffected, with recovery guidance provided. ### Source excerpt This incident has been mitigated. This post will be updated with pointers on how to close it. The Lix team remains available over all support channels to help recovering any system affected by it. ## A Java Conversion Puzzler: Understanding Implicit Casting and Overflow DevFeed: [A Java Conversion Puzzler: Understanding Implicit Casting and Overflow]() Original publisher: [Read original article]() Author: Peter Lawrey (noreply@blogger.com) Published: 2024-12-07T22:23:00Z Content type: article Language: en Sources: [Vanilla Java]() Topics: [Java](), [floating-point](), [Code]() Tags: [code](), [critical](), [exercise](), [floating-point](), [info](), [java](), [performance](), [puzzles]() ### AI overview This article explains a Java conversion puzzle involving compound assignment, implicit casting, floating-point rounding, and integer overflow. It shows why adding 0.0f can produce different results for int and long values, including a conversion to Integer.MIN_VALUE when the rounded value is cast back to int. ### Source excerpt This article explores a subtle Java conversion puzzle that challenges assumptions about how arithmetic operations, implicit casting, and floating-point conversions interact. Inspired by complexities often encountered in low-latency and high-performance environments, it demonstrates why a keen understanding of Java's type system is essential for building reliable and efficient applications. Introduction The following example demonstrates a scenario where an innocuous-looking arithmetic operation leads to a surprising result. While such questions are rare and arguably impractical, they highlight subtle behaviours that can affect correctness and performance, especially in critical systems like high-frequency trading platforms or complex data-processing pipelines. The Problem: A Surprising Print Statement Consider the following code: int i = Integer.MAX_VALUE; i += 0.0f; int j = i; System.out.println(j == Integer.MAX_VALUE); // true At first glance, one might assume that adding 0.0f to an int should not change its value. Indeed, the output true reinforces this notion. However, if you change int i for long i, things get weird: long i = Integer.MAX_VALUE; // only the type of i is changed i += 0.0f; int j = (int) i; System.out.println(j == Integer.MAX_VALUE); // false System.out.println(j == Integer.MIN_VALUE); // true What is going on, you might wonder? Let me start by explaining why using a long gives such a strange result. Understanding the Implicit Casting The key detail lies in how Java handles the += operator. It is not strictly equivalent to a = a + b; but rather: a += b; has a subtle difference which most of the time doesn't matter: // has an implicity cast here a = (typeOf(a)) (a + b); Another subtle feature of addition is that the result is the "wider" of the two types. This means that: i += 0.0f; is actually: i = (int) ((float) i + 0.0f); // or i = (long) ((float) i + 0.0f); The result of (float) i can be imprecise due to floating-point rounding. A float has a 2 ## Effective Kotlin Item 2: Eliminate critical sections DevFeed: [Effective Kotlin Item 2: Eliminate critical sections]() Original publisher: [Read original article]() Published: 2023-08-28T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Concurrency](), [Kotlin](), [Concurrent Programming](), [Operating system]() Tags: [bugs](), [collections](), [cpu](), [critical](), [execution](), [kotlin](), [state](), [workshop-learning-programming]() ### AI overview This tutorial explains why concurrent modifications to shared mutable state can produce lost updates and incorrect object states. It introduces threads, time slicing, and synchronization concerns in Kotlin/JVM, using an incrementing-variable example and discussing bugs involving collections. ### Source excerpt Learn why do we need to synchronize access to mutable state, and how to secure it. ## Ways to Decrease Performance: Velocity Tracking DevFeed: [Ways to Decrease Performance: Velocity Tracking]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-07-15T06:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Agile](), [Software Engineering]() Tags: [agile](), [article](), [critical](), [measuring](), [metrics-practices-ways-to-decrease-performance-developer-productivity-engineering-excellence](), [performance](), [practices](), [story-points](), [teams](), [velocity]() ### AI overview This opinion article examines velocity tracking and estimation in Agile software teams. It explains how teams use story points, velocity trends, and burndown charts, then begins discussing how these practices can harm performance, including the limitations of human estimation. ### Source excerpt Ways to Decrease Performance: Velocity Tracking This is the first article of my series, "Ways to Decrease Performance", which intends to trigger critical reflection on common "Agile" practices, that is, practices that I see many "agile" teams doing. ## The future of Keycloak Operator CRs DevFeed: [The future of Keycloak Operator CRs]() Original publisher: [Read original article]() Author: Václav Muzikář Published: 2022-09-02T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Quarkus](), [Cloud](), [Git]() Tags: [critical](), [declarative](), [deprecated](), [eol](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [operator](), [quarkus](), [rest-api](), [saml](), [source-of-truth](), [sso](), [ui]() ### AI overview The article describes Keycloak's new Operator, rewritten for the Quarkus distribution and available as a preview. It explains that Custom Resource Definitions for managing Keycloak resources are not yet available because supporting features, including file storage and read-only interfaces, are still being developed. The CRDs were expected to be added with support anticipated in Keycloak 21. ### Source excerpt A while back, we have announced a new Operator rewritten from scratch to provide the best experience for the Quarkus distribution. While the legacy Operator is now deprecated and will reach EOL with Keycloak 20, the new one is already available as a preview, see the installation guide. One of the most common concerns around the new Operator is the current lack of the CRDs for managing Keycloak resources, such as realm, users and clients, in a cloud-native way. One of the key aspects of the new Operator will be redesign of managing these Keycloak resources via CRs and git-ops. This new approach will leverage the new storage architecture and future immutability options, making the CRs the declarative single source of truth. In comparison to the legacy Operator, this will bring high robustness, reliability, and predictability to the whole solution. Before we would consider operator ready for leveraging CRs, we expect completing several features including but not limited to: File store (expected in Keycloak 20) to persist data in a file instead of DB. Read-only possibilities for administration REST API, UI Console and other interfaces. This is required for the new immutability concept which will be used to ensure any data coming from the CRs (and subsequently from the file store) are read-only from all interfaces. All of this is critical to proper CRs implementation, hence the new Operator is currently missing the CRDs for managing Keycloak resources. The missing CRDs will be added once Keycloak has the necessary support for it, which is currently expected in Keycloak 21. We have prepared a few options to alleviate the situation with missing CRDs in this repository. ## Building an Application Security Team DevFeed: [Building an Application Security Team]() Original publisher: [Read original article]() Author: Jonathan Marcil Published: 2017-10-15T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Application Security](), [Security]() Tags: [application-security](), [critical](), [false-positives](), [red-team](), [security](), [team](), [teams]() ### AI overview The article discusses how to build an application security team and why the role requires both broad and specialized skills. It contrasts product-based security tools with penetration testing services, comparing their coverage, accuracy, false positives, creativity, and technical depth. It also describes the evolution of penetration testing toward Red Team operations. ### Source excerpt [no description provided] ## Implementing Critical CSS on your website DevFeed: [Implementing Critical CSS on your website]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-02-28T21:34:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [modern web development](), [Web Development](), [Front end](), [inlining](), [render](), [Website]() Tags: [article](), [browser](), [critical](), [development](), [essential](), [frontend](), [how-to](), [implementing](), [inlining](), [insights](), [modern](), [modern-web-development](), [performant](), [render](), [shows](), [website]() ### AI overview This tutorial explains Critical CSS, a method for extracting the CSS needed for above-the-fold content and inlining it so the browser can render the page immediately. It presents the technique as part of building performant websites. ### Source excerpt Implementing Critical CSS is an essential part of modern website development, this article shows you how to do it