# configuration Configuration is the conditions, parameters, and specifications by which an information system or system component is described or arranged. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## New in Symfony 8.2: One Bundle per Component DevFeed: [New in Symfony 8.2: One Bundle per Component]() Original publisher: [Read original article]() Author: Javier Eguiluz Published: 2026-09-18T07:58:00Z Content type: article Language: en Sources: [Symfony Blog]() Topics: [Symfony](), [configuration]() Tags: [component](), [configuration](), [deprecated](), [forms](), [new-features](), [routing](), [services](), [symfony](), [validation]() ### AI overview Symfony 8.2 gives each component its own bundle, including its configuration, services, and related classes. Existing configuration keys continue to work through automatic registration and configuration aliasing, while several defaults and class locations change. ### Source excerpt Contributed by Nicolas Grekas in #65948 ,... ## Week Ending September 13, 2026 DevFeed: [Week Ending September 13, 2026]() Original publisher: [Read original article]() Published: 2026-09-18T06:22:00Z Content type: news Language: en Sources: [Last Week in Kubernetes Development]() Topics: [Kubernetes](), [releases](), [SDKs](), [Go Language](), [Post-Quantum](), [Security](), [TypeScript](), [configuration](), [Python]() Tags: [configuration](), [developer](), [go](), [instrumentation](), [kubernetes](), [news](), [post-quantum](), [release](), [sdks](), [security]() ### AI overview Developer News summarizes Kubernetes project updates for the week ending September 13, 2026, including kubelet static-binary discussions, SIG leadership and subprojects, AI Conformance changes, Agent Sandbox v1.0, the Kubernetes v1.38 release cycle, memory-management configuration, and post-quantum certificate support. ### Source excerpt Developer News ## Jemalloc 5.4 Released With Portability Improvements, Code Cleanups DevFeed: [Jemalloc 5.4 Released With Portability Improvements, Code Cleanups]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-17T22:37:11Z Content type: release Language: en Sources: [Phoronix]() Topics: [Code](), [Refactoring](), [test-coverage](), [bug](), [cpu](), [gcc](), [configuration]() Tags: [bug](), [code](), [configuration](), [cpu](), [desktop-linux](), [error-handling](), [gcc](), [improvements](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [process](), [profiling](), [refactoring](), [synchronization](), [test-coverage](), [thread](), [ubuntu-benchmarks](), [ubuntu-hardware](), [yield]() ### AI overview Jemalloc 5.4 is released with portability improvements, code refactoring, bug fixes, expanded test coverage, new allocation features, optimizations, and GCC 16 warning fixes. The release adds an operating-system abstraction layer for platform-dependent operations. ### Source excerpt Earlier this year Meta announced a renewed investment into the jemalloc memory allocator that's been popular for server and HPC use among various desktop use-cases too. After stagnating a bit in recent years, Jemalloc has been off to seeing new developments since Meta's announcement and out today is Jemalloc 5.4 as the latest step forward... ## Microsoft configuration change leaves SharePoint pages drawing a blank DevFeed: [Microsoft configuration change leaves SharePoint pages drawing a blank]() Original publisher: [Read original article]() Author: Richard Speed Published: 2026-09-17T15:17:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [configuration](), [Microsoft](), [Deployment]() Tags: [configuration](), [deployment](), [microsoft](), [microsoft-365](), [saas]() ### AI overview The document reports that a Microsoft configuration change caused SharePoint pages to display blank, with validation apparently occurring after deployment. ### Source excerpt Validation? Apparently that comes after deployment ## Announcing Microsoft Desired State Configuration v3.3.0 DevFeed: [Announcing Microsoft Desired State Configuration v3.3.0]() Original publisher: [Read original article]() Author: Jason Helmick Published: 2026-09-17T14:57:07Z Content type: release Language: en Sources: [PowerShell Team]() Topics: [PowerShell DSC](), [PowerShell](), [Windows](), [configuration](), [Model Context Protocol]() Tags: [announcement](), [configuration](), [mcp](), [microsoft](), [powershell](), [powershell-dsc](), [updates](), [v3](), [windows]() ### AI overview This release announcement covers the general availability of Microsoft Desired State Configuration v3.3.0. It describes new built-in Windows resources, a registry-backed adapter, expanded support, experimental export filtering, expression function updates, and Linux packages. ### Source excerpt This post announces the General Availability of Microsoft Desired State Configuration (DSC) v3.3.0, with new Windows resources, a registry adapter, server mode improvements, expression function updates, expanded what-if support, and experimental export filtering. The post Announcing Microsoft Desired State Configuration v3.3.0 appeared first on PowerShell Team. ## 7 Proxmox Checks I Make Before I Trust a New Host DevFeed: [7 Proxmox Checks I Make Before I Trust a New Host]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-17T12:55:35Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Proxmox](), [virtualization](), [configuration](), [Server](), [patches](), [Authentication](), [certificates](), [Logging](), [Kernel]() Tags: [authentication](), [certificates](), [configuration](), [kernel](), [logging](), [patches](), [proxmox](), [security](), [server](), [virtualization]() ### AI overview A practical checklist for validating a new Proxmox VE host before moving important virtual machines or containers onto it. The checks cover hostname, DNS, time synchronization, repositories, updates, kernel versions, and related system readiness concerns. ### Source excerpt Installing Proxmox VE Server on a new host or mini PC is the easy part in most cases. This process is usually a non event as you just have the... The post 7 Proxmox Checks I Make Before I Trust a New Host appeared first on Virtualization Howto. ## Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator DevFeed: [Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator]() Original publisher: [Read original article]() Author: Anil Joshi Published: 2026-09-17T06:43:32Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [Replication](), [export](), [Percona Server for MySQL](), [configuration](), [Server](), [Kubernetes](), [Database]() Tags: [cloud](), [configuration](), [database-trends](), [featured](), [innodb-clusterset](), [insight-for-dbas](), [kubernetes](), [kubernetes-operators](), [mysql](), [mysql-group-replication](), [mysql-high-availability](), [mysql-replication](), [open-source](), [operator](), [percona-kubernetes-operators](), [percona-operator-for-mysql](), [percona-server-for-mysql](), [percona-software](), [replication](), [uncategorized](), [yaml]() ### AI overview This tutorial explains how to configure cross-site replication between two Percona Operator for MySQL clusters to create a ClusterSet environment for disaster recovery and switchover between data-center and disaster-recovery members. It covers deploying the clusters, retrieving endpoints and cluster names, transferring credentials, and initializing the DR cluster. ### Source excerpt A while ago, we discussed the cross-site replication feature of the Percona PXC operator. Recently, a similar cross-site replication feature was introduced in the Percona (PS MySQL) operator v1.2.0, a topology based on Group Replication/InnoDB Cluster. In this blog post, we will explore how to add a DR Cluster to an existing DC Cluster to ... Continued The post Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator appeared first on Percona. ## Libreboot 20231021 released! DevFeed: [Libreboot 20231021 released!]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [coreboot](), [Hardware](), [boot](), [configuration](), [x86]() Tags: [article](), [asus](), [bios](), [boot](), [build-system](), [canoeboot](), [configuration](), [coreboot](), [free-software](), [hardware](), [libre](), [libreboot](), [opensource](), [release](), [uefi](), [workstation](), [x86]() ### AI overview Libreboot 20231021 is presented as a new testing release of Libreboot, with build-system improvements and the re-addition of three ASUS boards: KFSN4-DRE, KCMA-D8, and KGPE-D16. The release provides boot firmware for supported x86 and ARM machines and includes coreboot-based firmware support for the listed boards. ### Source excerpt Article: Libreboot 20231021 released! Web link: https://libreboot.org/news/libreboot20231021.html ## Binary Blob Reduction Policy DevFeed: [Binary Blob Reduction Policy]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [coreboot](), [configuration](), [Code]() Tags: [bios](), [canoeboot](), [code](), [configuration](), [coreboot](), [firmware](), [free-software](), [libre](), [libreboot](), [opensource](), [policy](), [uefi]() ### AI overview Libreboot's policy seeks to maximize software freedom across supported hardware by helping users study, modify, and share the project's source code and documentation. The article explains Libreboot's relationship to coreboot, its support for non-technical users, and its principled approach to reducing proprietary binary blobs and vendor code where possible. ### Source excerpt Article: Binary Blob Reduction Policy Web link: https://libreboot.org/news/policy.html ## Libreboot 20160818 release DevFeed: [Libreboot 20160818 release]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [coreboot](), [boot](), [configuration](), [cpu](), [Linux](), [LVM]() Tags: [article](), [bios](), [boot](), [canoeboot](), [configuration](), [coreboot](), [cpu](), [free-software](), [grub](), [libre](), [libreboot](), [linux](), [lvm](), [opensource](), [release](), [uefi]() ### AI overview The Libreboot 20160818 release introduces hardware and usability improvements compared with Libreboot 20150518, including increased VRAM allocations, improved video performance and battery life on supported systems, better display handling, and improved GRUB configuration and automatic Linux configuration discovery. ### Source excerpt Article: Libreboot 20160818 release Web link: https://libreboot.org/news/libreboot20160818.html ## Introducing Astra for Law DevFeed: [Introducing Astra for Law]() Original publisher: [Read original article]() Published: 2026-09-17T00:00:00Z Content type: release Language: en Sources: [OpenAI News]() Topics: [gpt-6-astra](), [OpenAI](), [Artificial Intelligence](), [API](), [configuration](), [context](), [Benchmark](), [ChatGPT]() Tags: [ai](), [api](), [astra](), [benchmark](), [capabilities](), [company](), [gpt-6-astra](), [openai](), [privacy]() ### AI overview OpenAI introduces Astra for Law, a legal AI foundation combining GPT-6 Astra with tailored settings, tools, context, legal search, privacy controls, and ecosystem plugins. It is designed for law firms and legal technology companies to build applications and workflows, with API access for customers such as Harvey and Legora. ### Source excerpt OpenAI for Law brings frontier intelligence for law, custom firm workflows, connected legal data sources, and legal-grade controls for confidential client work. ## AWS reimagines the getting started experience DevFeed: [AWS reimagines the getting started experience]() Original publisher: [Read original article]() Author: Micah Walter Published: 2026-09-16T17:50:14Z Content type: release Language: en Sources: [AWS News Blog]() Topics: [Amazon Web Services](), [AWS IAM](), [configuration](), [App]() Tags: [announcements](), [aws](), [aws-management-console](), [configuration](), [developers](), [free](), [getting-started](), [launch](), [news](), [permissions](), [project](), [team]() ### AI overview AWS announces a simplified getting-started experience with sensible defaults, managed project environments, simplified permissions, and $100 in Free Tier credits for most new customers. Customers can later activate advanced AWS features without migrating. ### Source excerpt AWS has reimagined the getting started experience with smart and sensible defaults to help developers get started fast so that they can focus on building. New customers can sign up and get started right away with $100 in Free Tier credits, managed project environments, and simplified team and resource permissions. If their workload evolves, customers can activate advanced features to access the full breadth and depth of AWS in one step, with no migration required. ## Native Splunk brings real-time insights to Cisco Nexus One DevFeed: [Native Splunk brings real-time insights to Cisco Nexus One]() Original publisher: [Read original article]() Author: David Keith Published: 2026-09-16T15:00:59Z Content type: release Language: en Sources: [Cisco Blogs]() Topics: [Nexus Dashboard](), [observability](), [telemetry](), [datacenter](), [Security](), [sensitive data](), [audit](), [configuration]() Tags: [analytics](), [audit](), [cisco](), [cisco-nexus-dashboard](), [configuration](), [data-center](), [data-center-networking](), [network](), [nexus-one](), [observability](), [real-time](), [sensitive-data](), [splunk](), [troubleshooting]() ### AI overview Cisco describes native Splunk embedded in Cisco Nexus Dashboard as an on-premises analytics and observability capability for data center and AI workloads. It processes telemetry locally, correlates network, security, configuration, and audit data, and provides dashboards, searches, and alerts for troubleshooting, data sovereignty, compliance, and cost efficiency. ### Source excerpt Discover how native Splunk embedded in Cisco Nexus Dashboard delivers real-time analytics, faster troubleshooting, and on-premises data sovereignty for modern data center and AI workloads. ## Why Kafka retention.ms can delay message deletion DevFeed: [Why Kafka retention.ms can delay message deletion]() Original publisher: [Read original article]() Author: Rogerio Santos Published: 2026-09-16T13:05:06Z Content type: tutorial Language: en Sources: [Red Hat](), [Red Hat Developer]() Topics: [Kafka](), [Apache-Kafka](), [configuration](), [file](), [Event-Streaming]() Tags: [broker](), [configuration](), [diagnose](), [event-driven](), [how-to](), [kafka](), [lifecycle](), [retention](), [storage](), [stream-processing]() ### AI overview This guide explains why Kafka messages can remain readable beyond a topic's retention.ms setting. Kafka deletes closed log segments rather than individual messages, and the active segment and continuous writes can delay removal of older records. ### Source excerpt A customer opened a support case with a deceptively simple complaint: a Kafka topic was configured with a 12-hour retention (retention.ms), yet messages produced on July 24 were still readable 4 days later, on July 28. Nothing was broken. The broker logged no errors. The retention policy was working as designed, but the segment layout and continuous write pattern delayed when the old records could actually be removed. The post Why your Kafka topic ignores retention.ms (and how to fix it) appeared first on Red Hat Developer. ## sem-ai 0.4.0: smaller responses, safer access, and pre-flight checks DevFeed: [sem-ai 0.4.0: smaller responses, safer access, and pre-flight checks]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-09-16T12:01:04Z Content type: release Language: en Sources: [Semaphore Engineering]() Topics: [AI-assisted coding](), [Claude Code](), [Command-line interface](), [Authorization](), [API](), [configuration]() Tags: [ai-coding-agents](), [api](), [audio](), [claude-code](), [command-line](), [configuration](), [permissions](), [pipelines](), [product-news](), [release](), [video]() ### AI overview Semaphore's sem-ai 0.4.0 release adds more compact workflow and pipeline responses, context switching across organizations and credentials, and support for managing pre-flight checks. The update is aimed at reducing context usage and enabling more targeted permissions for AI coding agents. ### Source excerpt AI coding agents work best when they receive the right information without unnecessary noise. They also need clearly defined permissions and reliable safeguards for the changes they make. sem-ai 0.4.0 improves all three areas. The release introduces more compact pipeline responses, flexible context switching, and support for Semaphore pre-flight checks. Watch Nick demonstrate the new [...] The post sem-ai 0.4.0: smaller responses, safer access, and pre-flight checks appeared first on Semaphore. ## The weekly snippet-server: open-sourced DevFeed: [The weekly snippet-server: open-sourced]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-02-01T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Snippet](), [configuration](), [email](), [Markdown]() Tags: [configuration](), [email](), [engineering](), [infrastructure](), [markdown](), [news](), [open](), [snippet]() ### AI overview Craig Silverstein describes Khan Academy's open-sourced weekly snippet server, a simple tool for sharing brief weekly work updates. It uses a textbox with optional Markdown formatting and makes snippets visible according to email-domain and server configuration. ### Source excerpt By Craig Silverstein When I joined Khan Academy, my first project was to write a version of the ... Read more ## Shared Selective Persistent Memory for Agentic LLM Systems DevFeed: [Shared Selective Persistent Memory for Agentic LLM Systems]() Original publisher: [Read original article]() Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [Apple Machine Learning Research]() Topics: [Large Language Model](), [agent observability](), [Framework](), [Code](), [configuration](), [Access Control](), [Git](), [Model Context Protocol (MCP)](), [CSV](), [SQL](), [Grafana]() Tags: [access-control](), [agentic](), [agents](), [code](), [configuration](), [csv](), [dashboards](), [git](), [llm](), [mcp](), [memory](), [platform](), [replication](), [sql]() ### AI overview This research introduces shared selective persistent memory for agentic LLM systems. The architecture retains reusable task specifications, data schemas, tool configurations, and output constraints while discarding session-specific reasoning traces. Shared workspaces support role-based collaborative reuse, and experiments report higher task completion than no memory or full-history persistence, along with zero-token data refresh and lower token costs. ### Source excerpt Agentic LLM systems that generate code through multi-turn tool use face a fundamental context problem: each session starts from zero, discarding the configuration choices, domain constraints, data schemas, and tool-use patterns that made previous sessions productive. Naively persisting entire conversation histories is both token-inefficient and counterproductive--irrelevant context degrades generation quality. We introduce shared selective persistent memory, a memory architecture for agentic systems that identifies and retains four categories of reusable context--task specifications, data... ## pgAssistant 3.8.0 : continuous improvement loop for Postgres DevFeed: [pgAssistant 3.8.0 : continuous improvement loop for Postgres]() Original publisher: [Read original article]() Author: Pgassistant Dev Team Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [PostgreSQL](), [Monitoring](), [recommendations](), [configuration](), [real-time]() Tags: [configuration](), [measurements](), [monitoring](), [postgres](), [postgresql](), [real-time](), [recommendations](), [release]() ### AI overview pgAssistant 3.8.0 expands the PostgreSQL analysis and tuning tool into a continuous improvement platform. It adds historical workload and environment measurements, compares consecutive collections, tracks recommendations and configuration changes, and helps teams measure changes while distinguishing correlation from causation. ### Source excerpt With this release, pgAssistant is evolving beyond PostgreSQL analysis and tuning to become a continuous PostgreSQL improvement platform. The new positioning is built around a continuous improvement loop: Observe -> Diagnose -> Prioritize -> Plan -> Implement -> Collect again -> Measure pgAssistant already helped identify what should be improved and turn recommendations into a prioritized Executive Plan with clear DEV and OPS ownership. Combined with pgAssistant Collector, version 3.8.0 goes further by adding historical workload and environment measurements. The objective is to answer four essential questions: What should we improve? What did we decide to do? What did we actually change? What was the result? Workload Insights compares consecutive collections and highlights: new and no-longer-detected recommendations; changes to the PostgreSQL version and configuration; workload evolution by statement type; changes in execution time and call volume; the queries with the greatest impact on the overall workload. The ambition is to correlate the application of pgAssistant recommendations and the Executive Plan with observed performance changes. Correlation is not causation, and a recommendation that is no longer detected does not necessarily prove that it was implemented. pgAssistant keeps these distinctions explicit while bringing the relevant evidence together in one place. pgAssistant is not intended to replace real-time monitoring. Monitoring shows what is happening now; pgAssistant helps teams decide what to improve next, organize the remediation work, and measure what changed afterwards. From recommendations to action--and from action to measurable evidence. pgAssistant 3.8.0: https://github.com/beh74/pgassistant-community pgAssistant Collector: https://github.com/beh74/pgassistant-collector pgAssistant Grafana : https://github.com/beh74/pgassistant-grafana ## Google tag gateway: Now on Webflow DevFeed: [Google tag gateway: Now on Webflow]() Original publisher: [Read original article]() Author: Webflow Team Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [Webflow Blog]() Topics: [gateway](), [webflow](), [Google](), [Confidential Computing](), [data](), [configuration](), [Deployment]() Tags: [confidential-computing](), [configuration](), [conversion](), [data](), [deployment](), [development](), [gateway](), [google](), [measurement](), [webflow]() ### AI overview Webflow announces Google tag gateway, which routes conversion data through a site's first-party infrastructure. Existing native Google tag integration users can activate it by republishing their site, while new users can follow a code-free setup workflow. ### Source excerpt When you build on Webflow, you're creating experiences designed to help your business stand out and grow. Underpinning those experiences with a strong measurement foundation can help you understand what's driving results and make more informed marketing decisions. Now, Webflow makes it easier to strengthen your measurement foundation. ## Cisco UCS Manager: Celebrating the legacy, shaping the future with Cisco Intersight DevFeed: [Cisco UCS Manager: Celebrating the legacy, shaping the future with Cisco Intersight]() Original publisher: [Read original article]() Author: Jacob Van Ewyk Published: 2026-09-15T21:00:37Z Content type: opinion Language: en Sources: [Cisco Blogs]() Topics: [Cisco](), [Server](), [Automation](), [configuration](), [API](), [legacy]() Tags: [api](), [automation](), [cisco](), [data-center](), [end-of-life](), [eol](), [infrastructure](), [legacy](), [lifecycle](), [management](), [server]() ### AI overview Cisco describes the legacy of Cisco UCS Manager and positions Cisco Intersight as the strategic platform for future Cisco UCS software management. The article also outlines announced end-of-sale and end-of-life milestones, including a planned Last Date of Support of December 31, 2030, subject to applicable contracts and service terms. ### Source excerpt Cisco UCS Manager shaped 17 years of infrastructure management. Now, with its end-of-life announced, Cisco Intersight carries that foundation forward with centralized visibility, automation, and scale. Learn the key dates for the UCS Manager EOL. ## Kubernetes v1.37: Memory QoS Graduates to Beta DevFeed: [Kubernetes v1.37: Memory QoS Graduates to Beta]() Original publisher: [Read original article]() Author: Qi Wang; Sohan Kunkerkar Published: 2026-09-14T18:30:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [releases](), [configuration](), [Linux](), [Kernel]() Tags: [clusters](), [configuration](), [container](), [kernel](), [kubernetes](), [linux](), [memory](), [qos](), [releases](), [upgrade](), [v1]() ### AI overview Kubernetes v1.37 promotes Memory QoS to Beta and enables it by default on Linux nodes using cgroup v2. The article explains the updated defaults, configuration options for memory throttling and tiered memory protection, and upgrade behavior intended to preserve existing runtime behavior. ### Source excerpt Memory QoS has graduated to Beta in Kubernetes v1.37 and is now enabled by default. On Linux nodes running cgroup v2, the feature uses the memory controller to give the kernel better guidance on how to treat container memory. It was first introduced as Alpha in v1.22, and expanded in v1.36 with tiered memory reservation. This post covers what changed in v1.37, what the Beta promotion means for cluster operators, and how to configure the feature. What changed in v1.37Memory QoS is Beta and enabled by default The MemoryQoS feature gate is now Beta in v1.37. This means every v1.37 kubelet has the feature gate turned on without any configuration change. Turning on the feature by default is safe because the default kubelet configuration does not enable memory throttling or memory reservation. No memory.high, memory.min, or memory.low values are written to cgroups unless you explicitly configure them. You can opt into specific behaviors through kubelet configuration fields: Set memoryThrottlingFactor (for example, 0.9) to enable memory.high throttling on Burstable and BestEffort containers. The default is null, which means no throttling. Set memoryReservationPolicy to TieredReservation to enable tiered memory protection via memory.min and memory.low. The default is None, which means no memory reservation. Default memoryThrottlingFactor changed to null In earlier Alpha releases, memoryThrottlingFactor defaulted to 0.9, which meant enabling the feature gate caused the kubelet to set memory.high on containers. In v1.37, the default is null, so the kubelet does not set memory.high unless you configure a value. This change was made because, with the feature gate now on by default, an automatic memory.high could throttle workloads that were previously running without throttling. Making it null ensures that upgrading to v1.37 does not change runtime behavior for existing clusters. If your kubelet configuration file already contains an explicit memoryThrottlingFactor value, that ## 🍔🧠 Pinterest's Fix for the Hardest Problem in ML Infra DevFeed: [🍔🧠 Pinterest's Fix for the Hardest Problem in ML Infra]() Original publisher: [Read original article]() Author: Alexandre Zajac Published: 2026-09-14T15:31:30Z Content type: article Language: en Sources: [Hungry Minds]() Topics: [recommendation systems](), [Feature Engineering](), [Inference](), [Streaming](), [configuration](), [Framework](), [data](), [Low Latency]() Tags: [batch](), [configuration](), [data](), [feature-engineering](), [low-latency](), [ml](), [pinterest](), [ranking](), [recommendation-systems](), [streaming]() ### AI overview Pinterest redesigned its user-sequence platform for ranking, retrieval, and recommendation systems by defining signals once and instantiating them consistently across streaming, batch, and serving workloads. The approach uses Python configuration with validated schemas, a shared execution engine, cooperating streaming and batch paths, and columnar time-partitioned storage to improve freshness, completeness, consistency, and operational efficiency. ### Source excerpt PLUS: OpenAI agents beat math 🧮, Test techniques for agents ⚡, Postgres survival guide 📖 ## nginx: The Map Variable That Fixes the URI in proxy\_pass DevFeed: [nginx: The Map Variable That Fixes the URI in proxy\_pass]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-14T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [nginx](), [proxy](), [Caching](), [configuration]() Tags: [cache-control](), [ci-cd](), [configuration](), [docker](), [networking](), [nginx](), [observability](), [proxy](), [reverse-proxy]() ### AI overview This article explains an nginx build failure caused by using a URI-bearing proxy_pass inside a regex location. A newer nginx version treated the previously accepted configuration as an error. The proposed fix uses a bare upstream in the regex location and a map on $uri to apply a path-specific Cache-Control policy. ### Source excerpt nginx: [emerg] invalid URI prefix in proxy_pass: a regex location needs a bare upstream, and a map on $uri keeps a path-specific Cache-Control header. ## Configuring Management IP Addresses to Virtual Network Devices DevFeed: [Configuring Management IP Addresses to Virtual Network Devices]() Original publisher: [Read original article]() Published: 2026-09-14T05:29:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [configuration](), [Orchestration](), [Vagrant](), [Cloud](), [ssh]() Tags: [cli](), [cloud](), [devices](), [dhcp](), [ip](), [ipv4](), [ipv6](), [management](), [netlab](), [network](), [networking](), [orchestration](), [server](), [ssh]() ### AI overview The article explains how to assign predictable management IP addresses to virtual network devices. It contrasts manual console-based setup with automated assignment through orchestration, containers, DHCPv4/DHCPv6, custom Vagrant boxes, and IPv6 mechanisms such as SLAAC. ### Source excerpt It goes without saying that if you want to configure (virtual) network devices with any semi-sane configuration mechanism1, the device must have a working IP address. Here's the time-honored method2 to assign an IP address to a virtual network device: Start the virtual machine (using a GUI)3 Open a new window: either a telnet session to the virtual console port or a full-blown virtual console (GUI) session. Manually configure the IP address, the SSH server, and the user credentials on the first interface. Read more ... [Next page]()