Update jasmine gem

What
Update Jasmine gem from 2.4 to 3.4 (major) and precompile missing assets
Bring other dependencies to date (minors)
Why
To keep project's dependencies up to date and be able to dockerize govuk_publishing_components
Visual Changes
No visual changes.
Note
A few tests are failing, will try and fix them now.
Update
After a bunch of hours spent to understand our tests I've found the main causes of the flaky tests, so briefly the updates are:

clear sessionStorage after each test dee29ef3000d7093b5a5ab6c5323e52d33014b63, otherwise step-by-step tests interfere
reset cookies after each test  2450e9a otherwise cookie functions tests interfere with the cookie banner tests
clone DEFAULT_COOKIE_CONSENT otherwise we operate on the same object affecting its default values 9d3bda3a4f8496ad1f56a5d156bc4dea611c1971 which results in interferences

Since it took me that long, I ended up linting the test files as I was looking at a lot of red-flagged code.
Trello card

Thanks @vanitabarrett. I'm going to merge this as I'm confident in changes and want to avoid doing a lot of rebase work. Hope this will unblock govuk_publishing_components from being dockerized @benthorner.

Almost @alex-ju ! Just one more thing: https://github.com/alphagov/govuk_publishing_components/pull/973.

@alex-ju having done all the hard work on this, would you like to update https://github.com/alphagov/govuk-docker#compatibility?

(I can confirm it now works.)


Data grouping re-render on data update

Currently, groupBy is only checked in ngOnInit. Hence if new options are subsequently added, they will not be grouped and will not even show up in the dropdown. Hence, groupBy should be checked subsequently to account for new data.

The specific use case I had was dynamically pushing new options to data in a for-loop.

Also ran into this issue today myself. Any possibility of a fix soon?

fixed. available in v2.0.0


Ignore all comits when .gitleaksignore fingerprint lacks SHA

Description:
This fixes #1155.
Checklist:

[x] Does your PR pass tests?
[x] Have you written new tests for your changes?
[x] Have you lint your code locally prior to submission?

Hi, Is it possible to merge this soon?
Thanks,

It would be great to see this in, is there anything else it needs?  With a large distributed dev team, a merge rather than rebase PR strategy, and a diverse technology set we generally have issues with multiple exceptions being required each time a change is merged to another branch due to the additional merge commit hashes.  I believe that this would make it much easier to ignore once where we cannot use a regex exclusion flag.


feat: Adds flake

This adds a flake.nix and associated files for a dev environment via nix and steps for building all the parts of wadm in an incremental way. Part of this was an experiment to see what we could get nix to do with monorepo deps in the simple case. Please note that this does not actually add this as part of the build pipeline, just adds the file the repo for people to use. Maybe in the future we can add in builds and caching into our pipelines.

Special thanks to @rvolosatovs for helping me figure out the cargo.toml munging


Foreign keys and table restore order

I'm porting the library to use with SQLite and noticed possible issue with foreign keys that make the table create order important. In MySQL foreign keys are created within table create statement. If the table referenced by a foreign key is not already in place, it would cause an exception. Same issue as with views/ methods dependencies.
Not sure, whether that should be handled by backup or restore.
Also capability to export/import only some tables creates dependency nightmare.

Can you try the following
SET FOREIGN_KEY_CHECKS=0;
INSERT.......
INSERT .......
INSERT.......
INSERT.......
SET FOREIGN_KEY_CHECKS=1;

and if this solved your problem?
If yes I will include a new option for temporary disabling the foreign key checking while restoring the database.

Nope. The problem is CREATE TABLE order. You cannot create a table that references not yet existent table.
The same is with dependent routines.
I solved the problem for sqlite by recursive table dependences analysis. TableCreate method first invokes the same method on the referenced tables. The solution still makes impossible to backup databases with circular references, but I don't think that would be a frequent case. At least it's not important for me. However the mysql is harder due to the routines. Not sure how to extract calls to dependent routines.

Can you provide 5 CREATE TABLE queries that have dependent foreign key on each other which will generate the error that you've mentioned. I will use that as sample data for solving this problem. Thanks.

Try to create table icons before table companies and you will get the error.
CREATE TABLE DoomyDatabaseName.companies(id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY, name CHAR(255) NOT NULL, registrationcode CHAR(50) NOT NULL, address CHAR(255) NOT NULL, phone CHAR(20) NOT NULL, email CHAR(255) NOT NULL, website CHAR(255) NOT NULL, dponame CHAR(255) NOT NULL, dpophone CHAR(20) NOT NULL, dpoemail CHAR(255) NOT NULL, contactpersonposition CHAR(255) NOT NULL, recordsofprocessingarepublic TINYINT UNSIGNED NOT NULL, insertedat DATETIME NOT NULL, insertedby CHAR(255) NOT NULL, updatedat DATETIME NOT NULL, updatedby CHAR(255) NOT NULL) ENGINE=InnoDB  DEFAULT CHARSET=utf8;
CREATE TABLE DoomyDatabaseName.icons(id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY, companyid INT UNSIGNED, iconbytes BLOB NOT NULL, KEY icons_companyid_index (companyid), CONSTRAINT icons_companyid_index FOREIGN KEY icons_companyid_index(companyid) REFERENCES companies(id) ON DELETE CASCADE ON UPDATE CASCADE) ENGINE=InnoDB  DEFAULT CHARSET=utf8;
From: Adrian Voo
Sent: Tuesday, March 05, 2019 3:56 AM
To: MySqlBackupNET/MySqlBackup.Net
Cc: Apskaita5 ; Author
Subject: Re: [MySqlBackupNET/MySqlBackup.Net] Foreign keys and table restore order (#31)
Can you provide 5 CREATE TABLE queries that have dependent foreign key on each other which will generate the error that you've mentioned. I will use that as sample data for solving this problem. Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I am able to identify any tables that have foreign keys references by executing the following SQL:
select table_name, referenced_table_name
from information_schema.key_column_usage
where constraint_schema='DoomyDatabaseName' and referenced_table_name IS NOT NULL;

with this, I can rearrange the CREATE TABLE in a specific order that will avoid the foreign key dependency error.

That will not work in hosting environment with limited priviledges.
Get BlueMail for Android
On 8 Mar 2019, 14:49, at 14:49, Adrian Voo<EMAIL_ADDRESS>wrote:

I am able to identify any tables that have foreign keys references by
executing the following SQL:
select table_name, referenced_table_name
from information_schema.key_column_usage
where constraint_schema='DoomyDatabaseName' and referenced_table_name
IS NOT NULL;

with this, I can rearrange the CREATE TABLE in a specific order that
will avoid the foreign key dependency error.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/MySqlBackupNET/MySqlBackup.Net/issues/31#issuecomment-470917335

According to MySQL documentation,
https://dev.mysql.com/doc/refman/8.0/en/information-schema-introduction.html
At the section: INFORMATION_SCHEMA and Privileges

Each MySQL user has the right to access these tables, but can see only the rows in the tables that correspond to objects for which the user has the proper access privileges. In some cases (for example, the ROUTINE_DEFINITION column in the INFORMATION_SCHEMA ROUTINES table), users who have insufficient privileges see NULL. These restrictions do not apply for InnoDB tables; you can see them with only the PROCESS privilege.
The same privileges apply to selecting information from INFORMATION_SCHEMA and viewing the same information through SHOW statements. In either case, you must have some privilege on an object to see information about it.

If a user has the privilege to "SELECT" data from a table, i.e. TABLE-A, then this user can get the information about "TABLE-A" at INFORMATION_SCHEMA.

Ok.
On 8 Mar 2019, 17:01, at 17:01, Adrian Voo<EMAIL_ADDRESS>wrote:

According to MySQL documentation,
https://dev.mysql.com/doc/refman/8.0/en/information-schema-introduction.html
At the section: INFORMATION_SCHEMA and Privileges

Each MySQL user has the right to access these tables, but can see
only the rows in the tables that correspond to objects for which the
user has the proper access privileges. In some cases (for example, the
ROUTINE_DEFINITION column in the INFORMATION_SCHEMA ROUTINES table),
users who have insufficient privileges see NULL. These restrictions do
not apply for InnoDB tables; you can see them with only the PROCESS
privilege.
The same privileges apply to selecting information from
INFORMATION_SCHEMA and viewing the same information through SHOW
statements. In either case, you must have some privilege on an object
to see information about it.

If a user has the privilege to "SELECT" data from a table, i.e.
TABLE-A, then this user can get the information about "TABLE-A" at
INFORMATION_SCHEMA.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/MySqlBackupNET/MySqlBackup.Net/issues/31#issuecomment-470957922

Hi, you may test the following build which I have already patched the code for solving the foreign key dependency "CREATE TABLE" order. You may provide feedback after testing this build
MySqlBackup.NET_Debug_Issue_31_v1.zip

A new release is published. version 2.2
you may download and have a try

Hi, a new version (v2.3) is released, where this problem is resolved. You may try it out.


Add import script for COVID-19 URLs for vulnerable people

We have been crowdsourcing URLs for council-provided Community Response
Hubs on TheyHelpYou. We've been collecting and verifying
these URLs on a publicly open Google Sheet. Updates to this
sheet are automatically added to our database within 15 minutes. We get
alerted to every change and manually check it for validity.
In theory, there are three different needs that councils should be
meeting:

Shielding extremely vulnerable people
Supporting non-shielded vulnerable people
Helping the public volunteer safely to meet the other two needs

We've found that councils at the second tier are meeting these needs, at
least in England. This means that they're being met by:

Counties (eg Surrey)
Unitary authorities (eg Milton Keynes)
Districts/boroughs (eg Manchester or Croydon)

In practice, a lot of councils currently have all three needs on the
same URL, certainly the first 2. Some of them have split volunteering
information into different pages or even sites.
We've exposed the URLs we have on a new API endpoint suitable for use
with this import script:
GET https://www.theyhelpyou.co.uk/api/export-local-links-manager?type=shielding&nation=E

The API returns a JSON object mapping GSS codes to URLs, for example:
{
    "E06000047": "https://www.durham.gov.uk/covid19help",
    "W06000009": "https://www.pembrokeshire.gov.uk/coronavirus-covid-19-community-information/i-need-some-help",
    "E08000019": "https://www.sheffield.gov.uk/home/your-city-council/coronavirus-support-for-people",
    ...
}

The type parameter must be one of shielding, vulnerable or
volunteering. If we don't have a specific URL for a council for the
requested type, the API will not return any data and that GSS code
won't be included in the response.
The nation parameter is optional to allow for filtering by Nation. If
provided, it must be one of E, N, S, or W.
The import script in this PR accesses this endpoint directly and fetches
data for each type, then creates Links for the relevant
ServiceInteraction and LocalAuthority.
For demonstration purposes, we've picked some LGSL and LGIL codes.
We've used LGSL code 1287 (Current emergency situations -
health) for shielded and vulnerable links, as it's intended for "an
ongoing emergency related to public health such as a flu outbreak". For
shielding we're using LGIL code 8, "Find information" as generally this
is informational and councils will engage with residents directly. For
help for non-shielded vulnerable people we've used LGIL code 6,
"Providing access to community, professionals or business networks" as
this is about requesting support.
We've used LGSL code 1113 (Provision of information on
volunteering opportunities available in the community) and LGIL code 8
for volunteering URLs. This combination isn't currently supported on
GOV.UK, and Local Links Manager only has two links, neither of which are
relevant.
It may be better to create new emergency codes for this or to re-use
others, in which case they're easy to change in a constant hash near the
top of the rake task.
As far as I'm aware, all that would be needed to get this data
accessible via GOV.UK would be to create Local Transactions in
Publisher for these LGSL and LGIL codes, then run this import script.
The "tiering" in Publisher's Local Services CSV would also
need updating to show that the LGSL codes chosen are provided by all
tiers, followed by running the import:add_service_tiers rake task.
I've not written an Import class for this like in
LocalAuthoritiesImporter because I hope this is more of a one-off
disposable task. Converting it to that format should be relatively
straight-forward if that is preferred.

cc @sihugh

Thanks very much, @boffbowsh!
Funnily enough @huwd, @StephenGill and I were just talking about doing something with your spreadsheet, and potentially even linking to TheyHelpYou from the coronavirus page as a resource for people.
As for this PR, I have pushed the branch so that Jenkins runs. I don't have enough :brain: to review the code today, but hopefully someone will get to this soon!

Great stuff, hopefully it's useful. While we're happy to host TheyHelpYou for a while, it's not as sustainable and doesn't have the clout of GOV.UK. I figured if the data were in LLM you'd have broken link checking and more ability for councils to keep it up to date themselves.
Looks like the build failed, probably rubocop. I think I've fixed it :grimacing:

@boffbowsh would it cause you problems if we added some links from GOV.UK to TheyHelpYou, hopefully as a short term measure?
eg from the confirmation page for www.gov.uk/coronavirus-extremely-vulnerable, which currently says:
It may take time for you to get support. If you have urgent care or support needs then contact your local authority.

That should be fine, it's all on AWS and hopefully pretty scalable. Let me know if any when you do that so I can monitor.

What's the rough volume of visits to that Done page?

Sorry, no GA on that page at the moment (it's the service confirmation page rather than the GOV.UK 'done' page).
@richardTowers may have an idea of how much traffic it's getting.

About 300,000 people last week, so ~43k requests / day.

FYI GOV.UK Platform Health team are looking at creating the new service(s) in LLM

Do you mean the best team? 😍

FYI GOV.UK Platform Health team are looking at creating the new service(s) in LLM

Do you know when this might be done, @nicholsj? We'd like to link to Paul's site as a short-term measure...

This has been merged via #629.


'Error: Not snapshotted yet' when aliasing a deployment to an external domain

The external domain currently points to an existing now deployment. However, I get the following error when attempting to alias a new deployment to the external domain. now --version is 8.5.4.
> Scaling deployment to match current scale.
> [debug] #1 POST /deployments/H2ozyadVlC41BmJV2NyGwrIo/instances: 481.726ms
> [debug] Retrying: Error: Not snapshotted yet.
Error: Not snapshotted yet.
    at module.exports.EventEmitter.setScale.scale.retry (/snapshot/now-cli/dist/now.js:1074:19)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
> [debug] #2 POST /deployments/H2ozyadVlC41BmJV2NyGwrIo/instances: 592.420ms
> [debug] Retrying: Error: Not snapshotted yet.
Error: Not snapshotted yet.
    at module.exports.EventEmitter.setScale.scale.retry (/snapshot/now-cli/dist/now.js:1074:19)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
> [debug] #3 POST /deployments/H2ozyadVlC41BmJV2NyGwrIo/instances: 633.948ms
> [debug] Retrying: Error: Not snapshotted yet.
Error: Not snapshotted yet.
    at module.exports.EventEmitter.setScale.scale.retry (/snapshot/now-cli/dist/now.js:1074:19)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
> [debug] #4 POST /deployments/H2ozyadVlC41BmJV2NyGwrIo/instances: 543.843ms
> [debug] Retrying: Error: Not snapshotted yet.
Error: Not snapshotted yet.
    at module.exports.EventEmitter.setScale.scale.retry (/snapshot/now-cli/dist/now.js:1074:19)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

seeing this trying to scale an instance, too....


[gmp] Build error - 'fat' does not build on Windows x64

This might be a bug in GMP itself, I cannot tell.  The reason for building gmp[fat] for me is that the plain build crashes with 'illegal instruction' on older CPUs without certain instruction sets.
Package: gmp[core,fat]:x64-windows -> 6.2.1#14
Host Environment

Host: x64-windows
Compiler: MSVC 19.29.30147.0
vcpkg-tool version: 2022-11-10-5fdee72bc1fceca198fb1ab7589837206a8b81ba
vcpkg-scripts version: 34d2cf7e6 2022-11-21 (16 hours ago)

To Reproduce
vcpkg install gmp[fat]
Failure logs
-- Using cached gmp-6.2.1.tar.xz.
-- Using cached gmp-arm64-asm-fix-5f32dbc41afc.patch.
-- Cleaning sources at C:/BUILD/vcpkg/buildtrees/gmp/src/v6.2.1-0c723d4b6f.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/BUILD/vcpkg/downloads/gmp-6.2.1.tar.xz
-- Applying patch asmflags.patch
-- Applying patch cross-tools.patch
-- Applying patch subdirs.patch
-- Applying patch msvc_symbol.patch
-- Applying patch arm64-coff.patch
-- Applying patch C:/BUILD/vcpkg/downloads/gmp-arm64-asm-fix-5f32dbc41afc.patch
-- Using source at C:/BUILD/vcpkg/buildtrees/gmp/src/v6.2.1-0c723d4b6f.clean
-- Found external ninja('1.10.2').
-- Getting CMake variables for x64-windows
-- Getting CMake variables for x64-windows
-- Using cached msys-gzip-1.11-1-x86_64.pkg.tar.zst.
-- Using cached msys-bash-5.1.008-1-x86_64.pkg.tar.zst.
-- Using cached msys-autoconf-2.71-3-any.pkg.tar.zst.
-- Using cached msys-diffutils-3.8-2-x86_64.pkg.tar.zst.
-- Using cached msys-binutils-2.37-5-x86_64.pkg.tar.zst.
-- Using cached msys-libtool-2.4.6-9-x86_64.pkg.tar.xz.
-- Using cached msys-file-5.41-2-x86_64.pkg.tar.zst.
-- Using cached msys-zlib-1.2.11-1-x86_64.pkg.tar.xz.
-- Using cached msys-libbz2-1.0.8-3-x86_64.pkg.tar.zst.
-- Using cached msys-coreutils-8.32-2-x86_64.pkg.tar.zst.
-- Using cached msys-grep-3.0-2-x86_64.pkg.tar.xz.
-- Using cached msys-sed-4.8-2-x86_64.pkg.tar.zst.
-- Using cached msys-libpcre-8.45-1-x86_64.pkg.tar.zst.
-- Using cached msys-m4-1.4.19-2-x86_64.pkg.tar.zst.
-- Using cached msys-automake-wrapper-11-4-any.pkg.tar.zst.
-- Using cached msys-gawk-5.1.0-2-x86_64.pkg.tar.zst.
-- Using cached msys-mpfr-4.1.0-1-x86_64.pkg.tar.zst.
-- Using cached msys-gmp-6.2.1-1-x86_64.pkg.tar.zst.
-- Using cached msys-libreadline-8.1.001-1-x86_64.pkg.tar.zst.
-- Using cached msys-ncurses-6.2-2-x86_64.pkg.tar.zst.
-- Using cached msys-automake1.16-1.16.3-3-any.pkg.tar.zst.
-- Using cached msys-perl-5.32.1-2-x86_64.pkg.tar.zst.
-- Using cached msys-libcrypt-2.1-3-x86_64.pkg.tar.zst.
-- Using cached msys-pkg-config-0.29.2-4-x86_64.pkg.tar.zst.
-- Using cached msys-make-4.3-3-x86_64.pkg.tar.zst.
-- Using cached msys-findutils-4.8.0-1-x86_64.pkg.tar.zst.
-- Using cached msys-libintl-0.21-1-x86_64.pkg.tar.zst.
-- Using cached msys-libiconv-1.16-2-x86_64.pkg.tar.zst.
-- Using cached msys-gcc-libs-11.2.0-3-x86_64.pkg.tar.zst.
-- Using cached msys-msys2-runtime-3.2.0-8-x86_64.pkg.tar.zst.
-- Using cached msys-which-2.21-4-x86_64.pkg.tar.zst.
-- Using msys root at C:/BUILD/vcpkg/downloads/tools/msys2/583ad6e4115a307a
-- Generating configure for x64-windows
-- Finished generating configure for x64-windows
-- Using cached msys-mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst.
-- Using msys root at C:/BUILD/vcpkg/downloads/tools/msys2/9a1ec3f33446b195
-- Configuring x64-windows-dbg
-- Configuring x64-windows-rel
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:131 (message):
    Command failed: C:/BUILD/vcpkg/downloads/tools/msys2/583ad6e4115a307a/usr/bin/make.exe -j 25 --trace -f Makefile all
    Working Directory: C:/BUILD/vcpkg/buildtrees/gmp/x64-windows-dbg/
    See logs for more information:
      C:\BUILD\vcpkg\buildtrees\gmp\build-x64-windows-dbg-out.log
      C:\BUILD\vcpkg\buildtrees\gmp\build-x64-windows-dbg-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_build_make.cmake:149 (vcpkg_execute_build_process)
  scripts/cmake/vcpkg_install_make.cmake:2 (vcpkg_build_make)
  ports/gmp/portfile.cmake:92 (vcpkg_install_make)
  scripts/ports.cmake:147 (include)

C:\BUILD\vcpkg\buildtrees\gmp\build-x64-windows-dbg-out.log
Makefile:1470: update target 'gen-fac.exe' due to: ./../src/v6.2.1-0c723d4b6f.clean/gen-fac.c ./../src/v6.2.1-0c723d4b6f.clean/bootstrap.c
compile cl.exe -DWIN32 -D_WINDOWS -D_DEBUG -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -Od -Xcompiler -RTC1 `test -f 'gen-fac.c' || echo './../src/v6.2.1-0c723d4b6f.clean/'`gen-fac.c -o gen-fac.exe
Makefile:1479: update target 'gen-fib.exe' due to: ./../src/v6.2.1-0c723d4b6f.clean/gen-fib.c ./../src/v6.2.1-0c723d4b6f.clean/bootstrap.c
compile cl.exe -DWIN32 -D_WINDOWS -D_DEBUG -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -Od -Xcompiler -RTC1 `test -f 'gen-fib.c' || echo './../src/v6.2.1-0c723d4b6f.clean/'`gen-fib.c -o gen-fib.exe
Makefile:1488: update target 'gen-bases.exe' due to: ./../src/v6.2.1-0c723d4b6f.clean/gen-bases.c ./../src/v6.2.1-0c723d4b6f.clean/bootstrap.c
compile cl.exe -DWIN32 -D_WINDOWS -D_DEBUG -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -Od -Xcompiler -RTC1 `test -f 'gen-bases.c' || echo './../src/v6.2.1-0c723d4b6f.clean/'`gen-bases.c -o gen-bases.exe
Makefile:1494: update target 'gen-trialdivtab.exe' due to: ./../src/v6.2.1-0c723d4b6f.clean/gen-trialdivtab.c ./../src/v6.2.1-0c723d4b6f.clean/bootstrap.c
compile cl.exe -DWIN32 -D_WINDOWS -D_DEBUG -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -Od -Xcompiler -RTC1 `test -f 'gen-trialdivtab.c' || echo './../src/v6.2.1-0c723d4b6f.clean/'`gen-trialdivtab.c -o gen-trialdivtab.exe
Makefile:1500: update target 'gen-jacobitab.exe' due to: ./../src/v6.2.1-0c723d4b6f.clean/gen-jacobitab.c
compile cl.exe -DWIN32 -D_WINDOWS -D_DEBUG -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -Od -Xcompiler -RTC1 `test -f 'gen-jacobitab.c' || echo './../src/v6.2.1-0c723d4b6f.clean/'`gen-jacobitab.c -o gen-jacobitab.exe
Makefile:1506: update target 'gen-psqr.exe' due to: ./../src/v6.2.1-0c723d4b6f.clean/gen-psqr.c ./../src/v6.2.1-0c723d4b6f.clean/bootstrap.c
compile cl.exe -DWIN32 -D_WINDOWS -D_DEBUG -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -Od -Xcompiler -RTC1 `test -f 'gen-psqr.c' || echo './../src/v6.2.1-0c723d4b6f.clean/'`gen-psqr.c -o gen-psqr.exe
gen-fac.c
Makefile:829: update target 'config.h' due to: stamp-h1
test -f config.h || rm -f stamp-h1
gen-fib.c
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\mini-gmp/mini-gmp.c(717): warning C4146: unary minus operator applied to unsigned type, result still unsigned
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\mini-gmp/mini-gmp.c(758): warning C4146: unary minus operator applied to unsigned type, result still unsigned
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\mini-gmp/mini-gmp.c(976): warning C4146: unary minus operator applied to unsigned type, result still unsigned
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\mini-gmp/mini-gmp.c(1012): warning C4146: unary minus operator applied to unsigned type, result still unsigned
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\mini-gmp/mini-gmp.c(1068): warning C4146: unary minus operator applied to unsigned type, result still unsigned
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\mini-gmp/mini-gmp.c(1215): warning C4244: 'initializing': conversion from 'const mp_limb_t' to 'unsigned char', possible loss of data
...
Skipped 375 lines
...

C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\gmp-impl.h(4686): error C2071: 'preinv_mod_1': illegal storage classlibtool: compile:  .././../src/v6.2.1-0c723d4b6f.clean/mpn/m4-ccas --m4=m4 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_mod_34lsub1 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc x86_64_mod_34lsub1.asm  -DDLL_EXPORT -DPIC -o .libs/x86_64_mod_34lsub1.obj

C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\gmp-impl.h(4687): error C2071: 'redc_1': illegal storage class
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\gmp-impl.h(4688): error C2071: 'redc_2': illegal storage class
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\gmp-impl.h(4689): error C2071: 'rshift': illegal storage class
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\gmp-impl.h(4690): error C2071: 'sqr_basecase': illegal storage class
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\gmp-impl.h(4691): error C2071: 'sub_n': illegal storage class
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\gmp-impl.h(4692): error C2071: 'sublsh1_n': illegal storage class
C:\BUILD\vcpkg\buildtrees\gmp\src\v6.2.1-0c723d4b6f.clean\gmp-impl.h(4693): error C2071: 'submul_1': illegal storage class
libtool: compile:  .././../src/v6.2.1-0c723d4b6f.clean/mpn/m4-ccas --m4=m4 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_sub_n -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc x86_64_sub_n.asm  -DDLL_EXPORT -DPIC -o .libs/x86_64_sub_n.obj
libtool: compile:  .././../src/v6.2.1-0c723d4b6f.clean/mpn/m4-ccas --m4=m4 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_rshift -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc x86_64_rshift.asm  -DDLL_EXPORT -DPIC -o .libs/x86_64_rshift.obj
libtool: compile:  .././../src/v6.2.1-0c723d4b6f.clean/mpn/m4-ccas --m4=m4 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_submul_1 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc x86_64_submul_1.asm  -DDLL_EXPORT -DPIC -o .libs/x86_64_submul_1.obj
m4  -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_x86_64_addmul_1 -DWIN32 -D_WINDOWS -D_DEBUG -DDLL_EXPORT -DPIC x86_64_addmul_1.asm >tmp-x86_64_addmul_1.s
libtool: compile:  .././../src/v6.2.1-0c723d4b6f.clean/mpn/m4-ccas --m4=m4 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I..  -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_com -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_com.s -DDLL_EXPORT -DPIC -o .libs/x86_64_com.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_addmul_1 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_addmul_1.s -DDLL_EXPORT -DPIC -o .libs/x86_64_addmul_1.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_bdiv_dbm1c -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_bdiv_dbm1c.s -DDLL_EXPORT -DPIC -o .libs/x86_64_bdiv_dbm1c.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_cnd_sub_n -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_cnd_sub_n.s -DDLL_EXPORT -DPIC -o .libs/x86_64_cnd_sub_n.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_add_n -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_add_n.s -DDLL_EXPORT -DPIC -o .libs/x86_64_add_n.obj
m4  -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_x86_64_mod_34lsub1 -DWIN32 -D_WINDOWS -D_DEBUG -DDLL_EXPORT -DPIC x86_64_mod_34lsub1.asm >tmp-x86_64_mod_34lsub1.s
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_copyi -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_copyi.s -DDLL_EXPORT -DPIC -o .libs/x86_64_copyi.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_dive_1 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_dive_1.s -DDLL_EXPORT -DPIC -o .libs/x86_64_dive_1.obj
m4  -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_x86_64_mod_1_4 -DWIN32 -D_WINDOWS -D_DEBUG -DDLL_EXPORT -DPIC x86_64_mod_1_4.asm >tmp-x86_64_mod_1_4.s
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_divrem_1 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_divrem_1.s -DDLL_EXPORT -DPIC -o .libs/x86_64_divrem_1.obj
m4  -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_x86_64_rshift -DWIN32 -D_WINDOWS -D_DEBUG -DDLL_EXPORT -DPIC x86_64_rshift.asm >tmp-x86_64_rshift.s
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_lshift -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_lshift.s -DDLL_EXPORT -DPIC -o .libs/x86_64_lshift.obj
m4  -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_x86_64_sub_n -DWIN32 -D_WINDOWS -D_DEBUG -DDLL_EXPORT -DPIC x86_64_sub_n.asm >tmp-x86_64_sub_n.s
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_lshiftc -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_lshiftc.s -DDLL_EXPORT -DPIC -o .libs/x86_64_lshiftc.obj
m4  -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_x86_64_addlsh1_n -DWIN32 -D_WINDOWS -D_DEBUG -DDLL_EXPORT -DPIC x86_64_addlsh1_n.asm >tmp-x86_64_addlsh1_n.s
m4  -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_x86_64_submul_1 -DWIN32 -D_WINDOWS -D_DEBUG -DDLL_EXPORT -DPIC x86_64_submul_1.asm >tmp-x86_64_submul_1.s
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_copyd -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_copyd.s -DDLL_EXPORT -DPIC -o .libs/x86_64_copyd.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_cnd_add_n -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_cnd_add_n.s -DDLL_EXPORT -DPIC -o .libs/x86_64_cnd_add_n.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_mod_1_2 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_mod_1_2.s -DDLL_EXPORT -DPIC -o .libs/x86_64_mod_1_2.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_gcd_11 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_gcd_11.s -DDLL_EXPORT -DPIC -o .libs/x86_64_gcd_11.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_mod_1_1 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_mod_1_1.s -DDLL_EXPORT -DPIC -o .libs/x86_64_mod_1_1.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_mode1o -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_mode1o.s -DDLL_EXPORT -DPIC -o .libs/x86_64_mode1o.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_mul_1 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_mul_1.s -DDLL_EXPORT -DPIC -o .libs/x86_64_mul_1.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_mod_34lsub1 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_mod_34lsub1.s -DDLL_EXPORT -DPIC -o .libs/x86_64_mod_34lsub1.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_mod_1_4 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_mod_1_4.s -DDLL_EXPORT -DPIC -o .libs/x86_64_mod_1_4.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_sub_n -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_sub_n.s -DDLL_EXPORT -DPIC -o .libs/x86_64_sub_n.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_rshift -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_rshift.s -DDLL_EXPORT -DPIC -o .libs/x86_64_rshift.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_addlsh1_n -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_addlsh1_n.s -DDLL_EXPORT -DPIC -o .libs/x86_64_addlsh1_n.obj
 clang.exe -DHAVE_CONFIG_H -I. -I.././../src/v6.2.1-0c723d4b6f.clean/mpn -I.. -D__GMP_WITHIN_GMP -I.././../src/v6.2.1-0c723d4b6f.clean -DOPERATION_x86_64_submul_1 -DWIN32 -D_WINDOWS -D_DEBUG -c --target=x86_64-pc-windows-msvc tmp-x86_64_submul_1.s -DDLL_EXPORT -DPIC -o .libs/x86_64_submul_1.obj
make[2]: Leaving directory '/c/BUILD/vcpkg/buildtrees/gmp/x64-windows-dbg/mpn'
make[1]: Leaving directory '/c/BUILD/vcpkg/buildtrees/gmp/x64-windows-dbg'

C:\BUILD\vcpkg\buildtrees\gmp\build-x64-windows-dbg-err.log
cl : Command line warning D9002 : ignoring unknown option '-Xcompiler'
cl : Command line warning D9002 : ignoring unknown option '-Xcompiler'
cl : Command line warning D9002 : ignoring unknown option '-Xcompiler'
cl : Command line warning D9002 : ignoring unknown option '-Xcompiler'
cl : Command line warning D9002 : ignoring unknown option '-Xcompiler'
cl : Command line warning D9002 : ignoring unknown option '-Xcompiler'
make[2]: *** [Makefile:494: fib_table.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [Makefile:494: mp_bases.lo] Error 1
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_cnd_sub_n' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_com' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_addmul_1' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_add_n' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_bdiv_dbm1c' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_copyi' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_dive_1' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_divrem_1' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_lshift' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_lshiftc' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_cnd_add_n' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_copyd' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_mod_1_2' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_gcd_11' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_mod_1_1' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_mul_1' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_mode1o' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_mod_34lsub1' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_mod_1_4' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: clangwarning: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
: clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_sub_n' [-Wunused-command-line-argument]
clangclang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
: warning: clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_rshift' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_submul_1' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D HAVE_CONFIG_H' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D __GMP_WITHIN_GMP' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D OPERATION_x86_64_addlsh1_n' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D WIN32' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _WINDOWS' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D _DEBUG' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D DLL_EXPORT' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-D PIC' [-Wunused-command-line-argument]
make[1]: *** [Makefile:1000: all-recursive] Error 1
make: *** [Makefile:790: all] Error 2

This feature gmp[fat] added by PR #27787. cc @dg0yt Could you help take a look this issue? Thanks in advance.

I spent some time reviewing various threads, notably

https://machinecognitis.github.io/Math.Gmp.Native/html/846f5c8a-6cba-433e-9f18-cde2ff5695cd.htm
https://gmplib.org/manual/Notes-for-Package-Builds
https://github.com/wbhart/mpir/issues/236

The key thing is that the current default build of gmp by vcpkg is only guaranteed to run on the machine it was built on, on others it might crash with 'illegal instruction'.  This is certainly bad for making universal packages.  The 'fat' build would be the solution, but it's not compiling with vcpkg.  Some of the above links suggest it could be possible in general, the last one (by the GMP authors) is pessimistic.  So I'm not sure.  But I assume that other packages ship some generic version, either "unoptimized" (with no special CPU instructions) or a 'fat' version (which chooses the code dynamically based on the actual CPU).
My ultimate goal is packaging MPFR; this library can be link either GMP or MPIR, but vcpkg only recognizes the GMP option.  I wonder whether there is a way of configuring MPFR to use MPIR with vcpkg.  Now, MPIR is more Windows-friendly, but it could still have issues generating a 'fat' build.
In both cases, GMP or MPIR, it might be a solution to switch the build to the "generic" unoptimized code path, which is slower than "fat" but works on any CPU.

I already started looking into this issue.

gmp[core,fat]:x64-windows -> 6.2.1#14

This version has two significant changes for this issue:

Addition of feature fat.
I tested this feature on linux host (x64 native and x64 mingw). With some minor changes to the port, it also builds with on mingw on windows.
However, I have no idea if this works with non-mingw toolchains on windows. (And I cannot test this locally.) We might build with this feature and run make check as part of a draft PR to get more insight.
Switch from yasm to clang for assembly with msvc toolchains on windows.
I just integrated what was prepared in separate PRs already. Certainly another change which could need more tuning.

I would propose to start without using fat on windows.

Did 6.2.1#13 work as expected?
Can we be sure that correct code is generated for modern CPUs? (make check should answer that.)
Can we tune the build to control the minimum support CPU?
Do we want to offer an opt-out feature to control assembler? Assembler is already disabled for some targets, and it might be a solution for users targeting old cpus.

@dg0yt thanks!
Not sure how I can help; if I understand correctly, 6.2.1#13 does not have fat.  As far as I can tell the 6.2.1#14 build is correct, but just on the same CPU where it was built.
GMP's configure offers --disable-assembly, which is probably a safe choice, but performance will be impacted.  I'm not sure by how much.
I tried installing MSYS and used mingw-x64 to build GMP fat, and this works, but obviously it does not help as this cannot be linked to non-mingw code, as you pointed out.
I wasn't aware that vcpkg builds GMP using the MSVC toolchain (it makes sense, though) - but I cannot tell what does it take to fix things.  Based on this https://github.com/wbhart/mpir/issues/236 I would assume that it's no easy thing.
In all, I think that having the --disable-assembly option would be nice and looks achievable to me.  It's not fat, but at least the binaries are supposed to be generic enough.

make check passes for gmp[fat]:x64-mingw-static on windows host (after minor portfile changes).

AFAIU feature fat shall get "supports": "!windows, mingw".

https://gmplib.org/manual/Notes-for-Package-Builds:
I read this while preparing #27787.

GMP should present no great difficulties for packaging in a binary distribution.

Sure!

When building a package for a CPU family, care should be taken to use ‘--host’ (or ‘--build’) to choose the least common denominator among the CPUs which might use the package.

Unlike for most other packages, it seems mandatory that we don't rely on config.guess but actively provide what we want to be the target (in vcpkg terminology) even for native builds.

For the record - I digged deeper into the crash that motivated building gmp[fat] in the first place.  I tried building mpir (instead of gmp) in 'generic mode' and mpfr 4.1.1 by hand, and I was still getting errors.  So the illegal instruction was caused by MPFR using the mulx instruction, which has been introduced here https://github.com/BrianGladman/mpfr/commit/120346327407844e4d08f58b7ec6fff05be3b991
So like GMP, also the MPFR package could use an option for a 'safe' build.  My comment in the above link shows how I worked around this bug.  I'm not sure how to add flags to vcpkg; all this is quite low-level this-or-that way stuff (do you prefer portability or speed...), and I'm not sure how all this fits in the vcpkg ecosystem.

@dg0yt based on the discussions with the MPFR dev team, my conclusions/comments are this:

the current way that vcpkg builds GMP, MPIR and MPFR results in optimized builds that may fail to run on other hosts and as such are not fit for redistribution
the correct way of building generic binaries differs for each library:

MPFR: the right way is using the "cross-compilation" mode which results in skipping any optimizations; using Visual Studio x64 command prompt + Cygwin, the incantation that worked for me was configure --build=x86_64-pc-cygwin --host=amd64-pc-cygwin ...
MPIR: this library offers several VS .sln projects, the one to use (which also does NOT depend on yasm) is 'gc', in my case 'lib_mpir_gc' (results in a static library)
GMP: as we discussed here, the right way is the 'fat' build, which is not available for Windows.  So what would probably work best is forcing a cross-compile, much like as with MPFR, my guess is that the very same thing as I used with MPFR would work ( configure --build=x86_64-pc-cygwin --host=amd64-pc-cygwin ...)

I'm not familiar enough with vcpkg so I'm not sure what's possible.  Is there a way of providing such builds as separate features?  Perhaps it is, since gmp[fat] is not an extension but rather a variant of the build.  So perhaps we could also have gmp[generic], mpir[generic], mpfr[generic_gmp] and mpfr[generic_mpir], all available for Windows x64 (I'm not sure how to trigger 'cross-compile' in a generic manner for any platform).  Does this sound right?

Can you re-confirm that the bug is in port gmp, not in mpfr?
What I found is that our port does not create native-to-host-CPU builds, because running autoreconf replaces gmp's sophisticated cpu detection scripts (condig.guess, config.sub).
And when it comes to our msvc/clang builds (-windows- triplets), it gets even more complicated because we need one triplet to make configure create the right makefiles (and I don't think it is cygwin), and we might also need deal with ASMFLAGS (but we already do).
 You may need to burn your desired CPU model choice into a custom triplet file. (And there already is VCPKG_MAKE_BUILD_TRIPLET.)
I can create a draft PR from my WIP but I'm a little bit short on time for this topic. That's why I want to know if there is something which needs to be fixed immediately in port gmp, given its generic CPU choices.

The bug that I observed was in the MPFR as built by vcpkg, not in GMP.
What I think that needs to be fixed in the gmp port is what you already suggested - mark gmp[fat] as unavailable for Windows.
I haven't checked but based on what you are saying regarding using special config.guess and config.sub - it looks like there is no need then for providing a "generic" build of GMP.  That's great.  Some may desire the opposite, of course, and get the optimized build, but that's not me :)
Thanks a lot for your support!

For the record, I opened a separate issue for the mpfr port here: https://github.com/microsoft/vcpkg/issues/28005

@fkonvick Is it possible to attach a screenshot showing the error message coupled with some details about the Windows version and this old PC/CPU we are using?
Can you also attach here a zip file containing the offending app that crashes? There are several old machines at work with different processors and Windows versions so I try to replicate this bizarre issue.
Cheers.

@sfhacker Sure!
Here are the binaries; this needs to have the MSVCRT 2019 (or newer) redistributable installed in order to run.
gecode-6.3.0-test.zip
Here's the crash dump.  It's showing Exception code: 0xc000001d in GecodeFloat-6-3-0-r-x64.dll (which statically links MPFR).
archimedean-spiral.exe.260.zip
The system is a plain vanilla Windows Server 2008 R2 with SP1.  Here's CoreInfo64 output: coreinfo64.txt.  Notably, BMI1 & BMI2 are missing.  I believe that this is because "Hypervisor is present", as according to the specs this CPU model does support BMI.
I think the minimal repro could be as simple as calling sin or sqrt.  The way to check a particular build is to examine config.log: if it performs the mulx instruction availability check and defines HAVE_MULX_U64=1, then the produced code will contain mulx.
I can provide instructions for building the binaries above.  Gecode's sources are available from GitHub, and the first step is running the x64 VS command prompt and vcpkg install mpfr:x64-windows-static-md.

We do not use Visual Studio at all nor do many other people!
We should not force/impose using a specific toolchain/dependencies to end users and/or developers.

I am in the process of  building gecode 6.3.0 from source and I will test it on Windows 2008 R2 server and report back here.
Cheers.

Just built gecode 6.3.0 from source on Windows 10 x64 (GMP 6.2.1 & MPFR 4.1.1) . Copied a few files onto Windows 2008 R2 Server (fresh install; no MSVC runtime; no Visual Studio; no MS Office; no SQL Server; etc). No crashes at all.

To avoid polluting this issue, I will raise a new issue on gecode github and continue posting there.

We do not use Visual Studio at all nor do many other people! We should not force/impose using a specific toolchain/dependencies to end users and/or developers.

I am in the process of building gecode 6.3.0 from source and I will test it on Windows 2008 R2 server and report back here.

Sure, but distributing a pre-compiled library package requires that we choose a specific toolchain (unless we provide many variants).  All preceding versions of Gecode distributed a similar .msi package suitable for use with MSVC (the key dependency is the CRT).  The key reason I believe is to make this easily available for beginners.
Of course, anyone may build from source whenever the pre-compiled binary does not work for any reason - license restrictions of the optional dependencies (GMP + MPFR, Qt), incompatible compiler, etc.  Hopefully we could also provide a vcpkg port at some point.
The error that you copied here indicates the lack of the MSVCRT, which I mentioned earlier.  I could send you the required DLLs for copying into the executables directory (for the 'local deployment' of the CRT).  Alternatively, download from Microsoft from here and install system-wide.
Should you have issues compiling Gecode please let me know.  Again, the failed app is the archimedan-spiral.exe, and there is one more - golden-spiral.exe, but the nature of the crash will be similar.

Just built gecode 6.3.0 from source on Windows 10 x64 (GMP 6.2.1 & MPFR 4.1.1) . Copied a few files onto Windows 2008 R2 Server (fresh install; no MSVC runtime; no Visual Studio; no MS Office; no SQL Server; etc). No crashes at all.

Yes, but note that this is only supposed to crash when you build your binaries on a computer with BMI2 support and then run the resulting binary on another machine which does not support the BMI2.

@fkonvick To make it clear, sfhacker is not talking about helping with vcpkg.

@LilyWangLL I'm not sure it's clear what needs to be done, so I'll recap: we should mark gmp[fat] as unavailable on Windows because it does not build (and it's not possible to work around this).  This seems very straightforward, and it is also the original reason why I opened this issue.

I can create a draft PR from my WIP but I'm a little bit short on time for this topic. That's why I want to know if there is something which needs to be fixed immediately in port gmp, given its generic CPU choices.

Hi @dg0yt, did you have created a branch to fix this issue in your repo? Do I need to submit a PR to modify the supports of feature gmp[fat]?

@LilyWangLL TBH I still don't know if it works or not, due to the mpfr aspect in this discussion. I'm very limited in what I can do for (MSVC) windows triplets.

@LilyWangLL TBH I still don't know if it works or not, due to the mpfr aspect in this discussion. I'm very limited in what I can do for (MSVC) windows triplets.

Thanks for your reply. About mpfr, issue https://github.com/microsoft/vcpkg/issues/28005 has been fixed, are there any more questions about mpfr?
About gmp[fat], I agree fkonvick's commen:

we should mark gmp[fat] as unavailable on Windows because it does not build (and it's not possible to work around this). This seems very straightforward, and it is also the original reason why I opened this issue.

I will submit a PR to change gmp[fat]'s supports as your suggestion: "supports": "!windows, mingw".

@LilyWangLL #28005 is no longer an issue with the most recent MPFR version, so I think that there are no more questions regarding this.
Regarding gmp[fat] I confirm that marking this as unavailable for Windows (at least, as long as it does not build) seems to be the best approach to me.


IvorySQL: Compatible with Oracle's built-in data types and built-in functions.

Compatible with Oracle's built-in data types and built-in functions.

#239


Create setup.py file to make it easy to import magvit2 into other projects

pip install -e magvit2 now installs all dependencies and makes it possible to do from taming.models.lfqgan import VQModel from anywhere (not just when cwd=Open-MAGVIT2)
Let me know if this is helpful

sorry, i just realized there is an import issue since there are top-level folder dependencies from main:instantiate_from_config


Update CheckBox and LoginForm component regarding grommet/grommet#285

reverse prop in CheckBox and its example.
No label example in CheckBox.
rememberMe value in onSubmit argument object.

Sorry but i did not see this PR until now. I've added docs for Checkbox. would you mind to update this PR to account only for LoginForm?

Sure. I completed the missing parts.

thanks a lot.


rpc: Add support for consensus_state endpoint

Closes #674

[x] Referenced an issue explaining the need for the change
[x] Updated all relevant documentation in docs
[x] Updated all code comments where relevant
[x] Wrote tests
[ ] Updated CHANGELOG.md

Codecov Report

Merging #719 (f9f4912) into master (25f7ba5) will increase coverage by 0.3%.
The diff coverage is 51.6%.

@@           Coverage Diff            @@
##           master    #719     +/-   ##
========================================
+ Coverage    40.0%   40.4%   +0.3%
========================================
  Files         202     203      +1
  Lines       12805   13007    +202
  Branches     3204    3290     +86
========================================
+ Hits         5130    5261    +131
- Misses       7348    7380     +32
- Partials      327     366     +39

Impacted Files
Coverage Δ

rpc-probe/src/kvstore.rs
0.0% <0.0%> (ø)

rpc-probe/src/quick.rs
0.0% <0.0%> (ø)

rpc/src/client.rs
7.2% <0.0%> (-0.3%)
:arrow_down:

tendermint/tests/integration.rs
0.3% <0.0%> (-0.1%)
:arrow_down:

rpc/src/method.rs
12.8% <33.3%> (+0.5%)
:arrow_up:

tendermint/src/vote.rs
68.4% <41.6%> (+0.7%)
:arrow_up:

rpc/src/endpoint/consensus_state.rs
52.3% <52.3%> (ø)

rpc/tests/parse_response.rs
98.9% <100.0%> (+<0.1%)
:arrow_up:

tendermint/src/hash.rs
58.7% <100.0%> (+1.7%)
:arrow_up:

rpc/src/order.rs
0.0% <0.0%> (ø)

... and 44 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 25f7ba5...f9f4912. Read the comment docs.


Character create, edit integration with backend

Closes #100
Closes #137

The resources/js/Components/Form/CharacterCreateForm.tsx file exceeds 250 lines, which CodeClimate is flagging. Aside from that, editing a character and confirming changes leaves the drawer open. It just goes back to the first step of the form.

Ah i see what's wrong, i can fix that really quick

The resources/js/Components/Form/CharacterCreateForm.tsx file exceeds 250 lines, which CodeClimate is flagging. Aside from that, editing a character and confirming changes leaves the drawer open. It just goes back to the first step of the form.

we do plan to refactor the table component related to codeClimate issue, but that will be later, the focus should be on a function character module by the end of the sprint


Fix merge conflict for pull request #45

This pull request needs to be merged prior to pull request #45 to fix the merge conflict created by index.html and style.css files being added to the main folder instead of a css effect folder.
Pull request #45 creates an index.html file in the main folder as a showcase for all of the effects.

Closes #63


Could we please have the option to reboot instead of just logout at the end?

As stated in the subject line: Could we have the option to reboot at the end instead of just a logout?

@jby, I'll take a look and see how easy it could be to implement. Any thoughts on how you would like it to be configured? At this point, the script is automatically making the decision to logout vs quit at the presence of FileVault configuration. As I type, it sounds like I am going to have to make some sort of decision tree. Like, if FileVault on, then reboot. If FileVault is not detected, then quit, unless admin states reboot.
Would there be need for a shutdown command as well?

No, I don't think so - and since reboot starts with a logout, I think that it will trigger FV enablement as well...

Hello, did this get implemented as the script is pretty awesome just at the end we need to the user to reboot as we install things like DisplayLink which require a reboot.
So or process would be at the end of DEP Notify user clicks Restart button, enters FileVault password and Mac reboots.

i got it
ContinueButtonRestart

ContinueButtonRestart

Can you elaborate how you did this? I want to reboot after completion.

Can you elaborate how you did this? I want to reboot after completion.

Visit this link: https://gitlab.com/Mactroll/DEPNotify#advanced-workflows
Scroll down to the "Completion" section and it has commands you can use to restart. You'll edit the script to use one of these commands.

Can you elaborate how you did this? I want to reboot after completion.

Visit this link: https://gitlab.com/Mactroll/DEPNotify#advanced-workflows
Scroll down to the "Completion" section and it has commands you can use to restart. You'll edit the script to use one of these commands.

Actually here: https://gitlab.com/Mactroll/DEPNotify#continuebuttonrestart

The above works just fine


Bug: Tab mode sometimes results in inability to request_accounts.

When I have the setting enabled to open prompts in a new tab, an account request pops up even though I already have the account approved for the site, and approving in that dialog sends a rejection to the dapp.

should be fixed as the permissions was rewamped


Added a convenient error message when running cargo test on Windows

@White-Oak I'm pretty sure we shouldn't say "Linux" specifically, since it should be okay on other Unix-like systems such as BSD. Do you know if unix also counts Mac OS X? If so, that can be counted as well.
I'd recommend changing the message to say "Unix-like systems" instead of "Linux".
Maybe we should consider moving the tests over to native Rust at some point so they can work on all platforms.

@eblalderon it would be cool to have a POSIX target :)

@ebkalderon I've changed unix to not windows. Eventually, tests would need to be rewritten in Rust, but that's a big and tirsome task, so until then this is a small change to help Windows users understand that it's not a code, but tests' nature, that fails them.

@White-Oak I agree, this is good enough for now. Thank you! Let's merge this.


Failed to load library libsgx_launch.so.1 when running rune exec or rune attest command

This is an error message and is not fatal.

This commit https://github.com/alibaba/inclavare-containers/pull/207 resolve this issue.


Temperature null when changing hvac mode

After upgrading from v0.9.7 to 0.9.8 the temperature is set to 'null' (shown as attribute) when changing hvac mode.
When this happens I have to manually set the temperature attribute via developer tool to be able to control the temperature.
Downgraded to v.0.9.7 and the temperature is persistent when changing hvac mode.
climate:
  - platform: dual_smart_thermostat
    unique_id: dual_smart_thermostat.hvac
    name: HVAC
    heater: input_boolean.hvac_heat
    cooler: input_boolean.hvac_cool
    target_sensor: sensor.temperature
    min_temp: 16
    max_temp: 30
    ac_mode: false
    cold_tolerance: 1
    hot_tolerance: 1
    precision: 0.1
    target_temp_step: 1.0

Same issue here.


Location services does not start correctly

First into the application without authorization, or executing a method
info.plist config：NSLocationWhenInUseUsageDescription
Location.getLocation(withAccuracy: .Block, onSuccess: { foundLocation in

})  { (lastValidLocation, error) in
           // something bad has occurred
           // - error contains the error occurred
          // - lastValidLocation is the last found location (if any) regardless specified accuracy level
 }

Hi, @itamaker, what's the problem?

Location services does not start correctly and no events is reported.
Fixed in 1.0.3 currently pushed both on CocoaPods and Carthage.


Updated Filtering Capabilities for Game List API Endpoint with Updated Game Model Attributes

The Game model recently got updated to contain many more fields -- inspired by BoardGameGeek -- than just the four initial fields (name, description, max_players, min_players). We wanted our API endpoint to be able to handle filtering by any of the original fields (which we have already done), but also be able to filter by the new fields.
This PR adds filtering by exact lookup for new integer type Game attributes including year_published, suggested_age, expected_playtime, min_playtime, max_playtime, min_players, max_players
In addition, it adds filtering based on lte and gte for the Decimal complexity attribute.

@majorsylvie added support for exact BGG_id filtering!

added support for lte and gte for additional Game model attributes including year_published, max_players, min_players, max_playtime, expected_playtime, min_playtime, suggested_age

Issue Score: Excellent


Update bucket key prefixes and add max number records config

Closing for now as adjustments need to be made based on feedback from clients


Error: Invalid value for "targets" / "0" / "sumo_http_url": expected a URL

Hello,
even after having a valid url in config.json I am running into this error,
Error: Invalid value for "targets" / "0" / "sumo_http_url": expected a URL
below is the config.json. (not showing url here on purpose)
{
"targets": [
{
"name": "mtga-hosted",
"url": "localhost:9000/metrics",
"sumo_http_url": "valid url"
}
]
}
Thanks,
Mithun

"url": "localhost:9000/metrics",
should be
"url": "http://localhost:9000/metrics",
sumo logic support helped me narrow down the issue.
it will be nice to have  a different error message for url and sumo_http_url.


callstack exceeded results in server crash

This might be the result of doing stupid things and using react-router in unexpected ways, but I found a mysterious crash that wound up being max callstack exceeded.  You can see this if you take the react-router-server-complex-example project and make the following changes:

Remove the <Switch /> element from ./components/App.jsx
Change NoMatch to use async loading like the other routes.

If you visit one route, it works fine... but visit another and hit refresh you'll get a server crash.
On my machine, Windows10 there is no actual error returned from the process.... but you can inspect %ERRORLEVEL% to see what the exit code is... here is the output from the shell,
D:\Code\react-router-server-complex-example>node_modules\.bin\babel-node.cmd --plugins system-import-transformer -- src/server.js
Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.
Example site listening on 3000!

^--- server crashes :(

D:\Code\react-router-server-complex-example>echo %ERRORLEVEL%
-1073741571

-1073741571 is a stack overflow exception.
I put a debugger on it in my own project where I found this initially, and I found that context.callback kept getting called, and went into another renderPass which ended up calling context.callback again.
I noticed the then callback in load was never fired, so add never gets called  and the exists check never passes  and the modules array kept getting the same module added over & over again.

Can you try with release 4.2.0, I believe this is fixed.

Hi, this works properly now, thanks!


Fails to load in JRuby: RangeError (bignum too big to convert into `long')

This module expects in multiple locations that it can convert the special numbers 0 and 2^64-1 into a time stamp. This does not work in JRuby, where it uses a signed long to work on times.
irb(main):002:0> require "ssh_data"
Traceback (most recent call last):
       16: from org/jruby/RubyKernel.java:1052:in `load'
       15: from /usr/share/jruby/bin/irb:11:in `<main>'
       14: from org/jruby/RubyKernel.java:1237:in `catch'
       13: from org/jruby/RubyKernel.java:1237:in `catch'
       12: from org/jruby/RubyKernel.java:1507:in `loop'
       11: from org/jruby/RubyKernel.java:1091:in `eval'
       10: from (irb):2:in `evaluate'
        9: from /usr/share/jruby/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:160:in `require'
        8: from org/jruby/RubyKernel.java:1017:in `require'
        7: from /var/lib/puppetserver/jruby-gems/gems/ssh_data-1.3.0/lib/ssh_data.rb:33:in `<main>'
        6: from /usr/share/jruby/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:85:in `require'
        5: from org/jruby/RubyKernel.java:1017:in `require'
        4: from /var/lib/puppetserver/jruby-gems/gems/ssh_data-1.3.0/lib/ssh_data/certificate.rb:4:in `<main>'
        3: from /var/lib/puppetserver/jruby-gems/gems/ssh_data-1.3.0/lib/ssh_data/certificate.rb:5:in `<module:SSHData>'
        2: from /var/lib/puppetserver/jruby-gems/gems/ssh_data-1.3.0/lib/ssh_data/certificate.rb:8:in `<class:Certificate>'
        1: from org/jruby/RubyTime.java:1336:in `at'
RangeError (bignum too big to convert into `long')

Thanks for the report. This is an unfortunate behavior of jruby.
jruby's stance on this seems to be that it is an accepted and known incompatibility https://github.com/jruby/jruby/issues/1304.
Fixing this is a breaking change, as we could no longer return Time.at((2**64)-1) for valid_before. It's unlikely we would be able to address this any time soon as the bar for breaking changes in this repository is high, and GitHub does not use this gem in a jruby environment.

Yeah, I imagined so much.
My fix would be to define marker objects representing those two special values, 0 and 2**64-1. They don't refer to real times, but are just approximated infinity. This is an incompatible API change if you consider the time values of infinity relevant and a compatible change if you expect people to use the existing constants.

Well, would it be an acceptable change to just use this different behaviour on JRuby? No incompatible change, but a maintenance burden.


Skaffolding - end of doIt execution returns unknown object through rsr and causes AlmostOutOfStack

To reproduce:

Setup direct connection with topaz servicing the connection.
Use a variant of SpkScaffoldingServiceClient class>>debugger_07b to execute this code: (client gsDebugger_07: '7 halt. GsFile _log: ''resumed''' usingDebugger: debuggerClient)  Will attach the variant method in a comment.
From my infantile debugger, hit resume (which sends #resume to the service),  see 'resumed' printed on stdout but then it gets an almost out of stack.

topaz 1 +> run^M
| spec connection |^M
spec := RsrAcceptConnection port: 29299. ^M
connection := spec waitForConnection. ^M
connection waitUntilClose^M
%
resumed
ERROR 2502 , a AlmostOutOfStack occurred (notification 2502), Smalltalk execution stack overflow, Red Zone.
Stack overflow,  Stack depth 3132

If you return a 1 at the end of the smalltalk execution, the almost out of stack error is avoided.

debugger_07b_eric

	"testDebugger_07b - trigger exception during doit and expect to trigger a remote debugger; resume execution, print stack to Transcript, resume execution and print result to Transcript"

	<example>
	| client debuggerClient sem |
	client := SpkScaffoldingServiceClient new registerWith:
		          self connection.
	debuggerClient := SpkScaffoldingDebuggerServiceClient new.
	Smalltalk at: #SPARKLE_DEBUGGER_SEMAPHORE put: Semaphore new.
	sem := Semaphore new.
	Transcript clear.
	Transcript
		cr;
		show: '=========';
		cr;
		show:
			'testDebugger_07b - trigger exception during doit and expect to trigger a remote debugger; resume execution, print stack to Transcript, resume execution and print result to Transcript ';
		cr;
		show: DateAndTime now printString;
		cr;
		show: '=========';
		cr.
	(client gsDebugger_07: '7 halt. GsFile _log: ''resumed''. 1' usingDebugger: debuggerClient)
		when: [ :result |
			Transcript
				cr;
				show: '=========';
				cr;
				show: 'doit result is ' , result doitResult printString;
				cr;
				show: '=========';
				cr;
				yourself.
			sem signal ]
		catch: [ :reason |
			Transcript
				cr;
				show: '=========';
				cr;
				show: 'CATCH: ' , reason printString;
				cr;
				show: DateAndTime now printString;
				cr;
				show: '=========';
				yourself.
			WorldState defer: [
				false ifTrue: [
					{
						'catch'.
						reason } inspect ] ] ].
	(Smalltalk at: #SPARKLE_DEBUGGER_SEMAPHORE) wait. "wait for stack to print"

	"debuggerClient resume." "resume execution"

	"sem wait." "wait for result"
	"Transcript
		cr;
		show: '=========';
		cr;
		show: 'SUCCESS ' , DateAndTime now printString;
		cr;
		show: '=========';
		cr"

AFAIK, Dale's scaffolding is no longer being used except as a code reference, so closing this issue. If this is still a relevant problem, please reopen or re-file.


Chapter link is broken

Looks like only Labs is relevant. There is no Chapter folder.

Where is the relevant course material that puts all the "pieces" in context?

@oleg-1login The course will launch tomorrow, April 14th. Please check back here!

Our team has been working getting the content out as we have it ready. The course will launch and be available tomorrow!

The course content has been uploaded in word and pdf formats.

Thank you all for putting this together!

Thank you all for putting this together!

Yep Im really happy about the modern tooling that surprised me.

"Chapters" link still gets 404 error
Where can i find the Word and PDF files?

"Chapters" link still gets 404 error
Where can i find the Word and PDF files?

Directly on the root of the repo: https://github.com/openmainframeproject/cobol-programming-course
Click on it -> Download

The chapter and lab links have been fixed in readme.md


What happened to TaxBrain parameter _ACTC_ChildNum?

The same TaxBrain testing script that ran fine yesterday on scalar parameter values, now gets this error:
ValueError: no TaxBrain parameter named _ACTC_ChildNum

Has something changed that I don't know about?
@talumbau

Martin said:

The same TaxBrain testing script that ran fine yesterday on scalar parameter values, now gets this error:

ValueError: no TaxBrain parameter named _ACTC_ChildNum

After several more runs of TaxBrain, this error seems to have disappeared.  Closing this issue.


BDS-123 : Supports Penetration testing with DWP /HIP/NPS

Update URL path and documentation.

Test this please.

Reviewed


core: Add Redis policy store

This is a requirement of https://github.com/ory-am/hydra/issues/306
$ go test
[...]
PASS
ok      github.com/ory-am/ladon 29.019s

Wrapped errors. Let me know if you're happy with that and I'll squash.

Looks good! I will test this code tomorrow for some final reviewing and going to merge it then. No squashing required!
One more thing, please sign your commit with git commit --amend -s :)

thanks!


default chain ?

Can we define the default chain?
https://docs.walletconnect.com/web3modal/vue/options It exists here but I couldn't manage to add it.

Can we define the default chain? https://docs.walletconnect.com/web3modal/vue/options It exists here but I couldn't manage to add it.

Hey. The first network specified will be the default.
createWeb3Auth({
    chains: [
        Chains.bsc, // bsc is default
        Chains.mainnet,
        Chains.polygon
    ],
})

What is your case for using the default network?

Oh okay, I got it. I was just trying to work on testnet and when I connected metamask it was changing my network but I wanted to work on testnet and I thought if I could change the default to testnet it would work :)
Thank you for the answer.

Oh okay, I got it. I was just trying to work on testnet and when I connected metamask it was changing my network but I wanted to work on testnet and I thought if I could change the default to testnet it would work :) Thank you for the answer.

You need to add a test network when configuring the package and then it won't switch
Like this:
createWeb3Auth({
    chains: [
        Chains.bscTestnet
    ],
})


No device

Hi!
After flash no device in win10

Hi!
This is just a low-level driver project for stm32. In this case, sine and cosine signals are generated in the left and right channels of the DAC. The project does not provide for a USB device. It can be an integral part of such a project.

Got it! I confused it with the USB DAC.

Could you please tell me how to make the device initialize as a USB sound card and start data transmission? The lower level is too complicated for me.


I find it runs so slow

I use https://github.com/alexkimxyz/nsfw_data_scraper
About 25w pictures
Machine info:
P40, I use four gpus
question: I find it runs so slow. 8 hours run 14 epoch.
Is this normal?

in my experience, pytorch is faster than tensorflow, about 200 pics/s(200 - 300 i think)  in my k80.
so one epoch which is 25w pics will take 250000 / 200 / 3600 = 3.4 hour.
that is normal


tls: configure downstream TLS certificate in Routes

This patch is part of the TLS proposal.
Fixes #103

Notes for reviewers
Please review the last commit only. This PR builds on top of #256.
/cc @robscott @bowei @jpeach @youngnick

@hbagdi can you allow access to the TLS proposal in https://github.com/kubernetes-sigs/service-apis/pull/281#issue-475549551?

I messed up the link to the Google doc.
This is the correct link:
https://docs.google.com/document/d/15fkzMrhN_7tA-i2mHKwZpqcjN1o2Pe9Am9Qt828x1lo
Also updated the link in the PR description. Sorry for the trouble.

I've updated the fieldnames to AllowOverrideViaRoute and RouteTLSConfig.
I've also updated language on requiring certificate at the listener level.
PTAL
cc @jpeach @yiyangy  @danehans @robscott

@hbagdi can you add an example to /examples as part of this PR?

@hbagdi you may also want to reference https://github.com/kubernetes-sigs/service-apis/issues/290 for field defaulting/validation behavior.

I've updated the descriptions and field names and also added an example (the example is based on the new flattened route which is not merged yet).
PTAL @bowei @robscott @danehans @jpeach @yiyangy @howardjohn

Thanks @hbagdi! This LGTM, will approve it and leave the final LGTM for someone else.
/approve

@danehans Fixed, PTAL.

/lgtm


pass seconds instead of percents to audioprocess event

Can you also explain this PR @akreal? What's broken exactly?

audioprocess passes seconds in createBackend, so it should do here.

Thank you very much!


Move SERVER_DIR to /var/lib in rpm

Fixes #1619.

Thanks, no problem. I have just changed the target branch to devel, we do not accept PRs to master. Will get there on the next release.


document table-returning modules

I have a tableconstructor-returning config file written in moonscript (though this seems to apply to lua as well), in the style:
--- @module myapplication.config
{
  some_variable: 5
  some_section: {
    some_subvariable: 10
    some_section_array: {
      { something: 1 }
      { something: 2 }
    }
}

and it seems kinda impossible to document this table (except by writing everything by hand in some markdown file, but then it still seems impossible to let LDoc handle it as a module description instead of a topic), because it just creates an empty module description file, no matter how many @table or @field tags i add.
even the outermost table seems to be ignored if tagged with @table default_config or something like that, maybe because LDoc can't see an assignment there.
and @exports is also wrong here because it (rightfully) complains it's just for filtering a module's previously documented locals.

this seems to kinda work:
--- @module myapplication.config
--- @table default_config
default_config={
--...
}
return default_config

but then LDoc handles it as myapplication.config.default_config which is wrong. using @module myapplication and @table config would fix this naming, but then it would present a module myapplication containing this table, which is also wrong because you have to require 'myapplication.config, not import config from require 'myapplication' as LDoc suggests.
also then it would still not allow for nested tables.

strangely, sometimes (sadly i can't currently reproduce when exactly) it tries to parse the table as a class and the members as functions, i'd guess because it sees the syntax ...: ... as class members instead of table constructor fields


28 Mar 2024 - Emerging Technologies Meeting Agenda

Date
20240328 - 2pm GMT/10am EST
Theme
DLT & Web3
Untracked attendees

Fullname, Affiliation, (optional) GitHub username
...

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene & roll call (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve past meeting minutes
[ ] Welcome & Announcements

[ ] Updates on current projects
[ ] Notices about upcoming events/deadlines

[ ] Deep Dive

[ ] Hedera Deep Dive

[ ] Any other Admin
[ ] Call to action

[ ] POC Program
[ ] Primers
[ ] Brain Trust membership

[ ] AOB
[ ] Thanks & Close Out

Zoom Details

https://zoom.us/j/98538837792?pwd=ZHg3QVVnaCtOT0tEZSs5c0hrZTg1dz09
Meeting ID: 985 3883 7792
Passcode: 152455

Join by Phone

Find your local number: https://zoom.us/u/adl5rhui4P

Keith O'Donnell | Feynic

Justin Atwell | Swirlds Labs / Hedera Hashgraph

Peter Smulovics / Morgan Stanley

Benjamin Rutter - Senso Studio

Bruno Domingues / Intel

Wes Geisenberger / HBAR Foundation

Summary of Meeting Minutes
Date: March 28, 2024
Event: Special Interest Group Meeting
Main Points:
00:07:53 - 00:08:00
Keith J. O'Donnell starts the official meeting, mentioning it's a special interest group session with mandatory notices.
00:08:26 - 00:08:35
Keith goes through mandatory notices, including the Linux Foundation Anti-Trust Policy and FINOS guidelines.
00:10:14 - 00:10:30
The meeting theme is Easter egg, and attendees are encouraged to use QR codes for participation and documentation.
00:10:50 - 00:10:53
Keith asks attendees to register their attendance via a link or QR code.
00:11:05 - 00:11:16
Keith introduces the agenda: announcements, deep dive into Hedera and Swirlds Labs sandbox, and other business.
00:11:21 - 00:11:59
Announcements include the launch of the FINOS project sandbox and upcoming events like OSF London, OSF New York, and the FSI Hackathon for Autism.
00:12:46 - 00:13:28
Highlighting upcoming events in April, such as a webinar on malicious open source components in financial services and the Symphony Innovate NYC conference.
00:13:34 - 00:14:53
Keith introduces Hedera and Swirlds Labs representatives to discuss their projects and the sandbox environment for Web3 and DLT.
00:16:07 - 00:16:29
Serg Metelin introduces Pathorn Tengkiattrakul, who will present the Stable Coin Studio, and Wes from the Page Bar Foundation will discuss sustainability.
00:16:33 - 00:41:03
Pathorn Tengkiattrakul presents the Stable Coin Studio, explaining the hybrid architecture of Hedera network services and demonstrating how to create and manage a stable coin using the platform.
00:41:06 - 00:42:46
Keith O'Donnell emphasizes that FINOS will provide materials and guides for users to explore the Stable Coin Studio and other tools in the sandbox.
00:42:46 - 00:42:56
Transition to the next part of the meeting where Wes Geisenberger will present on the Guardian ecosystem and sustainability efforts on the Hedera network.


GithubReleaseV0 - Link in list of changes does not escape spaces

Environment

Server - Azure Pipelines

Organisation: fernandreu-public
Team project name: Custom UI Editor
Build definition name: BuildAndTest
Build number: 20190309.5

Agent - Hosted:

Agent queue name: Hosted VS2017 2

Issue Description
My project name, Custom UI Editor, has spaces. This is fine for the release process, but the Markdown syntax does not seem to support them in links. Hence, the last line in the list of changes ends up looking similar to this:

This list of changes was [auto generated](https://dev.azure.com/fernandreu-public/Custom UI Editor/_build/results?buildId=94).

Perhaps replacing those spaces by %20 symbols in here would fix the issue?
Task logs
Let me know if these are necessary.
Error logs
Let me know if these are necessary.

Yes, possibly we need to encode the url.
Thanks @fernandreu for reaching out to us. Will update the thread with a fix soon.

Issue fixed with this PR #10770.


Consider renaming gradleKotlinDsl() dependency notation to gradleKotlinApi()

Current behaviour
if you're usinggradleKotlinDsl() in a binary plugin it has nothing to do with the Kotlin DSL.
It's just giving access to the same extension functions than the DSL does, in other words the "Gradle Kotlin API".
Expected behaviour
I can declare a dependency to the gradleKotlinApi() in order to get the Gradle Kotlin API.
Context
This was originally asked by @ducrohet

Thank you for your interest in Gradle!
This feature request is in the backlog of the relevant team, but this area of Gradle is currently not in focus. It might take a while before it gets implemented.


CramQC stage can not run on exomes

In the recent update to analysis_keys, the CramQC stage now hard codes picard_wgs_metrics as an expected analysis_key. However, when running on exome data this stage will produce picard_hs_metrics not picard_wgs_metrics.
In the current state, if the pipeline is run on exome data you get the following error (edited for clarity):
cpg_workflows.workflow.WorkflowError: Cannot create Analysis for stage CramQC: `analysis_keys` "
    ['somalier', 'verify_bamid', ... 'quality_yield_metrics', 'picard_wgs_metrics']"
is not a subset of the expected_outputs keys dict_keys(
    ['somalier', 'verify_bamid', ... 'quality_yield_metrics', 'picard_hs_metrics'])

I am not sure where this target dependent behaviour should be handled?

This is annoying, sorry @cassimons! Is it blocking you? If so, I'll remove these keys quickly now while I think about the best way to handle this.

Thanks @vivbak, that fix has got the pipeline running again for the moment.


move welcome page test to grc

for https://github.com/open-cluster-management/backlog/issues/10953

/lgtm