Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Since this repo doesn't have "issues". I'll do it here: #25

Closed
wants to merge 1 commit into from
Closed

Since this repo doesn't have "issues". I'll do it here: #25

wants to merge 1 commit into from

Conversation

terremoth
Copy link

@terremoth terremoth commented Mar 5, 2021

YOU CANT REPORT BUGS A SIMPLE WAY QUICKLY

When you get an error in your MySQL Workbench, it asks you to report or not a bug. So here we go.

image

Oracle just asks a FUCKING WHOLE PAGE FULL OF BUROCRACY TO FILL just to report a FUCKING BUG

You guys just can't do a simple way to report bugs here? WITHOUT ORACLE WONDERING TO KNOW WHERE I LIVE (WTFFFFFF)

oracle burocracy

This is why the repo doesn't receive 10 per cent of the problems it should have to being reported! No one will give the boring time to fill a bunch of fields "where the fuck I live" , "create an oracle account" just to report a disgrace of a bug!

You guys put in your mysql bug page:

  • huh how to ask questions the right way by eric raymond
  • durr how to have a good customer support
  • "How to Report Bugs Effectively" (YOU GOTTA BE KIDDING)

BLA BLA BLA

And just don't know hot to make a simple bug report system?????

This is THE FIRST THING you guys should FIX ONCE FOR ALL

A bug appeared just letting the workbench opened the whole night, doing just NOTHING and appeared "a bug".

I AM JUST TIRED OF THIS SHIT WAY - MAKE THINGS SIMPLE!!!

…RT BUGS A SIMPLE WAY QUICKLY

When you get an error in your MySQL Workbench, it asks you to report or not a bug. So here we go.
Oracle just asks a FUCKING WHOLE PAGE FULL OF BUROCRACY TO FILL just to report a FUCKING BUG

You guys just can't do a simple way to report bugs here? WITHOUT ORACLE WONDERING TO KNOW WHERE I LIVE (WTFFFFFF) to just
@mysql-oca-bot
Copy link

Hi, thank you for submitting this pull request. In order to consider your code we need you to sign the Oracle Contribution Agreement (OCA). Please review the details and follow the instructions at https://oca.opensource.oracle.com/
Please make sure to include your MySQL bug system user (email) in the returned form.
Thanks

@terremoth
Copy link
Author

BOT FIA DA POTA, tá me tirando né?
kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk

@mysql-admin
Copy link

@terremoth

  1. Reporting bugs to any bug system system requites having a user in that system. If you don't have one you are asked to register.
  2. Github PRs are for submitting contributions not bugs. If you have a bug to report in Wokbench, please register in the bug system and report it
    Thanks
    ==Omer

@mysql-admin mysql-admin closed this Mar 8, 2021
@terremoth
Copy link
Author

terremoth commented Mar 9, 2021

@mysql-admin

"any bug system requires having a user in that system"

No! just if this system is out of GitHub, I already have a GH account. The bugs could be reported here, in a common "issues" tab as normal repos.

Me, and 95% of the people won't create Oracle account just to report mysql bugs... and worst: fill a whole big form fields, including where I live... To god with that kind of policy. This is completely INSANE!

MySQL could be a even more better database and Workbench a even more better tool, if errors could go anonymously (without user sensitive data) or if users could report directly at its repository;

If you guys won't give a chance to my observations, you guys are the ones who loses, not me. I am the one who LIKES to report bugs and try (for free) make things be better.

@terremoth terremoth deleted the patch-1 branch March 9, 2021 23:09
@terremoth terremoth restored the patch-1 branch March 9, 2021 23:32
@terremoth terremoth deleted the patch-1 branch March 9, 2021 23:34
@aihua
Copy link

aihua commented Dec 18, 2023

Since the Severity of Bug #112440 is S3 (Non-critical), and it cannot be updated to S1 by MySQL Verification Team. So we reported it here. Can you fix it as macos 14(sonoma) is released?

@mysql-admin @mike-lischke @marcin1980 @mbodzek @akojima @rennox @gipulla @prashanttekriwal @nawazn @sreedhars @surbhat1595 @dhorecki @dhorecki @migueltadeu @kboortz @mtadeunet @bkandasa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants