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

depends: disable unused Qt features #16386

Merged
merged 1 commit into from
Jul 25, 2019
Merged

Conversation

fanquake
Copy link
Member

Related to #16354. Kept separate from #16370, because:

QT is a monster 😂 - dongcarl in #bitcoin-builds

I've done some basic testing on macOS 10.14 and Debian 9.9 so far. Would be good to have someone test on Windows.

I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing some of2 in #16354.

@maflcko
Copy link
Member

maflcko commented Jul 14, 2019

kernel/qsharedmemory_win.cpp: In constructor ‘QSharedMemoryPrivate::QSharedMemoryPrivate()’:
kernel/qsharedmemory_win.cpp:52:12: error: class ‘QSharedMemoryPrivate’ does not have any field named ‘systemSemaphore’
            systemSemaphore(QString()), lockedByMe(false), hand(0)
            ^~~~~~~~~~~~~~~
kernel/qsharedmemory_win.cpp:52:40: error: class ‘QSharedMemoryPrivate’ does not have any field named ‘lockedByMe’
            systemSemaphore(QString()), lockedByMe(false), hand(0)
                                        ^~~~~~~~~~
Makefile.Release:32576: recipe for target '.obj/release/qsharedmemory_win.o' failed
make[3]: *** [.obj/release/qsharedmemory_win.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/home/travis/build/bitcoin/bitcoin/depends/work/build/x86_64-w64-mingw32/qt/5.9.7-346a555d033/qtbase/src/corelib'
Makefile:36: recipe for target 'release' failed

@promag
Copy link
Contributor

promag commented Jul 14, 2019

Concept ACK, +1 for the documentation or features reference.

@molxyz
Copy link

molxyz commented Jul 14, 2019

Compiling on Windows-10 WSL I also got the same errors and a lot of these warnings:

In file included from ../../include/QtCore/qdebug.h:1:0,
                 from kernel/qsharedmemory_win.cpp:43:
../../include/QtCore/../../src/corelib/io/qdebug.h: In member function ‘void QDebug::Stream::setVerbosity(int)’:
../../include/QtCore/../../src/corelib/io/qdebug.h:99:42: warning: result of ‘(7 << 29)’ requires 33 bits to represent, but ‘int’ only has 32 bits [-Wshift-overflow=]
                 flags &= ~(VerbosityMask << VerbosityShift);

@DrahtBot
Copy link
Contributor

Gitian builds for commit 536590f (master):

Gitian builds for commit e1332da (master and this pull):

@fanquake fanquake force-pushed the slim_qt_597 branch 2 times, most recently from d235a61 to ed04310 Compare July 15, 2019 05:57
$(package)_config_opts += -no-feature-bearermanagement
$(package)_config_opts += -no-feature-colordialog
$(package)_config_opts += -no-feature-commandlineparser
$(package)_config_opts += -no-feature-concurrent
Copy link
Member

@laanwj laanwj Jul 15, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was scared here for a bit, but turns out concurrent is for high-level thread handling, an API that is not used in our project, and it's not necessary for low-level multithreading that we use.

@laanwj
Copy link
Member

laanwj commented Jul 15, 2019

Concept ACK

1 similar comment
@hebasto
Copy link
Member

hebasto commented Jul 19, 2019

Concept ACK

@practicalswift
Copy link
Contributor

Concept ACK

Do you have numbers for before vs after?

@fanquake
Copy link
Member Author

Rebased for #16408.

@dongcarl
Copy link
Contributor

For reviewers, here's a gist with all the configure flags, features, and libraries: https://gist.github.com/dongcarl/f15946dff501dea85977b2c2fb9f00a0

Copy link
Member

@theuni theuni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Concept ACK

@@ -70,19 +71,35 @@ $(package)_config_opts += -system-zlib
$(package)_config_opts += -static
$(package)_config_opts += -silent
$(package)_config_opts += -v
$(package)_config_opts += -no-feature-bearermanagement
$(package)_config_opts += -no-feature-colordialog
$(package)_config_opts += -no-feature-commandlineparser
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this remove the ability to add qt-specific runtime args to bitcoin-qt ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It shouldn't do. We don't use any QCommandLineParser functionality, and it is actually another layer on top of any command line argument handling done by QCoreApplication.

I have tested passing through some qt specific options, such as -qwindowtitle and they still seem to work:

Hello World

$(package)_config_opts += -no-feature-printpreviewdialog
$(package)_config_opts += -no-feature-printpreviewwidget
$(package)_config_opts += -no-feature-regularexpression
$(package)_config_opts += -no-feature-sessionmanager
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned on IRC, I remember originally making this platform-specific for good reason. Maybe it's no longer needed, but let's make sure to understand what's changed.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've done some basic testing on macOS 10.14 and Windows 10 (built using WSL) and couldn't find obvious runtime issues. Although it might be good to get a Windows user to verify this: @sipsorcery, @NicolasDorier ?

I can't see us using or including QSessionManager anywhere, nor making any calls to QGuiApplication::commitDataRequest or QGuiApplication::saveStateRequest which are Qts two session management signals. My other thought was that it might be being used by QSettings, however config settings in the GUI (i.e coin control) seem to be saved and loaded correctly on the next start.

Looking at our qt package, -no-sm was originally added as a Linux only config option at the introduction of depends. It then became -no-feature-sessionmanager during the Qt 5.9.4 upgrade.

$(package)_config_opts += -no-feature-udpsocket
$(package)_config_opts += -no-feature-undocommand
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do these disable ctrl+z for, for example, input fields?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, using something like ctrl-z (⌘-z on macOS) still works as expected. My understanding is that QUndoCommands are used when you build a QUndoStack, for example when editing a document. We don't use QUndoStacks or Commands at all.

@@ -35,6 +35,7 @@ $(package)_config_opts += -no-freetype
$(package)_config_opts += -no-gif
$(package)_config_opts += -no-glib
$(package)_config_opts += -no-icu
$(package)_config_opts += -no-ico
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For reviewers: We have .ico files in-tree, but they're processed at build-time by windres.

@fanquake
Copy link
Member Author

Updated to also disable the VNC QPA backend using:

$(package)_config_opts += -no-feature-vnc

which we have been building on Linux:

QPA backends:
  DirectFB ............................... no
  EGLFS .................................. no
  LinuxFB ................................ no
  VNC .................................... yes
  Mir client ............................. no

-no-feature-vnc doesn't appear if you pass -list-features to Qts ./configure, but you can check that it's being disabled by checking the config summary during a depends build.

@sipsorcery
Copy link
Contributor

tACK 248e22b (Windows 10 test only)

Didn't notice any discrepancies when running bitcoin-qt.exe built with this PR.

@laanwj
Copy link
Member

laanwj commented Jul 25, 2019

Qt has a VNC backend ?!? that's wicked cool, but yes, not useful for this project, the last thing you'd want is a wallet listening on a VNC port

ACK 248e22b

@laanwj laanwj merged commit 248e22b into bitcoin:master Jul 25, 2019
laanwj added a commit that referenced this pull request Jul 25, 2019
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to #16354. Kept separate from #16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in #16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
@bitcoin bitcoin deleted a comment from DrahtBot Jul 25, 2019
@DrahtBot
Copy link
Contributor

Needs rebase

@DrahtBot
Copy link
Contributor

Needs rebase

@molxyz
Copy link

molxyz commented Jul 26, 2019

I've got the Qt been running on Windows 10 but I'm not sure what we're disabling and what I should check in testing?

Btw while we're at this, could we get rid of the Main Window on the GUI that has no purpose for Windows Qt which was supposed to be changed since last version?

image

@sipa
Copy link
Member

sipa commented Jul 26, 2019

@molxyz There shouldn't be any observable differences from this PR. It's disabling things we aren't using anyway.

@molxyz
Copy link

molxyz commented Jul 26, 2019

@sipa Ah.. Ok, thanks for letting me know. So far I haven't seen any issue but will keep running the master.

konez2k pushed a commit to bitcoin-green/bitcoingreen that referenced this pull request Jul 27, 2019
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
@fanquake fanquake deleted the slim_qt_597 branch January 22, 2020 11:29
deadalnix pushed a commit to Bitcoin-ABC/bitcoin-abc that referenced this pull request Apr 2, 2020
Summary:
Backport of core [[bitcoin/bitcoin#16386 | PR16386]].

Depends on D5636.

Test Plan: Run the Gitian builds.

Reviewers: #bitcoin_abc, deadalnix

Reviewed By: #bitcoin_abc, deadalnix

Differential Revision: https://reviews.bitcoinabc.org/D5638
$(package)_config_opts += -no-feature-dial
$(package)_config_opts += -no-feature-filesystemwatcher
Copy link
Member

@hebasto hebasto Jul 16, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change causes bitcoin-core/gui#32, and it is fixed in #19536.

fanquake added a commit that referenced this pull request Jul 17, 2020
6457361 qt: Fix QFileDialog for static builds (Hennadii Stepanov)

Pull request description:

  This change partially reverts 248e22b (#16386) and makes `QFileDialog`s work again for static builds.

  Fixes bitcoin-core/gui#32.

ACKs for top commit:
  fanquake:
    ACK 6457361. Although it would be good to know exactly _why_ this fixes the issue. At this stage I also don't think this should be a blocker for 0.20.1.
  theuni:
    ACK 6457361

Tree-SHA512: 8ad27e0bcae6debd02f73b7c374743e37d4edd806922b103a2fe494cf2d9930fe9ef3107b5a6c61f3c466cf7462de2641171880398954e7f2c4f417f5bb820d7
PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this pull request Sep 11, 2021
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this pull request Sep 11, 2021
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
Munkybooty pushed a commit to Munkybooty/dash that referenced this pull request Nov 9, 2021
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
Munkybooty pushed a commit to Munkybooty/dash that referenced this pull request Nov 16, 2021
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
Munkybooty pushed a commit to Munkybooty/dash that referenced this pull request Nov 18, 2021
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
Munkybooty pushed a commit to Munkybooty/dash that referenced this pull request Nov 24, 2021
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
Munkybooty pushed a commit to Munkybooty/dash that referenced this pull request Nov 30, 2021
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
Munkybooty pushed a commit to Munkybooty/dash that referenced this pull request Dec 15, 2021
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
Munkybooty pushed a commit to Munkybooty/dash that referenced this pull request Dec 17, 2021
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
Munkybooty pushed a commit to Munkybooty/dash that referenced this pull request Dec 24, 2021
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
Munkybooty pushed a commit to Munkybooty/dash that referenced this pull request Jan 19, 2022
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
Munkybooty pushed a commit to Munkybooty/dash that referenced this pull request Jan 24, 2022
248e22b depends: disable unused Qt features (fanquake)

Pull request description:

  Related to bitcoin#16354. Kept separate from bitcoin#16370, because:

  > QT is a monster 😂 - dongcarl in #bitcoin-builds

  I've done some basic testing on `macOS 10.14` and `Debian 9.9` so far. Would be good to have someone test on Windows.

  I was thinking about adding some inline documentation, i.e info about where to find the lists of Qt features & libraries, as well as breaking the flags up so that it's clearer which libraries we are supplying, which we rely on Qt for etc. Could go towards addressing  some of`2` in bitcoin#16354.

ACKs for top commit:
  sipsorcery:
    tACK 248e22b (Windows 10 test only)
  laanwj:
    ACK 248e22b

Tree-SHA512: 2cdcea8d268de21d355a7625c4d352f65728df0b8d8cc0f396aca676f42099a819f95652dfbfc665c991ba12c52735c1e9b693df4b12e3ee178fd39356fba8e0
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Feb 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.