23 comments

[ 6.4 ms ] story [ 280 ms ] thread
(comment deleted)
A slight improvement on fuckit.py
That seems… dangerous, to say the least
You're not suggesting that you won't put this immediately into Production are you?
It's all fun and games until you get a subprocess.run(["rm", "/", "-rf"]) snuck in there that you fail to notice.
Hallucinate your data into the AI void
haha yes it did feel a bit wild just letting this run on my machine!

I wouldn't recommend running it on a script that's supposed to delete files

1. Definitely don't run it as root.

2. Obv run in sandbox/container.

[flagged]
[flagged]
A factory that makes hammers shouldn't always be responsible for a hobbyist smashing their thumb, sound risk management is required by the user
so we are just going to build the set up for the next terminator movie in real life and this time skynet self heals??
Oh my god! That looks so much fun and so dangerous at the same time.
It didnt pick up the bug in the else of the calculate function, presumably it is only running along the path that the script is running based on the inputs.
it will sometimes fix other bugs, but yeah the focus is on ones that caused the crash or are obvious
If they are so obvious, why didn't you just do it yourself the first time? Instead of yeeting large portions of your codebase at a 3rd-party web service?
Crashes are the easiest bugs to self-fix.
agreed! but it'd be nice to not have to jump back to the editor to fix a minor crash and then go rerun
ON ERROR GOTO NEXT, 2023 edition