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
-
GF: What are you doing there?
Dev: I've been trying to reproduce a bug for two hours now...
GF: You need two bugs the opposite sex, otherwise they won't reproduce.
From a sad true story.8 -
Today I received the best bug report I could've ever asked for..
Received an email from a member of our customer service centre containing a description of the bug they'd found and not only did it contain the steps to reproduce the bug, but a goddamn video of him reproducing the suspected bug!
The greatest feeling when the client decides to take time to make your life that little bit easier24 -
If Doctors Were Like Coders
(cross-posted from https://medium.com/@c09b6133a238/...)
Problem: The patient has a broken leg.
Solution:
1. Ask the patient to reproduce the exact scenario that resulted in the broken leg. Watch closely to see if the leg breaks again. Check for consistency by repeating the scenario a few more times.
2. Explain that this isn’t an intended use case for the leg, and besides, it only affects one person. Ask the patient if, all things considered, he really wants to prioritize his broken leg over your other work.
3. Point out that the patient’s other leg performs just fine under the same circumstances. Ask if he can use his other leg instead, at least as a workaround.
4. Attach several accelerometers to the broken leg and break it again. Stare at the data received from the accelerometers, then shrug and declare it useless.
5. Decide that the patient’s problem must be in his spleen. After all, that’s the only part of his body you don’t really understand.
6. Track down the people who created the patient. Ask them if he’s ever had spleen problems before. When they seem confused, explain that he has a broken leg. Ignore them when they tell you that the spleen they created could not possibly cause a broken leg.
7. Ask Google where a person’s spleen is. Spend half an hour reading the Wikipedia article on Splenomegaly.
8. Open the patient and grumble about how tightly-coupled his spleen and circulatory system are. Examine the spleen’s outer surface to see if there are any obvious problems. Inform him that several of his organs are very old and he should consider replacing them with something more modern.
9. Compare the spleen to some pictures of spleens online. If anything looks different, try to make it look the same.
10. Remove the spleen completely. See if the patient’s leg is still broken. If so, put the spleen back in.
11. Tell the patient that you’ve noticed his body is made almost entirely out of cellular tissue, whereas most bodies these days are made out of cardboard. Explain that cardboard is a lot easier for beginners to understand, it’s more forgiving of newbie mistakes, and it’s the tissue franca of the Internet. Ask if he’d like you to rebuild his body with cardboard. It will take you longer, but then his body would be future-proof and dead simple. He could probably even fix it himself the next time it breaks.
12. Spend some time exploring the lymph nodes in the patient’s abdominal cavity. Accidentally discover that if the patient’s leg is held immobile for six weeks, it gets better.
13. Charge the patient for six weeks of work.14 -
My boss typed up a GitLab ticket that looked like it took at least an hour to make. Screenshots, diagrams, how to reproduce the bug, dreams, hopes, desires, dinner recipes, marriage advice, how to diversify a portfolio. Honestly, the whole 9 yards.
The bug fix was changing a SQL Inner Join to a Left Join. 10 seconds.14 -
*Manager enters the room quickly*
Manager: Coffe2Code, we have a serious problem on the application, (We are working on a chat app).
Me: What? now just few hours before the Demo?, what is it?
Manager: when I send or receive a media message (audio or video) the sound is not playing, the file seems like corrupted !
Me: that's strange, let me debug it and see.
*Me spending an hour and could not even reproduce the bug..*
Me: Boss, I cannot see the bug, can I debug on your device quickly?
Manager: Sure, here it is.
Me: hold the fucking device, press VOLUME UP, IT WAS FUCKING MUTE. THERE WAS NO ISSUE MOTHERFUCKER.
Manager, oups ok good no issue then, thanks16 -
Got an email from client with subject starting with "VERY URGENT", the email mentioned how urgent it is to fix this issue multiple times, it implied that they couldn't do anything else while this issue existed, but they were very light on details. So sparse on them that I couldn't reproduce the issue. 15 minutes after the original email I write a reply asking for some clarifications.
They proceed not to reply for 4 days. Fix took 5 minutes after they explained the problem better.
Apparently it wasn't so urgent after all.6 -
If programmers were doctors.
Doctor A: the patient is having heart attack
Doctor B: we have to reproduce the heart attack to be able to heal him
Doctor C: why dont we just remove the hesrt and install a new heart
Doctor D: human heart are bad, maybe we should use animal heart21 -
GF: Why are working so late?
Me: Because no matter what I do, everything is working correctly.
GF: What....
The only career when you have to work late because everything is working like it should (cannot reproduce an issue).19 -
> 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 -
When you have a bizarre bug that you can't consistently reproduce, but you're already past your deadline.
7 -
We build a backup infrastructure at work to make sure that clients can restore their files and databases themselves when something gets fucked up.
We also have step by step tutorial on how to do this.
Every fucking day we get requests to restore backups.
Mostly used reason is "I'm a technical so I won't understand it".
With all due respect, if you don't understand this and keep asking without even trying, please don't host with us.
Because, if you did as I asked and actually read through the entire article, you would.
In case you're wondering, anytime one of us asks what part they don't understand, that question is simply ignored and they pushing for us restoring it anyways continues.
Sometimes they get angry and want to talk to someone higher up or start complaining that they're paying loads of money already and that it would just take us a second anyways.
If you would read the fucking tutorial/manual instead of trying to eat out your mother's badly shaved pussy and hopefully choke on it while you're at it, you wouldn't come asking us for it.
If you genuinely don't understand this article, feel free to ask but also provide us with cocksucking feedback.
Why do you think you have the right anyways to ask us to do it for free? We maintain the backup infrastructure which definitely isn't cheap but we do it so that you, pubic sniffing weazel, can do this shit on your fucking own.
You're entitled to ask us for help but not for asking us to restore your bullshit for free every freaking time.
Tip: give your parents some condoms. Because that way they hopefully won't reproduce again, we don't need more of you in this universe.7 -
User: We can not register three users on your website, it allowed us to register only first one
Me: What does it say? Some kind of error? Tell me so I can reproduce.
User: Well it says email address is already taken
Me: Uh...
- so yeah, they tried to register three users under the same email address.7 -
User: There’s a bug in the app
Dev: How do I reproduce it?
User: I don’t want it reproduced, I want it fixed!
Dev: …7 -
"Hey, Root, someone screwed up and now all of our prod servers are running this useless query constantly. I know I already changed your priorities six times in the past three weeks, but: Go fix it! This is higher priority! We already took some guesses at how and supplied the necessary code changes in the ticket, so this shouldn't take you long. Remember, HIGH PRIORITY!"
1. I have no idea how to reproduce it.
2. They have no idea how to reproduce it.
3. The server log doesn't include queries.
4. The application log doesn't include queries.
5. The tooling intercepts and strips out some log entries the legendary devs considered useless. (Tangent: It also now requires a tool to read the logs because log entries are now long json blobs instead of plain text.)
6. The codebase uses different loggers like everywhere, uses a custom logger by default, and often overwrites that custom logger with the default logger some levels in. gg
7. The fixes shown in the ticket are pretty lame. (I've fixed these already, and added one they missed.)
8. I'm sick and tired and burned out and just can't bring myself to care. I'm only doing this so i don't get fired.
9. Why not have the person who screwed this up fix it? Did they quit? I mean, I wouldn't blame them.
Why must everything this company does be so infuriatingly complicated?11 -
A real interaction I just had...
Team Member: "Can you handle this ticket for a bug fix?"
Me: "Whats the problem?"
TM: "We aren't exactly sure..."
Me: "Ok, so can you show it to me?"
TM: "We can't get it to happen again, and when it does the machine freezes and we can't debug it..."
Me: "So, if I find a fix then how do we test to make sure it worked?"
TM: "I'm not sure..."
Then today,
Product Manager: "How's that bug fix going?"
Me: "Well, let's see. The problem still hasn't been defined. I have never been able to recreate the issue. I have a hacky fix in a PR..."
PM: "Great, so we can deploy today?!?"
Me: "No, because we have no way to reproduce or test this issue at all..."
PM: "Do you think your fix will work?"
Me: "Honestly, no. If you're asking for my opinion then you can have it. IMO this is NOT a bug fix but a change to how the system operates altogether. This system was built by someone who didn't know what they are doing. We have done our best with it but it is a house of cards. And now the solution is to replace a card at the bottom layer. It is likely that no matter what fix we do (even when we can fucking test it) that it will topple the house of cards..."
PM: ~Looking at me in disbelief~
Me: "If you ask me for my honest professional opinion then you will get it. Keep that in the future if that honest response was outside what you expected."
PM: "I will do that, thanks for your assessment"
Where do we go from here? God only knows.
Praise Joe Pesci5 -
If a teamviewer sessions counts as "screenshare", I've got a good one.
The company I'm working for also got an internal video player in the webfrontend of it's product. A customer called in, because the player "stays black", instead of playing his videos. It's a player for a media library of the customer, so it can be any content. A collegue did some trouble shooting, but since the customer was not very experienced in IT they arranged a teamviewer session. At the appointed time, my collegue called the customer and asked him to reproduce the issue, while watching via teamviewer.
When opening the media player, it stayed black indeed, so my collegue asked the customer to try another video. From my desk I heard my collegue say "Oh god, no" (phone muted) pretty loudy and he asked us to come to his place quickly. The customer decided, it would be a good idea to try the video player with gay porn. So we stood there around my collegues desk, watching a hairy man, getting his asshole licked by another an even hairier man for a few secs.
The customer stopped the playback, said "ok, maybe the other file was just broken.", thanked my collegue and the call was over.
We had a few similar cases.9 -
Rant! I found a bug in payment provider's api. The bug involves sending an invalid (!) Stripe ID to that API, (which I send on purpose btw) Which causes a complete white page when you login to their systems and view the details of that customer. Btw the API will accept that invalid Stripe ID without questioning and returns a 200 status code back.
So I send a mail to there support saying "look I found this bug by accident, this is how you can reproduce it"
And the support team send me a message back saying "then don't send an invalid Stripe ID"...
You don't freaking say... *sigh*
9 -
Victory!
Today I finally closed a 'Nessy' bug (A scary bug you can't reproduce typically only sighted by one person). Below is my response...
"There were no errors in the error logs because writing to the error log was causing the error."
5 -
IBM
I have replied to them with scripts, curl commands, and Swagger docs (PROVIDED TO SUPPORT THEIR API), everything that could possibly indicate there's a bug. Regardless, they refuse to escalate me to level 1 support because "We cant reproduce the issue in a dev environment"
Well of course you can't reproduce it in a dev environment otherwise you'd have caught this in your unit tests. We have a genuine issue on our hands and you couldnt give less of a shit about it, or even understand less than half of it. I literally gave them a script to use and they replied back with this:
"I cannot replicate the error, but for a resource ID that doesnt exist it throws an HTTP 500 error"
YOUR APP... throws a 500... for a resource NOT FOUND?????????!!!!!!!!!! That is the exact OPPOSITE of spec, in fact some might call it a MISUSE OF RESTFUL APIs... maybe even HTTP PROTOCOL ITSELF.
I'm done with IBM, I'm done with their support, I'm done with their product, and I'm DONE playing TELEPHONE with FIRST TIER SUPPORT while we pay $250,000/year for SHITTY, UNRELENTING RAPE OF MY INTELLECT.11 -
Client: There’s a bug in the app
Developer: How do I reproduce it?
Client: I don’t want it reproduced, I want it fixed!
Developer:🤐🤐🤐5 -
aslkfjasf. i've spent 12 hours today (and lots more over the past two days) trying to reproduce a bug that my [sort of] coworker insists is present. I haven't seen any proof of it anywhere, let alone steps to reproduce it.
I've poured through the code, following all of its tangled noodles of madness from start to fuck-this-shit. I've read and reread the pile of demon excrement so many times i can still read the code when i close my eyes. so. not. kidding.
anyway, the coworker person is getting mad because i haven't fixed the bug after days, and haven't even reproduced it yet. This feature is already taking way too fucking long so I totally don't blame him. but urghh it's like trying to unwind a string someone tied into a tight little ball of knots because they were bored.
but i just figured out why I haven't been able to reproduce it.
the stupid fucking unreliable dipshit ex-"i'm a rockstar and my code rocks"-CTO buffoon (aka API Guy, aka the `a=b if a!=b`loody pointless waste of mixed spaces and tabs) that wrote the original APIs ... 'kay, i need to stop for breath.
The dumbfuck wrote the APIs (which I based the new ones on mostly wholesale because wtf messy?), but he never implemented a very fucking important feature for a specific merchant type. It works for literally every type except the (soon-to-be) most common one. and it just so happens that i need that very specific feature to reproduce this bug.
Why is that one specific merchant type handled so differently? No fucking idea.
But exactly how they're handled differently is why I'm so fking pissed off. It's his error checking. (Some) of his functions return different object types (hash, database object, string, nullable bool, ...) depending on what happened. like, when creating a new gift, it (eventually...) either returns a new Gift object or a string error basically saying "ahhh everything's broken again!" -- which is never displayed, compared against, or recorded anywhere, ofc. Here, the API expects a Hash. That particular function call *always* returns a Hash, no matter what happens in the myriad, twisting, and interwoven branches the code could take. So the check is completely pointless.
EXCEPT. if an object associated with another object associated with the passed object (yep) has a type of 8. in which case, one of the methods in the chain returns a PrintQueue that gets passed back up the call stack. implicitly, and nested three levels in. ofc.
And if the API doesn't get its precious Hash, it exclaims that the merchant itself is broken, and tells the user to contact support. despite, you know, the PrintQueue showing that everything worked perfectly. In fact, that merchant's printer will be happily printing away in the background.
All because type checking is this guy's preferred method of detecting errors. (Raise? what's that? OOP? Nah, let's do diverging splintered-monolithic with some Ruby objects thrown in.)
just.
what the crap.
people should keep their mental diarrhea away from their keyboards.
Anyway. the summary of this long-winded, exhaustion-fueled tirade is that our second-most-loved feature doesn't work on our second-most-common merchant type.
and ofc that was the type of merchant i've been testing on. for days. while having both a [semi] coworker and my boss growing increasingly angry at me for my lack of progress.
It's also a huge feature, and the boss doesn't understand that. (can't or won't, idk)
So.
yep.
that's been my week.
...... WHAT A FUCKING BUFFOON!3 -
devRant Android users - if you are a user who can consistently reproduce a devRant app crash and wouldn't mind helping me please let me know. You can comment here or email me at david@devrant.io
I'm trying to get rid of a couple of remaining crashes that seem to be happening in the Android app but we've never really been able to reproduce any of them. Thanks!74 -
Dev manager: Can you fix this issue?
Me: Yeah, but i cant reproduce it using the explanation given in the ticket. Can i get a step by step guide and a confirmation that the issue is reproducible.
Dev manager: you're the lead dev, you figure it out.
askdjasfkjksadjkasd!!
Do you want me to spend an hour not developing things trying to guess? because that is how you make me spend an hour not developing things6 -
People on github opening issues saying shit like "aye, your extension crashes. Please fix or I'll uninstall. Thanks.". How am I supposed to fix an error I know nothing about? Error message? Extension list? Stack trace? Steps to reproduce? Nope. Nothing.
Don't be like this, please.5 -
OMFG!! I just discover a fucking bug in a library used by thousand of people in scientific community!! 🤩🎉
Started when my program outputting strange result. I was in a huge fight with my supervisor about one of the function from the library. My hunch was telling me that this function is the source of the problem, but he insisted that no such bugs could exist in the library that has been used by thousands of people.
I couldn't reproduce the bug so I just stayed silent at that time,
But now, I finally got the bug showing. Yeah I am gonna shove it to his face next week.✊
I will also let the people who maintain the library know.
Feels so good being able to be a contributor PR to this famous library 😎
The downside is now I can't use this function, I have to implement by own function.5 -
PM (on slack): "we’re about to deploy to production".
Me: "ok"
… I keep on working on a task / remain available for any post deployment issues …
PM (5 minutes later on slack): "deployment broke production! We need to handle this NOW!"
My dev colleague has already called it a day, but I’m still online
Me: "ok I don’t have access to prod, can you describe what’s going on? I can’t reproduce on any other environment"
PM: …
10 minutes go by
Me: "anybody there?"
PM: …
45 minutes later, I realize PM is offline
The following day:
PM: "ok we got prod running again" (turns out it was client’s fault for not updating a config we as devs can’t access)
PM: "but we’re REALLY UPSET! You guys need to be available to intervene for any issues following deployment to production! At least one of you should be available!"
Me: "but, but…" 🫠14 -
"IT BROKEN!", the QA tester spoke in unintelligible broken English.
The developer asked for more details.
Then the QA person attempted to explain the problem in a surge of verbal diarrhea and horrible English.
Why do we hire people who don't speak the language of the development team as our QA people? I have nothing against devs and qa guys from India...but it makes my job really difficult when I can't even begin to understand what you are telling me, or even worse...you just tell me "IT BROKEN!" and don't give me a single bit of useful information on how to reproduce the error.
There was this wonderful QA person I used to work with. Her name was Ranjana. She was a beautiful Indian girl with two children, and the best QA person I ever worked with. She took screenshots, grabbed logs, and gave steps to reproduce everything she found. And then one day at stand up we were told she had died. And since then...there has been no one who has ever come close to her level of excellence.7 -
How to reproduce:
human - F**k
process - Fork
Is that skeumorphism of words/sound by Unix developers ?5 -
Freaking tech support.
Freaking sparkhire.
Their 'one-way interview' bs only supports flash. Flash. in production. in 2019. Flash died years ago, and its support ends next year. What the crap?
Anyway, I finally decided I should do the interview since they already have all of my information anyway. Thanks, "privacy-conscious" third party. Totally appreciate it.
I spent half an hour and couldn't get flash working on their site (but all other sites were fine), so I contacted their support. I gave them all the relevant specs (inc. ofc browser), the steps to reproduce, and all of my attempts at fixing the issue.
To their credit, I recieved a response within a few minutes. To their discredit: their response was: "What browser are you using?" This question was followed by my report (including, ofc, my browser and all the other overlooked details), immediately followed by a "debugging info" section appended by their support service that also included my browser, os, and other specs.
Learn to fucking read.
Their suggestion? Use google chrome. Barring that: record your 20-30 minute video by holding your phone in front of your face the entire time. I am so not kidding.
They also asked what page i was having difficulty on. You guessed it: the page url was also included within that "debugging info" section.
It wasn't a form letter, either. I'd understand if it was all automated, but it was a real person who was really typing up the emails, and really didn't bother reading a damned thing.
I did end up getting flash working, but their "tech support" (script-reader) was entirely useless.16 -
Our web department was deploying a fairly large sales campaign (equivalent to a ‘Black Friday’ for us), and the day before, at 4:00PM, one of the devs emails us and asks “Hey, just a heads up, the main sales page takes almost 30 seconds to load. Any chance you could find out why? Thanks!”
We click the URL they sent, and sure enough, 30 seconds on the dot.
Our department manager almost fell out of his chair (a few ‘F’ bombs were thrown).
DBAs sit next door, so he shouts…
Mgr: ”Hey, did you know the new sales page is taking 30 seconds to open!?”
DBA: “Yea, but it’s not the database. Are you just now hearing about this? They have had performance problems for over week now. Our traces show it’s something on their end.”
Mgr: “-bleep- no!”
Mgr tries to get a hold of anyone …no one is answering the phone..so he leaves to find someone…anyone with authority.
4:15 he comes back..
Mgr: “-beep- All the web managers were in a meeting. I had to interrupt and ask if they knew about the performance problem.”
Me: “Oh crap. I assume they didn’t know or they wouldn’t be in a meeting.”
Mgr: “-bleep- no! No one knew. Apparently the only ones who knew were the 3 developers and the DBA!”
Me: “Uh…what exactly do they want us to do?”
Mgr: “The –bleep- if I know!”
Me: “Are there any load tests we could use for the staging servers? Maybe it’s only the developer servers.”
DBA: “No, just those 3 developers testing. They could reproduce the slowness on staging, so no need for the load tests.”
Mgr: “Oh my –bleep-ing God!”
4:30 ..one of the vice presidents comes into our area…
VP: “So, do we know what the problem is? John tells me you guys are fixing the problem.”
Mgr: “No, we just heard about the problem half hour ago. DBAs said the database side is fine and the traces look like the bottleneck is on web side of things.”
VP: “Hmm, no, John said the problem is the caching. Aren’t you responsible for that?”
Mgr: “Uh…um…yea, but I don’t think anyone knows what the problem is yet.”
VP: “Well, get the caching problem fixed as soon as possible. Our sales numbers this year hinge on the deployment tomorrow.”
- VP leaves -
Me: “I looked at the cache, it’s fine. Their traffic is barely a blip. How much do you want to bet they have a bug or a mistyped url in their javascript? A consistent 30 second load time is suspiciously indicative of a timeout somewhere.”
Mgr: “I was thinking the same thing. I’ll have networking run a trace.”
4:45 Networking run their trace, and sure enough, there was some relative path of ‘something’ pointing to a local resource not on development, it was waiting/timing out after 30 seconds. Fixed the path and page loaded instantaneously. Network admin walks over..
NetworkAdmin: “We had no idea they were having problems. If they told us last week, we could have identified the issue. Did anyone else think 30 second load time was a bit suspicious?”
4:50 VP walks in (“John” is the web team manager)..
VP: “John said the caching issue is fixed. Great job everyone.”
Mgr: “It wasn’t the caching, it was a mistyped resource or something in a javascript file.”
VP: “But the caching is fixed? Right? John said it was caching. Anyway, great job everyone. We’re going to have a great day tomorrow!”
VP leaves
NetworkAdmin: “Ouch…you feel that?”
Me: “Feel what?”
NetworkAdmin: “That bus John just threw us under.”
Mgr: “Yea, but I think John just saved 3 jobs. Remember that.”4 -
Dear Managers,
This is not efficient:
Boss: * calls *
Me: * answers *
B: there's a bug in feature ABC! The form doesn't work!
M: ABC uses a lot of forms. Is it Form A, B, or C?
B: Umm... let's just go on a Zoom call!
* 5 minutes trying to set up a Zoom call *
* 3 more minutes trying to find the form *
B: This form in here.
M: It works fine for me. What data are you inputting?
B: * takes 5 minutes trying to reproduce the bug * (in the meantime, the call is basically an awkward silence)
You spent 5 minutes wasting both of our times trying to set up a Zoom meeting, and another 8 wasting MY tine trying to find the bug.
This is efficient:
B: There is a bug in form C. If I try to upload this data, it malfunctions.
M: Thank you. I'll look into it.
You saved me 8 minutes of staring at a screen and saved us both another 5 minutes of setting up a meeting.6 -
How it is to be a dev in my country?
At bit of an odd question this week.
For me (in the USA), it's being technical support for *every* website my family uses.
Over the weekend my wife visited her aunt and I get a call.
Wife: "How do I create an ebay account?"
Me: "I don't like where this is going. We already have an account."
Wife: "Not for me, dummy, Aunt T. She found some books she wants to buy on ebay."
Me: "You go thru the process to create an account? Email, name, password, etc."
Wife: "We tried that, but it's not working."
<few seconds of silence>
Me: "Oookaaay...why isn't it working? Is there an error?"
Wife: "I don't know, we already clicked off of it. Something about the email."
<few more seconds of silence>
Me: "Can you reproduce the error and tell me?"
Wife: "Uggh..are you serious? We've done it like 10 times, its not working. Just tell me what I need to do."
Me: "If you can't tell me the error, I can't help you. I'm not there and can't see what you see."
Wife: "Stop being an asshole."
<Aunt T takes the phone>
T: "Said something about using another email address. Does that help you?"
Me: "Are you sure you don't already have a ebay account?"
T: "No, I don't think so. I hate ebay. but I really want these books. I don't want the same problems as last time."
Me: "Last time?"
T: "Yes, I bought a coffee cup on ebay from China and it never arrived."
Me: "OK, so you do have an account?"
T: "I don't know, I mean, I never got the cup."
Me: "What email address did you use? I'll send a 'remind me' email so you can reset the password and login"
<go thru the motions, she is able to login>
T: "Ahhh...I do have an account! There are the golf balls I bought for <husband> for Christmas."
<face smack>
Wife: "Why didn't you do this from the start? I thought you knew a lot about computers. We basically figured this out ourselves. Goodbye!"
<click>11 -
My head hurt today when I heard this: "We could not reproduce the problem but we put in a fix and are pretty sure that it will fix the problem."1
-
Im going to fucking murder the QA team if they don't stop sender bullshit issues!
QA: hey dev, there is an error with attached files.
Me: okay what's the issue?
QA: it's just a random file that gets attached. Can you fix it by the end of the sprint(tomorrow)?
Me: I need to investigate it a bit before I can tell you how long it will take, how can I reproduce it?
QA: idk, it was just there.
*several hours of testing later*
Me: I've tried to cause the 'issue' on my local server, the test server and the live server. But I haven't seen it and I have no clue what could cause it.
*30min. before I go home*
QA: dev you have to fix it before you go home! Because we have some other important issues you have to fix tomorrow!
FUCK YOU AND YOUR IMAGINARY ISSUES I'M GOING HOME1 -
So I was strolling around some open source project on GitHub, this particular one had thousands of issues. A lot of them were closed by the maintainer with comments like "I can't reproduce it", "It's working fine for me", "Pretty sure you have some bad configurations on your machine", et cetera, smh
4 -
As much as I love opensource I hate really hate some of its actvie community members (read this as "freetards" <-- see urbandictonary). As a .Net + web devloper with minimal C experience (I just started learning it) and literally no Python experience its not really easy to contribute for me to many (most) opensource software for linux. I am using some <unnamed software> and I found a <critical bug>, it was easy to reproduce and I wrote for list of possible solutions, found it in a code and linked and basically wrote a docummentation longer than any other I ever wrote for every single project I did ever, combined. This <software> was critical for my server and since owner of github repo and few other people there were really active, I hoped that this bug with pretty good documentation will be solved fast, I went to my bed with a heroic feeling of an open source community contributor that helped saving world. I was horribly wrong. Tomorrow, I got 3 passively agressive responses from owner and other 2 freetards that summed up said <other1>:"oh thats nice, fix i yourself and commit it", <other2>:"have a sex with yourself" in a nice way, and <owner>: "fix my softwate and create mrege request". After replying that I have no experience my Python skills are not on a level requied for such an action, he messaged me on twitter I have linked to my GitHub profile saying even less nicely that I am a "retarded c*nt" and that I should learn Python and fix it myself. This makes me stay with my Windows based Server for some time now, fuck this. I googled his github nickname and guess what. Our main freetard is admin on an <unnamed linux forum> and mebmber of many other "computer help" with literally half of his posts just slightly toxic posts about how everyone should use linux and how supreme it is ober anything other, the other hals was crying why linux has only 1% of market share. Oh boi I am not sure why but ITS MAYBE BECAUSE OF FREETARDS LIKE YOU.
And the funnies thing is, hes not only freetard, he is just fullstack retard. One of his posts is "helping" to some <noob windows user> installing Linux. tl:dr for this las part: Freetard basically wiped all data of that <noob>.
PS: Bless everyone who do not respond "oh nice, now you can do it yourself"10 -
My project at work (an electron/angular desktop app) has an exceedingly rare bug that causes it to crash-to-desktop while loading. Nothing about the bug makes sense, and there's no way to catch or detect it until the next run, and it happens 100% of the time for affected users.
There have been six confirmed cases so far (out of 500k+ users), and nothing linking them together. None of the fixes discovered by those users have worked for other affected users.
The worst part?
I was the first of those cases. I inadvertently fixed it for myself and haven't been able to reproduce it since.
I'm stumped!19 -
You know what really grinds my gears?
When a manager writes up some bullshit "this doesn't work".
Then you waste your time following up, and they say, "oh yeah, this so and so pop up came up with validation error X".
YEAH? AND I'M SUPPOSED TO KNOW THAT WHEN YOU WRITE ABSOLUTELY NO STEPS TO REPRODUCE, JUST COMING TO ME WITH "HEY, X IS BROKEN" GOD JUST GET FUCKING 1% TECHNICALLY LITERATE THATS ALL I ASK FOR I'M SO SICK OF YOUR SHIT2 -
So Friday afternoon is always deployment time at my company. No sure why, but it always fucks us.
Anyways, last Friday, we had this lovely deployment that was missing a key piece. On Wednesday I had tested it, sent out an email(with screenshots) saying "yo, whoever wrote this, this feature is all fucked up." Management said they would handle it.
The response email. 1(out of 20) defects I sent in were not a defect but my error. No further response, so I assume the rest were being looked into.
In a call with bossman, my manager states that the feature is fixed, so I go to check it quickly before the deployment(on Friday).
THERE IS NO FUCKING CODE CHECK-IN. THE DEV BASTARD JUST SAID THAT MY USECASE WAS WRONG, SO MY ENTIRE EMAIL WAS INVALID.
I am currently working on Saturday, as the other guy refuses to see the problem! It is blatant, and I got 3 other people to reproduce to prove I am not crazy!
On top of that, the code makes me want to vomit! I write bad code. This is like a 3rd grader who doesn't know code copy-pasted from stack overflow! There is literally if(A) then B else if(!A) then B! And a for loop which does some shit, and the line after it closes has a second for loop that iterates over the same unaltered set! Why?! On top of that, the second for loop loops until "i" is equal to length-1, then does something! Why loop???
The smartest part of him ran down his Mama's leg when it saw the DNA dad was contributing!
Don't know who is the culprit, and if you happen to see this, I am pissed. I am working on Saturday because you can't check your code or you lied on your resume to get this job, as you are not qualified! Fuck you!15 -
During QA for a huge project when our dev team was confident of the stability of the project, We started introducing small bugs, QA team use to raise bugs in Jira, we marked them as not reproducible.
Frustrated QA started coming to our cubes - at this point dev team worked in a perfect coordination like a man to man marking in hockey. While one dev asked QA guy to reproduce the bug in front of him while the other dev has already fixed it.
Continued for a couple of days till our team lead was satisfied with the revenge. -
I once had to make a shitty canvas game as part of a marketing campaign when I worked for an agency, for fuck only knows what. You dragged a shopping trolley back and forth in an aisle, and got points for catching items that fell from the top.
The initial round of feedback had the complaint that sometimes players weren't receiving points for items. I spent a night playing this senseless game over and over, but I never failed to get the points for an item. I was pretty confident that it worked, it wasn't like the logic was complex, so I sent it over.
Second round of feedback had the same complaint. They were getting quite annoyed by it, said that it was a bad user experience. Again, I could not reproduce it at all: the game was an equally tedious waste of life on every device I tried it on.
In exasperation, I asked the sales guy whose pitch it had been to get me a video or a more detailed report. The client was quite arsey, as they saw it, at having to do bug-fixing for us, but they did agree.
Anyway, it transpired that they were angry that players were not receiving the points for the items they *failed* to catch. The way they saw it, the game wouldn't be fun if you were punished for not catching items - so they wanted the player to get ten points for every item on screen, regardless or not of whether they caught it in their trolley. Of course, I thought. Silly me.
I was actually quite impressed at how a marketing department could accidentally undermine the very notion of a game whilst seeking to make one more fun.8 -
That moment that you get some kind of pretty critical error/bug/crash in an application in production and you can't reproduce it anymore and you're just sitting there praying that it won't happen again 😥4
-
my boss asked me to log in 1h30 after i logged off because "a user has been experiencing this bug the entire day and i should fix it because we're on maintenance tomorrow " but a) it's a known bug that we can't reproduce, he should've notified sooner the issue; b) it's not a big deal, i can fix it tomorrow, it's just not ticking a column in the database; c) I'm off work, go cry about it2
-
My internship is coming to an end and I think my boss is testing my limits.
So, in the beginning of this week, he assigned me a non reproducible bug that has been causing trouble to the whole team for months.
Long story short, when we edit or create a planned order from the backend, once in fifteen, a product is added to the list and "steals" the quantity from another product.
Everyone in the company has experienced this bug several times but we never got to reproduce it consistently.
After spending the whole week analyzing the 9 lines of JS code handling this feature, reading tons of docs and several libraries source code. I finally found a fix by "bruteforce testing" with selenium and exporting screenshots, error logs and snapshots of the html source.
This has been intense but was worth the effort, first, I fix a really annoying bug and second, I learned a lot of things and improved my understanding of Javascript.6 -
I've told the same story multiple times but the subject of "painfully incompetent co-worker" just comes up so often.
I have one coworker who never really grew out of the mindset of a college student who just took "Intro to Programming". If a problem couldn't be solved with a textbook solution, then he would waste several weeks struggling with it until eventually someone else would pick up the ticket and finish it in a couple days. And if he found a janky workaround for a problem, he'd consider that problem "solved" and never think about it again.
He lasted less than a year before he quit and went off to get a job somewhere else, leaving the rest of our team to comb through his messy code and fix it. Unfortunately, our team is mostly split across multiple projects and our processes were kind of a mess until recently, so his work was a black box of code that had never been reviewed.
I opened the box and found only despair and regret. He was using deprecated features from older versions of the language to work around language bugs that no longer existed. He overused constants to a ridiculous degree (hundreds of constants, all of which are used exactly once in the entire codebase, stored in a single mutable map variable named "values" because why not). He didn't really seem to understand DRY at all. His code threw warnings in the IDE and had weird errors that were difficult to reproduce because there was just a whole pile of race conditions.
I ended up having to take a figurative hacksaw to it, ripping out huge sections of unnecessary crap and modernizing it to use recent language features to get rid of the deprecation warnings and intermittent errors. And then I went through the same process again for every other project he'd touched.
Good riddance. -
"Never trust a user or client, when dealing with 'bugs', always try to reproduce."
very useful advice from an old colleague1 -
Noticing a bug once or twice but not being able to reproduce it after that gives me anxiety. This job is detrimental to one's mental and physical health. Serious question. How to unfuck yourself?4
-
Life as a developer:
Yesterday I could reproduce the bug everything I ran the program, but I could not debug it. Visual Studio would not break at my breakpoints.
Today Visual Studio works fine but the bug cannot be reproduced at all.
I should have become a florist instead...4 -
Add a random string (like "AnyBrowser/1.2.3") to your user agent string, and get warnings about unsupported browsers, reduced functionality, and Google drive completely refusing to start at all.
It's the very same browser, just another user agent string. Ever heard of feature detection? Ever heard of usability, accessibility, progressive enhancement? How can developers be so lost in 2022?
I just tried to reproduce the reason why Vivaldi stopped adding their brand to user agent strings but sails under false flag pretending to be Google chrome. So it doesn't show up in browser statistics either and Google people can keep thinking everyone is using their shitware.3 -
Unsurpisingly, an in-house client reported a visual bug in IE. So I candidly asked him which version of browser he was running. He told me with confidence: 11. As I couldn't reproduce the bug I asked him where he found the version number. He answered: "below the laptop on a sticker".
Well, it happened to be the year of construction of the computer.2 -
Sometimes in the middle of the night I have awesome design ideas (for logos, UI, etc.), so I wake up, turn on my PC, open Photoshop/Illustrator/XD, and try to reproduce the thought making it a real thing.
Every fucking time the result is garbage…3 -
That feeling when you spend the day fearing a ticket in your queue and when the moment comes and you try to reproduce it, you discover that it was actually resolved the whole time..
2 -
A conversation with my dear sister...
She: Hey Davide, why does this message appear?
Message of youtube: "This video is not available in your country"
Me: It means that whoever uploaded the video wants to reproduce it only in the country chosen by him during the upload.
She: Ah, but how can I do to see it?
Me: You have to go through a proxy. Wait a minute... I arrive...
She: But using the incognito mode could not work?
Me: No 😑😑
Me (thinking): No please... no... please... what was the question? No...
I like you anyway ❤3 -
Trying to find a bug. Found a possible line in the code where it might be originating from.
Not I put a breakpoint in there. I can't reproduce the bug anymore.
Sometimes I think I should just go home and play games :(2 -
Fucking lazy customer support that files bugs with "<some functionality> is not working" with no steps to reproduce or any other description of the issue, deserve to die in the same hell as it is figuring out the rest of the details.
-
Working with client at different timezone (+3 hours difference). Client time: 5 P.M.
C: a blocker issue found
Step to reproduce:
Step 1: import the attached file
Step 2: blabla
Please get this fixed today.
Me: *where's the attached file?* Opens up ly*c, type his name and.... status offline.
Okay then, time to post my first rant. And get depressed until cob. 😔1 -
I hate lying customers.
Today a customer opened a support ticket related to his website account. Apparently he is losing his session right after the login success.
I've debugged everything, checked all logs and couldn't reproduce it.
I know every bit of business logic on the website by heart.
The only explanation could be that his browser either doesn't allow cookies or expires them after page change.
So I asked him to check.
"Yes, cookies are allowed in my browser" he wrote.
Well... fuck me... I will change the code to put the session ID in the URL as well. If it works - and I'm 100% sure of that - I will personally mail him a collection of the finest turds.4 -
Aaaaand my team leader once again worked directly on the DB without touching the code, so I can't reproduce his local DB on my machine.
JUST WHY
4 -
Things that piss me off in github issue comments:
- "halp it doesn't work!!!" no description, no steps to reproduce, nothing.
- people writing comments in a random ass language that nobody understands so everybody except them has to go through the effort of translating it.
- issue comments that escalate into a meme fest because the issue was linked on reddit or some other platform -
STOP sending me fucking videos of the bug you are experiencing. I don't get paid as much as I do to sit around and watch your stupid fucking screen captures for 37 minutes just to find 30 seconds of meaningful information to reproduce something you could have put in a paragraph and emailed to me.
Either you meet me halfway and actually understand the expected outcome and how it differs from what you experience enough to verbalize it, or I ain't fucking fixing your shit. For fucks sake, a 40 minute screen recording with no audio does NOT count as a valid reproduction.3 -
I tried to switch to protonmail from gmail 2 years back. But left in a week when I lost 2 important drafts.
I informed them about the bug. And the steps to reproduce it. But they denied to fix it.9 -
I’ve noticed a bug in HR that I would like to report. Steps to reproduce:
1. Get offer on LinkedIn/Email
2. Respond politely and optimistically that you’re interested but would like to scale down you’re hours to 32 per week, changes in pay are accepted.
Result: 404 Not found
Expected result: I’m only human let me work part time pls6 -
Costumer called.
feature xyz doesn't work.
Spent hours trying to find the bug causing the malfunction, couldn't reproduce it on my devices.
Called to the customer to have a look on his device.
Feature xyz works as intended, the only bug: Too less patience at Layer 8.
Device just needs a little moment to establish a connection.
Patience is a virtue. -
> Laravel lets you create migrations to manage the state of the DB
> your colleague doesn't give a flying fuck, just raw SQL on the db to perform every change
> performed initial insertions without seeders, can't reproduce his db on my local environment
> can't even run migrations anymore 'cause it would break everything
7 -
If Schrödinger submitted his cat experiment as a GitHub issue, what label would it get?
"can't reproduce".2 -
Me: OK, Google.
Google: Hi, how can I help?
Me: Open example.com
Google: OK, which browser?
Me: Google Chrome.
Google: Sorry, I didn't get you.
Me: Google Chrome.
Google: Sorry, I didn't get you again. Just say the name of the app.
Me: *Looks at the list and finds Chrome (without 'Google')* Chrome
Google: *Opens Chrome*
I couldn't reproduce it as the. Latest version of Google Assistant now opens the page in a WebView.
7 -
Depressed since yesterday.
Updated all our clients Dialers. Stellar performance. Suddenly one of 15 can’t hang up three way calls.
It’s one of our biggest clients. And they just started. We upgraded the dialers so the answering machine detection would improve for them and it did, along with vast performance upgrades as well. Suddenly, this issue.
2 days in they pull the plug until we fix it. The issue is sporadic and we cannot reproduce. No one else is having the issue. I can’t even debug it properly as it’s a third party dialer with no customizations on it. I found out where the error is, but no idea the workflow they got it to happen with or why. It’s so frustrating. It happens using the dialer native interface, and our integration via api calls. The channel doesn’t get sent to the command for some random reason, and only sometimes.
So even if it’s fixed they don’t trust the system. Now they are losing the full integration we have with the crm and dialer and it’s going to be a mess of data for them. All because of this one issue. They love the CRM though...
If they had just stayed on one more day I’m sure I could have found it. Now I have to play forensic scientist and look through old data, without being able to see the client code that was causing the issue.
Just threw some cash down to be able to talk to the dialer engineers and hopefully see what’s up. What a nightmare. And I have so many other projects for the platform due so soon...
Sigh. Super depressing.1 -
"Did you manage to reproduce this issue in-house?"
Yes, off course we managed to reproduce your fucking random reboot issue that happen to two in thousand customers and might happend just after boot of after several hours or days or not at all when you, as you said yourself, were doing nothing. While at it we also turned lead to gold, water to wine and resurected Elvis (although he is a little bit grumpy and mumbles something about brains). -
teamLeader: We can't release because your change doesn't work, it breaks on the machine ABC123
iHateForALiving: I diagnosed the issue and I still don't know what's related to. BUT I'm 100% sure it's not related to my change, or anything that has changed in the last 24 months. Anyway we can take a look at this, just give me admin credentials for this machine.
teamLeader: no we can't.
iHateForALiving: ... Wait what? How am I supposed to reproduce the issue? Why can't I access the machine?
teamLeader: It's in use by the testers.
iHateForALiving: What for?
teamLeader: ... Educational purposes!
They report some issue on some particular machine, then refuse to give us access to said machine to reproduce the issue because they have "educational purposes", me and God know fuck kind of education I have in mind for this circus but as soon as I get my hands on them they'll get a hint.1 -
So today I lost around two hours because I solved a bug before trying to reproduce it 👏👏👏
The client reports the bug, I open up VS and already go to the source file that might be affecting it, see a variable assignment that was just outside of the If statement it was supposed to be in, and after that I try to reproduce the error.
Guys, please, be smarter than me next time.3 -
I'm facing big issues on one of my apps and luckily a user is helping me doing some tests as I can't reproduce the issue. He just sent me an email and guess what?! He wrote "happy weekend". No. It's not going to be an happy weekend for me.1
-
@dfox in case you havent already discovered it i have found a bug with notifications in the iOS app.
Steps to reproduce:
1. open notifications
2. tap one of them as many times as you can really fast
3. It generates a new view controller for every time you tapped it.
obviously having to tap furiously is a bit obnoxious but i originally noticed it when the app was running slow and i tapped the notification a second time. It created 2 new view controllers instead of one so i had to actually go back twice to get back to the notifications screen.6 -
So, by a cruel twist of fate I ended up on the front line of tech support for the app we've built. It's aimed at non-IT professionals, in general people who are not expected to know too much about computers but who should have at least two neurons to bash together in their pretty little heads.
No.
It really makes me drop my faith in humanity considerably. Clicking a confirmation link is too much. Filtering an excel sheet is too hard, despite it being their technically main work tool. Tickets are basically "shit's broken go fix". What is broken? How to reproduce it? Why do you expect the person on the other side of the screen to be a fucking diviner? I recently ran all out of dove guts to search for the answers of your questions.4 -
I was working on a new feature for this legacy project.. Just minding my own buisness then all out of the blue I got an email from our client (before the email I exported the live database because I needed to reproduce a weird bug) saying the sync stopped working
<backstory>
The database needs to sync every 15 minutes because it has a master-master relationship with a 3rd party database..
</backstory>
So I was like shiiit! Did I do that!? So I checked the logs, nothing... I called the 3rd part to check if they have problems, nothing.. Then I checked the network logs... Again all fine... 30 nervous minutes later, I got a new mail... Saying it finally synced... Still have no clue what happened or if it ever was a problem... God damn clients man... -
Should have kept a copy of my best code off of my work computer. That way it wouldn't have been confiscated along with the computer during the layoffs. [sniff] I had some beautiful Stored Procedures I can't satisfactorily remember how to reproduce. 😅4
-
So what's up with some devs, QAs and managers that create bug tickets with little to no information on what is the actual bug? I can semi-understand in the case where you document it only for you to read later.
Fuck you if you think that a ticket with only a title saying "fix all the bugs for this release" or "this feature is not working" is an appropriate way of documenting a bug.
Fuck you even more if when you are being asked to provide more info to reproduce the issue so someone else can actually be sure it is fixed or not (environment, steps, expected result, actual result, etc.), you simply say that you don't have the time for it and documenting tickets is a waste of time.
Hiring YOU was a waste of time!4 -
To peoples asking on StackOverflow or making an issue on Github:
Please, include enough code to reproduce your issue.
But don't put your entire project either
It should be as easy as possible to run and read your code.
Otherwise, peoples trying to help will get lost and give up2 -
my boss, recently: "Partner company is complaining about seg-faults in our software" [the system is still in testing, not deployment]
me: "tell me what steps to reproduce the error and I'll fix it"
boss: "I'd like to prevent seg faults from happening no matter what"
...I literally can't even at this point5 -
The most crazy issue I've fixed was caused by a TCP behavior which I didn't know, called the "half-closed connection".
There was a third-party application installed on a production server which called a LDAP server for retrieving users information. During the day we had several users using the application and all worked fine. During the night, when the application was not accessed, something happened and the first call to the application in the morning was stuck for about 5 minutes before returning a response. I tried to reproduce the issue in a testing environment without success. Then I discovered that the application and the LDAP server were located on two different networks, with a firewall between them. And firewalls sometimes drop old connections. For this reason network applications usually implement a keep-alive mechanism. Well, the default LDAP Java libraries don't set the keep-alive on their connections. So, I found a library called "libdontdie", which force the keep-alive on the connections. I installed the library on the server, loaded it at the startup and the weird stuck behavior in the morning disappeared.2 -
Three days ago my focus was shifted from a development role to a support role. I was shifted to replace another support guy who had used fraud to get the position. I have no experience with this role but there was decent KT and I'm catching on fine. During onboarding and KT I'm serving as the first contact for new tickets and whatnot...
Today I got a ticket with an error on our production instance that no one had ever seen before. It prevented the guy from using our service entirely. I tried to reproduce it and... I couldn't use the service either. No one could. Everything was down. I could see the sweat building on my manager's forehead.
Thankfully another member on my team has done a bit of support before, so we collaborated with each other and other teams throughout the day to figure out what's wrong and how to fix it. I'm listening to them chat remotely as we speak - so far I've been working on it 9 hours straight.
This service is used by everyone - it's a business critical service with due dates on actions and escalations to managers... Imagine if the support ticketing service for your company crashed. That means a lot of people are asking what's wrong, requiring extensions, etc. I've been answering to managers and seniors in the business throughout the day.
The best part? We figured out why the server went down, and the reason is fantastic: someone updated the server's code without telling anyone, and all they had done was remove critical parsing code. Just took it right out, pushed, redeployed. We don't know who did it or who even has access to do that. I guess I have some detective work cut out for me after we've fixed everything that was broken by that.
I miss coding already.1 -
We basically don't unit test at work. I write some tests for my code and honest to God people complain I'm wasting time saying a test bed and manual tests are good enough. We don't write test beds for about half of our production code and rely on integration tests for the rest. We only test release builds which have been symbol stripped, I get handed a crash report with no stack trace that I'm unable to reproduce and expected to stay late to fix it for some arbitrary internal deadline.
I've since moved to R&D where basically I'm left to do my own thing so it's better.
We don't project manage. Project leads take time estimates and double them so management might cut them some slack. This doesn't matter because management made up time estimates before the project started. Last project I was on had a timeline of 3 months and took a year.
We have released broken products. Not that any of the above really matters, our software products have made about 50k revenue in 2 years. There are 6 people on software. Fortunately hardware has made about 3 mill. That said our hardware customers are getting frustrated with us as we keep fucking up, shipping broken products and missing deadlines.
I've been working there about a year and a half and will be looking for a job at the end of the current project.
I joined devRant about when I was most pissed off with my job, my rant frequency has definitely gone down since I moved over to R&D. -
2nd part to https://devrant.com/rants/1986137/...
The story goes on...
After I found more bugs that seem to be related to the communication break, and took a closer look, I sent detailed logs of my research and today we had a conference call.
"We have 2,5 million user, our system is widely-used and there is no plan to change it" they said.
And "We cannot reproduce the issue, but even if there is one, you will have to work around the problem, because we cannot make changes on our side" was one answer
As well as "If we would make changes, we will have to re-certify everything"
So I said we told 'em about the issue to let them improve their system. And I can work around it, I already figured out a solution for my side, but if there is a bug, they'd better fix it for future releases.
And with my additional research I have a bad vibe of some kind of memory leak involved on their "certified" implementation, and that could trigger various other problems.
But it is as always, if I try to be nice, I just get kicked in the ass. I should really be more of an asshole. -
Software runs fine on several in-house instances. First time customers hosting it themselves. Runs fine. Users start using. Server need absurdly high processing power and fucks up. I can not access customers Server to debug. Only hope, get copy of their images to reproduce their setup. And have *** one single fucking hour *** to go into it before having to tell in emergency meeting if we can fix it or they would blew the project.
I didn't expect, but found the cause, a single very badly written query. Written by myself years ago I have to admit.
They also gave me one hour to produce a patch. I did but but lost so many hair.4 -
This hurricane fucking sucks. My power was out nearly all day today. It went out at 6ish this morning, and didn't come back on until 4-5ish in the afternoon.
I was coding on my laptop, trying to reproduce the sampling procedures we talked about in AP stats (hoping that I'd better understand the material if I could connect it to stuff I was doing in another class), and there was a piece of syntax I had forgotten over the summer, and it irritated the hell out of me that I couldn't just Google the answer.
Eventually I just drove to a Starbucks and hung out there for about an hour or two till the power came back on. I was terrified the power would just go out again before I got back home.3 -
So in the project I’m working on we were about to do a push to live, no major functionality just minor adjustments and nice to have stuff. One of the things I did was a reminder, nothing special just sends an email out if something hasn’t been done for 3 days and then sends an email every day following. Push to live and every thing goes fine with no issues. Day 1 there are no issues. Day 2 there are no issues. Day 3 and I’m inundated with people telling me that the emails are getting sent to practically everyone, shit. What have I done? What have I missed?
So I start looking at the live database hoping for a data problem, no such luck. I look at my code looking for something blatantly obvious but nothing. I start replicating the data but I can’t reproduce this bug and it’s annoying the hell out of me. I checked one of the emails that the client sent to us more thoroughly and seen that it was sent at 07:01. This is odd as our webjob runs at 1am so I start looking at environmental factors and started looking at release management, more out of hope than expectation. I check the staging environment and see that the webjob ran at 7:00. Coincidence I thought, the webjob gets packaged on the release pipeline and everything in the database was dummy data anyway but I’d better check anyway. The database was an exact copy of the live database, turns out a “senior developer” wanted to sanity check everything by running live data through the code so he copied the database over. It was fine for the first couple of days but the data was now 3 days out of date triggering my email code and I get hit with the shit storm. I’ve never met such an incompetent developer in my fucking life, functions 700 lines long, classes that are over 20000 lines, repetition every where and the only design patterns he’s used is when he picks up a child’s colouring book. I can live with the fact that he writes code like someone on their first day of University But copying a database because he wants to “visualise” the fucking data is absolutely farcical. No wonder the project is fucked with a “developer” (in the loosest possible use of the word) is at the helm. -
today is the day i will write a bunch of passive agressive redmine tasks with fucking steps to reproduce the fucking bugs and fucking info on the fucking environment of the fucking bug! i mean you have the time and skills to attach bunch nonsence screenshots with color coded arrows and circles, carefully cropping out info i could actually use, like the fucking url and browser, but you cannot consolidate your thoughts well enough to write down the steps that led to a bug??? fuck these people3
-
Did anyone ever felt that everyday is a loop? Mine is as follows
Bug Reported -> Try to reproduce -> Check on web -> Check iOS -> Check iOS 13.x -> Update or get hold of other simulator/devices -> Check iOS 13.x2 -> Fix it -> Now it breaks on Android -> Fix it -> Get it QAd -> QA feels their should be some more design changes -> Make him/her understand that what is priority for now -> Now everyone has started testing app and everyone have their opinion (designers are asleep at this point) -> Get all of the team in sync -> Start release -> 99% -> Some yells "wait" -> One more thing -> Sleep with nightmares -> Repeat
PS: We have a responsive web application that is also wrapped in Cordova for iOS and Android.5 -
QA: There is a problem
Me: Ok how do I reproduce it?
QA: You do x
Me: I have done x and there isn’t a problem
QA: Oh it only happens sometimes
Me: Fair enough, I’ll try a few times
...
Me: Are you sure x is how you do it?
QA: Oh no actually it’s y
FML2 -
the funny thing about bugs, they reproduce on their own just fine, and often where you don't want to them. the trick is figuring out how they reproduce so you can work out how to make them stop reproducing. to do that, you have to intentionally reproduce them.2
-
Devrant freezes when switching to different app then back again. A bit random though, has happened a couple of times but can't reproduce it.3
-
Full round of QA, full round of internal testing, and the client still finds a bug nobody can reproduce.
🤷🏻♀️🤷🏻♀️🤷🏻♀️1 -
How are you supposed to fix bugs in your program where:
1. it has been investigated before and was not found how to reproduce it
2. it cannot be tested at all
3. never happens on the test environment
fml19 -
This week was one of those weeks were it feels like it's never ending
Monday, delayed trains and the legacy project's new update went live
Tuesday, not a lot of work so I did some self study (best day of the week)
Wednesday, again train delay, and some funny little sh*t ripped the valve from my bike... I mean sure if you let the air out, haha little fun but completely removing the valve? That's just f'n low...
Thursday, the legacy project had a weird bug that I can't reproduce but has to be fixed before the end of this week...
Friday... To be continued... I hope it will be a quiet quick and easy day... 😟3 -
24 hours while a "pool" in my school (pool is a two-weeks fast formation where you can work 24h/24 to understand how a programming language works)
It was a C++ pool with a garbage subject meant to reproduce the functioning of a factory with... Factories.
Unit tests were use to mark us, so you know the struggle6 -
Yesterday was a horrible day...
First of all, as we are short of few devs, I was assigned production bugs... Few applications from mobile app were getting fucked up. All fields in db were empty, no customer name, email, mobile number, etc.
I started investigating, took dump from db, analyzed the created_at time stamps. Installed app, tried to reproduce bug, everything worked. Tried API calls from postman, again worked. There were no error emails too.
So I asked for server access logs, devops took 4 hrs just to give me the log. Went through 4 million lines and found 500 errors on mobile apis. Went to the file, no error handling in place.
So I have a bug to fix which occurs 1 in 100 case, no stack trace, no idea what is failing. Fuck my job. -
Wasted a day as Shitlock Holmes with the build chain.
It would not reproduce the firmware hexfile that had been checked in. Reverse engineering that along with the mapfile to find out the cause, it was a const string that was guarded by an ifdef from another file that was auto-generated as prebuild step via a script that fetched some version control info.
Or, it would have been if the installation instructions had been correct and someone had described that no spaces in the absolute path name of the project are allowed. Otherwise, that shit just failed silently.
I then had to reverse engineer the intended workflow from the commit history in the version control to figure out that the last dev obviously hadn't quite understood the project specific workflow and how the version control interacts with these build scripts.
At least, I finally did get a matching hexfile.1 -
I need some time off. Just had this convo with a dev-manager about an 'issue' with our system change mgmt calendar (Blazor) app.
K: "In the system drop-down, it's not filtering when I type."
Me: "Let me check <I attempt to reproduce>, yep, not working. Do you get the same error? Looks like duplicate data from the database is causing a problem."
<this is over MS Teams, about 5 minutes go by with no response, then>
K: "No error, its not working."
<I find the bad data, delete it, TADA, the filtering is working again>
Me: "The filtering is working again, at least for me. You sure you didn't see an error?"
<wait 5 minutes again>
K: "No, no error."
Me: "You didn't see a little red banner at the bottom and in all caps..ERROR"
<send him a screen-shot of the error I still had in another tab>
K: "Yes, I saw that one, but no other errors. Filtering is working again. Thanks"3 -
When a tester found a bug that you never think of and you cannot reproduce it. What is your response ? 😄3
-
Had an AI course in my 3rd year at uni.
Well turns out, we learnt how to reproduce a switch case in prolog.
Hated it. Felt raped by stupidity. Missed 3/4 of classes but was still better than most at reproducing switch lol.1 -
In an IT management class, the professor wanted us to estimate the operation costs for a small IT company, breaking them down by service offered. I remember creating a markdown file, multiple times executing the line `echo $RANDOM >> estimations.md`. We rounded the numbers slightly, pimped the document a bit and submitted a nice PDF. When we had to present our work, the professor asked us how we had proceeded to calculate those results. We told him a story about an Excel file we worked on, but did not submit, because we thought he'd be interested in the end result and not care about those details. He asked us to submit that Excel calculation, because he wanted to comprehend our method. So we got together, created an Excel sheet, copied our "estimations" into column C and called it "service cost". For column B, we used the same "cost per man hour" value (scientifically estimated using the RAND() function) for every row. Finally, we divided the "service cost" by the "cost per man hour" for every row, put the result in column A and called it "effort (in man hours)". The professor, being able to "reproduce" our estimation, accepted our solution.2
-
I don't know why I'm doing this but when I go to websites that aren't mine and found that there's a bug in their site or system, I kinda happily report these bugs and issues to their email with screenshots, findings and steps to reproduce the bug.
Just recently, I just went to a site and found a peculiar timeout error, eventhough it was less than a second to respond back. Only to find that there was an undefined JavaScript variable in their code.
Is there a bug bounty for fixing code?6 -
fucking T_PAAMAYIM_NEKUDOTAYIM when you want to reproduce it to someone, who does't believe this, I simply cannot do it, but if you want to just do your thing, it gets you on every corner6
-
Why can't my team including my boss learn to stop making assumptions... And mixing seperate issues into one...
If there's a fucking production issue, first step is to reproduce it... AKA ask what the user did and what he expects....
Not...
User: hey we call this url and get an error
Dev: ok rollback -
Found a reproduction to a bug that all the team tried to reproduce for 2 days. Damn this feels great!1
-
I hate it when someone asks me for help in a part of his code, then I find that the problem is the whole code not just that part.
I have 3 options:
- try to make it work, and get lost in his shit, not refactored code.
- tell him that I am not that good so he get out of my face
- kill him, so he can reproduce
PS: just kidding -
An issue occurs, resolve it with a "Could not reproduce", client asks for a report on what happened, what parts did it affect and how will we prevent it in the future...
To make things worse it looks like it might have been an issue with MSSQL server throwing weird data out and not a problem with my code...10 -
I was in dependency hell for two days.
Im a junior working in a team creating an ember app. Suddenly a main component refuses to work since an addon threw "EmberObject undefined"... Nobody could reproduce it and we where out of ideas, so I tried fixing it for 2days (7h total). I finally got it working after updating yarn :D
It never felt so good working again :) -
I absolutely treasure the bug reports we get from users. Nothing helps bring the product closer to perfection than the informed critique of end-users.
Recently, however, this one dude is filing a new fucking report every time he encounters the same fucking bug. "X happens for operation Y on file A"
"X happens for operation Y on file B"
.
.
.
"X happens for operation Y on file Z"
Jumping Jesus Christ, man, I'm pretty sure we can identify a pattern after the first two!
I don't expect him to know about the work we do to reproduce a problem after one report but fucking hell, have some faith that we'll get the picture after two or three.
These are fully detailed bug reports too, so it's not like he's just being a troll. -
Colleague: The user said this [Total line] is not the average she expected.
Me: Okay? But she knows that averages are weighted?
Colleague: I'm gonna call her.
... 30 minutes fast forward
Colleague: Okay she wants an average, but she wants us to divide it by something else.
Me: Okay? But she knows an average is the sum of one thing divided by the sum of another thing and not just anything?
Colleague: Yeah, she said she wants it to be kinda this in relation to that.
Me: Okay, so rather some percentage value?
Colleague: To be honest, she just wanted to reproduce this old Excel formula.
God has left this planet ... and I admire my colleague for not completely freaking out in the face of the user.3 -
Buy dell, hp, lenovo and any other craptop company out there and fire all the numbnuts working there so that they slowly die of unemployment in the fucking gutters where their useless asses rightly belong. Oh and castrate them too so that they don't reproduce.
I'm considering going full Lannister on them but that might be too harsh.5 -
Fack I hate this CMS we have. Using Fetch and sending data as encoded JSON doesn't get parsed nor recognized by the CMS. I was pulling my hair out, understanding the differences, switched back to XHR... and then noticed the buggar:
XHR sends data as "FormData()".
I switched everything to FormData and TADAAA IT WORKS MOTHERFUCKA
Lost a whole fucking day on this trying to understand whether it was my code or the CMS the problem.
Ah yes, of course, I had to reproduce the CMS on my machine, instead of having the developers lend us a "development" platform on it, so obviously I don't know what's happening under the hood :))))))))2 -
Been put on debug duty, shit fucking SUCKS ASS.
Demotivating as hell seeing other people implementing cool features while you're doing this stupid shit trying to reproduce bugs that appear in production. Fucking hell.11 -
How to reproduce:
- have a single login form for admins and ordinary users
- add a second button right next to 'login' which reads 'login as admin' in order to have a separate login for them
- release a new version of software with this change solely and changelog informing about it
- have customers admin tell you everybody is complaining about not being able to login with thwor admin accounts5 -
- Bug-Report -
Description:
If you go to the comments section on your profile and click on an comment you made to a collab, devRant will load it as a normal rant instead of a collab and, therefore, nothing is shown.
Device Details:
- Device: Phone
- Android Version: 6.0
devRant Version:
1.9.0.3
Steps to reproduce:
- Write a comment to a collab
- Go to Profile -> Comments
- Click on that comment
- It will load it as a normal rant (See image)
Actual behaviour:
Show as normal rant
Expected behaviour:
Show as collab
I hope you can reproduce...
@dfox, @trogus8 -
That sadness when you cannot figure out reproduce the performance of a program and the VM won't cooperate :(
-
Client (who hosts our programs on their website) sends an email there is an issue! Resolve is asap. - I drop a brick if my boss finds out about this he will kick off.
I look into it the best I can but there is no testing environment for their website so do the best I can on our environment. Every thing seems to be doing exactly what it should and can't reproduce. So I email client I can't reproduce and everything looks fine are you sure it's not at your end?
They email back I got someone at our end to look at it and he's sure it's your end. So I spend a rather long time looking into this and still find nothing so email back for more information and a video of them reproducing the issue.
They email back: umm sorry seems it was our side that was causing the issue, only noticed it when making the video.
*sigh* more time wasted thanks clients! -
Anybody else got this weird little glitch?
Steps to reproduce:
1. Scroll down until the header darkens
2. Hover over any of the header options
3. Scroll up until the header becomes transparent but not fully
Notes:
- Can't use a screenshotting tool, the refresh fixes the glitch
- Can't select the element in devtools, glitch disappears
8 -
"Can you go through this hours-long process to reproduce an issue i saw and debug it? I don't have bandwidth."
"Sure, but I'm pretty sure the issue is actually due to your recent changes in [related feature], and I'm pretty busy myself."
"No, that's not how that works. Please figure out the real issue." (Strongly implying it was my fault)
*Goes through hours-long process to reproduce* (yes this procedure could be improved but this is a rant not a planning meeting)
*Of course, it was his change*
"Oh. Well, it's not really a priority." -
Is it a Bug or a Feature?
Why am I seeing all the ++ scores in Binary?
(I Checked, those are up votes in Binary)
Devs are you drunk? Or is it April fools?
EDIT : steps to reproduce
1.open devrant app
2.click on any rant that appears in the feed
2 -
Been working on a particularly elusive HTML menu sizing glitch for over a year now, trying to get it to appear consistently enough to track down its cause. Finally a) got it to happen in a browser so I could hit it with Chrome Inspector and b) figured out what was probably causing it and fixed it.
And then...
*happens again*
*cannot reproduce the issue, but bossman can*
me --> *commits suicide*5 -
I hate it when something used to not work and then by the time I've fixed it and gotten approval to deploy it I can't even reproduce it anymore (before deploying the fix)...
-
So I'm basically fucked.
There's a major bug on an SPA I developed for a client, but I can't reproduce it because I don't have a recent iPhone or iPad (the only ones I have a way too old and either way I can't debug them without a mac) and I can't reproduce the bug on my android.
To overcome this in the past I installed a hackintosh on my pc and used it's iphone emulator, but I fucked it up and had to reinstall all my OSs but was too lazy to reinstall macos. Now I don't remember how to install it anymore, idk where I downloaded the fucking mojave virtual box image and the macos bootable usb stick I have just doesn't work anymore (probably some missing kext or whatever).
I really do not know what I'm gonna do. There's this ios-webkit-debug-proxy thing that might help me, but it just looks like it's a hassle to install and since I don't know what I'm doing the chances of it working are pretty slim. I might try that but I'm fairly confident it won't work. And even if it does, I still can't install chrome on the iphone I own because it's too old and my dad probably won't let me upgrade it to a new version.13 -
I just wanna cry rn, I'm not even mad. Something happened while trying to install High Sierra on my third partition and somehow both my drives (HDD and SSD) stopped working. Nothing boots. Files? Probably gone. Fuck fuck fuck fuck fuck. I was careful, I didn't click or execute anything I didn't know. How? Just... How?
Now I have to hope my important stuff is still there and I can recover it. If it's just the EFI fucked up, ok, I can fix it. If the partition table is fucked up (most probable) idk if I can fix it, hopefully I can. AAARGH
There goes my entire day or even the entire weekend... All because I don't own a piece of shit of an iPhone and needed an emulator to try to reproduce an issue on a fucking webapp for a client.8 -
Got a question guys!
I want to capture screenshots from a live video stream being broadcast over HTTPS, such as the one on this link:
https://open.ivideon.com/embed/v2/...=
I can do it locally using the chrome webdriver in selenium, but cannot reproduce the same in a server I'm accessing remotely. I tried using headless browsers like phantomJS, but apparently it doesn't support video players -_-
I'm confused because I don't even know what to search for anymore, I've been stuck with this one thing for the last 17 hours. Any help would be greatly appreciated!5 -
is it so hard to screen capture only the relevant details necessary to reproduce a bug? i just watched a video where for 2:30 min, literally nothing happened. and half of rest of the time, they randomly click stuff, as if they've forgotten what they want to show. nobody can give me this lost lifetime back. and the testuff video player is so crappy that i can't even reasonably jump forward / backward or increase playing speed. i even prefer crappy, wiggly upright phone videos if they are on point and don't steal my time. SHOW ME THE BUG ALREADY2
-
Customer calls
Talking about some new feature he haven't totally thought about. so i tell him to think about it.
Talking about a bug, but can't reproduce it.
Talking about another enormous new feature but halt it after hearing the initial estimation.
Total time waster = 1.5 hours for every day.
DON'T LET CUSTOMERS WASTE YOUR DEVELOPMENT TIME.
instead of talking - use project tracking software (i.e. JIRA) -
Humans need to create and program robots because soon they are going to sexually incompetent to reproduce.6
-
We are being run in a simulation. But the simulation is physical. We exist as humans being run on the simulation called Earth. Our brains are designed to interface to a hub. This brain power is used to do calculations for a much larger system. The benefit to using biological systems is they self repair and reproduce. This allows the simulations to scale over time.
Another benefit is we are creating all terrain vehicles (humans) for alien consciousnesses. Big foot is an upgraded atv for high mountain ranges.9 -
My job isn't stressful all the time. Sometimes I'm in meetings and I'm just bored. And sometimes I have a coke to drink. That's pretty nice.
But right now my app is breaking and I don't know why. It either corrupts the heap sometimes or breaks the execution engine sometimes or attempts to write pointers I don't control into protected memory sometimes. Can't reliably reproduce them. And every time I try to debug one it causes the other.
But I do have a Coke. -
Worst support experience so far: German ISP sent their cheap default router which I opted for, hoping that I didn't need to rent a costly FitzBox. Provider activates the connection, everything fine, but slow and unstable on my Linux laptop only. Try using their website, their support chat etc. as they made it very hard to even open a support ticket. I gather all the information, ping, traceroute, netstat, logfiles, router settings, broadband measurement etc. and finally manage to open a support ticket of my issue adn they say they will send an engineer to my place in about 4 days. I stay at home that day and wait for the whole day, nothing happens!
I get back to them, even get a phone call after waiting about 1h in the waiting queue, only to listen to someone tell me that the appointment had been cancelled as the ticket had already been closed. WTF! They said they measured my connection and could not reproduce any error. Did not even mention my lengthy log files etc. It took my own research and another hint that there is an incompatibility with that specific router and some specific devices so I should really replace their cheap router with a FritzBox device. What they also did not tell, that you dont need to rent their branded FritzBox, there are cheap second hand models from another ISP that you can reconfigure by simply chosing another ISP in a dropdown list that contains every popular German ISP. But why are they popular? You can only choose between the different bad ones, that's why they don't seem to make an effort.3 -
When you find a bug in the AWS console, and the internal AWS team can finally reproduce it after weeks of going back and forth. 💪 🧠
-
I have a genuine question for y’all folks: How do you define what’s your next job going to be ? As in what you set your mind to, I guess. I’ve been through multiple stages of thoughts during the past two years and I find myself stuck.
On the one hand I work at a decent company and I have a great team with a lot of benefits and an OK salary but on the other hand I want change, more challenges and to get a little bit more of 💰(I’m not complaining about what I have but I’m clearly on the low tiers of the salary range for a software engineer).
At first I thought I wanted to completely change my work area and go for music, then I thought I wanted to work for the biggest IT players (Google, Microsoft, etc…). Turns out none of these two ideas really suit me. I also don’t want to work in a startup, I’ve only had bad experiences so far and don’t seek to reproduce them yet again.
So I guess a more precise question is: If you were in my shoes, with all that in mind, what would you do?
As for the reasoning as to why I’m asking here: devRant is literally the only place I know with so many people that work in the same field, but that also have a lot of different experiences and background 😁2 -
so the new QA guy just raised 8 new tickets all of which are UI related
full stop is missing
buttons are slightly misaligned
need to add a space in between
etc
all these things can be fixed over a 5 minute call, but noooo he took screenshots, created report, created 8 separate jira tickets with the steps to reproduce and attached screenshots and sent the testing report to all the managers
is this normal in big companies? i feel like it's grossly inefficient and unnecessary
I work in a 20 person startup, the previous qa guy used to call me up directly and explains the issues, he only creates tickets for the things which couldn't be fixed in an hour, I usually fix most those things in under an hour and he provides sign off
9 -
does anyone know where I can report bugs on here?
just a simple one, if you write a response that is too long, then delete some characters to make it fit, and the remaining is <= 20 characters, it won't post, web version... using chrome... I could get more detailed and reproduce if anyone cares3 -
Broke it. It happened once with normal usage, and i managed to reproduce it by switching excessively fast between notifications and the rant icon. :D
3 -
Little addition on my rant about the enter and leave instructions being better than push mov sub for stackframes:
I had that debate with a friend of mine, who tried the same code ... and failed to get enter to be as fast. Infact, for him, enter was twice as slow, on his older computer even 3times as slow.
Mhh... pretty bad. basically blows up my whole point.
I tried the code on my computer... Can't reproduce the error.
Weird.
"Which CPU are you on?"
>"I'm on Intel"
Both of his computers are on intel. I use an amd ryzeni1600. Now this might be a bit of a fast conclusion, but I think that its safe to say that intel should atleast do better for SOME parts of their CPUs.9 -
"Please provide steps to reproduce" seems to be the catch-22 when people try and kick up a fuss about a bug I'm certain doesn't exist.
It's funny because then they report the bug, they word it like I've ruined their life, that can simply cannot continue to function until this error is fixed, yet those simple magic words "Provide steps to reproduce" seems to put their prioritise back into perspective or at the least scares them back into the void from which they came. -
If someone owns a OnePlus 5 I would be very pleased if you could try to reproduce this issue here:
https://github.com/devRant/devRant/...
Thanks a lot!6 -
we need you to fix this bug that cannot be reproduced
ugh so now i have to go figure out how to reproduce it? i dont think this shit is even priority4 -
I joined this company last month and all of a sudden I'm assigned to fix the most important fucking annoying bug that no one in the dev could reproduce.
Im beating my qss going behind people asking questions. Because iits my second month and I'm still fucking new.6 -
So a couple of months ago I had some stability issues which seems to have caused Baloo go crazy and create an 1.7 exabyte index file. It was apparently mainly empty as zfs compressed it down to 535MB
Today I spent some time trying to reproduce the "issue" and turns out that wasn't that hard.
So this little program running on FreeBSD with a compressed (lz4) zfs dataset creates an 1.9 Exabyte large file, nicely compressed down to 45KB :)
#include <stdio.h>
#include <fcntl.h>
#include <unistd.h>
#include <sys/limits.h>
int main(int argc, char** argv) {
int fd = open("bigfile.lge", O_RDWR|O_CREAT, 0644);
for (int i = 0 ; i < 1000000000; i++) {
lseek(fd, INT_MAX, SEEK_CUR);
}
write(fd, " ",1);
close(fd);
}3 -
SharePoint have something called 'event receiver'. An event is triggered when the user inserts a new record in a list. That event must update a column in the same item. After a few minutes it starts to throw conflict errors while trying to update said column. Doesn't happen with every user. Also I wasn't able to reproduce this behavior in the dev environment.
So now I just recursively call the update method, passing an iterator parameter, repeating the same method until it successfully update the record. Or after 6 failures email someone to see what's going on. Just did it today and published at 7PM. Tomorrow gonna be a long day and I know I deserve it.1 -
Why does Europe have to format their currency with commas where decimals should go and decimals where commas should go? I suspect it causes our currency formatter to drop the commas so values like 87,56 turn into 8756; amounts 100 times the intended amount. Somehow I can’t reproduce the bug but business users keep complaining about it happening. Not even my code and yet I’m stuck sifting through it to track down this one weird edge case. 😖7
-
Back in the early noughties I had an interview for the new job. A couple days before the interview I've visited that company's website. There was search input. Of cause I've entered some hacky things into it. And after several attempts I hacked it. The site was down in an infinite loop.
Two days later I told interviewer about the bug and what I did to reproduce it. He was surprised and checked the website. It was still down the same way.
I was totally ashamed. I was supposed to report that problem somehow.
BTW I got the job:) -
Devrant app bug report:
You can see the type content selection menu through the UI
To reproduce:
1. Have the rant of the week banner
2. Open type selection menu
3. Close the rant of the week banner
4. Now the menu is behind the rants
5 -
**18 fuckin hours with full concentration on this Friday starting from 9:30 AM**
I'd developed a big feature for this release and it was being tested by QA guys.
There was this fuckin QA who raised a bug on Friday morning saying that one of the work flow is not working as expected. I debugged it in various scenarios including the one suggested by that dick head but I couldn't reproduce it.
On stating that, QA got pissed and told me that I've not developed it correctly. *Yeah fuck head now you are telling me*
My lead asked me to make some changes in the flow and then check. Did that but no luck.
Finally at 3AM on Saturday, this fuckin nut job QA mails me saying that he was giving in WRONG Inputs 😡
Yeah. It was that bad! -
I'm so sick and tired of the human dick head parade. Epic has us register for a fucking GitHub organization and people found a way to abuse the pull request and sending 300,000 close to 400,000 people notifications so now we're dealing with spam that's going out with random shit including someone ripping their ass hole open (picture...). Over 200 emails I swear to god. This is why castration should be legal.
Unsubscribed from one, someone creates a new useless PR.4 -
Currently debugging a project that was written over 4 years ago...
At first all was well in the world, besides the ever present issue off our goddamn legacy framework. This framework was written 7 years ago on top of an existing open source one, because the existing one was 'lacking some features' & 'did not feel right'.
Now those might be perfectly fine reasons to write a layer on top of a framework, but please, for all future devs sanities, write fucking documentation and maintain it if you're going to use said framework in all major projects!!
Anyhow back to the situation at hand, I'm getting familiar with the project, sighing at the use of our stupid legacy framework, attempting to recreate the reported bugs...
Turns out I can't, well I get other bugs & errors, but not the reported ones. I go to the production server, where I suddenly do can reproduce them...
Already thinking, fuck my life, and scared for the results... I try a 'git status' on the production server....
And yep, there it is, lo and behold, fucking changes on production, that are not in git, fuck you previous dev who worked on this and your stupid lazy ass modifcations on production!
Bleh, already feeling royally pissed, there's only 1 thing I can do, push changes back to git in a seperate branch, and pray I can merge them back in master on my dev environment without to much issues...
Only I first have to get our sysadmi. to allow pushing from a production server back to our git server...
Sigh, going to put on my headphones, retreat to my me space and try to sort out this shitpile now... -
when you're the unlucky fuck and/or too stupid to get green builds so you get flamed when the flaky automated tests (from before your time, not written by you) rear their head and shit all over you
you then get flamed for not going out of your way for fixing them, as the team verbally agreed to do so, but very rarely if at all has anybody done so (it's not so easy trying to fix something when you don't have consistent steps to reproduce)1 -
Just spent an hour salvaging some code from an app project I abandoned so I can reuse it in the future and add what I salvaged to a portfolio of small things I've made.
It was a simple multiple player name menu that generated player objects once the user was done entering names.
Loads of potential future uses.
No point letting it sit inside an abandoned project even if it is somewhat trivial to reproduce. -
**sighs** push and deploy release on stagimg server at 1pm. Wait for 3hours for QA to provide feedback. The minute you start packing, 16 but tickets logged back to back with minimal steps to reproduce. FML
-
Reproduce production defect on local.... Apache ProxyPass for the redirection... Apache Crashes.... Fiddler to the rescue... fingers crossed.
-
Actually got my testing program done today! I got some help and the person told me what was happening and how the function worked and helped me understand everything and what to do to not reproduce the same error and it was such an enjoyable talk/explanation. It makes me feel so much better when I actually learn what I’m doing wrong.2
-
Part I think 3 of Mathematica fails.
So, I'm doing a plot. Initially, I hit the following error: "Value of option PlotRange -> {{3,19},{0,1.1}} is not All, Full, Automatic, a positive machine number, or an appropriate list of range specifications."
Me:Okay, let's change it to PlotRange -> Automatic, maybe I don't know what I'm doing.
Mathematica:"Value of option PlotRange -> Automatic is not All, Full, Automatic, a positive machine number, or an appropriate list of range specifications."
Me:Uh, what? Well then... Oh, please don't tell me it's because of a space in between.
Mathematica:"Value of option PlotRange -> Automatic is not All, Full, Automatic, a positive machine number, or an appropriate list of range specifications."
Me:Oooookay then, what's the problem?... oh wait, there's another space. Why is it that sensitive to whitespace though?
--------------------------------------------------------------------------
That fixed it. Then, when I tried to reproduce it, suddenly adding a space and reevaluating did not raise the error.6 -
That one bug that is always elusive, only happens once during development, you can't seem to reproduce it and think its fixed, and only reoccurs on production or during a demo 🤔 damn it
-
Is docker even suitable for anything that isn't deployment?
So much time, so much effort, so much trial and error, and I still feel like I don't know what Docker is for.
I had a development VirtualBox machine, which I used just to compile my code and test my application. So I said "why don't I just use Docker? It would be way simpler". Also because that fucking Virtualbox image was like 10GB, and it was slow af.
The VirtualBox machine wasn't created by me, but it was just given to me by a previous developer, so I just had to imagine what I needed and pick up the pieces. In few hours I was ready with my Dockerfile.
So I tried it, and....... obviously it didn't work. I entered inside my container and I tried to manually execute commands in order to see where it breaks, and I tried to fix each of them. They were just the usual Linux dependencies problems, incompatibility among libraries, and so on.
Putting everything in order, I started over again with a virgin Ubuntu image, and I tried to fix every single error that appeared, I typed something like 1 hundred commands just to have my development machine up and running.
Now I have a running container that works, I don't know how to reproduce it with a Dockerfile, and I don't know what I'm supposed to do with it, because I'm afraid that any wrong command could destroy the container and lose all the job I did. I can't even bind folders because start/exec doesn't support bindings, so I've to copy files.
Furthermore, the documentation about start/exec is very limited, and every question on StackOverflow just talks about deployment. So am I wrong? Did I use containers for something that wasn't their main purpose? What am I supposed to do now? I'm lost, I feel so much stupid.
Just tell me what to do or call a psychologist8 -
Built something cool for some people. They are Happy - except of one. He reported Strange behaviour and weird bugs - can't reproduce this shit.. But suddenly He told me something.. guess what? He uses Internet Explorer. Yeah, you're right. Nearly nothing works quiet correct on this piece of Old Browser shit.
-
You know my earliest design relating to ML was something intended to mimic human evolution by creating large trees of ideas and rules regarding emotions and how they regulated decisions and priorities.
I somehow think that was a better approach. It was more complex but it was better.
and i could reproduce the stolen diagram from memory as well.
hey is it illegal for someone to sell the contents of a storage locker with your birth certificate in it ?2 -
Existence is pain, and since you cannot take anybody's consent before giving them birth -- humans should not reproduce.
I have thought this over, would love to see if anyone can find holes in the premise or the conclusion.23 -
Anyone else using DevRant on iOS 16.0?
It crashes about 1-3 times a day. I haven’t been able to intentionally reproduce. The app just closes.
This never happened in previous versions.
I’m not an iOS dev so not sure how I can help prepare for public release. I’m not even sure if it is the OS, but since it worked with last iOS, I’m guessing.
Some of the events when it crashed.
1. Browsing comments on someone’s post
2. Double tapping to like a comment (it might be the rant as well, I don’t exactly remember)
3. Opening a rant from the list of rants.
Cannot reproduce. For example, relaunching the app and opening the same rant again didn’t cause a crash.4 -
Hi @dfox I saw an android user report this bug recently as a rant, and now I'm seeing it in iOS (latest app and os version).
Scrolling to the bottom, no more rants load. The little message shows stating that more rants are loading, but when you keep trying to scroll down there are none.
When I change the sort order from Algo to Recent or Top, I can't reproduce the issue. Seems to be only Algo.
Have tried killing the app and restarting to no effect. I hadn't noticed this bug last week interestingly, but can't confirm whether that's just coz I didn't scroll enough.2 -
Having this stress at work especially when they monitor your performance during the WFH . Not doing rocket science or stuffs. but angular front end dev.
api dependency was delayed.
Stuck at some bugs which I think user can never reproduce but a tester did.
All of them is busy with their own ML stuffs and impediments.
Having issues with staying home and work. I dont know this is just me or someone else having the same issue. I am just trying to share. Anything you wanna add? -
"ok Google, remind me to call the dentist tomorrow at midday"
"perfect, I'll remind you tomorrow at midnight"
And here, guys, there's the importance of unit tests
(I reproduce the bug with the Italian version, but it's probably due by the AM/PM settings)1 -
Rant
Fucking async tasks in c# are the bane of my existence right now.
It's running one to call the ms graph API and then if you click at the wrong moment it throws an exception and crashes to desktop but I can't bloody reproduce it because the API call is so fast3 -
> mfw a non-dev customer shows me an exception that is easy to reproduce to answer my sarcastic questions whether she got any problems with the application
> mfw no dev or PM ever thought of using the application like this1 -
QA raised several issues. I updated the code, now he’s struggling to reproduce those. Exceptions are working as expected! 😁2
-
Spend like 3 weeks in mem-checking with valgrind and ASAN, because there seemed to be some leaks. So painful and scary. You loose all confidence in your software, the checking tool, your own sanity.
Some spurious result prevailed, could only move it around. Boss could not reproduce the problem on his machine; Ubuntu 18 with GCC 7, mine was Debian 9 with GCC 6, so I tried older Ubuntu with GCC 5. Also no problem.
Fuck it, I'm switching to clang. -
Why are the smelly crustacean's that reproduce asexually and then die modeled after new York Jews in Futurama ? Lol thought I'd ask on this our continued fucking anniversary2
-
So I was writing some text and from time to time it moves me to beginning of line, but I am dumb and miss keys sometimes. I was trying to write fast, click something wrong and bam - fucked my text.
But actually fucking not, there is some shitty bug on my Manjaro machine for sure and usually hard to reproduce (happens in Firefox at messenger, libreoffice at writer) and now on fucking godot after two seconds it moves me to start of line every fucking time.
I am not even sure if it is just Manjaro stuff, because I don't remember if it happens on Windows, too
Top Tags
Weekly Rant
View