Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#65215 - [mysql-workbench] Unix socket connection no longer works

Attached to Project: Community Packages
Opened by Brendan (esbdb) - Monday, 20 January 2020, 05:07 GMT
Last edited by Christian Hesse (eworm) - Monday, 28 June 2021, 07:04 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Since updating mysql-workbench recently, I can no longer use unix sockets to connect to a mysql instance.
It looks like the option to use unix sockets has broken completely.
When trying to open a connection that is setup to use a unix socket, mysql workbench gives an error that indicates that it didn't actually try use a unix socket,
but rather tried connecting to tcp 127.0.0.1:NULL. It also says 'wrong or unkown protocol'

Additional info:
* package version(s): 8.0.19-1
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
- Setup connection to a mysql server on a unix socket
- Attempt to connect using the unix socket
- fail connecting
This task depends upon

Closed by  Christian Hesse (eworm)
Monday, 28 June 2021, 07:04 GMT
Reason for closing:  Fixed
Additional comments about closing:  mysql-workbench 8.0.22-1
Comment by freswa (frederik) - Monday, 20 January 2020, 13:54 GMT
Does this issue also occur with package 8.0.18-2?
Comment by Brendan (esbdb) - Tuesday, 21 January 2020, 08:19 GMT
package 8.0.18-2 is working correctly
Comment by freswa (frederik) - Tuesday, 21 January 2020, 13:30 GMT
Ok, could you copy&paste the error message then?
Comment by Brendan (esbdb) - Wednesday, 22 January 2020, 06:19 GMT
You can't copy the text, I attached a screenshot
   2020-01-22-081915_573x303_scr... (35.1 KiB)
Comment by freswa (frederik) - Thursday, 23 January 2020, 22:21 GMT
I can't find any change that could've caused this. Can you do a bisect between d6dcc4254205a2a8aff01efd9aa9d1afd2711ee5 and af0e9b673fa534243e3f0f777913a905ed974c00 of the repo here? https://github.com/mysql/mysql-workbench
Comment by Brendan (esbdb) - Friday, 24 January 2020, 05:32 GMT
how do I run a development version without installing it? There seems to be no documentation in the repo.
Comment by freswa (frederik) - Friday, 24 January 2020, 19:56 GMT
Since it brings a lot of shared objects, I'd rather modify the PKGBUILD to build a certain commit like so:
source=("${pkgname}::git+https://github.com/mysql/mysql-workbench.git#commit=${commit}"

You can also use mysql-workbench-git and modify that PKGBUILD:
https://aur.archlinux.org/packages/mysql-workbench-git/
Comment by loqs (loqs) - Friday, 24 January 2020, 21:07 GMT
@frederik can you reproduce the issue?
Comment by freswa (frederik) - Friday, 24 January 2020, 21:58 GMT
Yes
Comment by loqs (loqs) - Saturday, 25 January 2020, 23:10 GMT
I can reproduce the issue. Building package from source I can still reproduce the issue.
Building the package with mysql-connector-c++-8.0.18-src.tar.gz the issue is not reproducible.
Comment by freswa (frederik) - Saturday, 25 January 2020, 23:29 GMT
Could you try jdbc submodule @3c74bb instead of cbbbae with the 8.0.19 mysql-connector-cpp code?
Comment by loqs (loqs) - Sunday, 26 January 2020, 01:28 GMT
e35adc4848d4a4813681fb878dcfa0844b5318e9 good
ea395db0879569937127ba892d0ed510e1af1389 good
804d267515282eebf81183ea17b5dad36f88382f bad
326c9cd897c5dba6335b52e2be5a6022489010b7 bad
9fe938a2633f887a14ff16f60d004e661c2db5b5 with jdbc 3c74bbbda5271fb2a80b03419f31e6ef934433e0 bad
9fe938a2633f887a14ff16f60d004e661c2db5b5 with jdbc 62e5f03cb75fc91965ec881f2301df3a3a73e6c1 good
next planned build 9fe938a2633f887a14ff16f60d004e661c2db5b5 with jdbc d9c32878b7be76048994a683be73327e2962ae05
Comment by Christian Hesse (eworm) - Sunday, 26 January 2020, 22:38 GMT
f234e4b814e406b147d98e5c236a23a41643fff0 is the first bad commit
https://github.com/mysql/mysql-connector-cpp/commit/f234e4b814e406b147d98e5c236a23a41643fff0
Comment by Christian Hesse (eworm) - Sunday, 26 January 2020, 23:00 GMT
https://bugs.mysql.com/bug.php?id=98406
Comment by Brendan (esbdb) - Tuesday, 12 May 2020, 11:07 GMT
can't believe a regression like this is staying broken for so long :/
Comment by loqs (loqs) - Monday, 28 June 2021, 05:13 GMT
Was this fixed by [1] which added in 8.0.22?

[1] https://github.com/mysql/mysql-connector-cpp/commit/3387369fc3ee09aa18fcff30666ca1a8903b8c72
Comment by Christian Hesse (eworm) - Monday, 28 June 2021, 07:03 GMT
Looks like, I can successfully connect via socket.
Thanks for keeping track!

Loading...