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

fix signal for socket error #519

Merged
merged 1 commit into from
Sep 10, 2024
Merged

Conversation

vifactor
Copy link
Contributor

@vifactor vifactor commented Aug 8, 2024

The QAbstractSocket::error signal existed in Qt<5.15, but was renamed to QAbstractSocket::errorOccured probably to avoid
https://stackoverflow.com/a/48250710

Since the codebase still uses the old style of connections the compiler could not detect that signal does not exist anymore and error was reported only on runtime:
"qt.core.qobject.connect: QObject::connect:
No such signal QTcpSocket::error(QAbstractSocket::SocketError)"

@alexmucde
Copy link
Collaborator

Need to be tested before integration. Do you have tested this?

@alexmucde alexmucde added the bug label Aug 14, 2024
@alexmucde alexmucde added this to the Release v2.27.0 milestone Aug 14, 2024
@vifactor
Copy link
Contributor Author

vifactor commented Aug 14, 2024 via email

@vifactor vifactor force-pushed the fix-signal-name branch 2 times, most recently from 82190ea to 6bbe9f5 Compare September 5, 2024 08:46
@alexmucde alexmucde self-assigned this Sep 9, 2024
@alexmucde alexmucde self-requested a review September 9, 2024 12:57
@alexmucde
Copy link
Collaborator

@vifactor Please add your signed off statement to the commit message.

@alexmucde alexmucde assigned vifactor and unassigned alexmucde Sep 9, 2024
The QAbstractSocket::error signal existed in Qt<5.15, but was renamed to
QAbstractSocket::errorOccured probably to avoid
https://stackoverflow.com/a/48250710

Since the codebase still uses the old style of connections
the compiler could not detect that signal does not exist anymore
and error was reported only on runtime:
"qt.core.qobject.connect: QObject::connect:
No such signal QTcpSocket::error(QAbstractSocket::SocketError)"

Signed-off-by: Viktor Kopp <vifactor@gmail.com>
@vifactor
Copy link
Contributor Author

vifactor commented Sep 9, 2024

sorry, done!

@alexmucde alexmucde merged commit 0ba5dcd into COVESA:master Sep 10, 2024
4 checks passed
@alexmucde
Copy link
Collaborator

Causes now build issues with Ubuntu 20.04, still uses Qt 5.12.8. Still a lot of users using Ubuntu 20.04 on our side, maybe revert and new PR for later integration?

@vifactor
Copy link
Contributor Author

Ok, I see, I'll did not know 5.12 is still in use. I'll prepare a PR handling properly different Qt versions.

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

Successfully merging this pull request may close these issues.

2 participants