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

Backports for v4_5_x part 2 #18452

Merged
merged 21 commits into from
Feb 11, 2023

Conversation

sledgehammer999
Copy link
Member

@sledgehammer999 sledgehammer999 commented Jan 24, 2023

These will be merged (and rebased) after #18271.

Here is the list of the backported PRs for quick reference:
PR #18086
PR #18104
PR #18110
PR #18154
PR #18199
PR #18200
PR #18218
PR #18227
PR #18236
PR #18240
PR #18279
PR #18326
PR #18285
PR #18434
PR #18432
PR #18456
PR #18466

@sledgehammer999 sledgehammer999 added this to the 4.5.1 milestone Jan 24, 2023
@sledgehammer999
Copy link
Member Author

After this I want to make the next release.

@glassez was not backporting #18227 #18218 deliberate?

Also how about #18110?

@glassez
Copy link
Member

glassez commented Jan 25, 2023

@glassez was not backporting #18227 #18218 deliberate?

They didn't look like bugfixes. However, I don't mind them, since they don't affect anything around.

Also how about #18110?

For me it fixes a "visual" bug. So if you want to backport it I don't mind.

@xavier2k6
Copy link
Member

After this I want to make the next release.

Please take my #18339 (comment) in to consideration/review.

@glassez
Copy link
Member

glassez commented Jan 25, 2023

Please take my #18339 (comment) in to consideration/review.

If you're hinting that @sledgehammer999 should have upgraded to MSVC 2022, then I'm in favor.
@sledgehammer999, it would also be nice to check the build for the ability to produce a valid stack trace. For example, you can inject some bug that obviously leads to a crash (division by zero, or something else), and check how it behaves, and only then rebuild it without that bug for release.

@xavier2k6
Copy link
Member

xavier2k6 commented Jan 25, 2023

If you're hinting that @sledgehammer999 should have upgraded to MSVC 2022, then I'm in favor.

Yes

it would also be nice to check the build for the ability to produce a valid stack trace. For example, you can inject some bug that obviously leads to a crash (division by zero, or something else), and check how it behaves, and only then rebuild it without that bug for release.

Windows 10 21H2+ & Windows 11 seems to be the big issue currently.

It's easily reproducible via Qt 6 with the "when trying to paste using an empty clipboard" scenario from #18317 which is now fixed from upstream in upcoming Qt 6.4.3 ETA: 28.02.2023

(Have observed no issues either with Qt 6.4.2)

If you don't have a Windows 11 system available to you, I will test the release binaries for you if you want.
Have a system with Windows 11 22H2 Build 22621.


BTW (UPDATED tools are also available):
nasm 2.16.01
Ninja 1.11.1
NSIS 3.08

@sledgehammer999
Copy link
Member Author

The Qt6 builds are using msvc2022 starting from v4.4.3.
I can reproduce the issue @xavier2k6 is mentioning but inserting a deliberate crash. Running the app from inside WinDbg I can get a meaningful stacktrace. This at least denotes that the *.pdb file isn't corrupted.
I doubt that this has something to do with the SDK version used. My hunch is that this is a misconfiguration of Boost.Stacktrace. I am doing tests now to see if I can fix it.
Reminder: Our stacktrace functionality changed backends in v4.5.0.

@sledgehammer999
Copy link
Member Author

@xavier2k6 do you do the builds yourself? Are you able to test with builds fully statically linked?

@glassez

This comment was marked as off-topic.

@sledgehammer999

This comment was marked as off-topic.

@glassez

This comment was marked as off-topic.

@glassez

This comment was marked as off-topic.

@sledgehammer999
Copy link
Member Author

Let's continue in #18456

@Pentaphon
Copy link

For me it fixes a "visual" bug. So if you want to backport it I don't mind.

Please do.

sledgehammer999 and others added 11 commits January 27, 2023 18:01
I also fixed it on Transifex.
Leftover from the system tray code refactoring.
Upload an AppImage artifact on CI builds. This AppImage is a
simplified version of the official one. It is meant to help
with debugging PRs that fix issues.
Don't want torrent search history to pop up next time you try to search for torrents, right?
There are people who would search for 18+ content and what they searched would load up next time they are about to search.

PR qbittorrent#18285.
@sledgehammer999
Copy link
Member Author

I backported: #18110 #18218 #18227 #18456

@sledgehammer999 sledgehammer999 marked this pull request as ready for review January 28, 2023 15:03
@sledgehammer999
Copy link
Member Author

Also backported PR #18466.
@glassez can you approve? (I won't merge immediately)

@Pentaphon
Copy link

Pentaphon commented Feb 10, 2023

Is 4.5.x going to be a short run of fixes in favor of 4.6.0? I thought 4.5.1 was due a month ago?

@xavier2k6
Copy link
Member

Is 4.5.x going to be a short run of fixes in favor of 4.6.0?

More than likely yes for the near future anyway, qBittorrent 4.5.2 will possibly include a Qt upstream fix for a certain type of crash soon after Qt releases it at end of February & it's confirmed by team members that it indeed fixes reported upstream issue.

I thought 4.5.1 was due a month ago?

We don't give any guaranteed deadlines & it's best not to take anyone's comments etc. out of context as a fact.

@glassez

This comment was marked as off-topic.

@sledgehammer999 sledgehammer999 merged commit 0a8d604 into qbittorrent:v4_5_x Feb 11, 2023
@sledgehammer999 sledgehammer999 deleted the stage_v4_5_x branch February 11, 2023 22:54
@xavier2k6
Copy link
Member

@xavier2k6 do you do the builds yourself?

I've build previously mostly following the wiki guide, but lately for testing purposes etc - I use GHA CI provided builds.

Are you able to test with builds fully statically linked?

Yes, following the wiki guide etc.

@xavier2k6

This comment was marked as off-topic.

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

Successfully merging this pull request may close these issues.