# Crashes Published articles for Crashes. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## What to expect at the Zephyr Project Meetup (September 15, 2026) - Amsterdam, Netherlands DevFeed: [What to expect at the Zephyr Project Meetup (September 15, 2026) - Amsterdam, Netherlands]() Original publisher: [Read original article]() Author: Susan Remmert Published: 2026-09-09T05:00:04Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Embedded Systems](), [Fuzzing/Fuzz testing](), [Open Source]() Tags: [2026](), [blog](), [c](), [c-plus-plus](), [crashes](), [developer-tooling](), [embedded](), [embedded-systems](), [event](), [events](), [firmware](), [fuzzing](), [harness](), [jetbrains](), [meetup](), [memory-corruption](), [open-source](), [simulator](), [zephyr]() ### AI overview The Zephyr Project Meetup in Amsterdam on September 15, 2026, will bring together embedded developers, contributors, students, and engineers to share practical knowledge about Zephyr RTOS. The agenda includes talks on JetBrains' work with Zephyr, fuzzing Zephyr with AFL and Renode, and making hardware development easier with Schematik. ### Source excerpt What are developers in the Netherlands building with Zephyr? On September 15, the embedded community will meet in Amsterdam to exchange practical knowledge, discuss current work, and learn more about the Zephyr RTOS. The event is open to experienced contributors, first-time users, students, engineers, and anyone curious about open source embedded development. ## The thread is the Workflow: Durable AI agents without changing Agent code DevFeed: [The thread is the Workflow: Durable AI agents without changing Agent code]() Original publisher: [Read original article]() Author: Greg Haskins Published: 2026-09-03T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [AI Agent](), [Langgraph](), [Code](), [Framework]() Tags: [agent](), [ai-agents](), [community](), [crashes](), [durability](), [langgraph](), [state](), [workflow]() ### AI overview The article explains how Temporal Workflows add durable execution to LangGraph-based AI agents without requiring changes to the agent code. It describes mapping Agent Protocol Threads to Temporal Workflows, Runs to Activities, and checkpoints to Workflow state so executions can recover after worker crashes. ### Source excerpt Learn how Temporal Workflows can make LangGraph-based AI agents durable, preserving threads and checkpoints across crashes without changing agent code. ## Timers, Timeouts, and the Art of Waiting in Temporal DevFeed: [Timers, Timeouts, and the Art of Waiting in Temporal]() Original publisher: [Read original article]() Author: Joshua Smith Published: 2026-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [SDKs](), [Code](), [Processes]() Tags: [concurrent](), [crashes](), [deployment](), [developers](), [how-to](), [scaling](), [sdks](), [temporal-concepts](), [timeout](), [waiting]() ### AI overview This tutorial explains that Temporal timers provide durable business-logic waiting, while Activity and Workflow timeouts detect failures. It describes how timers survive Worker or process failures and can support large numbers of concurrent waits. ### Source excerpt Timers and timeouts look similar in Temporal but solve different problems. Learn how each one works and how to choose the right tool for durable waiting. ## Player sessions that survive anything DevFeed: [Player sessions that survive anything]() Original publisher: [Read original article]() Author: Cecil Phillip Published: 2026-05-28T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [sessions](), [Actor](), [backends](), [Processes](), [Server](), [Python]() Tags: [actor](), [backends](), [build](), [crashes](), [database](), [distributed](), [how-to](), [python](), [server](), [sessions](), [temporal-concepts](), [workflow]() ### AI overview This article presents a Temporal Python pattern for modeling each multiplayer player session as a durable, uniquely addressable Actor Workflow. The workflow keeps player state, resumes after server failures, coordinates game actions, and uses Continue-As-New to prevent unbounded history. ### Source excerpt Build multiplayer player sessions that survive server crashes. See how to model each player as a durable Actor Workflow in Temporal Python. ## Haskell Debugger for GHC 9.14 DevFeed: [Haskell Debugger for GHC 9.14]() Original publisher: [Read original article]() Published: 2026-01-07T00:00:00Z Content type: tutorial Language: en Sources: [Romes' Musings]() Topics: [debugging](), [Haskell](), [Neovim](), [Visual Studio Code](), [Protocol (disambiguation)](), [GitHub Issues]() Tags: [bytecode](), [crashes](), [debugger](), [debugging](), [editor](), [haskell](), [issue](), [performance](), [protocol](), [vscode]() ### AI overview This article announces that the Haskell Debugger is ready for GHC 9.14 and explains how to install it and configure editors through the Debug Adapter Protocol. It covers VSCode and Neovim integration, project-based session configuration, robustness goals, current limitations, and planned callstack and multithreading support. ### Source excerpt This post was first published inline to the Haskell Discourse, where there was some discussion about the debugger: 1 The Haskell Debugger for GHC 9.14 The Haskell Debugger is ready to use with GHC-9.14! The installation, configuration, and talks can be found in the official website. The tl;dr first step is installing the debugger: $ ghc --version # MUST BE GHC 9.14 The Glorious Glasgow Haskell Compilation System, version 9.14.1 $ cabal install haskell-debugger \ --allow-newer=base,time,containers,ghc,ghc-bignum,template-haskell \ --enable-executable-dynamic # ON WINDOWS, DO NOT PASS --enable-executable-dynamic ... $ ~/.local/bin/hdb --version # VERIFY IT'S THE LATEST! Haskell Debugger, version 0.11.0.0 The second step is configuring your editor to use the debugger via the Debug Adapter Protocol (DAP). - For VSCode, install the haskell debugger extension. - For Neovim, install nvim-dap and configure it for haskell-debugger - For other editors, consult your DAP documentation and let others know how! Bug reports and discussions are welcome in the haskell-debugger issue tracker. My MuniHac 2025 talk also walks through the installation, usage, and design of the debugger. Do note much has been improved since the talk was given, and much more will still improve. 1.1 A little bit more info The debugger work is sponsored by Mercury. It's the project in which I've spent most of my full working days (for almost a full year now), with the invaluable help from my team at Well-Typed. The debugger is meant to work both on trivial files and on large and complex codebases1. It is a GHC application so all features are supported. Like HLS, it also uses hie-bios to automatically configure the session based on your cabal or stack project. Robustness is a main goal of the debugger. If anything doesn't work, or if you have performance issues, or something crashes, please don't hesitate to submit a bug. We've got a small but respectable testsuite, and have tested performance by debugging G ## Carl Bialorucki hired to improve ReactOS test suite DevFeed: [Carl Bialorucki hired to improve ReactOS test suite]() Original publisher: [Read original article]() Published: 2025-07-04T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [Testing](), [Development](), [Windows](), [Kernel](), [WINE](), [x86]() Tags: [2025](), [automated](), [crashes](), [development](), [free](), [open-source](), [os](), [project](), [pull-requests](), [react](), [reactos](), [testing](), [win32](), [winapi](), [windows](), [wine](), [x86](), [x86-64]() ### AI overview Carl Bialorucki announces a full-time contract with ReactOS Deutschland e.V. to improve ReactOS's test infrastructure. The work targets failures, crashes, hangs, and bugchecks in kernel-mode and user-mode tests on newer Windows versions and x86 and x86_64 systems, while syncing Wine tests to Wine 10.0. ### Source excerpt Hi, my name is Carl J. Bialorucki. I started making a name for myself in the ReactOS community by contributing several shell improvements. In May of 2024 I was added to the core development team and in March of 2025 I led the release of ReactOS 0.4.15 after the previous release manager was unable to continue working on the project. I'm pleased to announce that I was hired for a full-time contract position with ReactOS Deutschland e.V. in May of 2025. ## Designing high-performance financial ledgers with Temporal DevFeed: [Designing high-performance financial ledgers with Temporal]() Original publisher: [Read original article]() Author: Tim Imkin Published: 2025-03-18T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Architecture & Design](), [Scalability](), [Transactions](), [Resilience](), [integrity]() Tags: [accounting](), [compliance](), [crashes](), [design](), [financial](), [fintech](), [high-performance](), [ledger](), [payment](), [performance](), [reconciliation](), [resilience](), [temporal-concepts]() ### AI overview The article discusses designing high-performance financial ledgers around scalable transaction handling, double-entry bookkeeping, flexible metadata, and resilient workflow coordination. It presents Temporal's durable execution as a way to address failures caused by network issues, service downtime, and process crashes. ### Source excerpt Learn how Temporal's durable execution solves core challenges -- scalability, reconciliation, and compliance -- to create reliable, future-proof ledger systems. ## Building resilient event-driven architecture for finance with Temporal DevFeed: [Building resilient event-driven architecture for finance with Temporal]() Original publisher: [Read original article]() Author: Tim Imkin Published: 2025-01-23T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [event driven](), [Architecture & Design](), [Orchestration](), [reliability](), [Scalability](), [Microservice](), [distributed-systems]() Tags: [business-logic](), [coupling](), [crashes](), [databases](), [distributed-systems](), [error-handling](), [event-driven-architecture](), [microservices](), [orchestration](), [reliability](), [retries](), [scalability](), [temporal-concepts]() ### AI overview This article examines the complexity of choreography-based event-driven architecture in financial services, including fragmented business logic, design-level coupling, decentralized error handling, and limited observability. It presents Temporal's durable execution and workflow orchestration as a centralized approach for building more resilient and maintainable systems. ### Source excerpt Discover how Temporal simplifies event-driven systems, replacing complexity with scalability, reliability, and centralized workflows. ## Mobile Observability Beyond Crash Tracking and Aggregate Metrics DevFeed: [Mobile Observability Beyond Crash Tracking and Aggregate Metrics]() Original publisher: [Read original article]() Author: Hanson Published: 2024-12-10T07:38:37Z Content type: opinion Language: en Sources: [hanson.wtf]() Topics: [observability](), [Mobile](), [Monitoring](), [telemetry]() Tags: [android](), [app-performance](), [crashes](), [latency](), [metrics](), [mobile](), [monitoring](), [observability](), [performance](), [sdks](), [tech](), [work]() ### AI overview The article argues that basic mobile monitoring, such as crash counts and aggregate performance metrics, does not provide true observability. It advocates actionable production data that helps developers investigate who is affected by issues and why. ### Source excerpt The Observability-Free Zone For most companies, "mobile observability" is a misnomer. I say this because the data that most mobile devs have to "observe" their app in production is laughably simplistic. The vast majority make due with basic crash tracking and precomputed metric aggregates as the only lens into how their app is performing in [...] ## Caffeine's Effects on Focus, Energy, Sleep, and Productivity DevFeed: [Caffeine's Effects on Focus, Energy, Sleep, and Productivity]() Original publisher: [Read original article]() Author: Richard Donovan Published: 2024-02-16T13:01:23Z Content type: opinion Language: en Sources: [The Modern Software Developer]() Topics: [Software](), [coding]() Tags: [crashes](), [dependency](), [developer](), [energy](), [headaches](), [mood](), [productivity](), [software-developer]() ### AI overview This commentary examines caffeine's short-term effects on focus and energy, its relationship to adenosine and tiredness, and the risks of dependence, jitters, crashes, disrupted sleep, and morning grogginess. It recommends balancing intake to avoid overreliance. ### Source excerpt Words < 950 - Read time < 5 mins ## Preventing WorkManager crashes when updating Android worker classes DevFeed: [Preventing WorkManager crashes when updating Android worker classes]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2022-04-27T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Android](), [migration](), [App](), [implementation]() Tags: [android](), [background-work](), [blogs](), [crash](), [crashes](), [implementation](), [lifecycle](), [migrate](), [retry](), [scheduled](), [workmanager]() ### AI overview This tutorial explains how Android WorkManager can crash after an app update when pending work references a worker class that was removed, renamed, or moved. It discusses cancelling or migrating pending work and using a custom WorkerFactory. ### Source excerpt WorkManager is great to schedule background work on Android. However, since scheduled work lives outside of the app lifecycle, you might run into unexpected crashes. ## Stressing memory on Android DevFeed: [Stressing memory on Android]() Original publisher: [Read original article]() Author: Amanjeet Singh Gurtatta Published: 2021-10-15T19:58:26Z Content type: tutorial Language: en Sources: [Amanjeet Singh]() Topics: [Android](), [Tool](), [observability](), [x86]() Tags: [android](), [crashes](), [devices](), [instrumentation](), [memory](), [mobile-performance](), [native](), [performance](), [processes](), [stress](), [stresstest](), [test](), [tool](), [x86]() ### AI overview This article explains how Android memory pressure can affect application processes, including native-memory risks and process killing by LMKD. It introduces stressapptest as a tool for reproducing memory pressure on test devices and validating instrumentation and crash-related behavior. ### Source excerpt This post talks about stressing memory on any android device and what happens when device is under memory pressure. ## Undetected NDK crashes during a Firefox Focus Android release DevFeed: [Undetected NDK crashes during a Firefox Focus Android release]() Original publisher: [Read original article]() Published: 2020-10-05T18:08:05Z Content type: opinion Language: en Sources: [Colin The Shots]() Topics: [Firefox](), [Android](), [Google Play](), [Google](), [browser](), [releases](), [bug](), [dashboards]() Tags: [android](), [c-plus-plus](), [chrome](), [code](), [crash-reporting](), [crashes](), [dashboards](), [firefox](), [google-play](), [releases](), [reporting](), [sentry](), [uncategorized]() ### AI overview A Mozilla engineer recounts how Firefox Focus 8.0.4 for Android developed previously undetected NDK crashes during its Christmas 2018 production rollout. Sentry and Socorro missed crashes occurring inside Chrome WebViews, while Google Play Console exposed them as the rollout expanded. ### Source excerpt I loved working at Mozilla for the almost two years that I spent there. But even a great job has hard days. The weeks around Christmas of 2018 were a stressful nightmare. I'd been working as the ## Implementing a Global try-catch for an Android Application DevFeed: [Implementing a Global try-catch for an Android Application]() Original publisher: [Read original article]() Author: Dmitry Samoylenko Published: 2020-08-19T00:00:00Z Content type: tutorial Language: en Sources: [Dmitry Samoylenko - Android Developer Blog]() Topics: [LineageOS](), [Java](), [Crashlytics](), [Firebase]() Tags: [android](), [crashes](), [crashlytics](), [firebase](), [java]() ### AI overview This Android tutorial explains how the ActivityThread and Looper architecture causes uncaught errors in activity or view callbacks to terminate an application. It presents a global error-handling approach that restarts the looper so the application can respond again, while recommending that caught crashes be sent to Firebase Crashlytics because they will no longer appear as standard crashes in Google Play reports. ### Source excerpt Where in the Application is the main() Method Hidden? ## Porting Syzkaller to ReactOS (Evaluation-1) - GSoC 2020 DevFeed: [Porting Syzkaller to ReactOS (Evaluation-1) - GSoC 2020]() Original publisher: [Read original article]() Published: 2020-06-30T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Fuzzing/Fuzz testing](), [boot](), [Google](), [coding]() Tags: [boot](), [coding](), [crashes](), [free](), [fuzzing](), [google](), [logging](), [open-source](), [os](), [react](), [reactos](), [results](), [ssh](), [win32](), [winapi]() ### AI overview A GSoC 2020 progress report describes porting Syzkaller to ReactOS. The author reports booting ReactOS with UBSan enabled, getting Syz-stress and Syz-executor working, adding initial kernel32 function definitions, and fuzzing ReactOS with about 107 definitions, which produced approximately four crashes. Planned work includes SSH access, rebasing, shared-memory and KCOV support, and automated virtual-machine fuzzing. ### Source excerpt Hey, I am Suraj K Suresh (@Freakston), In this post I'm going to be listing out what I've completed in Coding period-1 of GSoC. Status The initial part of setting up Syzkaller and being able to fuzz ReactOS is done. The link to grab ReactOS compatible syzkaller is as follows: Github. The detailed instruction on setting it up can be found here. Work-done Boot ReactOS with UBSan enabled. The branch which has UBSan enabled can be found in extravert34's fork of ReactOS. ## Porting Syzkaller to ReactOS - GSoC 2020 DevFeed: [Porting Syzkaller to ReactOS - GSoC 2020]() Original publisher: [Read original article]() Published: 2020-06-04T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Kernel](), [Testing](), [Google]() Tags: [crashes](), [free](), [gsoc](), [kernel](), [linux](), [open-source](), [os](), [porting](), [react](), [reactos](), [testing](), [win32](), [winapi]() ### AI overview A ReactOS GSoC student describes porting Syzkaller, a Google coverage-guided kernel fuzzer, to ReactOS. The work includes restoring Windows x64 and x86 support, adapting required synchronization functions, and investigating a zombie executor process. ### Source excerpt Hey, I am Suraj K Suresh (@Freakston), one of the GSoC students of ReactOS. This is the first time I've applied for GSoC and my mentors for the project are Victor Perevertkin and Timo Kreuzer. My project is "Porting Syzkaller to ReactOS". The project is getting one of the most famous Linux fuzzers to fuzz ReactOS. The project will lead to improvement of the kernel codebase by detecting code crashes. ## PG ConnectionBad (could not connect to server No such file or directory) DevFeed: [PG ConnectionBad (could not connect to server No such file or directory)]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-04-08T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Development](), [Homebrew](), [osx](), [Rails]() Tags: [crashes](), [development](), [errors](), [osx](), [personal](), [postgres](), [rails]() ### AI overview A troubleshooting note for a PostgreSQL connection error on an OSX Mojave development machine. It explains that a stale postmaster.pid file can make Homebrew falsely report PostgreSQL as running, and recommends verifying that PostgreSQL is stopped before removing the file and restarting the service. ### Source excerpt I've recently had the situation where my personal development box (OSX Mojave, Rails, Postgres) has become unstable with, at times, multiple crashes per day. I logged in this morning and found myself getting errors like this: PG::ConnectionBad (could not connect to server: No such file or directory) I did some digging and even though Postgres appeared to be running to brew, it was a false positive due to a leftover postmaster.pd file. Here was the fix: First make sure that postgres isn't running use ps i.e. **ps auwwx grep post**. Delete the file: /usr/local/var/postgres/postmaster.pid i.e. rm /usr/local/var/postgres/postmaster.pid At this point brew will, foolishly and oddly, still think Postgres is running so do do a brew restart postgres Here's a handy Stack Overflow reference. Note: Make absolutely sure that postgres is NOT running before you delete postmaster.pid or you risk serious database corruption / data loss. ## From RxJava to Kotlin Flow: Error Handling DevFeed: [From RxJava to Kotlin Flow: Error Handling]() Original publisher: [Read original article]() Published: 2020-02-24T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [kotlin-flow](), [RxJava](), [Error Handling](), [reactive](), [Exception](), [Coroutines](), [Programming]() Tags: [coroutine](), [crashes](), [error-handling](), [exception](), [kotlin](), [kotlin-flow](), [reactive](), [rxjava]() ### AI overview This tutorial compares error handling in RxJava and Kotlin Flow. It explains that RxJava propagates stream errors as terminal events to an Observer's onError callback, while Kotlin Flow uses coroutine exception handling, including try-catch and propagation to parent jobs or coroutine scopes. ### Source excerpt Source This post is part of series of comparing RxJava to Kotlin Flow. Previous articles were about Threading and Backpressure. Introduction Error handling is fundamental in reactive programming. Reactive streams might fail with exception and propagate it as an event downstream notifying consumers on the error that happened. As in previous articles, we'll try to compare RxJava and Kotlin Flow error handling mechanisms. This might help us to migrate existing code from RxJava to Kotlin Flow and also understand how to properly use Kotlin Flow. ## Why Some Applications Should Crash on Unhandled Exceptions DevFeed: [Why Some Applications Should Crash on Unhandled Exceptions]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2017-03-08T00:00:00Z Content type: opinion Language: en Sources: [Jeroen Mols]() Topics: [App](), [exceptions](), [Code]() Tags: [android](), [app](), [architecture](), [blogs](), [cleancode](), [code](), [crash](), [crashes](), [developers](), [exceptions](), [issue](), [notify](), [production](), [state](), [tips](), [trace]() ### AI overview This article argues that applications should sometimes crash when they reach an unsupported state. It uses null checks as an example, explaining that excessive checks can clutter code and conceal deeper issues, while unhandled exceptions can expose problems through crashes, traces, and crash reporting. ### Source excerpt Too many times I've seen developers trying to avoid crashes at all cost. But are unhandled exceptions really that bad? And are null checks really the answer? ## USB stack improvements GSoC - Week 7 DevFeed: [USB stack improvements GSoC - Week 7]() Original publisher: [Read original article]() Published: 2016-07-12T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [USB](), [ReactOS](), [Refactoring](), [Open Source](), [Programming]() Tags: [crashes](), [free](), [gsoc](), [improvements](), [open-source](), [os](), [react](), [reactos](), [refactoring](), [usb](), [win32](), [winapi](), [windows]() ### AI overview A Week 7 GSoC report on ReactOS USB stack work describes fixes to hub and Plug and Play interface handling, device creation routines, and existing functions. Testing found that physical-device removal crashes were gone, and a USB flash drive and composite device worked after reconnection. ### Source excerpt I'll start this report from the good news. After starting GSoC's coding period, I was doing fixes and improvements of hub layer and was not repeating tests which was done by me in community bonding period (results provided in my first blog post). So by the end of this week I decided to test surprise-removal on VBox with 2k3 working with our USB stack. As result I saw that crashes on device removal (physical) are gone! ## USB 1.1 UHCI improvements GSoC - Week 4 DevFeed: [USB 1.1 UHCI improvements GSoC - Week 4]() Original publisher: [Read original article]() Published: 2016-06-20T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [USB](), [debugging](), [Memory Leaks](), [Programming]() Tags: [crashes](), [debugging](), [free](), [guides](), [memory-leaks](), [open-source](), [os](), [programming](), [react](), [reactos](), [usb](), [win32](), [winapi]() ### AI overview This Week 4 progress report describes debugging ReactOS USB hub unload crashes and investigating PnP request handling in the WDM-based USB stack. Two crash-causing issues were fixed, allowing usbhub to be uninstalled with usbccgp loaded, although memory leaks and other stack issues remained. ### Source excerpt TO LEARN HOW TO SWIM, YOU NEED TO GET INTO THE WATER. At the start of the week I was debugging the system crash on ROS's usbhub unload in Win2k3. I spent a lot of time asking questions and discussing topics related to WDM with my mentor Thfabba. He kind of kickstarted me, giving small tasks and then analyzing with me the results. During that sessions I have gathered many new tips related debugging and also started feeling much more confidently working with WDM. ## Google SoC lwIP Report Week 3 DevFeed: [Google SoC lwIP Report Week 3]() Original publisher: [Read original article]() Published: 2016-06-12T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [lwIP](), [Data structures](), [SOC](), [client](), [Google](), [Server]() Tags: [client](), [crashes](), [data-structure](), [free](), [google](), [lwip](), [open-source](), [os](), [react](), [reactos](), [report](), [server](), [soc](), [tcp](), [win32](), [winapi]() ### AI overview A week-three development report on integrating lwIP with a driver. The author corrected IP address extraction and achieved a successful TCP connection, then investigated operating-system crashes caused by incorrect socket binding and connection-context handling. ### Source excerpt In week 3, I discovered a lot more about how data is being passed around. After more in depth inspection of the memory, I realized that Winsock was passing on the correct IP address; I just wasn't aware of the data structure it was using. After modifying my driver to correctly extract the IP address from the IRP, my test server and client performed a successful TCP connection hand shake, with my client program exiting correctly. ## June 2014 Meeting Minutes DevFeed: [June 2014 Meeting Minutes]() Original publisher: [Read original article]() Published: 2014-07-09T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [meetings](), [Development](), [bug]() Tags: [bug](), [complete](), [crashes](), [development](), [free](), [jira](), [meetings](), [memory](), [open-source](), [os](), [react](), [reactos](), [view](), [win32](), [winapi]() ### AI overview Minutes from ReactOS's June 2014 meeting, held on July 3, 2014, covering developer briefings and development priorities. Developers discussed work on memory management, the shell, shutdown support, infrastructure, the IRC bot, and ReactOS stability and promotion. ### Source excerpt Due to scheduling conflicts (World Cup) the June meeting was moved to July 3rd. 2014-07-03 19:00 UTC dev.reactos.org, #meeting Proceedings Meeting started at 19:22 by Aleksey Bragin. Point 1: Developer Briefings Point 2: Development Focus Point 1 Developers went over brief summaries of their current work and their intended plans. Aleksandar Andrejevic has been working on the memory manager and intends to complete the transition from using the old MEMORY_AREA to virtual address descriptors. ## Developer services offline DevFeed: [Developer services offline]() Original publisher: [Read original article]() Published: 2013-11-25T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Hardware](), [upgrade](), [servers]() Tags: [crashes](), [developer](), [free](), [git](), [hardware](), [open-source](), [os](), [react](), [reactos](), [recovery](), [server](), [sysadmin](), [upgrade](), [uptime](), [win32](), [winapi]() ### AI overview ReactOS developer services went offline after an unstable host server followed an attempted hypervisor upgrade. The outage affected virtual machines and services including mail, mailing lists, SVN, Git, buildbot, Testman, Jira, the old ReactOS website, and secondary DNS. The team was working to restore services on a new server, with mail issues and recovery timing still unresolved. ### Source excerpt Updated at 13h21 CET: We are trying to restore all the services at the moment, on a new server. Everything should be working again. Let's hope it will be a stable server this time... Except issues with mail server and delays with mails for the moment. Dear all, On Saturday, we attempted an upgrade of one of our old hypervisor. If the upgrade went fine, it appears that the new server provided by our hoster is totally unstable. [Next page]()