Protect your garden from leaf-footed bugs https://www.allforgardening.com/1946591/protect-your-garden-from-leaf-footed-bugs/ #BugsAndInsects #GardeningAndLandscaping #GardeningTexas #texas
Search
253 results for “bug”
-
Bug cleanup from the last update then getting back to new content. #wendigoblue #pixelart #gamedev #screenshotsaturday #gamemaker
-
Cool story Apple (trying to approve my kid's purchase, password is correct and accepted everywhere else). Going on for weeks now.
-
Bug Google Home : un haut-parleur a englouti 3 To en 2 semaines 😱 Google confirme une mauvaise config serveur, corrigée. Mais d'autres appareils restent suspects (22 Go pour un détecteur de fumée ?). Vérifiez votre conso si vous avez un plafond. #GoogleHome #ViePrivee #Tech
https://www.wired.com/story/google-home-speaker-bug-oct-2026/
-
Bug pode deixar Galaxy S26 Ultra praticamente inutilizável
-
¿Coches con propulsores de cohete? 🚀🏎️ Mate Rimac confiesa que quisieron hacer volar al Nevera con toberas de gas frío antes de enfocarse en Bugatti. #Rimac #TeslaRoadster #Hypercar #NoticiasMotor #Bugatti
-
Bridge bug lets one wallet print $2.7M in fake tokens; the chain halts, the natives pump. Incentives clear.
https://www.cryptoninjas.net/news/initia-halts-l1-and-rollups-after-2-7m-exploit-tied-to-unauthorized-token-minting/ -
Signal bug could keep your mic - and camera - on after hangup https://www.theregister.com/security/2026/10/21/signal-bug-could-keep-your-mic-and-camera-on-after-hangup/5304528
-
A bug report lands in a team chat. Three people suggest fixes. Someone corrects the original report....#ai #beginners #webdev #programming #software #coding #development #engineering #inclusive #community
GitHub Copilot in Teams: A Chat-to-Code Handoff Template for Beginners -
Muchos bugs en iOS27.1 con el simulador del iPhone Duo, me está costando la vida sacar unas míseras capturas de pantalla.
-
Nothing bugs me more in #truecrime when it is treated like an injustice that a killer did not get the death penalty. Pure and simple, no government should ever have to power to put somebody to death no matter what their crimes were. I am an absolutist on that matter, especially in a justice system so prone to mistakes and having no understanding of how mental illness works beyond their thin definitions of what legally counts as "insanity." EVERY execution is a miscarriage of justice.
-
Small bugfix release for Exosphere, my simple, agentless CLI and TUI driven patch reporting application for remote UNIX-like systems.
It fixes a compatibility issue on FreeBSD with pkg >=2.8.0.
https://github.com/mrdaemon/exosphere/releases/tag/v3.0.4
#exosphere #linux #freebsd #openbsd #homelab #SRE #Python #Software
-
The reported bug was a carrier lookup returning 404 because an international phone number never reached E.164 normalization. The traceback pointed at
normalizePhone. The agent searched the repo for "normalize", got backnormalizeEmail,normalizePhone, andnormalizeAddress, picked the first match, and spent the pass rewritingnormalizeEmailinto a prettier helper. It wrote a few unit tests against that helper, went green, and reported done. The original phone path never changed.A keyword search returns a naming family, not a call graph. The agent matched tokens, not the failing symbol, and "I edited a function called normalize" became "I fixed the bug."
Why it lands on the lookalike
A broad search ranks by token overlap. Everynormalize*function scores well on the same word, and nothing in the loop asks which symbol appears in the failing stack frame. The agent sees three interchangeable helpers and treats the first as the obvious target, because the traceback's exact function name was never pinned to the task as an anchor.Naming families invite the slip. When
normalizeEmail,normalizePhone, andnormalizeAddresslive near each other and share a similar signature, they read as one generic utility even though their callers, inputs, and failure modes differ. The agent refactors the shared-looking helper rather than the one on the failing path, and its own new tests cover whatever it touched, so green confirms the edited code, not the reported bug.The human review helps it through: we skim the diff for a sensible-looking cleanup, see tests pass, and miss that the edited function never appears in the original traceback.
The tells that the wrong function got fixed
- The edited symbol is absent from the failing stack trace. Compare the function in the diff against the frame in the original report; if they differ, the edit never sat on the failing path.
- The failing test references a different symbol. A green suite built around
normalizeEmailsays nothing aboutnormalizePhone; the new tests target the helper the agent chose, not the failure someone filed. - The original repro still fails on the exact input. Feed the reported phone number back after the fix; a silent 404 that still appears means the untouched path stayed untouched.
- The diff touches a happy path that already worked. A cleanup of an unrelated normalization function reads as polish, not a carrier-lookup fix.
- The agent describes the change generically ("improved normalization") instead of naming the failing endpoint or stack frame.
Anchor the failing symbol before editing
The cheap guard is to pin the exact symbol from the traceback into the task before the agent touches anything: the module, function, and file the stack names are the only legitimate targets. A broad keyword search may surface neighbors, but none of them may be edited until the failing one is resolved.- Require a before/after repro run on the original input. The agent must run the failing case before the edit and again after, and the second run has to pass on the same reported input. A clean helper with no connection to the repro fails this gate.
- Check callers against the failing request. After choosing a symbol, grep its call sites and confirm one matches the reported request path; if none lines up, the match is a near miss.
- Search from the stack frame, not the keyword. Start from the frame the traceback names, then walk outward to siblings; do not let a generic token list pick the target for you.
- Attach the minimal failing case to the agent. When the repro stays visible through the session, done means that specific input behaves, not that an adjacent helper got cleaner.
Edited is not fixed
Green after a near-match cleanup proves only that the touched function passed its own new tests. Pin the symbol from the traceback, run the original repro before and after, and make sure the edited call site matches the failing request. When the agent patches the first lookalike it finds, the bug did not move; the agent just worked on the wrong page.#aiagents #aicode #contextengineering #codereview #software #coding #development #engineering #inclusive #community
The agent patched the lookalike function from a keyword search, so the failing symbol stayed broken -
The elk are bugling again, but off in the distance this time.
I don't recall hearing them so often in October. I usually leave to go south sometime between November 15 and December 25th and I thought that's when they moved through the area. Is it possible that they are moving through earlier? I don't know.🤷🏼♀️
-
Had a nasty bug in Wallflower: I optimized the clock to run with way less system resources by porting it from SwiftUI to low-level CoreAnimation. However, on some devices the clock didn’t reset the animation on significant time changes like when europe changed to winter time last night. So it might show the wrong time this morning. Putting the app to the background or restarting resets the animation, and sets the clock right. Sorry about that, fixing it now.
-
AI discovers severe PHP bug affecting up to 70% of the web
OpenAI's GPT-5.6 model found a critical PHP vulnerability that can let hackers run code on servers. Emergency patches for modern PHP versions are out, but older versions remain at risk.
-
-
Changes in R-devel Bug Fixes:
‘unzip(., unzip = "internal")’ no longer leaks the zip handle on error, thanks to Kevin Ushey, see PR#19233
https://developer.r-project.org/blosxom.cgi/R-devel/NEWS/2026/10/24 -
Changes in R-devel Bug Fixes:
The internal method of ‘untar()’ now checks the whole path of every member, so that a final component of ‘".."’ or ‘"~"’ can no longer place a link or file outside the extraction directory; rejects hard- and symbolic-link targets restored as file copies, which resolve outside the extraction directory or pass through a symbolic link; applies the ‘umask’ to extracted files; also no longer restores ‘setuid’ or ‘setgid’ permission bits. Simi...
https://developer.r-project.org/blosxom.cgi/R-devel/NEWS/2026/10/24 -
Why This PHP Bug Is So Dangerous? - YouTube #devopsish https://www.youtube.com/shorts/h2D8QF7n7r0
-
Squeee moving past container bugs, some upgrades to agenticboard and loops
-
Reports of PHP bug exploitation attempts grow as experts downplay viability of exploits https://therecord.media/php-php2shell-exploitation-attempts-pocs
-
PHP2Shell is a real bug - patch anyway. But a lot of this week's outages weren't about the bug.
No working exploit at release, PoCs that needed an LFI to "work", and still dozens of services pulled offline with no compromise.
The pattern: nobody knew where PHP was running, who owned it, or who could decide. Going offline for an hour to patch is fine. Staying offline because you can't find your own servers isn't.
Wrote it up: https://www.apidemia.com/knowledge-base/did-php2shell-scare-you-into-turning-your-site-offline-hire-a-cto/
-
The PHP Bug That Broke The Internet.
-
Der php-Bug hat jetzt definitiv negative Auswirkung auf meinen Arbeitsablauf.
-
The PHP bug forced me to update a legacy service still running on Ubuntu 22.04; I chose to switch to Debian 13 (Trixie) because Ubuntu is getting a bit annoying lately.
The transition went smooth and most system commands are perfectly compatible with my muscle memory.
Debian stable tends to be a bit less bleeding edge, but for a legacy system I value LTS much more, so... good choice so far! #linux #debian #ubuntu
-
Changes in R-devel Bug Fixes:
The internal method of ‘untar()’ now checks the whole path of every member, so that a final component of ‘".."’ or ‘"~"’ can no longer place a link or file outside the extraction directory; rejects hard- and symbolic-link targets restored as file copies, which resolve outside the extraction directory or pass through a symbolic link; applies the umask to extracted files; also no longer restores setuid or setgid permission bits. Similarly,...
https://developer.r-project.org/blosxom.cgi/R-devel/NEWS/2026/10/23 -
Changes in R-devel Bug Fixes:
‘delete.response’ inadvertently converted indices (attributes ‘response’, ‘offset’, ‘specials’) from integer to double. It also replaced ‘NULL’ components of ‘specials’ with ‘logical(0L)’.
https://developer.r-project.org/blosxom.cgi/R-devel/NEWS/2026/10/23 -
Max-severity GitLab bug allows remote code execution over 12 years of releases https://www.theregister.com/security/2026/10/22/max-severity-gitlab-bug-allows-remote-code-execution-over-12-years-of-releases/5304854
-
Leading with Ben Bugün Ülkemden Gitmek Istedim by Deniz Tekin. Give the vocal score a look.
https://chordyes.com/chord/deniz-tekin-ben-bugun-ulkemden-gitmek-istedim
#guitarstand #guitartuner #turkish #indie #femalevocalist #political #acoustic