One if the best 404 page.

Feels like I found value of "NAN"
i.e, finding non-ranter dev @ devrant!
"Write no rant
Comment no rant
++(view) all rant "
@Ghored
I guess he should be given a badge or something!
Never able to achieve that stage of satisfaction,
Bsod in windows,
Grub rescue for Linux,
Gradle build problem for android,
404 errors,
What not ?
Yet I really feel like today , I met a ironical legend of dev community!
A full bow to you my friend

Rant Mode: ON

Do you know what really grinds my gears? Those dreaded "404 Page Not Found" errors. It's like a digital black hole, sucking your users into a vortex of frustration.

And don't get me started on inconsistent coding standards. It's like trying to decipher hieroglyphics written by different ancient civilizations. Why can't we all just follow the same conventions?

Oh, and software updates that break everything! You spend hours perfecting your code, only for a new update to come along and wreak havoc. It's like the universe is conspiring against developers.

But hey, despite the rants, we developers are a resilient bunch. We thrive on solving problems, no matter how infuriating they can be. So, here's to the endless debugging, the endless coffee, and the endless love-hate relationship with coding. We wouldn't have it any other way.

Rant Mode: OFF

Phew, that felt good. Thanks for letting me vent!

Wrote some unit tests to check for 404 errors that called a fake endpoint key...

Months later create that same endpoint key for unrelated reasons and spend a half hour trying to figure out WHY ON EARTH the 404 tests are all failing...

🤦‍♂️

IIS curse you and your nuances!

I launch my local web application (which was working fine) and now get CORS errors and 404 not found. Wtf. I clean the solution rebuild, same thing. Then I restart my PC and try again. Same thing.

Then I use Firefox instead if chrome and it magically works. Wtf!

It's hard to fix broken things when they fix themeselves afyer trial and error

ye ok so officially rust doesn't have a headless browser I can use

there is two.

one will randomly just throw errors totally randomly at you, about some event not coming back or the connection being closed. which means every single unwrap for every single "wait for this element to exist on the page" or trying to access an element is literally a blow-up minefield

the repo is filled with small issue tickets like how the docs keep pointing to 404 pages but I worked around that by just brute forcing everything with debug logging (despite data types being missing / not where they should be in return objects...)

and then there's apparently whatever selenium driver is and that has half as many stars and even worse sounding issue tickets and I already spent 6 hours writing code that took me 20 minutes to write in JavaScript like 8 months ago so I think I don't want to write another stupid headless browser script for it to be utterly useless

I guess I could just have loops and potentially caching. so if it has a mysterious event or connection error, try again! that's literally what I did with fucking reqwest. I don't even know why that nonsense is broken. I have thousands of proxy'ed network connections going and some of them randomly hang and I'm reasonably sure it's reqwest just not cleaning something up

I really wonder if rust people have brain aids. they wanted it to be safe so they just don't get safety exercises in for their brains, and do nonsense like this where they can't go from level 0 safety brain to ohno now I have to do networking and turns out that's extremely error-prone and needs brain-can-account-for-safety-9000 level and they just can't do it because no brain exercises make them all smooth and not wrinkly like everyone else gets in the skull jello by actually using the brain jello

How in the FUCK does the first tutorial on the django website not FUCKING WORK, i've spent the past 5 fucking days trying to get anything at all to work, but no 404 Errors when i follow the guide WORD FOR WORD, trawled through looking for spelling errors but nothing. Fuck This

Well shit! ... "We don't really validate we just give you a 404 if the field is formatted incorrectly, that is part of the V3" how the fuck do I know that.

Days spent trouble shooting these cannot find errors, for a damn incorrectly formatted date field. Fuck sakes!

Life not found...

Does anyone know how to solve the 'Uncaught SyntaxError: Unexpected token <' error? It's on the first line <!DOCTYPE html>, I've even tried deleting that line, but got the same error on <html>.

I've been looking for answers for a while now, and nothing works for me! I know as soon as I post this, I'll get the answer immediately tho.

All the other pages work fine, with no errors and no warnings, all the js/css/whatever files are called in the same file which is shared by all the pages (app.blade.php).

The only 404 errors I'm getting are from the images, but I've tried deleting the img paths and still get the same error. I'm also getting 404 on the images on app.blade.php but those are working fine on the other pages, so I don't think that's it.

The controller was basically copy/paste from another project. I've tried dd($product) and looks fine.

Long story, short: everything looks fine and I'm going crazy. Anyone know what it could be?

At university: Error 404

But as I say: you can learn from everything, from good how to do the things, from bad how to not do the things.

One example: don't copy code directly from a PowerPoint presentation, it will change the " to other symbol and make you look like a fool when the compiler throws errors and you don't figure it out why