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 easier

I love how "shotgun debugging" works.

Let's say the microwave doesn't work. I put my burrito in it, press buttons. Nothing happens.

Any sane person would trace the possible cause: Check if it is plugged in, maybe the fuse is blown? Nah, we don't have time for this: Let's try shotgunning it!

- Turn the burrito upside down.
- Try aligning the burrito in different cardinal directions.
- Press random buttons
- Remove burrito wrapper
- Separate burrito into single components, sort them onto a plate in a nifty layout and try microwaving that.
- Remove each component of the sorted burrito plate and try microwaving the plate with less and less items.
- Try microwaving each separate item and then later reassembling them back into burrito to see if it gets heated after the act.
- Try putting a cat on top of the microwave.
- Pour water on cat
- Notice a strong reaction involving water and the cat.
- Try catching the cat for additional testing.
- Go to the hospital to get stitches on your open wounds.

Later write a bug report to the maintainer: "Microwave doesn't work. Tracked the issue down to the moisture level of the cat, additional testing needed."

An open letter to the guy that commented on my website:

«Function X does not work. This program is shit. I am going to uninstall it and tell everyone.»

I'm sorry that my completely open source project didn't work for you. The fact that I lost countless days and months and years working on it in my free time, without ever asking for a cent, just trying to do something good for the community, doesn't give me the right to release a feature that may be buggy.

You could have opened a bug report. But that takes time. A whole 2 minutes. I understand the urge to post such a harsh public critic on my website. That's why I was so calm and understanding when I replied to you there.

However, it's a long time I wasn't browsing devRant and I confess I felt the urge to tell you to go fuck yourself. And this is the best place to do it! I'd pay to know you. I'd love to see your face. Oooh you must be so confident of yourself. I'm sure you have accomplished a lot in your life. So here's my message:

Go Fuck Yourself Asshole

I prefer silent kills.

× open Jira ticket classified as a BUG REPORT
× Title: "Mike"
× Description: "Mike is working with us"
× assign it to Mike

× reopen it every time it's closed

Receiving a bug report from the manual tester “numeric input does not work”.

He accidentally disabled Num Lock on his keyboard.

Client: Urgent! App is crashing!
Me inside: Wtf, Crashlytics didn’t send me anything, it betrayed me...
Me: What’s wrong?
Client: Some random user sent me email that app is crashing SOMEWHERE(!?)
Me: ................................... no problem, I’m working on it.

*Tomorrow*
Me: Fixed, everything works fine now (didn’t do anything actually)
Client: Great, nice work!

Client never mentioned that “problem “ anymore.
#likeaboss

Me: *finds severe bug in school-contracted software, emails teacher about who to talk to to get it fixed*
Teacher: "should I report you on grounds of computer misuse and hacking or...?"

thanks fucker, school-contracted company it is.

Python. Changed a function to return a tuple instead of one value in some database code. Tests pass, gets deployed, everything works. End of the month comes. Suddenly, we get a report that we're draining people's bank accounts and credit cards.

It turns out there was an untested bit of code inside the billing process that used this function. It used the function that was changed. To make matters worse, when the exception was thrown, the billing had already completed successfully, and due to another unrelated bug it would retry despite this.

So, needless to say, type safety and good unit tests are things I prioritize nowadays.

My biggest dev blunder. I haven't told a single soul about this, until now.

👻👻👻👻👻👻

So, I was working as a full stack dev at a small consulting company. By this time I had about 3 years of experience and started to get pretty comfortable with my tools and the systems I worked with.

I was the person in charge of a system dealing with interactions between people in different roles. Some of this data could be sensitive in nature and users had a legal right to have data permanently removed from our system. In this case it meant remoting into the production database server and manually issuing DELETE statements against the db. Ugh.

As soon as my brain finishes processing the request to venture into that binary minefield and perform rocket surgery on that cursed database my sympathetic nervous system goes into high alert, palms sweaty. Mom's spaghetti.

Alright. Let's do this the safe way. I write the statements needed and do a test run on my machine. Works like a charm 😎

Time to get this over with. I remote into the server. I paste the code into Microsoft SQL Server Management Studio. I read through the code again and again and again. It's solid. I hit run.

....

Wait. I ran it?

....

With the IDs from my local run?

...

I stare at the confirmation message: "Nice job dude, you just deleted some stuff. Cool. See ya. - Your old pal SQL Server".

What did I just delete? What ramifications will this have? Am I sweating? My life is over. Fuck! Think, think, think.

You're a professional. Handle it like one, goddammit.

I think about doing a rollback but the server dudes are even more incompetent than me and we'd lose all the transactions that occurred after my little slip. No, that won't fly.

I do the only sensible thing: I run the statements again with the correct IDs, disconnect my remote session, and BOTTLE THAT SHIT UP FOREVER.

I tell no one. The next few days I await some kind of bug report or maybe a SWAT team. Days pass. Nothing. My anxiety slowly dissipates. That fateful day fades into oblivion and I feel confident my secret will die with me. Cool ¯\_(ツ)_/¯

it doesn't work is not a bug report.

Posting a bad review is not a bug report 😡

Be me
> find an eslint bug
> report it on their github
> ask to assign it to self
> start working on it
> spend half a day to find out the source of bug
> realises the bug is coming from a library eslint is using
> report it on the library's github
> ask to assign it to self
🤦🏻‍♂️

For fuck sake, one small bug and my app immediatly gets a 2 star rating. HOW ABOUT YOU REPORT THE FUCKING BUG TO ME SO I CAN FUCKING FIX IT. MY EMAIL IS IN THE GODDAMN DESCRIPTION. HOW FUCKING HARD IS IT TO SEND ME AN EMAIL INSTEAD OF A WORTHLESS RATING.

Please do not confuse your google search with my daily rants

- For devRanters

When you want to report a bug. Only to find another one...

Me becoming responsible:
Help in household chores ❌
Help siblings ❌
Finish college work ❌
Report every bug i encounter in Pubg ✔️

I really wonder which genius came to Shopify to report a bug on Spotify

Is it just me or is the...

!!pointless story

Bug report comes in from a coworker. "Cloudinary uploads aren't working. I can't sign up new customers."

"I'll look into it" I say.

I go to one of our sites, and lo! No Cloudinary image loads. Well that can't be good.

I check out mobile app -- our only customer-facing platform. None of the images load! Multiple "Oops!" snackbars from 500 errors on every screen / after every action.

"None of our Cloudinary images load, even in the mobile app," I report.

Nobody seems to notice, but they're probably busy.

I go to log into the Cloudinary site, and realize I don't have the credentials.

"What are the Cloudinary credentials, @ceo?" I ask.

I'm met with more silence. I use this opportunity to look through the logs, try different URLs/transforms directly. Oddly, everything seems fine except on our site.

I check Slack again, and see nothing's changed, so I set about trying to guess the credentials.

Let's see... the ceo is basically illiterate when it come to tech, so it's probably not his email. It's a startup, and custom emails for things cost money, and haven't been a thing here forever, so it's probably oen of the CTO's email aliases. he likes dots and full names so that narrows it down. Now for the password.... his are always crappy (so they're "easy to remember") and usually have the abbreviated company name in them. He also likes adding numbers, generally two-digit numbers, and has a thing for 7s and 9s. Mix in some caps, spaces, order...

Took me a few minutes, but I managed to figured it out.

"Nevermind, I guessed them." I reported.

After getting into Cloudinary, I couldn't find anything amiss. Everything looked great. No outage warnings, metrics looked fine, images all loaded. Ex-cto didn't revoke payment or cancel the account.

I checked our app; everything started loading -- albeit slowly.

I checked the aforementioned site; after a few minutes, everything loaded there, too.

Not sure what else to do, and with everything appearing to work, I said "Fixed!" and closed the issue.

About 20 minutes later, the original person said "thanks" -- never did hear anything from the ceo. I've heard him chatting away in the other room the entire time.

Regardless, good thing for crappy passwords, eh?

So I found a bug in Bootstrap 4 today that was causing responsive tables to break. I looked at it for a while and threw a bunch of potential fixes at it, to no avail.

I was about to open a bug report when I stumbled upon the cause...

I spelled “table-responsive” wrong 🤦‍♂️

Tester's bug report: "Both bars started to flash and jump like in Harlem Shake."

received a bug report from a client on a mobile app.

title: bug on information page.
description: all text field make first​ letter capital.

*what! this is your keyboard, stupid!

after he didn't understand, I made a text change listener, and make the first letter lowercase, he is happy. heheh 😨

Kudos to the devrant team for epic response time!
<50min from bug report on Twitter to workaround on prod!

So today is Monday. A bug report comes asking to be fix. I feels weird reading the report. Then I check the codes.

SOMEONE MESSING WITH MY CODES!!!

The other developer codes a very un-dynamic function that gives birth to bugs. Know what? He replaced my original codes with his faulty codes. 😑 😐

So today, our "senior tester" logged a bug because he "Viewed Page Source" on the web based report he's testing and the Year values are hard coded! So 2017 will have to added manually!
I burst out laughing so hard, all my colleagues think I'm having a mental breakdown.

Alright, the blog seems to be running again and its not breaking yet which is a good sign :P.

Although nothing has changed on the front end yet, the backend has been partly rewritten to be more efficient and of course, post sorting based on posting date!

I'm aware of most of the front end issues so no need to tell me all of them again, I'll look at that tomorrow as I need sleep right now :(

If you'd find any bugs/security issues, please, don't exploit them but report them instead! I take security very seriously and will try to patch any security bug as soon as I can :)

Having to deal with stupid testers who think your app should be resistant to water and black magic and report a bug if it is not

Fucking URLs, people.
They're not hard.

If you're going to give me a bug report, TELL ME THE GODDAMN URL.

If, after yelling at you several times for not providing the url, you instead just fucking GUESS at the url, YOU'RE A GODDAMN BLITHERING IDIOT AND YOU'RE WASTING MY GODDAMN TIME.

ALT+D, CTRL+C or CMD+L, CMD+C

SO HARD. ASDFASDJGHLKASDHFLJKSGDFSKDF

Reached out to Apple to report a bug where my screen gets pushed down 50% and leaves an odd blank area. Turns out the bug is literally a feature 😂

!rant & story_time
This happend to the startup I was working for at ~2011. I was a junior Android dev, working on a very popular app.
During experiments for a new feature, I discovered that the system AlarmManager has a serious bug - you can set a repeating alarm with interval=0ms. If your app takes more then 1 ms to handle the Intent, then the AlarmManager will start to fill up the intent Queue, with unexpected results to the OS. causing it to slow down, and reboot when it ran out of Ram. Why? my guess was that because the AlarmManager was part of the OS, then any issues caused by it caused the system process to ran out of ram, crashing it, and the whole system with it. the real kicker was that even after a reboot, the AlarmManager still had Intents queued, causing the device to bootloop for a while, untill the queue was cleared. My boss decided to report the problem to google, as this was an issue in the OS. I built an example app, that caused the crash 10-30 seconds after starting, and submitted to Google. Google responded later that day with "not an issue, no one will ever do this".
Well... At this point I decided to review the autoupdate feature in our app, to make sure this will not happen to us. We just released a new feature where a user can set an update schedule option in the app settings - where you could setup a daily, weekly, or hourly update for the app. after reviewing it, It looked good, and the issue was not triggered in the manual QA I did. So, it was all good. And we released an updated version to the store.
After we did an update-install, we discoverd that, there was a provlem reading the previous version SharedPrefs value for the update schdule settings, and the value defaulted to 0...
the result was, our app caused all our users to go into a bootloop, and because the alarm was reset when the devices booted up, the bootloop could only be solved in a factory reset, or removing our app, before the device rebooted, and then waiting a few reboot cycles.
We lost 50 places in the market, and it took us 6 months to get back to where we were.

It was not my fault, but it sucked big time!

When you receive a "bug report" from one of the clients:

Subject: contact form
Message: It doesn't work

When your team members report a bug in my code, when they actually changed the specs and didn't tell me 😳

I just had to ran to get my train in time. When I sat back I saw this alert on my phonescreen.

That's nice of the Riot app developers to detect frustration like that :)

So we got this bug report today. This guy's my hero. If more people wrote bug reports like this, they would see faster results.

I just experienced my first sleep paralysis. Where do I submit a bug report?

I found a vulnerability in a food delivery app api that allows me to add credit to my account. I ate my first free meal today but i feel bad about it. What should i do 😞.

1- continue hacking free credit and eating free food.

2- stop and forget i found this bug

3- report the bug in exchange for money/credit

4- report the bug for free

Finding a bug as a developer: "Fuck..." *start working on an undocumented hotfix that breaks other parts of the application"

Finding a bug as a tester: "Yeah, right.." *start writing a comprehensive report including all possible failure scenarios and how world famine will increase and men develop boobs if this bug is shipped into production"

Finding a bug as a PM: "Well, the other parts work, right ?" *click randomly on nearby buttons and input fields to "check" if everything is all right. Ditch said report from tester*

bug report arrives
10 mins later
the issue couldn't reproduced, done 👍

My first bug report to chrome was resolved today.

Slowest triage ever and they doubted me every step of the way.

I've caught the efficiency bug.

I recently started a minimum wage job to get my life back in order after a failed 2 year project (post mortem: next time bring more cash for a longer runway)

I've noticed this thing I do at every job, where I see inefficiency and I think "how can I use technology to automate myself out of this job?"

My first ever application was in C++ for college (a BASIC interpreter) and it's been so long I've since forgotten the language.

But after a while every language starts to look like every other language, and you start to wonder if maybe the reason you never seriously went anywhere as a programmer was because you never really were cut out for it.

Code monkey, sure. Programmer? Dunno, maybe I just suffer from imposter syndrome.

So a few years back I worked at a retail chain. Nothing as big as walmart, but they have well over 10k store locations. They had two IBM handscanners per store, old grungy ugly things, and one of these machines would inevitably be broken, lost or in need of upgrade/replacement about once a year, per location. District manager, who I hit it off with, and made a point of building report with, told me they were paying something like $1500 a piece.

After a programming dry spell, I picked up 'coding' with MIT app inventor. Built a 'mostly complete' inventory management app over the course of a month, and waited for the right time.

The day of a big store audit, (and the day before a multi-regional meeting), I made sure I was in-store at the same time as my district manager, so he could 'stumble upon' me working, scanning in and pricing items into the app.

Naturally he asked about it, and I had the numbers, the print outs, and the app itself to show him. He seemed impressed by what amounted to a code monkeys 'non-code' solution for a problem they had.

Long story short, he does what I expected, runs it by the other regionals and middle executives at the meeting, and six months later they had invested in a full blown in house app, cutting IBM out of the mix I presume.

From what I understand they now use the app throughout the entire store chain.

So if you work at IBM, sorry, that contract you lost for handscanners at 10k+ stores? Yeah that was my fault (and MIT app inventor).

They say software is 'eating the world' but it really goes to show, for a lot of 'almost coders' and 'code monkeys' half our problem is dealing with setup and platform boilerplate. I think in the future that a lot of jobs are either going to be created or destroyed thanks to better 'low code' solutions, and it seems to be a big potential future market.

In the mean while I've realized, while working on side projects, that maybe I can do this after all, and taken up Kotlin. I want to do a couple of apps for efficiency and store tracking at my current employer to see if I'm capable and not just an mit app-inventor codemonkey after all.

I'm hoping, by demonstrating what I can do, I can use that as a springboard into an internal programming position at my current gig (which seems to be a company thats moving towards a more tech oriented approach to efficiency and management). Also watching money walk out the door due to inefficiency kinda pisses me off, and the thought of fixing those issues sounds really interesting. At the end of the day I just like learning new technologies, and maybe this is all just an excuse to pick up something new after spending so long on less serious work.

I still have a ways to go, but the prospect of working on B2B, and being able to offer technological solutions to common and recurring business needs excites the hell out of me..as cringy and over-repeated as that may sound.

This is the last straw. I am so done with Chrome.

…

I woke up AGAIN this morning to my MacBook shining away brightly, having not gone to sleep the ENTIRE night. I did some better research this time and discovered it's actually Chrome that is causing this.

Yes Chrome is deciding whether my MacBook goes to sleep or not.

I am not ok with this. Worse, it doesn't even have any ability to change this behavior. It's basically a hidden "feature" of Chrome: it wastes your hydro too!

This is not the first time this has happened either. Last time my MacBook wasn't properly plugged in and it completely drained the battery, shutting it right off. I ranted about that already.

But I am just SO fucking livid about this right now. What on EARTH is going through google's mind that they think this is in any way even REMOTELY acceptable?

I've already filed a bug report but I think this is the last straw. I am just sick to death of Chrome. This bug is literally costing me money and damaging my property.

Shove it right up your fucking ass, Google. Right up there and twist it around.

I'm switching back to a real browser.

I wonder how a bug report on devRant may look like.
Something like a bug report and a fix on the same email?

Never compare yourself to others.

Never force yourself to code.

Understand that coding is like any profession and it may not be right for you.

Don't base your success on whether or not you you understand everything you're looking at. Base your success on whether you can accomplish your goal(s), AND structure your code in such a way that it is logical and readable by others.

Learning something well but slowly is better than trying to find the fastest route and constantly having to "refresh your memory".

You don't have to like Python, Java, pHp et cetera, but find what languages you *do* like.

If you aren't frustrated, you or someone else isn't trying hard enough.

Monoculture sucks.

Time is money.

Always negotiate your salary.

Coffee will dramatically improve your efficiency and productivity.

Don't expect other people to understand your job, least of all find it interesting.

You won't get paid anything decent until you're actually a senior with a good amount of projects under your belt.

Your employability relies a lot more on your social skills and how you present yourself than what you would expect. Sharpen your social skills. No matter how talented you are no one will hire a "talented social cripple", especially for team work.

Never let an epiphany pass you by. Some of the best ideas come to us when we least expect it.

Be humble.

Empathy is a required feature in all programming.

Open source is better than closed source.

Open source does not mean "You don't get paid".

You will need to exercise more than most people due to having a lifestyle that is more sedentary than most.

Delete Facebook, Twitter, Instagram, Snapchat, Reddit, Tumblr, Pinterest and any other source of procrastination.

Use the right tool for the job.

1 hour of market research is worth 100 hours of programming.

When you accomplished something explain HOW.

# comment // your /* fucking <! - - code

Follow established style guidelines or fuck off.

Privacy is a right not a privilege.

Pay your knowledge forward.

Always be improving, be it your code or your knowledge.

Don't be that guy who says "I'm not an "x" developer, I'm a "y" developer". You'll be the first to get fired. Learn whatever you need to stay ahead of the curve.

When it's Python vs Java vs Kotlin vs JavaScript vs CSS vs Ruby etc. C++ always wins.

If you find a bug, REPORT IT.

You can never have too many side projects.

Don't leave your readme.md blank.

Bug: Call
Me: I see, I call your 'bug' and raise you a 'Fix'
Bull: Raise 200
Me: Fold :/

"I'm getting an error. It's just not working right."

Stupidest. Bug. Report. Ever.

Please stop wasting our time with tickets like this people, it only requires is to then spend more time just figuring out what the issue is.

🙄🔫

Part of a product I used to work on contained a one time password generator that randomly strung together a few words from a word list.

Nothing wrong with the security, but this word list hadn't been filtered, so we did have a "bug report" from a customer who had a one time password that contained a questionable phrase:

"fucking pork Muslim"

...Call me a terrible person, but I never did get around to fixing that...

My fucking habit

*a wild bug appears(non-critical)

*fixed the bug

*try out some stuff to make sure it doesn't break the other cases

*commented the fixed part of the code to make sure I'm actually working on the problematic part of the code

*realized the screen I'm working has minor UI flaws

*fixed the UI issue

*found some shit codes I've been meaning to clean up since back when

*notice the code could use some linting rule changes

*69 changes and 6 commits later

*smoke test

*deployed to prod

*saw bug report within hours after deployment

*app crashing on prod on the buggy case

Apparently I forgot to test the case and uncomment the fix 🙃

Dear people who leave bad reviews...

Do not use a review as a bug report, saying something crashes on your device and telling the developer to "fix this" isn't a review.

It is barely a bug report but a review is on quality, not individual issues .-.

I FREAKED OUT

I WAS A DIFFERENT PERSON FOR SOME REASON

Dfox thanks for the heart attack, I thought I got hacked.

So I was using Coffee Meet Bagel to talk to a girl who is currently travelling. We noticed that the messages were sorted out of orders with incorrect time due to the different time zone we are in.

So naturally, I sent them a big report.

Their support team replied by telling me to do the usual. Restart, update, reinstall, delete everything etc (it’s their default answer!!).

I told them I have done those.

They then rephrased my bug report and told me this is expected as the chat was between two parties with a different time so the messages are sorted out of order due to the time difference.

I guess most developer will get ticked off by that... so I sent them a few pseudo code on how chat across different time zones should have been dealt with...

Life of a developer. Debugging and coding even when on a dating app... 🤷🏽‍♂️

> Young dev apprentice me pair programming with another developer
> Dude checks bug report of a customer, saying something about a "Blind SQL Injection"
> Young me asking what that "Blind" part means
> "Dunno man, maybe u gotta close your eyes when hacking this"

Guess what, the issue was never fixed

I recently found a vulnerability in a food delivery app where i can add credit to my account. as some of u suggested I decided to report it. Here is their response of me asking (before explaining the bug) if i will be legally prosecuted and if ill be rewarded. this was their response. I feel they were mean. Thoughts ?

Reading my old code after a bug report

Bug (Feature) report and planning day

So we have a bug.
Yesterday I spend the morning sorting through other people's code to find out what is causing this bug report it to team leader once I find it. He asks me find out who made it and hunt them down! So git blame... Turns out it was him :S felt awkward mentioning it to him so didn't. 5 minutes later team leader "oh it was me"

So this one made me create an account on here...

At work, there's a feature of our application that allows the user to design something (keeping it vague on purpose) and to request a 3D render of their creation.

Working with dynamically positioned objects, textures and such, errors are bound to happen. That's why we implemented a bug report feature.

We have a small team tasked with monitoring the bug reports and taking action upon it, either by fixing a 3D scene, or raising the issue to the dev team.

The other day, a member of that team told me (since I'm part of the dev team) he had received a complain that the image a user received was empty. Strange, we didn't update the code in a while.

So I check the server, all the docker containers are running fine, the code is fine, no errors anywhere.

Then, as I'm scratching my head, that guy comes back to me and says "I don't know if it can help you, but it's been doing it for a week and a half now".

"And we're only hearing about it now?!", I replied.

"Well, I have bug reports going back to the 15th, but we haven't been checking the reports for a while now since everything was fine", he says as if it was actually a normal thing to say.

"How can you know everything is fine if you're not looking at the thing that says if there's an issue?!", I replied with a face filled with despair.

"Well we didn't receive any new reports in a while, so we just stopped looking. And now the report tool window is actually closed on my machine", he says with a smile and a little laugh in his tone.

In the end, I got to fix the server issue quite easily. But still, the feature wasn't working for 1.5 weeks and more that 330 images weren't sent properly...

So yeah, Doctor, the patient's heart is beating again! Let's unplug the monitor, it should be fine.

Welcome to my little piece of hell :)

Why the heck do users give a 1-Star rating instead of submitting a bug report?
Oh yeah I know, because that could help me -.-

I got a bug report with a typo in it. The subject read "...action X takes long time thank expected."
The thank is supposed to be "than".

I chuckled and immediately created a snapshot that shows the result of the action and the success message says, "Action successful, thank you for your patience."
I shared it with my team but no one even acknowledged it. 😞

I wonder whether this is a bug in Chrome, or if it's just Google drawing the conclusion from my northern geo-position, that we still haven't left the stage of building longships, raiding England and Scotland, burning monasteries and writing awesome poetry and literature in weird characters sets.

Well, I'm not Ragnarr f*cking Loðbrók or Egill Skallagrímsson, so I can't read electronic component data sheets the way those guys did.

I'll go grab my chisel, so I can carve a bug report into a suitably flat stone and shove it down the TCP/IP series of tubes leading to Google.

Rant!!!!!!!
When you work hard on building frontend and suddenly, you realise whenever you restart your localhost, some URLs don't work. And it's random. Error logs also seem meaningless as the latest error report keeps changing the error location from file to file. Wasted hours to identify the abnormal behaviour.
I always had the mentality to keep its programmers fault in order to always consider all possible flaws.
But realised later that it was the OS setting issue. Did a stacktrace about 300 lines and found out the root cause(hopefully as no issues till now). The bug was related to total allowed open files at a time.

I can drink my coffee with extra confidence now whenever they report a bug.

Dear Devrant community,
please, tell me that I can report Safari's JavaScript debugger as a bug... Yeah, the whole debugger.

I can't stand anymore on how much it sucks!

To all you fuckers out there giving bad app rating because some shit does not work on your shitty phone and you are to fucking lazy to report the bug via the fucking "send log to dev"-button that pops up with the exception.
Go fuck yourself.
And to all the user whose bugs I fixed and did not change their Bad rating - fuck you too.
And oh.. The fucktards that did not even install the app and give a Bad rating because i am your competitor - guess what...fuck you.

Let me get this straight. I don't have a paid Apple Developer account so I can't report iOS 10 bugs?

Anybody want to report a bug for me that double clicking the home button no longer launches Apple Pay from the lock screen?

This, always.
That's why i love my linux machine

Today I got an email that my bug report for alsa-driver is no longer valid, because Ubuntu version it was reported on is no longer officially supported.

Previous email related to that issue was from 7 Aug 2011, where they changed status to "confirmed".

Almost a decade.

I wouldn't say I'm complaining, maintaining open source is really hard, but that's an experience I had in 99%. Almost any issue I create (and I only make them when really desperate) dies in "stale". What's more annoying most of issues I end up searching google shares the same fate.

And maybe that's totally ok for non-trivial issues, but annoying AF.

Dont do with your friends but try on your enemies muhahaha

@dfox tiny bug report: when playing gifs, it first plays the first ~1s of the gif, then starts again and then plays normally.
I'm using Android 6.0.1.

My partner can't wrap her head around why I write all forms of communication in a formal matter, whether it be an email, bug report or text message.

I keep telling her you never know who you are actually talking to unless your face to face, anyone else agree with this logic?

How? Why?! How???

Does anyone notice that when you go to a 404 page on Google that the title has a "1" at the end, like someone was trying to put three !s but let go of shift to early.

I was going to submit a bug report, but I kind of like that 1 there, for some odd reason.

(If me posting this rant gets it fixed, I will be upset)

//Friends made me do this LOL
Haxk20 guide on using arch as pro.
//TL;DR Fucking read it dammit. I cant explain it in few lines.
Go to AUR.
LLVM-git
mesa-git
lib32-mesa-git
^ are a requirements if you want to have snappy system most of the time.
Do not fucking use AUR helpers. They are shit most of the time and break stuff like LLVM also they are for noobs who cant manage their shit (Really dont use them god dammit)
DO NOT USE PRECOMPILIED VERSIONS OF GIT PACKAGES. NEVER EVER !
Works surely but you can never trust anybody else just yourself (Remember this also for other things. The only person you can truly trust is yourself) Also precompilied shit breaks sometimes.
Run latest commit from mainline. I build every day if i can. If i cant or the mood is not right then once a week is fine.
Update Arch every day. Take care of the system.
I so many times hear Arch is piece of crap and breaks.
No its not. You just cant take care of your god fucking damn system.
If you dont upgrade every day stuff will break and you will be forced to make a force update which is never good (Only if package mantainer says so).
If you cannot take care of the system then arch isnt for you.
And if you still think arch is broken most of the time then see this:
Mesa, llvm, git, linux-next (+ few patches on top of that), xorg, wayland, gnome, firefox-nightly, libdrm and surely many more built from git at least once a week. (kernel and basic stuff built daily mostly) and having testing repos enabled at all times.
The last time i had unbootable GUI was 2 weeks ago and just because i upgraded LLVM without then building mesa. (YES YOU NEED TO DO THAT).
This is beyond bleeding edge as most people say. Yes its crazy but its fucking stable. Whats my point ? that if you say arch is unstable then think of this post and think again before saying. Its stable. You just cant take care of the system.
Restart after kernel update. I cannot say this enough. If you upgrade something low level then either source it. (Most people wont even have clue what that is so then reboot) Or the easiest option. REBOOT.
If you have bug. REPORT IT.
We are in dev community and im suprised most people here wont report bugs.
Are you dumb or what ?
What if your shit had bugs and people wont report them ? They would stay there and frustrate people more and more.
For real. Report bugs you find in kernel or IDK where. Without the report it wont get fixed. And be nice to devs. Dont expect help if you dont provide logs. ALWAYS PROVIDE LOGS.
Also if you run linux then run all AMD system FFS. Nvidia is shit on Linux. The company wont do shit for you. AMD has dedicated devs to opensource drivers. And opensource drivers are on parrity and heck most of the time better then proprietery.
I think thats all.
Sorry but friends made me do it.

devRant bugreport

Im getting more and more bugs in devRant on my LG G2.

- Links cannot be opened
- profiles can not be viewed
- double tapping a rant opens the rant twice (tapping five times opens it 5 times) instead of voting it up.
- once in a while an opened rant shows up again under all the comments (with all comments as well). When this happens its exactly the ammount of comments.

Im not sure where to report this. If @dfox could take a look at this?

Gonna look up my android version in a sec. (edit version: 4.4.2)

Okay i earlier rants i mentioned that the performance on my laptop drops when i disconnect the power and thats true. But i have noticed something really fucking weird today. Im starting to switch to i3 because GNOME lags when not connected to AC. But then i started skyrim and i played without AC power and i was having 50 fps on ultra settings. Wait what ? then i connected AC and performance was same. Disconnected and fps stayed the same. Amazing. So it seems GNOME is doing some shit when i disconnect power and just lags a lot. Im gonna try Fedora 29 to see if its GNOME thats really fucked up or just my distro. If its distro then well fuck it im gonna install pure arch as i wanted in first place but needed to test it and then kind of forgot about it. I really fucking hope its my distro thats fucked up. That my sound weird but i love GNOME and if GNOME is fucked up then well thats fucked up. I will probably file a bug report but it might never get solved and that shit.

IF YOU KNOW ABOUT THIS ISSUE AND FOUND A FIX OR YOU ARE HAVING THE SAME ISSUE WRITE A COMMENT !

@dfox @trogus
I have selected the algo mode for sorting .
Idk why but my feed is a little too full with rants I have already ++'ed . I am coming across the same rants multiple times,for days. Despite refreshing nothing happens.
I mean I can change the sorting mode for fresh rants but I suggest the algorithm be improved in a way that rants that have been upvoted or commented on by the user, no longer exist in the feed after refresh.

If this already exists then I am probably experiencing a bug, so I'd like to report that.

@dfox bug report time (at least it looks like one)!

I have ~400 upvotes atm.
For shoes in pic you need 1500 of them.
How i did this?
I equipped them when they were free afaik.

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.

Client writes a bug report: This and that doesn't work.
Me: This functionality never was implemented. Please open a feature request.
Client: But this is a bug. Without this feature, the service won't work as we expect.
Me: But this wasn't in the requirements for release. So you have to contact the PM for a feature request.
Client: THIS IS A BUG! FIX IT!
Me: GO FUCK YOURSELF! THIS IS A NEW FEATURE AND YOU HAVE TO PAY FOR IT!
Unfortunately, I never sent the mail. But I kept it in the drafts. Maybe someday...

A few days back I read an article about ethical hacking and get rewarded for bug bounty. I thought that might be interested.

AND

I'm about to send out my first ethical hack report to a company! I'm nervous because I don't know how they'll respond. It's an xss vulnerability, and I really hope they'll fix it.

"One misstep from developers at Starbucks left exposed an API key that could be used by an attacker to access internal systems and manipulate the list of authorized users," according to the report of Bleeping Computer.

Vulnerability hunter Vinoth Kumar reported and later Starbucks responded it as "significant information disclosure" and qualified for a bug bounty. Along with identifying the GitHub repository and specifying the file hosting the API key, Kumar also provided proof-of-concept (PoC) code demonstrating what an attacker could do with the key. Apart from listing systems and users, adversaries could also take control of the Amazon Web Services (AWS) account, execute commands on systems and add or remove users with access to the internal systems.

The company paid Kumar a $4,000 bounty for the disclosure, which is the maximum reward for critical vulnerabilities.

@trogus @dfox [BUG REPORT] Here's how this view looks on an iPhone 6SE.

Reported a freesync bug where its not working on eDP.
Its fixed now. Just have to edit EDID and well report a freesync range but then i have a freesync working laptop on linux.

Spent 2 hours last night (leaving an hour late) with the IT guy hunting down a problem that affected at least 12 other teams. It didn't crash the app, but did prevent MANY scripts from working, and thus nothing could be committed.
I found the culprit, made a solution, and posted in the email chain my solution. (it required a code review and a client-side update)
Someone responded asking for another dev to confirm my report. That dev did and them dumbed it down for those who can't understand programming talk. Then EVERY EMAIL after that thanked that dev for "fixing the root problem" and "solving their scripts".
And just now, the PO for the bug was replaced to that dev's team. (previously was my team's PO)

Got a weird bug report, 6 red bull later i'm a energizer bunny on speed. But have found and fixed a severe underlaying bug. Can't believe noone had noticed for years.

Now i'm afraid to report it to my boss cause it most likely costed us a lot of money over time. And I just got shafted in the pay raise so my loyalty is low.

FUCKING HELL.
Im supposed to report a fucking bug when i see one but once i do NOBODY fucking responds to the fucking bug and its sitting there for 3 days now without a fucking message from them.
I know kernel devs have a lot of work but ffs when i report a high priority bug then it most likely means that its fucking breaking entire system.
This is fucking crazy.

Report a bug when you see one but ffs respond to it when you get it FFS !!!!!!!!!!
This would give me an idea that its being fixed.
But its sitting there from 5.0 rc1 and no fucking message from anybody and i dont know if they are doing something or not.
I mean when my fucking machine locks up just due to watching video then i mean something is fucking wrong dont you think ?
I even posted them full dmesg of the issue and just nobody.
On one bug i got a response to send them dmesg so i did. After that they havent responded to it. And no fix. I would agree if they were fixing it but not responding but it doesnt seem like it.
This is fucking driving me nuts.
I just want to make the laptop stable but i cant like this.

Fucking hell. Webrenderer in Firefox is broken on latest mesa. Fuck. Well time to report a bug.

You know how my 'about' here says I create features from bugs?!? Well if you didn't before, now you do.. :P

Anyhow, today the most bizzare thing happened.. Customer played 'reverse uno card' on me..

Meaning?!

They reported a feature missing on uat env, when in fact I fixed a bug they have on prod..

Not sure how I should feel about this, but it sure made my day! (: I just hope they will not open a bug report for this missing bug..

Quick Tutorial: How to find a missing bug.

0) Wake up & have breakfast
1) Goto work
2) Do your job until the end of the working day
3) Make a backup
4) Shutdown your PC
5) Stand up
6) Go to the office door
7) Grab the door
8) Now the phone rings
9) Turn and go back
10) Take the phone
11) Now you get the bug report

This is a well approved method.
It always works!

When your qa team is too lazy to take a real app screenshot of a bug report and uses photobooth on their mac to literally take a backwards photo of the phone screen and then doesn't even flip the image.

With onions, tomatoes....

"During the middle of a song the game crashes for no apparent reason!!!PLEASE FIX!!!"

Actual bug report on github. Apparently pressing the "Report error" button is to complicated for some people...

01001000 01100101 01101100 01101100 01101111 00101100 00100000 01010111 01101111 01110010 01101100 01100100 00100001

> Opened devRant to read some cool rant.
> Scrolled down the feed to find awosm rant.
> Found an interesting rant, touched it to view it.
> Read the rant.
> press back to find more awosme rant but, (boom💥) again on top of feed.😡😡😤
> Now need to scroll down again :/ :(
FIX THIS!!!!

All my tasks was development, last week our boss gave me a testing task, and I completed it.
He said that the developers will hate me if I keep reporting every expected/unexpected, small/big, normal/critical bugs , so that he sent me back to the development team.
I just wondering if I misunderstand the word "testing"!!?

I really lost my faith in our profession.
A Software&Hardware solution that costs more several 10.000€ is broken after every update.

The Producer even achieves to break untouched features in new releases.
No communication at all. If you report Bugs, they are your fault. The whole system has absolutely no security at all.
It is unsecure by design.

And even if they hear your Bug report you have to pray that they will fix it.
Most if the time you have to wait the whole year for a new release tio get your bugfixes.
But there are also bugs that are untouched for years.

WHY? WE PAY YOU!
I want to cry

This is probably VERY OLD, but why don't devRant supports Markdown? Having to upload (not paste or drag) code screenshots and having to UPPERCASE to yell or emphasize text feels... quite non-dev.
I found the bug repo and checked the Markdown issue has... almost three years.

I just came by the @highlight bot. Seriously? There are several layers of "wrong" with that hahah

Bonus: not very good UX to write a message, try to post it, and ONLY THEN get to know there's a time limit. This should show when you open the form, not when you submit it.... But I just sent a bug report on that, at least.

Bonus 2: if the char limit is 5k, why's the textbox so tiny on the web?

Bug-report:

Fastly pressing 2 different items in the bottombar results into a disabled content.

Pressing an item again fixes it, but still...

Correction: Pressing a different item and then the previous item causes it

So we have this really annoying bug in our system that customers keep complaining about. I've explained in detail, multiple times, why the part they think is a bug is not a bug and the workaround they keep asking me to apply doesn't make sense, won't fix the issue, and won't even stick (the system will notice that the record they want me to delete has been removed and it will repopulate itself, by design).

I've told them what we need to do as an actual workaround (change a field on the record) and what we need to do to properly fix the bug (change the default value on the record and give proper controls to change this value through the UI). We've had this conversation at least three times now over a period of several months. There is a user story in the backlog to apply the actual fix, but it just keeps getting deprioritized because these people don't care about bug fixes, only new features, new projects, new new new, shiny shiny new.

Today another developer received yet another report of this bug, and offered the suggested workaround of deleting the record. The nontechnical manager pings everyone to let them know that the correct workaround is to delete the record and to thank the other developer for his amazing detective work. I ping the developer in a private channel to let him know why this workaround doesn't work, and he brushes it off, saying that it's not an issue in this case because nobody will ever try to access the record (which is what would trigger it being regenerated).

A couple hours later, we get a report from support that one of the deleted records has been regenerated, and people are complaining about it.

🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄

@dfox where did the report button go
Supervillian detected

>makes a bug report about the JS linter in Eclipse Che not working

> makes it a P2 bug (moderate severity)

> confirms in their current implementation it doesnt work

> escalates to P1 (high severity)

wow for once Eclipse is actually making their shit better

I've just received an urgent bug report email saying something like:

Stop sending [item] to destination. This should have been taken care of in the initial work, but we forgot to say so.

... The work they requested was that [item] gets sent to destination if the user checks a checkbox. If I wasn't supposed to build this, then what did they want me to build in the first place?!

I just created an Oracle account just to comment on a mysql bug report in order to inform people to use mariadb as a fix ¯\_(ツ)_/¯

^w should delete back a word, not to the beginning of the line! This is broken because instead of readline, Oracle's mysql-client uses editline.

Yet why the fuck do you compile mysql-client with editLine wrapper that breaks the common keybindings?

Licenses is why. Oracle wants to avoid using GNU GPL, and readline uses just that, so they use editline since it has BSD. And they just don't seem to give a damn if it breaks usability.

?rant
We bought an expensive middleware which helped development speed and stability a lot. Something did not work and after a week I located the bug in the middleware. Support was adequate and the bug got fixed after my report.
I'm not mad at the developers, because bugs happen, and this one was hard to catch, even with tests.
On the other hand I have to explain my boss what took so much time.
It really wasn't my fault, but I also don't want to shame the middleware company, because it will make it harder for me to buy their stuff (and I quite like their products) or even any software at all.

@dfox @trogus
How about adding feature and bug report in app?
Add it in more tab like the discussions.
When clicked, there will be two tabs called feature and bugs. We can report them and dfox can make a checkbox only for him to click when viewed. That way, it would be more efficient.

I HATE the idea of only releasing on pre-determined schedules despite work being completed and just waiting for that day to arrive.

I'm a co-founder of a small software company. We have partnered with another particular company that also writes software. Some of our clients have access to paid content of that company's services through our application.

Every once in a while, our clients will report issues with that company's service to us, because they access it through our application. They think it's our issue.

We then pass the report on to the partner company, telling them that their stuff is broken. Their reply goes like this:

"Ok. We'll get the bug fix scheduled, and we'll release it next Thursday."

"Next Thursday? The issue is now, they can't use the service."

"That's our scheduled release date."

O.M.G.

We voluntarily walked away from our safe, cushy jobs working for other people, taking enormous pay cuts to start this company. Now, we're 6+ years in, disrupting established fat-and-happy competitors in this space. I GUARANTEE you that if we had that same attitude, we would have been absolutely obliterated early on.

We are quick. Guided by kanban boards, our suite of unit tests and integration tests is vast and kick-ass. With continuous integration and the click of a button we know if we broke something or if the piece we're working on is ready to be pushed to production, IMMEDIATELY. Our "release schedule" is when the damn thing is complete.

It isn't all bad. Our integration with them has been beneficial for both of us. I just loathe their snail's pace which negatively affects our mutual customers. It can make us look bad, and we can do nothing about it.

Blah.

Open source is poison, hoax and source of much troubles.

Even as I love OSS, and I use it a lot, when things go south, they go south terribly.

There was "security" updates in one OSS program I have been using, that accidentally prevented use cases which specifically affected me. I raised bug report, made issue and gave small repro for it.
One of the core developers acknowledges that yes, this is problem, and could be handled with few added options, which users of similar use case could use to keep things working. He then tags issue "needs help" and disappears.
After I have waited some time, I ask help how I could fix it myself, like how to setup proper dev environment for that tool. Asked it in their forums few days later, as issue didn't get any response. Then asked help in their slack, as forums didn't get any help.

Figured out how to get dev environment up, fix done (~4 lines changed, adding simple check for option enabled or not) and figured out how to test that this works.
I create pull request to project, checking their CONTRIBUTING and following instructions there. Then I wait. I wait two weeks, and then one of the core develors goes to add label "needs response from maintainer". That is now almost two weeks ago...

So, bug that appeared in October, and issue that was created October 8th, is still not fixed, even as there is fix in PR for 28 days this far.

And what really ticks me off? People who make statements like: "it is OSS, have you thought of contributing and fixing things yourself?" when we run into problems with open source software.

Making fix yourself ain't biggest problem... but getting it actually applied seems to be biggest roadblock. This kind of experiences doesn't really encourage me to spend time fixing bugs in OSS, time is often better spend changing to different tool, or making changes in my own workflow or going around problem some kludge way.

I try to get business starting, and based on OSS tools. But my decision is staggering, as I had also made decision to contribute back to OSS... but first experiences ain't that encouraging.

Currently, OSS feels like cancer.

When a fucking $60 paid WordPress theme has endless-scroll implemented, but the client decided for a static start-page and this damn theme will continue loading content when scrolling to the bottom, but doesn't display the new content, because it should be a static page. (It still loads content but just disables displaying the new content)

So, in three minutes scrolling the start page, I downloaded 0,5GB of images, that aren't visible.
Told the client, who's using this theme on 8 websites (and paid 8 times). He's writing a bug report.

Bug report:

iOS 10 (latest) + iPhone 6

Can't scroll past initially loaded rants on algo screen

Also, love the new tag picker...

Epic comment:

1+2+3+4+....infinity = -1/12
SRC: Numberphile

Dear god, id like to file a bug report(see attached video)

Reported my first bug today ☺

Why!!!
Why must some devs make life complicated!!!!!!

So, here I am enjoying my day (well enjoying the meetings that are taking me away from working) when I get a bug report that script X isn't sending out emails anymore.

Ok that's weird, this as far as I know uses the same email class as every other email being sent out from this project, and they all work.

Let's go have a quick dig...

function sendEmail(){
/*do a bunch of stuff*/
}
Is being used, well that's odd, it should be $emailService->send()
But what ever, it's probably an old wrapper for legacy sake since this script was written years ago. But nope, I almost cried, it's a wrapper for mail() isolated into this script.

Like for fucks sake, why in the hell would this be used when there's an entire fucking class that's tried and tested and only looses 1 email every few months, coz shit happens.

Errrrr.... sometimes i really wonder why people can't just do what they need to do the first time round.

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.

Complete bug reports for devs: Error name, stack trace, what did you do when it happened and all that stuff

Complete bug report for users: it crashed help

DevRant android app.
Profile page - once scrolled down couldn't scroll back to profile view(top).

So this is a fun bug. Oneplus 5 with android 7.1.1, happens when switching from a fullscreen video (Netflix) to devrant

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.

So I got a job and on the first day I was giving a task to fix a bug which they said it was urgent that the software is been used by the financial department, so if I don't get it fixed soonest they would be loosing money.

I completely don't know how the software works, so I thought they would give me some time to get familiar with the code base but fu*k I gat to fix this if not they would See me as a person who does not know his stuff.

Some minute later, the CTO messaged me asking me how I introduced the bug in the first place, I was like I have not even cloned the repo, I have not pushed any code lol. At that point I know I'm gonna be so f**ked in this job .

So after sometime I fixed it but I had to get permission from the lady that manages the database because I was not given access and I need to update a field name in a table for everything to work well. I asked the lady to help update the field since she is the only one that has access to it and its urgent and every body is waiting for me. She told me to wait for 1hr and remind her that she's busy right now, after some hrs I reminded her but she kept telling me she will update it later.

Nobody wants to hear that I was not the one delaying the fix, so since I can push some code to the report and it's get deployed, I wrote a script to update the field and I removed the code later. With that done the fix was live and everybody was happy!

The next day, the lady came to me and was like I tried to update the field when I went home but it has already been update but I don't know why. I told her I don't know too :p😃

!rant

Err...
Week 64 has already passed ^^"

\Bug Report/

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 10

They tell me to only review security in the security reviews I'm doing (and if I bring to attention that they're implementing a weak encryption so even though they're not using it at the moment it might cause issues so be careful with that they say to only review security 😵) and then I see this mssql in a where:
AND ISNULL(field, 0) IS NULL
And I think wtf, should I report that? I did and it's a bug and they're thanking me now....
God dammit it's hard to "review security" here...

Speling eror is not my bug

A program I was using did not recognize a flag that I needed, so I edited the EXE file (using notepad++, no hexeditor) to replace a flag whose name was actually checked with the one I needed. Worked like a charm.

The response for my bug report was "this feature should not be there in the first place, we will remove it". Lucky me they did not remove it earlier.

A tale of silos, pivots, and mismanagement.

Background: Our consultancy has been working with this client for over a year now. It started with some of our back-end devs working on the API.

We are in Canada. The client is located in the US. There are two other teams in Canada. The client has an overseas company contracted to do the front-end of the app. And at the time we started, there was a 'UX consultancy' also in the US.

I joined the project several months in to replace the then-defunct UX company. I was the only UX consultant on the project at that time. I was also to build out a functional front-end 'prototype' (Vue/Scss) ahead of the other teams so that we could begin tying the fractured arms of the product together.

At this point there was a partial spec for the back-end, a somewhat architected API, a loose idea of a basic front-end, and a smattering of ideas, concepts, sketches, and horrific wireframes scattered about various places online.

At this point we had:
One back-end
One front-end
One functional prototype
One back-end Jira board
One front-end Jira board
No task-management for UX

You might get where this is going...

None of the teams had shared meetings. None of the team leads spoke to each other. Each team had their own terms, their own trajectory, and their own goals.

Just as our team started pushing for more alignment, and we began having shared meetings, the client decided to pivot the product in another direction.

Now we had:
One back-end
One original front-end
One first-pivot front-end
Two functional prototypes
One front-end Jira board
One back-end Jira board

No worries. We're professionals. We do this all the time. We rolled with it and we shifted focus to a new direction, with the same goals in mind internally to keep things aligned and moving along.

Slowly, the client hired managers to start leading everything in the same direction. Things started to look up. The back-end team and the product and UX teams started aligning goals and working toward the same objectives.

Then the client shifted directions again. This time bigger. More 'verticals'. I was to leave the previous 'prototypes' behind, and feature-freeze them to work on the new direction.

One back-end
One conceptual 'new' back-end
One original front-end
One first-pivot front-end
One 'all verticals' front-end
One functional prototype
One back-end Jira board
One front-end Jira board
One product Jira board
One UX Jira board

Meanwhile, the back-end team, the front-end team overseas, all kept moving in the previously agreed-upon direction.

At this stage, probably 6 months in, the 'prototypes' were much less proper 'prototypes' but actually just full apps (with a stubbed back-end since I was never given permission or support to access the actual back-end).

The state of things today:
Back to one back-end
One original front-end
One first-pivot front-end
One 'all verticals' front-end
One 'working' front-end
One 'QA' front-end
One 'demo' front-end
One functional prototype
One back-end Jira board
Two front-end Jira boards
One current product Jira board
One future product Jira board
One current UX Jira board
One future UX Jira board
One QA Jira board

I report to approximately 4 people remotely (depending on the task or the week).

There are three representatives from 'product' who dictate features and priorities (they often do not align).

I still maintain the 'prototype' to this day. The front-end team does not have access to the code of this 'prototype' (the clients' request). The client's QA team does not test against the 'prototype'.

The demos of the front-end version of the product include peanut-gallery design-by-committee 'bug call-outs', feature requests, and scope creep by attendees in the dozens from all manner of teams and directors.

Bugreport, when someone posts a rant it shows it 2 times.

I just received a bug report that stated 'Hardware state constantly flapping'.

Bug report: "The patching system is not working."

"The patching system is not working.
The patching system is not working.
1. Download patch
2. Try to install patch.
3. Observe: the patching system is not working.
Expected behavior: The patching system is working. "

!!rant life toptags bottags
My tags seem to be okay. Let's go.
I'm 14. I live in a place where nobody smart lives, and the school I go to has no coders.
Last year, all my friends moved. The only friend I had left now hates me, simply because they yelled at me everyday and I yelled at them once.
I am in the middle of my exams. I also have the flu, but thankfully it's not the e-flu, otherwise you guys should prepare for 24/7 headaches.
Due to the medications I am taking, I'm half-asleep all the time, and I probably am messing up all of my grades.
My entire extended family is in India, and I go there 2 times a year. I miss them so much right now :(.
At the same as doing exams, I am trying to keep my laptop (primary) and PC (secondary, desk) configuration and setup approximately synchronized. In order to do that, I am setting up my dotfiles repository.
Except that all my laptop config (which works) is written horribly, and I need to rewrite it all.
At the same time, I have 3 other projects going on: An OS written in D, a source-based package management system written in D, a small website (not online), and a whatever's cooking in my mind at this moment.
Right now, I'm supposed to be studying for my French exam.
Instead, I'm here, typing this out on my phone.
I have a classmate in school who can type QWERTY at 80WPM. I'm learning Dvorak (Programmer's!) and my current speed is 33WPM, after about 2 months of half-hearted practise during work time and at school.
Sometimes, I look at the world we have here, and what we're doing to it, and I wish that sometimes we could simply be content with life. Let's just live, for once.
I find ~60 random songs in one go, simply by finding a song I know on YouTube and going to the 'Mix - <song>' playlist. I download them all (youtube-dl), and I listen to them. Sometimes, I find this little part in a song (Mackelmore & Ryan Lewis - Can't Hold Us beginning instrumentals, or Safe and Sound chorus instrumentals) that make me feel so happy I feel like all's good in the world. Then the song moves on and with it, my happiness.
I look at Wayland, and X, and I think - Why can't we have one way of doing things - a fixed interface to express anything, so that one common API exists for everything of that type? And I realise it's because they feel that they're missing something from the others. Perhaps it's a bug nobody's solved or functionality that's missing, and they think that they can do better than that. And I think - Well, that's stupid. Submit a fucking bug report or pull request instead of reinventing the wheel. And then I realise that all the programming I've ever done in my life IS simply reinventing the wheel. And some might say, "Well, that guy designed it with spokes and wood. I designed it with rubber and steel," but that doesn't work, because no matter what how you make it, it's just a wheel. They both do the same thing. Both have advantages and disadvantages, because nothing's perfect. We're not perfect because we all have agendas and wants and likes and dislikes and hates and disgusts and all kinds of other crap, and our DNA's not perfect because it manages to corrupt copy operations (which is basically why we die of old age, I think).
And now I've lost my train of thought and this is too large to scroll over so I'm just going to move on to the next topic. At this point (.), I have 1633 letters left.
I hate the fact that the world's become so used to QWERTY because of stuff that happened 100 years ago that Dvorak is enough of a security to stop most people from being able to physically use my laptop.
I don't understand why huge companies like Google want to know about me. What would you do with this information? Know how to take over my stuff when the corporation-opocalypse comes around? Why can't they leave me alone? Why do I have to flash a ROM onto my phone so that Google cannot track me? What do you want, Google?
I don't give a shit any more, so there's my megarant.
Before anybody else (aside from myself) tells me that this is too big, all these topics are related simply because my train of thought went this way. There's a connection between each of these things, but I just don't know what it is.
Goodnight, world. 666 is the number of characters I have left. So is 42, for that matter (thanks, Douglas Adams!). Goodbye.

Fug: A feature request, disguised as a bug report. There are far too many fugs in my life.

Users have use cases, test cases, user manual etc documented material with them at the time of UAT.
But in the end users do only those things which they don't suppose to do..!! 😑😥

- 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, @trogus

Worth to try...

!rant, more of an incredulous/cruelly amused "you had ONE job..."

so: biggest IT/PC/electronics store in my (and neighboring) country. their webpage, of course with the function to buy online, because of course.

the big green "Buy" button does nothing. doesn't work. doesn't react. I keep clicking it multiple times, shorter, longer, etc, because maybe their JS scripts are just shit so they slow.

nope.
okay. open devtools, JS console.
hover over the button: "Error: isMobile is not a function".
click the button: "Error: isMobile is not a function"

WAT.
search for isMobile in the script.
173 occurences.
fuck this.
console: isMobile = function(){return false;}
because I'm not on my phone.

click the "Buy" button.
works flawlessly.

...HOW?
THE WHOLE PAGE IS AN ESHOP YOU COMIC RELIEF INCOMPETENTS! =D

173 uses of non-existing function that blocks business-critical feature, THE ONLY CORE FEATURE FOR WHICH YOUR SITE EVEN EXISTS, and NOBODY, not the dev who fucked it up, NOT EVEN QA, noticed it??? =D =D

if I was the boss of the devs, or even boss of the whole company...
git blame
...and then i'd go the whole chain from the dev who caused the bug, through all of the QA people who "tested" that version before deploy, and I would personally, on the spot, fire each and every single one of them.

mainly because of who knows how much money this stupid not even a proper bug lost them.
but secondarily, because clearly none of those people give a single shit (n)or have an idea how to do their jobs.

=D =D

yeah but I was a good guy, filed a bug report in the "Complaints" section of their Contact form.
it goes to some call-center-like peon, so it starts with a sentence "forward this to your site's dev people outright to file as a bug, thank you".

but... HOW.... =D
HOW can you let something like this through? =D
the bottleneck of your whole user interaction, which forms first of the three steps OF THE MAIN AND MOST IMPORTANT FUNCTION of your whole business... =D
...I...
...does not compute =D

...BUT THEY USING ANGULAR, SO THEY ALL MODERN AND HIGH-TECH AND EVERYTHING'S FINE!!! =D =D

please tell me who had the great idea that someone should put screen shots of a web page in a excel sheet to include as their "bug" report. I cant fathom that someone once thought this idea was "good"

Fuck, I want to report a bug to KDE, but the more I think of it the more it looks like it's someone who implemented the shit.

It's a feature!

For some fucking reason KDE launcher overrides the commands from one of my programs with its shortcut entries. That's mostly OK.

Now, the problem is that if for some reason the shortcut goes broken, KDE makea sure it is stores in some sort of database, so that even if you delete it from the disk you will still have a broken link overriding the real command.

Until here it's OK. The thing is that, if you delete the shortcut , you will be prompted with a message showing its contents, asking if is it secure to launch the corresponding shortcut?

I'm like, what? Man I deleted the file, there's no shortcut anymore, just let it go and show me the original command.

why would I want you to store previously deleted shortcuts so you may make sure I launch my programs through them?

PS: forgot to tell the whole problem started from a bug in another program, which for some nonsensical reason creates shortcuts calling system commands through itself rather than just calling them out. The result is that once this program is removed all the shortcuts it created no longer work.

South Africa Release notes version v3.0.2

In 1994 SA underwent one of the biggest system upgrades since 1948. In this new rolling release since the system update called apartheid the system has been annexing resources, locking it down, making it closed source, closing it off community updates and from global updates and minimizing services across the board. On 27 April 1994, the new democratic system update was released with a new system monitor, release resources and balancing efficiency in the system. Though there were remnants of the old code in the system, it was being rewritten by a new generation of users, open source resources were established, giving users the right to choose among themselves how to grow the system , and how to better the experience for all.

In 1999 a new system monitor was created by the users, it wasnt as popular as the ground breaking Madiba release but it was a choice by the community to move forward and grow. The system was stable for a few years, new users were able to develop more on the system, making it more lucrative monetary wise. There were still remnants of the apartheid code but the new generation of developers worked with it making it there own, though they had not yet had admin rights to help change the system, they created a developer culture of their own. A new system resources balancer was introduced called BBEE, that allowed previous disadvantage users more admin rights to other system resources, helping the user base to grow. Though the balancer was biased, and flawed it has helped the system overall to grow and move forward. It has major holes in security and may flood some aspects of the system with more outdated software patches, users have kept it in its system releases until the resource balancer moved the system into a more stable position.

The next interim system monitor release was unexpected, a quiet release that most users did not contribute towards. The system monitor after that nearly brought the system down to a halt, as it was stealing resources from users, using resources for its own gain, and hasn't released any of it back to the system.

The latest user release has been stable. It has brought more interest from users from other countries, it had more monetary advantages than all other releases before. Though it still has flaws, it has tried to balance the system thus far.

Bug report as of 16 Feb 2018
*User experience has been unbalanced since the 1994 release, still leaving some users at a disadvantage.
*The three tier user base that the 1948 release established, creating three main user groups, created a hierarchy of users that are still in effect today, thought the 1994 release tried to balance it out, the user based reversed in its hierarchy, leaving the middle group of users where they were.
*System instability has been at an all time low, allowing users to disable each others accounts, effectively
killing" them off
*Though the infrastructure of the system has been upgraded to global standards ( in some aspects ) expansions are still at an all time low
*Rogue groups of users have been taking most of the infrastructure from established users
*Security services have been heightened among user groups though admins were still able to do as they pleased without being reprimanded
*Female users have been kicked off the system at an alarming rate, the security services have only kicked in recently, but the system admins and system monitor has not done anything about it yet

Bug fixes for a future release:
*Recreating the overall sysadmin team. Removing some admins and bringing others in
*Opening the system more globally to stabilize it more
*Removing and revamping the BBEE system, replacing it with more user documentation, equalizing the user base
*Giving more resources to users that were at a disadvantage during the first release
*Giving the middle group of users more support, documentation and advantages in the system, after removing the security protocols from the user base
*Giving new users who grew up with the post 1994 release more opportunities to help grow the system on a level playing field.
*Establishing the Madiba release principles more efficiently in the current system

Bug report : date_created is wrong by one day, but only in the afternoon. Gaaah ! Why did nobody save the user's offset...
Or better yet just normalize to UTC!?!?

Details of the bug report sent by our customer:
"Sometimes some errors happens on website".
Me:
"Be patient man... I feel you!".

!rant
Bug (or feature ?) report
I don't know if it's a bug, a feature, and something that just happens to me.. When I view someone's profile and I want to scroll down to see the rants, the "first scroll" stops at the end of the profile. Then I can scroll down more. And after, if I want to see the profile again I can't scroll up. I ended up finding out that tapping the username lets us see the profile again. I'd like to point this out because the behavior seems kinda weird to me, I don't know what others think about it

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

During the company's Xmas event, we were off-site at a place that does events to do a team-building event followed by dinner party.

An error report came up, it wasn't a showstopper, but it was fairly serious, and the perfect excuse to sit out the BS improv team-building exercises that the powers that be thought would be a good idea to have.

Probably my favorite bug ever.

Bug: attach an image to a rant, then remove it and tap add image again.

Gallery opens, devRant crashes behind

Oneplus 3T, android 8, there's no update available in play store...

That old Windows copy and paste bug issue again. :-)

I wonder if its due to some Linux code someplace..

Anyhow, I was using a remote desktop application and copying some text from there, and trying to post it into Firefox..

Except it was posting the previous thing I pasted, and not the thing I really wanted to paste !

But, if I open Notepad, and paste to there, it does correctly paste the last thing I copied, and not the previous thing.

If I then copy that, and try posting it into Firefox, it works correctly !

So, its all Firefox's fault !!!

So, where do I report bugs in Firefox ?

Though it could be an OS bug.. ?

I'd have to test more applications, when I get time !

I bet this doesn't happen under Linux. :-)

Or does it ?

Magento Debugging Horror!
Changing lots of things in magento with no problem. Continuing development for quite sometime. Suddenly decide to clear cache to see affect of a change on a template in frontent. Suddenly magento crashes! There's no error message. No exception log. No log in any file anywhere on the disk. All that happens is that magento suddenly returns you to the home page!
Reverting all the changes to the template. Clear the cache. Nope! Still the same! Why? Because the problem has happened somewhere in your code. Magento just didn't face it, because it was using an older version of your code. How? Because magento 2 even caches code! Not the php opcache. Don't get me wrong. It has it's own cache for code, in a folder called generated. Now that you cleared all the caches including this folder, you just realized that, somewhere something is wrong. But there is no way for you to know where as there is absolutely no exception logged anywhere!
So you debug the code, from index.php, down to the deepest levels of hell. In a normal php code, once the exception happens, you should see the control jumps to an exception handler, there, you can see the exception object and its call stack in your debugger. But that's not the case with magento.
Your debugger suddenly jumps to a function named:
write_close();
That's all. No exception object. No call stack. No way to figure out why it failed. So you decide to debug into each and every step to figure out where it crashes. The way magento renders response to each request is that, it calls a plugin, which calls a plugin loop, which calls another plugin, which calls a list of plugins, which calls a plugin loop, which calls another plugin.....
And if in each step, just by accident, instead of step through, you use the step over command of your debugger, the crash happens suddenly and you end up with the same freaking write_close() function with no idea what went wrong and where the error happened! You spend a whole day, to figure out, that this is actually a bug in core of magento, they simply introduced after your recent update of magento core to the latest STABLE version!!! It was not your mistake. They ruined their own code for the thousandth of time. You just didn't notice it, because as I said, you didn't clear the `generated` folder, therefore using an older version of everything!
Now that after spending 7 hours figuring out what has failed with absolutely no standard way of debugging and within a spaghetti of GOTO commands (Magento calls them plugin), why not report it to github? So you report it with a pull request. This also takes 1 hour of your time. Just to next day get informed that your pull request is rejected because another person already fixed the bug and made the same pull request. It was just not on the latest stable version yet!
So you decide to avoid updating magento as much as possible. Because you know that the next Stable version will make your life and career unstable. But then the customer complains that the Admin Panel is warning him of using old Magento version which might pose SECURITY THREATS!

For our product there is a common type of bug we get reported. It is not really a bug, also it is not a feature - instead it is a missing or incomplete feature.

For example to help users we add a search feature on one screen, but there is no search on some other screen. Now the absence of search on that screen is apparently a bug.

To make things worse to report the bug users try to trick us. They say something like:
"Hey can you help me? How can I find things in the abc screen?"

So I explain how to browse for the item or whatever.

Then they say:
"Ok now how do you do that on the xyz screen?"

Slightly suspiciously I now tell them how you can browse for the item like before or we have this new feature eg. search you can use if that is quicker.

Now they say:
"Don't you think it would be better to have that search on the first screen?"

OK now I realize this is just a trick and the person doesn't actually need help using the software. So I tell him how we only added the feature on one screen and if he thinks there is value adding it on other screens he can put enhancement request in and if wants he can talk to my boss about making it a priority.

Then they go on asking other rhetorical questions like:
"why was it designed like this?"
"Are you guys deliberately trying to make life harder for people by making them learn different ways to do things?"

I now want to delete the new search feature but luckily it is close to lunch time so I have a good excuse to escape the conversation.

!Rant
Bug Report / Feature Request.

Just 2 things that bother me with the web app.
1. You can't modify rants or comments - only delete them.
2. On the profile page the web version does not replace line breaks "\n" with html breaks "<br>". (See the code on my profile on mobile vs web.

Just thought I'd mention them since I use the web app more than the mobile.

Bug report @dfox
=D

Bug report workflow for our customer support department.
1. Use eyes
2. Use brain

Just printed as poster

@dfox, there's still occasionally some weird stuff happening when my phone is on rotate. (Sadly I don't know how I did this.)
I'd be glad to help if you need anything from me.

Bug Report:
Collab link posted in Rants doesn't redirect to Collab posts.

Hello god, I'd like to report a bug.
this.IsSocial is true, but this.BeSocial() throws a NotImplementedException.
I'd like this fixed ASAP, at least by changig this.IsSocial to false since the BeSocial method is not implemented, but this mismatch is killing me...

Anybody know the URL of gods issue tracker? I really need to file this bug...

testing feature: that is not what the specs say this how this is suppose to work. so, I write a bug report.

conversation with developer goes as follows

developer: this is not a bug. sends the bug report back.

me: the specs say it is a bug. I resubmit the bug.

developer: sends it back saying that it has been changed in the new specs.

me: how do I get the new specs?

developer: it is on the server, go ask your boss on where ecaxtally on the server they are. then, he closes the bug report.

I found a bug in Twitter; does anybody know who I can report it to?

So I accidentally used an email as a username to create an account through Jira for mongodb to report a bug.. That apparently breaks the entire Jira login system. I cant recover my account, and I can't create another account because my email is already in use.. Thanks Jira for deciding I'm going to bar before I go home today...

Last week, I didn't come up with something for this. Just now I experienced such a moment and remembered that there was a weekly rant on this topic.

The first bug report for my first ever project got resolved and the client commented with thanks and told to keep it up.
It feels awesome.
(tears of joy all over my eyes)

It's a moment that took me more than a year's effort to get a bug report and a positive feedback post it's fix.

I am all motivated now to work even better and wait for such awesome moments.

Trying to find if there is a bug on Devrant.
I'm calling the herd (meaning a group of Devranters I added on a list for a specific topic).
If you are on the list and didn't receive a notify, please tell me so I can report it.

Dear God, why are punishing me by another bug report related to Edge?

Console dock freezes commonly for MINUTES, literally. It doesn't support objects, so every object is very usefully converted to "[object Object]" string. And now I am discovering that change event on input is magically not firing?

What a day. This would be solved in Chrome or Firefox in a matter of minutes, for a same time Edge doesn't even manage to render a page with dev tools opened FFS...

3 or 4 weeks ago me and management had a talk about new features in our product...
So we implemented the new features and then we released the app...
Today I got a really long bug report that summarizes into the following sentence -> BUG: Everything works exactly as we talked 4 weeks ago.... And apparently that is bad 😣

Like c'mon dudes if now it is a bug then why the fuck I needed to code that feature?! Time totally wasted for nothing! 😤

Fix My Lighthouse!

If a pentester find a very critical bug and the boss is not aware of him knowing this type of exploitation (no one is expecting him to find such flaws)

Should he report it ? Or reporting will make him suspicious ?

@dfox devRant search seems a tad iffy - if I search for "wk19" I see results for pretty much every weekly rant, not just wk19 ones.

Bug report

Using a physical keyboard seems to prevent me from being able to complete a post. I can open both a comment and new rant, type the contents but am not able to post. The button doesn't do anything.

Switching off the keyboard seems to cause strange behaviour (deleted this rant the first time I was trying)

My setup:
Moto z play android 7.0
SwiftKey keyboard app
Logitec K810 Bluetooth keyboard

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.

"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.

My devRant app crushes quite often on iOS 12.1. Is it a well known problem or not?
Also, the emoji keyboard sometimes jumps back to English keyboard instantly without press anything

What do you use for virtualisation? Proxmox? ESXI? SmartOS?

Only docker/lxc or also kvm/openvz?