GitHub Actions Cron Jobs Routinely Run Hours Late With No Alerts, Dev Finds

·1 views

A developer running a public test repository found that GitHub Actions scheduled workflows consistently started hours behind their set times, with an average delay of 2 hours and 42 minutes across seven days. The every-five-minute workflow fired only 97 times out of roughly 2,016 expected slots in a week, a 5% execution rate. GitHub documents its schedule trigger as best-effort, but the developer argues the bigger problem is the complete absence of notifications when runs are skipped or silently disabled. GitHub itself acknowledged in June that scheduled job drift had worsened as workflow volume grew over 30% in two months. In response, the developer built a read-only GitHub App called Cronwake that monitors scheduled workflows across an organisation and sends alerts via Slack, Discord, or PagerDuty when an expected run fails to appear.

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)

Fields Medalist Yu Deng on Hilbert's 6th Problem, Randomness, and AI in Mathematics

Yu Deng, a 2026 Fields Medal recipient, gave an in-depth interview discussing his breakthrough work on Hilbert's sixth problem, which had remained unsolved for over 125 years. His research builds a rigorous mathematical bridge between microscopic particle systems governed by Newtonian mechanics and macroscopic fluid dynamics equations. Deng explained that randomness, rather than complicating such problems, often simplifies them by allowing researchers to focus on typical outcomes instead of tracking every individual particle trajectory. He also shared that AI tools are becoming valuable collaborators in mathematical research, recounting how GPT produced a one-page proof in an hour for a lemma that took him five days to prove across four pages. Looking ahead, Deng identified quantum field theory and the construction of infinite-dimensional measures, including the Yang-Mills problem, as among the most important open challenges he hopes to tackle next.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Codename One Adds MCP Server Support, Letting AI Agents Control App UI Semantically

Codename One, an open-source cross-platform Java/Kotlin framework, has introduced Model Context Protocol (MCP) server support via pull request #5377. The feature allows AI coding agents such as Claude Code or Codex to interact with a running Codename One simulator or desktop tool by reading a structured semantic UI tree rather than relying on screen coordinates. Developers can activate the server with a single API call, choosing either a loopback socket mode or a stdio transport for direct MCP host integration. Built-in tools let agents snapshot the UI, locate elements by label or ID, enter text, and trigger actions — all executed safely on the app's event dispatch thread. Applications can also register custom typed tools with JSON schemas, enabling agents to call app-specific logic alongside the standard UI controls.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Solana Dev Arc 12: How to Audit Programs for Account Validation Flaws

A structured seven-day coding arc (Days 78–84) focused on auditing Solana programs for security vulnerabilities rooted in faulty account validation rather than complex cryptography. Developers reviewed existing Anchor programs by examining each instruction for missing ownership checks, signature requirements, and PDA verification. The exercise involved writing adversarial transactions, applying property-based testing and fuzzing, and reproducing a real account-substitution exploit. A key takeaway was that Anchor constraints such as Signer, has_one, seeds, and bump should handle most validations before the instruction handler ever runs. The guiding principle throughout was that every account and input must be treated as untrusted until the program explicitly proves otherwise.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why WebAudio Beats the Speech API for Detecting Silence in Voice Apps

A developer building a browser-based AI mock interview tool found that relying on the Web Speech API to detect when a user stops talking produces unreliable results due to network latency, audio buffering, and the recognizer rewriting interim transcripts. These issues cause the system to misread active speech as silence and genuine pauses as ongoing activity. To fix this, the developer instead uses a small WebAudio graph that reads raw microphone waveform data and calculates loudness via root-mean-square analysis, making silence detection a direct acoustic measurement. Two separate thresholds distinguish a brief thinking pause from a completed answer, preventing the AI interviewer from either cutting the user off or waiting indefinitely. The Speech API is kept solely for transcription, while all timing and turn-taking logic is handled by the waveform signal.

0 comments Read more at DEV Community