Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "bug reporting"
Best conversation this week:
A: *reporting a visual bug* The text on this page seems to be placed too far to the right, is this intended?
B: No, it's indented.2
Maybe I could get better bug reports from clients if I made them use this.
I wonder if it has Jira integration.5
Hey everyone! Recently there was a bug discovered which caused many (but not all) “user x posted a new rant” subscription notifs (both in-app and push) to not get sent out for the last week or so. It should be fixed now. Unfortunately though, they won’t be backfilled, so make sure you take a look at your favorite ranters’ profiles since you might not have been notified about their most recent rants.
A big thanks to @gitpush for reporting the issue and thanks to @linuxxx for help testing/confirming the fix worked.
For the basic cause: when we overhauled/fixed push notifs on Android in the last build (about a week ago), we had to convert to FCM. When a “user posted rant” notification was getting sent out, the asynchronous worker would process all of the subscription notifs in a loop. So for users who have a lot of subscribers, somewhere in the loop, something was failing, likely having to do with the new FCM send method. This is now fixed and all push notifs in that worker are also done asynchronously.
Let me know if you have any questions and apologies for the loss of subscription notifs!15
No, not as e-mail or for privacy reasons. Sure, that too, but it comes with "free" stuff.
It sucks because it's breaking every possible record in the worst, shittiest, most insanely stupid APIs and integrations out there on the entire fucking planet!
It is comically stupid!
Aside from their LOVE of hard-deprecating APIs every few months, requiring constant, time consuming maintenance of every tool that integrates deeply with Google services, some of their APIs, for expensive stuff, look like they've been written by Bobby McFartface from 7th grade.
Take a look at DoubleClick Search (their ad performance reporting tool, that sure does sound like one). To upload custom, additional data, you must pass in a ton of parameter, and they REQUIRE some of them to have a specific, hardcoded value. What's the point in passing that parameter then you dickheads?!
But fine, so you uploaded some stuff using the API. Now you want to delete everything and try again after you fixed a bug - well you fucking CAN'T! You can't delete stuff, you can only mark them as "deleted" using an update call.
Bulk operations? Fuck no!
Can I just add on top? Well of course not! That will raise a ton of exceptions. Same message should be transmitted using the PUT, not POST request, in order to edit.
Can I send everything to PUT? Of course not! You can't edit something that's not there, dummy!
Can I see what's there so that I can update it, and add what's missing?
Well of course not! Why on Earth would you need to see what information is in there after you uploaded it? Who needs that anyway?
Simply send, pray, and hope that everything will be fine (it will not).
Like holy fucking crap, it can't get any more stupid!
Google is a huge pile of idiots who feed on only a single cow - the search engine.
It's times like these when I think that Google right now is the worst thing that exists for everyone in tech. It's dragging everyone down with their monopolies everywhere and complete idiocy in managing them.6
After I lost a months of work, I was assigned a bug to retest.
Well, something wasn't right. The results were not as expected.
I sat with developer for entire day. We fought, we laughed, we were frustrated, we were trying hard. We literally had no time to even take a leak. We struggled while my entire team was enjoying gala time jerking off each other.
Seniors and managers didn't help when we seeked for help.
Struggled like shit. And found a major bug in one of our earlier realises which is running in production for top clients. Just to remind you, this bug might cause few million dollars of financial loss if that feature is executed.
Well, we report it immediately. My dev friend was excited that we'll be appreciated and rewarded for this discovery. I was sceptical and afraid already because I know shit heads who rule us.
It was observed that one of our other manager was responsible for testing this functionality when it was built and it was missed by her.
Fuck!!! Nobody says a word. And I and my dev friend get questioned that why wasn't it detected earlier.
What the fuck!!! We didn't even know such a functionality existed. We never worked on it. It was missed by some asshole and we get blamed.
Look on my dev friend's face when we were being bashed for no reason was priceless 😂
I could see his world getting shattered.
I stood up for him and myself. Defended ourselves and by now, I have enough experience to game the system.
So I get ourselves out safely and teach my dev friend this valuable lesson on how to deal with shit heads in such situations.
Another corporate lesson: never get excited for reporting something which others missed as it will be dumped upon you and you'll be fucked for doing good.4
Me: Wish I got one guilty free murder pass..
God: GRANTED! Which software tester would you like to kill?4
Just used my first "It's not a bug, it's a feature" explanation 😂. However, the irritating part is, I had to explain it to another person from IT industry (I mean testers) who is from another company.
And it's really a feature and not a bloody bug. Stop reporting it on the bugs list 😥3
Hoo boy, this is a (very) long one, so read at your own risk,
I'd say, don't judge/generalize people biased by the minority that represent the larger group,
But on the other hand, it's very difficult to do so, especially when working in a group consisting of several dozens of people (devs, tech leads, testers, designers, etc), in separate sub groups
Well first, the devs aren't working with the expected atentiveness to quality & detail, I am not in any way the best developer in terms of knowledge, in fact I might be just a mediocre developer compared to the other tech leads or the other fellow developer, but one thing is that I always tried to learn and try my best to do it in the best way I can,
Quite frequently (and from several specific persons only) I had the honor to experience these farce,
Some people just don't want to admit that they are wrong, clear as day, this specific part here is not doing what it's supposed to do due to someone's negligence, and I was trying to find out how it actually works and how can we fix this, that's right, "we", I'm not even pushing anyone to clean up his mistakes alone, I'm also taking part on it because that became my responsibility when I touched that part of the code, and it's my duty to make sure the job is done, and what did they do? Long story short, somehow the guy was getting angry for an unknown reason, then speaking in high tone implying that it's not his problem anymore, passing the responsibility to someone else, and ultimately everyone said I should figure it out by myself, yeah fuck you all, in the end I was very relieved to be moved back to my original squad and not having too much interaction with their group,
Some (probably) less worse occurences are the devs who rush ahead before they code, literally, it's not the usual "code first, think later", it's way more advanced version of it, let's say some tester found a bug, then it's assigned to a developer, the developer doesn't even bother to check the ticket description, only read the vague title, and doesn't even bother to check the actual behavior on the app, suddenly, there's a Pull Request waiting to be merged, it's mind blowing to see how his PR doesn't actually solve anything, in the end, it confuses several reviewers until they actually run it on their local machine and found out that the bug is either has been fixed or not recurring anymore or the fix doesn't do shit, fucking waste of time
And what about the testers? Sure let's not forget the stereotype about devs vs testers and vice versa, but the ones I'm working with is a real piece of work,
I have no problem with the testers who put a lot of bug tickets, or the ones that is very critical in their bugfinding process, at least that means they are doing their job properly, the ones that dotheir job improperly are the ones that ends up wasting everyone's time, just like above
One time, a tester was reporting a certain UI bug, a certain text was overflowing, it's an edge case and was assigned to me since I works mostly on UI,
A day went by with no avail at my attempt to replicate the bug, turns out he was testing it with his personal phone, which was not included in the device requirement for the project nor described in the bug ticket, but since the screen resolution checks out, the bug is considered valid,
Second day went by with no avail of replicating, my time spent trying all kinds of devices, simulators, emulators, until, the 3rd day a very lucky occurence happened with one other testing device, and another tester reported duplicate bug, obviously I borrowed the phone, and inspected every inch of possibilities, until I noticed something, "the font's kinda bigger on this phone" I thought, then I checked the settings, and lo and behold, the bug is caused by the device's font settings, fuck it, and fuck you
Another time was when I'm not sure whether the testers was being lazy or just acting preoccupied with something, when we create a PR, the specific branch must be tested by tester to ensure nothing broke because of the changes, then only when the tester OK'd it, the PR will be merged,
This thing frequently happens, especially when working cross teams, it's as if that the other team's tester is not responsible for my work, eh, here's two middle finger for you, I'll include my toes also, YOU ARE THE ONE REPORTED THE BUG FOR FUCK'S SAKE, and now you act like it's none of your business?, what's so hard about testing one single branch for a single teeny weenie feature and say ok on it, it won't even take 15 minutes, because I can do it in just 10 minutes, but only the testers had the authority to say that a certain PR is good to merge, fuck it
Last, the point above, "only the testers had the authority to say that a certain PR is good to be merged", and they seem to be flaunting it and act like an important person, fuck you
That doesn't cover half of the antics I saw, but whew, it sure is refreshing to finally speak it out3
Start raising tickets/bugs like you were going to the doctors and things would get fixed a lot faster.
X page doesn't work.
Great information there what about the page isn't working?
Doesn't answer the question and gets pissy when you have to ask them again.
If this was a doctor's appointment all you would've done is walked into my office and yelled it hurts over and over.
Then proceeded to shit on my floor as you're leaving because I didn't diagnose the problem fast enough.
What were you trying to do when the system took a crap?
What did the red text say?
Can you take a screenshot? because the old saying a picture paints a thousand words holds some truth.
If you can go to the doctor and give them a full run down of when you got sick and what symptoms you got in the same order they happened why do you struggle to do the same when reporting a bug.5
Worst exp. with manager/higher-up?
Too many to pick the worst, but here are a few:
Manager demoted me because he believed I would be a roadblock to his wet dream of re-writing all the business services in WCF
Manager spent years and wasted countless man hours retiring a single ASP.Net web service by converting the individual supporting assemblies into specific WCF services..
Manager once berated me for 'missing' time log entries
Manager scolded me for not fixing a 'bug' while praised another developer who re-wrote a reporting application due to a fixable hardware problem and deleting the source code files from source control.
Manager wanted to rewrite all our code in XML.
Manager wanted integration with a new phone system knowing the hardware+software did not exist yet ..
Manager wanted me to 'take the lead' to speed up a web site in a foreign country we didn't control.
Last Scrum Meeting, set up our new Container Server and installed Sentry (Bug Reporting Tool) on it. I was pretty proud, since it was one of my first DevOps thingies I had to work on. (I may end up as a DevOps Engineer after my Internship) In the scrum meeting, the colleagues just start saying everything with a French accent and just laugh about their french jokes while I'm in the middle of showing them sentry.. they were literally unstoppable... 😡 And weren't paying any attention to my presentation.
With personal hotspot on, certain pages cut off half of the bottom navigation bar - profile is one such page (see attached ss).
iPhone 6 on iOS 105
Just had a discussion with a support person, it seems I need or use safari or opera OS to be able to watch a recording of an open class I has.
The platform they jse works on with flash (fucking hate it), and it seems linux is not supported because I need to install flash.
I was just reporting a stupid bug, I am watching these on my phone and staying away from installing flash.
Found an issue on Medium.com as I was not able to comment on some stories.. after some followups I found that it is because of CORS... they stopped responding after I responded with the reason. :(
My life was troublesome today, had to help a non programmer to run jar files.
The jar executed well from command line in Windows 10 but didn't work on double click.
Did all the tricks, registry edits, cmd commands and at last I found a miracle tool called Jarfix.
Just double click and all okay.
The root cause of the problem was 7zip.
This bug is reported in the Oracle bug reporting and they have closed it as " Will not fix" low-priority report.2
Tfw you're done with dealing with idiotic bug reports ("Game crashed pls fix", "Not working pls fix", like that) you force the bug reporters to read a copy-pasted version of Simon Tatham's Bug Reporting Guide (https://chiark.greenend.org.uk/~sgt...) on a page before going to the bug reporting page and set a minimum of 100 words in the bug report filter just to filter the BS.
EDIT #1: Spelling errors1
Wasting time of 20+ developers to deliver a 'how to use a bug reporting system', coz:
- you've only 2 newembers in team, and
- just to have a bi-weekly meeting.
Is not productive, motivating and wise by any means.
Combined $$$/hr amount here is quite an important metric.2
What is a cool naming scheme for the servers
for example we have 6 environments for the QC to run their tests, what would be a cool way to name them
I thought of bugs names,since we are a bug reporting company
what do you think guys9
How 2018 brings an aww bug.
At my company, we've a reporting application. Which kind of provides analysis of client's weekly business. When you open the application it shows their business trend starting from Sunday to day of week.
As usual their is an endpoint to get the data basis on start date. As soon as date changed to 1st Jan, it stopped showing data. Given that it was a long weekend, no one was available from the tech. Support team got tremendous amount of tickets for this. Later on Tuesday while debugging we got to know while forming the date in the application the logic was like this
- get current year
- get the date and month on start of week
Combine these 2 and request the data. All the time it was fetching data starting from 31 Dec 2018.
Open a older case in #JIRA and either I'm in past or this thing is messing with me today Jan 30, 20182
Spend about half the day fixing a bug. Whilst reporting it complete on our ticket system, QA change the ticket's expected outcome. Ffs.
I think one of the great things about this app is how we handle bug reporting. Any time someone posts about a bug, people independently do extensive tests to determine the extent of the bug (or at least what devices are affected), and people nearly always give detailed replication steps. I think this is a great feature of this community1
As someone who has been developing a game (not even close to 20% done) and dealing with bug reports, I'm pissed off by this one report from a game I play, which I'll just shamelessly copy-paste it here for y'all to read and rant
"Title: [sic]lag never fixed
[sic]i dont wanna report lag doesnt mean there's no lag ,
the LAG is real, and is getting worse and worse everyday, vespa please fix the problem,
i used to think i could bear this lag, but i cant ,i just cant, after 5+ times game crashing everyday,my patient is losing . you say u are fixing it every maintenance,but what is this BXXX SXXX?all i could see it you are trying your best to grab money from my wallet(well u FXXXING successed),and the promise you made to fix the lag never ever ..........
sorry for my bad Chiglish, but./......"
I'm not a developer of the game, but this pisses me off. The guy wants fixes on the "lag"; which lag?? latency?? FPS?? random freezes??; while giving absolutely ZERO details on the "lag" AND accusing the company of stealing money without doing sh-t, which is not true as far as I can tell in-game. So, I instinctively waltzed in and ranted at how sh-t the report is in detail, and accused him of inhibiting the game's development because of his sh-t report, and he replied with this (I told him I'm a game dev in the reply I mentioned):
"[sic]as a person who made this game should know what lag is just like u know what fuk is as a human being,and i said game crash ,thats the best way i could explain as a normal player not like you an arrogant indie game dev!and if u cant understand what course the game crash,as a player like me how could i know, thats the reason im asking for help here,and i hope they dont have such indie game dev like you who doesnt know lag(game crash)"
M-th-rf-ck-r. For the first time, I see true ignorance. While writing this, I'm typing my next reply for the m-th-rf-ck-r that lacks common sense on reporting a bug. For f-ck sake if I found him I'll put a bullet through his head.3
I've just spent 4 hours trying to fix a bug on prod. that can be fixed in 30 secs. At the end I remembered that I should check the error log. FML (error reporting turned off, logs only)
Another vendor just sabotage our launch!
Only reporting a bug to C-level a minite before offical launch. 😡 Had to put our servers at maintenance mode immediately.
Same user. One profile was loaded, one was not. Look and see. A reload of the rant fixed it. Idk if it's a bug. I'm reporting it anyway.