home.social

#debugging — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #debugging, aggregated by home.social.

  1. Creusot is here to save the day by proving your #Rust #code is flawless because, apparently, you can't be trusted to write it correctly in the first place! 😅 It's like having a glorified #spell-checker for developers who think they're programming wizards but still need a safety net. 🧙‍♂️🛡️
    github.com/creusot-rs/creusot/ #Creusot #Debugging #Developer #SafetyNet #HackerNews #ngated

  2. Creusot is here to save the day by proving your #Rust #code is flawless because, apparently, you can't be trusted to write it correctly in the first place! 😅 It's like having a glorified #spell-checker for developers who think they're programming wizards but still need a safety net. 🧙‍♂️🛡️
    github.com/creusot-rs/creusot/ #Creusot #Debugging #Developer #SafetyNet #HackerNews #ngated

  3. Creusot is here to save the day by proving your #Rust #code is flawless because, apparently, you can't be trusted to write it correctly in the first place! 😅 It's like having a glorified #spell-checker for developers who think they're programming wizards but still need a safety net. 🧙‍♂️🛡️
    github.com/creusot-rs/creusot/ #Creusot #Debugging #Developer #SafetyNet #HackerNews #ngated

  4. Creusot is here to save the day by proving your #Rust #code is flawless because, apparently, you can't be trusted to write it correctly in the first place! 😅 It's like having a glorified #spell-checker for developers who think they're programming wizards but still need a safety net. 🧙‍♂️🛡️
    github.com/creusot-rs/creusot/ #Creusot #Debugging #Developer #SafetyNet #HackerNews #ngated

  5. Creusot is here to save the day by proving your #Rust #code is flawless because, apparently, you can't be trusted to write it correctly in the first place! 😅 It's like having a glorified #spell-checker for developers who think they're programming wizards but still need a safety net. 🧙‍♂️🛡️
    github.com/creusot-rs/creusot/ #Creusot #Debugging #Developer #SafetyNet #HackerNews #ngated

  6. Struggling with performance, hard-to-reproduce bugs, or profiling bottlenecks on Linux? KDAB has upcoming training courses covering advanced QML architecture and C++/Qt and on .

    Training schedule: training.kdab.com/scheduled-tr

  7. Struggling with #QML performance, hard-to-reproduce bugs, or profiling bottlenecks on Linux? KDAB has upcoming training courses covering advanced QML architecture and C++/Qt #debugging and #profiling on #Linux.

    Training schedule: training.kdab.com/scheduled-tr

    #QtDev #CPlusPlus

  8. Oh, look, a *riveting* 2026 treatise on how to make #Python #code as #mysterious and indecipherable as a cryptic crossword puzzle, because who doesn't love #debugging an #enigma wrapped in a mystery? 😂 Let's all revel in this groundbreaking "let's hide everything" strategy, ensuring your library remains utterly unintuitive and *brilliantly* #unmaintainable. 🤦‍♂️ #Innovation!
    blog.glyph.im/2026/05/opaque-t #Innovation #HackerNews #ngated

  9. 🔍 highlight/highlight

    highlight.io: The open source, full-stack monitoring platform. Error monitoring, session replay, logging, distributed tracing, and more.

    Tracks frontend errors with session replays, logs and traces while linking them together for debugging, self-hostable or via SaaS

    ⭐ Stars: 9277
    📅 Last Update: May 25, 2026

    github.com/highlight/highlight

    #selfhosted #homelab #selfhost #selfhosting #opensource #monitoring #debugging

  10. 🔍 highlight/highlight

    highlight.io: The open source, full-stack monitoring platform. Error monitoring, session replay, logging, distributed tracing, and more.

    Tracks frontend errors with session replays, logs and traces while linking them together for debugging, self-hostable or via SaaS

    ⭐ Stars: 9277
    📅 Last Update: May 25, 2026

    github.com/highlight/highlight

    #selfhosted #homelab #selfhost #selfhosting #opensource #monitoring #debugging

  11. 🚀 Breaking News: #Academia invents #CPPL, because what we really needed was another programming language! 🎉 Move over, Python—now you can spend quality time #debugging circuits with commands that sound like robot haikus. 🤖💥 Thank you, Simons Foundation, for funding our collective headache. 🙏
    arxiv.org/abs/2605.17892 #BreakingNews #ProgrammingLanguages #SimonsFoundation #HackerNews #ngated

  12. 🚀 Breaking News: #Academia invents #CPPL, because what we really needed was another programming language! 🎉 Move over, Python—now you can spend quality time #debugging circuits with commands that sound like robot haikus. 🤖💥 Thank you, Simons Foundation, for funding our collective headache. 🙏
    arxiv.org/abs/2605.17892 #BreakingNews #ProgrammingLanguages #SimonsFoundation #HackerNews #ngated

  13. 🚀 Breaking News: #Academia invents #CPPL, because what we really needed was another programming language! 🎉 Move over, Python—now you can spend quality time #debugging circuits with commands that sound like robot haikus. 🤖💥 Thank you, Simons Foundation, for funding our collective headache. 🙏
    arxiv.org/abs/2605.17892 #BreakingNews #ProgrammingLanguages #SimonsFoundation #HackerNews #ngated

  14. 🚀 Breaking News: #Academia invents #CPPL, because what we really needed was another programming language! 🎉 Move over, Python—now you can spend quality time #debugging circuits with commands that sound like robot haikus. 🤖💥 Thank you, Simons Foundation, for funding our collective headache. 🙏
    arxiv.org/abs/2605.17892 #BreakingNews #ProgrammingLanguages #SimonsFoundation #HackerNews #ngated

  15. 🚀 Breaking News: #Academia invents #CPPL, because what we really needed was another programming language! 🎉 Move over, Python—now you can spend quality time #debugging circuits with commands that sound like robot haikus. 🤖💥 Thank you, Simons Foundation, for funding our collective headache. 🙏
    arxiv.org/abs/2605.17892 #BreakingNews #ProgrammingLanguages #SimonsFoundation #HackerNews #ngated

  16. New early access chapter in The Ice Line Nightmare is up on Ko-Fi and Patreon!

    Debugging an unknown ward that's a few hundred years old is a tricky process. Not least because the original caster is *probably* dead.

    patreon.com/posts/ice-line-cha

    ko-fi.com/post/The-Ice-Line-Ni

    #fantasy #writing #amWriting #debugging #magicWorksLikeTech #itsAMess

  17. 🚀 Oh joy, another tool for the 3 people who actually want to visualize #C++ ASTs. Now everyone can spend their weekends pretending to understand deeply nested tree structures while sipping artisanal coffee ☕. Because who doesn't love #debugging their life away in a shiny new GUI? 😂
    uvic-aurora.github.io/acav-man #AST #visualization #GUI #codinghumor #artisanalcoffee #HackerNews #ngated

  18. Wakeup and suspend has worked really well this year. Today got first issue. Network stopped working after wakeup.

    I have always stored the journalctl log for each of the issues, today DeepSeek v4 Pro came up a reason of some sort. For todays issue at least.

    DeepSeek V4 PRO saying network driver becomes fragmented after multiple wakeups?

    Who knows!

    #Linux #Debugging

  19. Flipper Zero unter Arch Linux – wichtiger Hinweis

    Falls der Flipper Zero unter Arch nicht erkannt wird und ihr „/dev/ttyACM0: Permission denied“ bekommt:

    Die Udev-Regeln der Flipper-App erwarten die Gruppe „dialout“. Arch nutzt dafür aber die Gruppe „uucp“.

    Fix:
    1. Udev-Regel anpassen: dialout → uucp
    2. User hinzufügen: sudo usermod -aG uucp $USER
    3. reboot

    Danach läuft der Flipper Zero unter Arch auch ohne sudo.

    #flipperzero #archlinux #linux #udev #opensource #debugging #foss #archusers

  20. Every team learns differently — that’s why KDAB’s in-company #training programs are built around your goals. Customize the curriculum, schedule, and location to fit your needs. Explore topics like #QtDev, #Cpp, #QML, #3D, #Debugging, and more.

    Learn more: training.kdab.com/in-company-t
    training.kdab.com/in-company-t

  21. Every team learns differently — that’s why KDAB’s in-company #training programs are built around your goals. Customize the curriculum, schedule, and location to fit your needs. Explore topics like #QtDev, #Cpp, #QML, #3D, #Debugging, and more.

    Learn more: training.kdab.com/in-company-t
    training.kdab.com/in-company-t

  22. Every team learns differently — that’s why KDAB’s in-company #training programs are built around your goals. Customize the curriculum, schedule, and location to fit your needs. Explore topics like #QtDev, #Cpp, #QML, #3D, #Debugging, and more.

    Learn more: training.kdab.com/in-company-t
    training.kdab.com/in-company-t

  23. Every team learns differently — that’s why KDAB’s in-company #training programs are built around your goals. Customize the curriculum, schedule, and location to fit your needs. Explore topics like #QtDev, #Cpp, #QML, #3D, #Debugging, and more.

    Learn more: training.kdab.com/in-company-t
    training.kdab.com/in-company-t

  24. Every team learns differently — that’s why KDAB’s in-company programs are built around your goals. Customize the curriculum, schedule, and location to fit your needs. Explore topics like , , , , , and more.

    Learn more: training.kdab.com/in-company-t
    training.kdab.com/in-company-t

  25. 🔍 Spark + Elasticsearch Debugging 🧵

    Building a cybersecurity analytics platform. Hit 2 blockers:

    ❌ JAR path mismatch → Fixed absolute path
    ❌ No data nodes (single-node Docker ES) → Added es.nodes.wan.only=true

    ✅ Result: 89 records loaded. Working pipeline!

    Lesson: Verify JAR paths + disable node discovery for single-node ES.

    #PySpark #Elasticsearch #DataEngineering #CyberSecurity #Debugging

  26. 🔍 Spark + Elasticsearch Debugging 🧵

    Building a cybersecurity analytics platform. Hit 2 blockers:

    ❌ JAR path mismatch → Fixed absolute path
    ❌ No data nodes (single-node Docker ES) → Added es.nodes.wan.only=true

    ✅ Result: 89 records loaded. Working pipeline!

    Lesson: Verify JAR paths + disable node discovery for single-node ES.

    #PySpark #Elasticsearch #DataEngineering #CyberSecurity #Debugging

  27. When two Hetzner servers died at the same time

    On May 12, 2026, two of my Arch Linux + LUKS servers at Hetzner became unreachable at the same moment. Both had been running for 4+ months without issue. Both had received the same pacman -Syyu the day before, but had stayed on the old kernel until the morning the websites stopped responding. I rebooted — SSH never came back. nmap -Pn -p 22 showed filtered from anywhere. No ping. No banner. The Hetzner Robot panel insisted the hardware was fine.

    Several hours went into hypotheses that turned out to be wrong:

    • The encryptssh initcpio hook referencing a /usr/lib/initcpio/udev/11-dm-initramfs.rules file that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway.
    • PermitRootLogin no in sshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd shows closed, not filtered.
    • Predictable interface-naming drift after the systemd 260 upgrade. Patched the .network config to match by MAC. Useful hardening; not the cause.
    • Stale GRUB stage1 + core.img in the MBR. Arch never re-runs grub-install after a grub package upgrade. Refreshed it. Still filtered.
    • Kernel 7.0.5 regression. Downgraded to 6.18.3, the kernel that had run for 4 months. Still filtered. So the kernel itself wasn’t it either.

    The clue was in the persistent journal: a single recorded boot from December 31 to May 12 10:13 UTC, and absolutely nothing after. Every reboot since the upgrade was failing before systemd-journald could flush to disk — so the failure had to be in the initramfs, before the root filesystem was even mounted.

    What it almost certainly was

    Hetzner Dedicated servers configure the initramfs network with ip=dhcp on the kernel command line. That depends on Hetzner’s DHCP server replying to whatever request format the current kernel sends. Somewhere between kernel 6.18 / iproute2 6.18 and kernel 7.0 / iproute2 7.0, the request format changed enough that Hetzner’s DHCP stopped responding. Effects:

    • Old kernel at runtime kept the interface already configured (Phase A — 32 hours of healthy operation after the package upgrade).
    • New kernel cold-boots, hits DHCP, never gets an IP, dropbear cannot listen, port 22 stays filtered.

    Hetzner’s own documentation has been quietly moving away from ip=dhcp toward static IPv4 in the kernel command line. The fix is exactly that:

    GRUB_CMDLINE_LINUX="cryptdevice=/dev/md1:cryptroot ip=A.B.C.D::GATEWAY:255.255.255.255:hostname:eth0:none"
    

    One line in /etc/default/grub, grub-mkconfig, reboot. No more dependency on Hetzner’s DHCP responding to whatever your current kernel sends.

    Why it matters for anyone running this stack

    If you run Arch on Hetzner Dedicated with full-disk encryption and remote unlock via dropbear, the ip=dhcp shipped by installimage is a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routine pacman -Syyu. The static-IP version is what Hetzner now recommends and removes the entire dependency.

    Tooling

    While debugging, I turned the whole rescue / chroot / diagnose / fix workflow into a Python CLI (hal) — including hal fix static-ip, which derives the static cmdline directly from your existing systemd-networkd .network file:

    github.com/kevinveenbirkenbach/hetzner-arch-luks

    Single command, idempotent, reversible (the original /etc/default/grub is backed up to .hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you.

    #ArchLinux #bootFailure #debugging #DevOps #DHCP #Dropbear #fullDiskEncryption #GRUB #Hetzner #initramfs #kernelUpgrade #Linux #LUKS #mkinitcpio #pacman #postmortem #PythonCLI #serverOutage #sysadmin #systemdNetworkd