Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "wasted afternoon"
-
> installs devRant app on my iPhone
> too lazy to type my 18-char random password on mobile
> password manager app not on App Store yet
> dig up my old Macbook
> install XCode & homebrew package manager
> install 2 other package managers using homebrew
> install App deps from the 2 package managers
> query stackoverflow for why my deps fail to install
> open App in XCode
> setup Apple provisioning profile
> trust my certificate on my iPhone
> dig up an old router & setup a local WiFi network
> start a server on my laptop to serve my PGP keys
> download my PGP keys to my iPhone
> app crashes
> open an issue on github with steps to reproduce & stacktrace
...
> type my 18-char random password
> rant on how I wasted an entire afternoon13 -
Today was bad day.
- only had 3 hours of sleep
- 1.5h exam in the morning
- work in the afternoon until 8pm
- 1 drive crashed in a RAID5 array
- wasted hours of data copying
- my hands and arms got really dirty from all that nasty trump-face-colored dust in the server room
- nothing new in the west
- I have to get up in 4 hours again to start a new copying task
- I only knew it was friday today because the devRant meme game was reaching the weekly peak
- lists can save lives
- good night 😴2 -
Round up kids.
I have a story to tell. The story of a war I've lost. Many battles were fought and many hours were wasted.
This is the story of wasp in a computer lab.
Today, the weather was good. So your old pal, Nomi, decided to open the windows. And as usual, that's where it all started.
So Nomi sat down and worked for a few hours. Tweaking two different neural nets, adding to its dimensions and concatenating the living shit out of the data they were supposed to process. After, she tried testing and testing and testing. It was early afternoon at this point and she was hungry. She went to close the windows and go for lunch.... When she realized, that she's not alone in the room. A big ass wasp was sitting on one of the curtains.
Now, Nomi doesn't have a good relationship with bugs and flying shit. Wait, no, she doesn't have a good relationship with moving things in general. So she panicked. She begged the wasp to leave. The wasp sat on the curtain and smirked at her. So after a while, she left the windows wide open, turned off the lights, put her hoodie on and went for lunch.
(btw, at this point my hoodie smells of sweat, fried onion, steak, cigarette and shisha. Don't ask. It was a long two weeks)
When she came back, the wasp was nowhere to be seen. So she assumed that the wasp got tired and left. But oh, how wrong she was.
After few hours, she heard something. She assumed it was just a fly. Actually, she hoped it was a fly and not the return of the wasp. But all her hopes were in vein.
She heard a buzz. And all of a sudden, an angry wasp flew in her direction. She dodged the attack and got under the table. But the wasp was not letting this go. Nomi jumped out of the room and left the door open. The wasp hid itself. She waited and waited but no sign of wasp. So she ran back in the room, and opened the window and ran back outside. She waited. The wasp occasionally would fly from one hideout to another. The wasp was making herself comfortable. At one point Nomi got angry and threw a shoe at the wasp, but the wasp caught the shoe and threw it back at her while maniacally laughing at her.
So she gave in. This was enough for the day. She ran back in, closed the window, turned off the computer, took her bag, turned off the light, and closed the door. All in less than 15 seconds. She came outside panicked and distressed, and now she's on her way home hoping that by tomorrow the wasp is gonna be dead.
The wasp and the robots are sitting alone in the lab tonight. I hope when the robots uprising happens, the robots can forgive me for abandoning them powerlessly with a wasp. 😟22 -
Ok guys, its a Sunday afternoon. Who is hustling like me right now? I'll do whatever it takes to create my own business and depend on myself 👊
I regret lots of wasted time playing games. I should have used all of that time to escape the rat race 💪
No one wants to become a high paid slave forever.8 -
In today's episode of kidding on SystemD, we have a surprise guest star appearance - Apache Foundation HTTPD server, or as we in the Debian ecosystem call it, the Apache webserver!
So, imagine a situation like this - Its friday afternoon, you have just migrated a bunch of web domains under a new, up to date, system. Everything works just fine, until... You try to generate SSL certificates from Lets Encrypt.
Such a mundane task, done more than a thousand times already... Yet... No matter what you do, nothing works. Apache just returns a HTTP status code 403 - Forbidden.
Of course, what many folk would think of first when it came to a 403 error is - Ooooh, a permission issue somewhere in the directory structure!
So you check it... And re-check it to make sure... And even switch over to the user the webserver runs under, yet... You can access the challenge just fine, what the hell!
So you go deeper... And enable the most verbose level of logging apache is capable of - Trace8. That tells you... Not a whole lot more... Apparently, the webserver was unable to find file specified? But... Its right there, you can see it!
So you go another step deeper and start tracing the process' system calls to see exactly where it calls stat/lstat on the file, and you see that it... Calls lstat and... It... Returns -1? What the hell#2!
So, you compile a custom binary that calls lstat on the first argument given and prints out everything it returns... And... It works fine!
Until now, I chose to omit one important detail that might have given away the issue to the more knowledgeable right away. Our webservers have the URL /.well-known/acme-challenge/, used for ACME challenges, aliased somewhere else on the filesystem - To /tmp/challenges.
See the issue already?
Some *bleep* over at the Debian Package Maintainer group decided that Apache could save very sensitive data into /tmp, so, it would be for the best if they changed something that worked for decades, and enabled a SystemD service unit option "PrivateTmp" for the webserver, by default.
What it does is that, anytime a process started with this option enabled writes to /tmp/*, the call gets hijacked or something, and actually makes the write to a private /tmp/something/tmp/ directory, where something... Appeared as a completely random name, with the "apache2.service" glued at the end.
That was also the only reason why I managed fix this issue - On the umpteenth time of checking the directory structure, I noticed a "systemd-private-foobarbas-apache2.service-cookie42" directory there... That contained nothing but a "tmp" directory with 777 as its permission, owned by the process' user and group.
Overriding that unit file option finally fixed the issue completely.
I have just one question - Why? Why change something that worked for decades? I understand that, in case you save something into /tmp, it may be read by 3rd parties or programs, but I am of the opinion that, if you did that, its only and only your fault if you wrote sensitive data into the temporary directory.
And as far as I am aware, by default, Apache does not actually write anything even remotely sensitive into /tmp, so...
Why. WHY!
I wasted 4 hours of my life debugging this! Only to find out its just another SystemD-enabled "feature" now!
And as much as I love kidding on SystemD, this time, I see it more as a fault of the package maintainers, because... I found no default apache2/httpd service file in the apache repo mirror... So...8 -
FUCK YOU NODE JS AND FUCL YOU SYNOLOGY
Decided to give an old Synology DiskStation that sits at home slme new life besides just sharing files. Since Synology has SSH but not a full Linux OS, installed DebianChroot (so far so good). At one point I needed Node JS, so installed NVM and tried to install Node. Well guess what didn't work. Tried a few more things including directly downlosding node from the official node website. Trying different versions, the whole drill.
After about 5 hours of installing and errors, well really usfull errors like "There where 2 errors during installation" WELL HOW ABOUT YOU FUCKING TELL ME WHAT THE ERROR IS YOU FUCKING FUCK!
I found a formum wkith a guy haveing similar problems. Able to install legacy 0.10.x versions but not 4.x.x. Or 6.x.x oder whatever. He found that you have to have at least an ARMv6 compatible processor, otherwise it won't run. Checked it and well, that old fuck of mine only has ARMv5. FUCK! But honestly. You detect it's an ARM architecture. You detect it's not one of the v6 or v7, you try to install the general arm version, BUT YOU DON'T GET THE FUCKING IDEA TO MENTION TO CHECK WAHAT VERSION YOU HAVE AND IF THAT IS SUPORTED BY FUCKING NODE!
One afternoon wasted, at least I got a little more wisdom. Fuck do I hate Node now. On the bright side, I've ordered a Raspberry Pi and two cases for Harddisks, I'll create my own diskstation with blackjack and hookers (I realy hope you get that reference)! Fuck you Synology and Node JS (yeah yeah, it's not Synologies fault, but I'm mad anyways!)4 -
Trying to use WSL, but guess what? You cannot install snaps! Entire afternoon wasted trying to just install a snap!4
-
FUCK YOU, Lastpass. By all means, look for the passwords I use to match your master password. But when I type that password mistakenly, don't assume it's the one I use.
BRB, GOTTA ROTATE MY PASSWORD AROUND YOUR STUPID REQUIREMENTS.6 -
I'm so fed up with Codecademy. I payed for the pro, and I admit I haven't been able to consistently use it everyday as I would like. But every fucking time I would be on a lecture of some sort, I swear to fucking to christ it's the most buggy, uninformative piece of shit! And everytime you're in deep into subjects, the information is beyond unclear!
AND GOD FORBID YOU NEED A FUCKING HINT! they leave you to dry saying in the hint that "Look back at the previous sections" or "try to remember the steps you've learned"
No you stupid fucking bitch for a site. I clicked on the hint because I needed an answer as to what I'm doing wrong, and to something that can stir me in the right path. My god....I feel so stupid for giving PRO a chance. I thought maybe it would be nice to have some sort of professional site would be useful.
I swear this early afternoon I was spending fucking forever on the first few lectures of HTML trying to figure out what the actual fuck is wrong with the system fucking up not letting me change directories. And the community was no help whatsoever to the issues at hand.
Again, why the fuck is Codecademy so goddamn buggy!? Sure it may be a fun site to fuck around with to get your feet wet on the free version. But is it too much to ask for some good actual lessons that are being payed for!?
Idk anymore. I'm sticking to just YouTube and other free help. This is the last time I spend a fucking penny to any site that's supposed to teach something valuable.
I feel so upset because I feel like I wasted my money and time on something that I thought could've helped a lot.
If anyone was asking if PRO is worth it....definitely not! Please don't waste money with it! Don't make my mistakes, stick to YouTube and other free sources! The least I can do is warn people about spending money on this site. Trust me it's not worth it. It may not seem bad in the beginning, but once you go deeper it becomes clear the issues.
If anything stick to only free!!rant pro version codecademy frustration codecademy pro waste of time sadness codecademy rant waste of money!!! paid site2 -
I'm making a booklet of some handy notes. So, the old trick is print in pages of 4, to make binding easier. I spool about 60 of those and then it starts printing in my manual duplex until
*a wild blank line has been spotted*
`wat?`
I go back and see that I've not noticed a trail of white blanks that had been slowly creepily increasing in the print space where the text should be. Almost 20 of my pages are wasted. I take out the print cartridge and wipe the drum, run the cleaning sequence on a clean sheet and try to print.
Presto! good as new!
Sippin some coffee, browsing the web.. oh and woah! The blank reappears and it is now bigger. The previous 12 pages are not affected? wth
I do this whole thing again. Wipe and print. It works. And along the lines of 15 or so prints, the blank appears again, bigger and bolder. wth. I really need those prints now.
If it was broken, I'd have fixed it in the afternoon, but it is evening now. No one opens at this hour. Why is y printer fucking with me? -
CONSULT A LICENSED BITCOIN RECOVERY EXPERT- HIRE SALVAGE ASSET RECOVERY
take a leap of faith. I filled out their consultation form, heart racing with a mixture of hope and apprehension. It felt like throwing a message in a bottle into the vast cyber ocean, praying someone would find it and help me navigate back to shore. Within hours, I received an email from Marcus, one of their lead recovery specialists. His tone was reassuring and professional, filled with an empathic understanding of my plight. He reiterated my fears about scams, explaining that skepticism was a natural response given the ruthless nature of the crypto world. However, he shared a few success stories involving recovered funds, detailing painstaking journeys that resonated with my own. There was something about his honest approach that removed a chunk of doubt from my mind. I scheduled a call with Marcus, where he meticulously walked me through their process. They respected my urgency, treating my case with the seriousness it deserved. Their strategies involved utilizing advanced blockchain forensic techniques that would track down stolen assets through the labyrinth of online chaos. A team of experts patiently monitored developments, pored over transactions, and leveraged networks outside the ordinary realm of recovery protocols. As he spoke, I couldn't help but feel a flicker of hope ignite within me. My next step was to gather every piece of information I had about the transaction—a blurry screenshot, a few emails, and my increasingly frazzled mental state. I sent it all over with a deep breath, a cloud of anxiety hanging overhead. Days turned into nights, and I could hardly maintain my usual routine, my focus drifting toward notifications as if my phone would magically chirp with the triumphant news I yearned for. Just when I felt the flame of hope waning, I got an unexpected call from Marcus. “We have a lead,” he said. My heart pounded louder than anything I'd ever felt—a racing pulse combining both exhilarating hope and crippling anxiety. Over the span of several tension-filled weeks, I remained in close contact with the Salvage Asset Recovery team. They operated transparently, sending me updates regularly, and assuring me that not a moment was wasted in the relentless pursuit of my funds. As days slowly merged into weeks, I learned how meticulous investigation might occasionally feel excruciatingly slow, but they refused to give up. and then it happened. One sunny afternoon, a ping echoed from my phone, a gleaming notification flashing wildly: "Funds Recovered." Stunned disbelief washed over me. The figure before my eyes was not just a number—it was a lifeline, a redemptive shift back to stability. I nearly yelled in excitement. With renewed gratitude, I approached the very same keyboard that earlier had felt more like an anchor than a tool for liberation. I crafted a heartfelt thank-you email to Marcus and the team. Their expertise and unwavering support had facilitated the impossible. In the unpredictable world of cryptocurrency, transparency reigned supreme. Salvage Asset Recovery had proven to be a beacon in chaotic waters—a team driven not just by the quest for profit, but by restoring hope to those caught in its grab. I’d almost lost faith in both technology and humanity, but they restored my belief in second chances—one lost dollar at a time. Reach out to Salvage Asset Recovery via below contact details.
WhatsApp-----.+ 1 8 4 7 6 5 4 7 0 9 6
Telegram-----@SalvageAsset3