Legion documentation for GASNet

As requested in today's meeting, below is my list of comments/suggestions for updating the Legion GASNet page at http://legion.stanford.edu/gasnet/
This is a cut-and-paste of the email thread from March 30, 2017.
Let me know if I can offer any further clarification on any points.
Hope this helps..
-D

*** Sec: Building GASNet

Para 1: "BE SURE THE CONFIGURE SCRIPT BUILDS THE CORRECT CONDUIT." - Suggest adding some text like "The GASNet configure script finishes by printing a summary of detected conduits that will be built."

Para 2: Suggest adding a note like "The full list of configure arguments can be seen with configure --help"

Para 2: On the configure args described:

--enable-par : this is enabled by default whenever pthreads are detected (all modern systems), so there's really no reason to ever specify it explicitly
--enable-segment-fast : this is the default, no reason to ever specify it explicitly
"--with-segment-mmap-max=<#>GB ... Default is 1MB"
The default is actually 2GB, and there's rarely any direct motivation to change this aside from wanting to allow for a larger FAST segment by default (and the environment variable can override this default at runtime).
"... which results in GASNet start-up times of several MINUTES with large (e.g. 48 GB) address spaces."
The startup-time issue is specific to ibv-conduit (which defaults to attempting to pin up to 2/3 or physical memory), and setting a low --with-segment-mmap-max actually no longer affects the behavior of that probe (if it ever did). All it does is artificially limit the segment size of all conduits (and that truncation happens AFTER the expensive probe in the case of ibv-conduit). The appropriate workaround for the ibv-specific startup issue is to set GASNET_PHYSMEM_MAX (and possibly GASNET_PHYSMEM_PROBE) in the environment at job run time (see ibv-conduit/README for details). There is not currently a configure-time mechanism to tune the default values for those settings, but we may look into adding one since that seems valuable (UPDATE: GASNet 1.30.0 is expected to contain a configure-time mechanism for tuning this)
--enable-cross-compile: this is a "semi-documented" flag which is automatically added by all the cross-configure scripts. There's no reason for a user to ever type this (especially since cross-compilation won't work without all the other settings provided by the cross-configure script).
*** Sec: Configuring GASNet for Performance

On the Keeneland example configure command:
--enable-segment-fast : this is the default, so has no effect
--enable-par --enable-pthreads : this is probed and enabled by default, so this "force" option has no effect unless pthreads are broken on this system (in which case it errors out, a useful behavior but probably irrelevant in this context)
--disable-portals : this conduit no longer exists, unless perhaps you meant to type --disable-portals4 (although those drivers are unlikely to be in your environment)
--with-segment-mmap-max=4GB : see above
--disable-pshm : The performance cost for PSHM support is actually very small (especially when not used at runtime). Conversely, the performance cost to running more than process per node without PSHM support is very significant, and that's the likely mode of operation in hybrid MPI apps. So I'd advocate removing --disable-pshm as a general recommendation (in which case you can also remove --disable-aligned-segments, which is implied in all current conduits by the default --enable-pshm).
Text below referring to these options should probably also be deleted.

"We instruct GASNet that it should pin 4 GB of memory on each node to be used for its fast active message segment using the --enable-segment-fast --with-segment-mmap-max=4GB flags." - the phrase "fast active message segment" is misleading, it's just the "GASNet memory segment" (ie used by all GASNet ops, not just AM).

"The --disable-pshm and --disable-fca flags disable shared memory and fast atomic operations which are unnecessary for Legion and can sometimes degrade performance."
--disable-fca has nothing to do with atomics - it controls support for using Fabric Collective Accelerator drivers from Mellanox. These drivers are unlikely to be installed on your system (in which case it's automatically disabled), but even if support is detected it should not degrade general performance (unless the drivers are broken, I guess). So that argument can probably be removed as well.

On the Titan example configure command:
"cross-configure-crayxe-linux" has been renamed in the latest GASNet release to "cross-configure-cray-gemini-{alps,slurm}"
--enable-gemini : Automatically added by the cross-configure script, so this is arg redundant and has no effect
--disable-portals --enable-par --enable-pthreads : See above
--with-target-cxx : GASNet does not use CXX anywhere except udp-conduit, which the script disables for this platform - so this argument has no effect. On the related body text it would probably be better to say something like "The cross-configure script is human-readable and can easily be edited to change things like the location of the compute node C compiler if it's not in a standard location".
Other text below referring to these options should also be updated.

If we are looking to show examples for some other configure options that users might want situationally, here's a few of the more interesting ones cut-and-paste from the GASNet/README:
For example to build 32-bit code when your gcc and g++ default to 64-bit:
configure CC='gcc -m32' CXX='g++ -m32' MPI_CC='mpicc -m32'
or similarly, if you want libgasnet to contain debugging symbols:
configure CC='gcc -g' CXX='g++ -g'   (however also see --enable-debug, below)
Some of the useful configure options:
--enable-debug - build GASNet in a debugging mode. This turns on C-level
  debugger options and also enables extensive error and sanity checking
  system-wide, which is highly recommended for developing and debugging
  GASNet clients (but should NEVER be used for performance testing).
  --enable-debug also implies --enable-{trace,stats,debug-malloc},
  but these can still be selectively --disable'd.
--enable-trace - turn on GASNet tracing (see usage info below)
--enable-stats - turn on GASNet statistical collection (see usage info below)
--enable-debug-malloc - use GASNet debugging malloc (see usage info below)

There are also variables for helping configure find conduit drivers if they are installed in a non-standard place, eg:
--with-ibvhome=/path/to/ibv/drivers
** Sec: GASNet Performance Environment Variables

I would add a sentence somewhere mentioning GASNET_VERBOSEENV=1, which enables GASNet's environment variable readout at runtime, and is often a good starting place to see which variables might be relevant to this run (and confirming they were set as the user expected). GASNET_BACKTRACE=1 is also very helpful when debugging. The full list is of course in the top-level GASNet README and *-conduit/README

GASNET_AMRDMA_MAX_PEERS:  Delete everything after "In some cases we have found.." (based on the findings earlier in our email thread)

GASNET_GNI_MEMREG "Most often needed when running applications without the -ll:rsize flag (see below)." - This is a broken reference - there is no "below".

As a general point, one thing that seems to be missing from this page is instructions on how to link up a build of the Legion tree with the copy of GASNet the user has just successfully installed (ie how does the user tell Legion the GASNet install prefix and conduit to use). This might be covered somewhere else in the Legion documentation (although I could not find it on the Getting Started page or in README.md). It may be worthwhile to either explain that here or link that other documentation.

@bonachea Thanks again for writing this up.  I did a bit of documentation cleanup this morning.  When you get a moment, can you look over the updated page and see if I missed anything major?  (Regarding your last suggestion, the "Getting Started" page now tells users about the GASNET_ROOT Makefile variable for pointing at the right GASNet install location.)

@streichler Looks much improved - thanks for your attention on this!
A few places still reference obsolete or redundant configure arguments, but I believe those remaining cases should all be harmless.
The only remaining non-trivial inconsistency I noticed was in the instructions for Titan that reference:
ln -s other/contrib/cross-configure-crayxe-linux cross-configure

these scripts were recently renamed, I believe the correct script for Titan is now:
ln -s other/contrib/cross-configure-cray-gemini-alps cross-configure

CC: @phhargrove

Yeah, I waffled a little on the "historical" examples there because they were correct for that particular system, GASNet and system software versions, and if I change things, I have no way of testing that they still worked on that config.  My inclination is to just remove that section and instead find a way to point at a primary source that shows how we currently configure things for our dev systems.


Is it possible to guess the amount of memory RetDec will need for decompilation?

Is there a way to guess the amount of memory retdec is going to need for decompilation?
I'm thinking of creating a web service to automate decompilation. The idea is to spin up a cloud instance with the right amount of memory, do decompilation and shut it down once decompilation is done.
To optimize costs (= decide which cloud instance to spin up) it would be good if I could know how much memory the process is going to take up.
Sam

Hi. I am afraid that there is no simple relation between static properties of the input file and the amount of memory RetDec will need to decompile it. A rule of thumb may be the bigger the file, the more memory RetDec may need, but this is generally an oversimplification. The amount of memory depends on many factors, including the number of instructions in the file, whether RetDec is able to correctly decode the instructions, detection of statically linked code, and decompilation parameters (e.g. selective decompilation may require less memory than full decompilation).
One of our long-term goals is to reduce memory requirements of RetDec (#13), but this is going to be a long run.

Ok, I figured the the bigger the file, the more memory RetDec may need was going to be my only option.
Another question, is there a way to continue decompilation where it left it of? That way I can start on a normal machine but continue on a machine with more memory in case decompilation stops due to memory shortage.


get(key: K,  compute: suspend (K) -> V ) doesn't support compute function that returns null

According to the documentation for get

If the specified key is not already associated with a value, attempts to compute its value and enters it into this cache unless null.

However, when I create a cache with non-nullable values and try to update it using a compute function that can return null I get a compilation error: (scratch file showing the compilation error)

import com.sksamuel.aedile.core.Cache
import com.sksamuel.aedile.core.caffeineBuilder
import kotlinx.coroutines.delay
import kotlinx.coroutines.runBlocking

val cache: Cache<String, String> = caffeineBuilder<String, String>().build()

suspend fun foo(): String? {
    return cache.get("key") { _ -> asyncFun("a") }
}

suspend fun asyncFun(s: String): String? {
    delay(1)
    when (s) {
        "a" -> return null
        else -> return s
    }
}

fun main() {
    runBlocking {
        println("key = ${foo()}")
    }
}

main()

Compilation error is on asyncFun:

Type mismatch. Required: String Found: String?

Changing the type of the cache to <String, String?> results in null being saved to the cache (not the desired behavior):
import com.sksamuel.aedile.core.Cache
import com.sksamuel.aedile.core.caffeineBuilder
import kotlinx.coroutines.delay
import kotlinx.coroutines.runBlocking

val cache: Cache<String, String?> = caffeineBuilder<String, String?>().build()

suspend fun foo(): String? {
    return cache.get("key") { _ -> asyncFun("a") }
}

suspend fun asyncFun(s: String): String? {
    delay(1)
    when (s) {
        "a" -> return null
        else -> return s
    }
}

fun main() {
    runBlocking {
        println("key = ${foo()}")
    }
}

main()

1.3.1 is released with a getOrNull method that allows nulls.


QR Install & Update do not work

So i tried to update FBI but it gave me this error after some wating (sorry for the bad quality): https://i.imgur.com/3OyEfEN.jpg
after that the update in FBI didn't work i downloaded the version 2.4.7 and it gives me the same error.
QR/Network Install do not work either.
Using: N3DS EmuNAND 11.3.0-36E with Luma3DS

This error generally indicates a problem with your internet connection. Check your Internet settings and make sure you can connect with other apps.

Every other app can connect to the internet it's only happening in FBI.

Well, that error usually means the HTTP service couldn't establish a connection, so it doesn't seem likely to be an issue with FBI itself.

Update: Got it working by removing the static ip address and dns.


Transparent background will become black background

i transfer a picture which its background is transparent,hoever after editing,its background will become black

can you provide a sample project to reproduce this ?

Same issue happening earlier it was working fine


Search Does Not Include Enchantments

Mod version: 1.12.2-1.3.9
When searching for the title of an enchantment, such as "fortune", any items with the enchantment, including enchanted books, are not included in the results. This also leads to mismatches when syncing with JEI's search.

try #fortune

Oops, sorry for not catching that. Closing, then.


db: functional tests fail if run twice against same DB

I think this has something to do with the migrations table not being dropped.

Some steps to reproduce
Window 1:
$ rkt version
rkt version 0.15.0
appc version 0.7.4
$ sudo rkt run --interactive --net=host quay.io/coreos/postgres
...

Window 2:
$ ./git-version
09d8d8423cac115cfaf22ffde89c62e46a8f6cc9
$ DEX_TEST_DSN=postgres://postgres@localhost/postgres?sslmode=disable ./test
Running tests...
ok  	github.com/coreos/dex/connector	0.040s	coverage: 22.7% of statements
ok  	github.com/coreos/dex/db	0.068s	coverage: 6.4% of statements
ok  	github.com/coreos/dex/integration	3.191s	coverage: 0.0% of statements
ok  	github.com/coreos/dex/pkg/crypto	0.008s	coverage: 75.7% of statements
ok  	github.com/coreos/dex/pkg/flag	0.002s	coverage: 97.5% of statements
ok  	github.com/coreos/dex/pkg/http	0.010s	coverage: 72.1% of statements
ok  	github.com/coreos/dex/pkg/net	0.031s	coverage: 71.4% of statements
ok  	github.com/coreos/dex/pkg/time	0.007s	coverage: 100.0% of statements
ok  	github.com/coreos/dex/pkg/html	0.004s	coverage: 78.9% of statements
ok  	github.com/coreos/dex/functional/repo	19.941s	coverage: 60.0% of statements
ok  	github.com/coreos/dex/server	3.730s	coverage: 48.3% of statements
ok  	github.com/coreos/dex/session	0.011s	coverage: 75.3% of statements
ok  	github.com/coreos/dex/user	2.625s	coverage: 37.4% of statements
ok  	github.com/coreos/dex/user/api	0.007s	coverage: 82.4% of statements
ok  	github.com/coreos/dex/user/manager	0.505s	coverage: 68.1% of statements
ok  	github.com/coreos/dex/email	0.004s	coverage: 42.8% of statements
Checking gofmt...
Checking govet...
Success
$ DEX_TEST_DSN=postgres://postgres@localhost/postgres?sslmode=disable ./test
Running tests...
ok  	github.com/coreos/dex/connector	0.027s	coverage: 22.7% of statements
ERROR: Failed purging : <nil>
ERROR: Failed purging : <nil>
ERROR: Failed purging : <nil>
ERROR: Failed purging : <nil>
ERROR: Failed purging : <nil>
--- FAIL: TestGetPlannedMigrations (0.09s)
	migrate_test.go:40: expected non-empty migrations
FAIL
coverage: 6.4% of statements
FAIL	github.com/coreos/dex/db	0.103s
ok  	github.com/coreos/dex/integration	2.922s	coverage: 0.0% of statements
ok  	github.com/coreos/dex/pkg/crypto	0.012s	coverage: 75.7% of statements
ok  	github.com/coreos/dex/pkg/flag	0.014s	coverage: 97.5% of statements
ok  	github.com/coreos/dex/pkg/http	0.007s	coverage: 72.1% of statements
ok  	github.com/coreos/dex/pkg/net	0.012s	coverage: 71.4% of statements
ok  	github.com/coreos/dex/pkg/time	0.002s	coverage: 100.0% of statements
ok  	github.com/coreos/dex/pkg/html	0.004s	coverage: 78.9% of statements
ok  	github.com/coreos/dex/functional/repo	19.521s	coverage: 60.0% of statements
ok  	github.com/coreos/dex/server	3.493s	coverage: 48.3% of statements
ok  	github.com/coreos/dex/session	0.003s	coverage: 75.3% of statements
ok  	github.com/coreos/dex/user	2.262s	coverage: 37.4% of statements
ok  	github.com/coreos/dex/user/api	0.005s	coverage: 82.4% of statements
ok  	github.com/coreos/dex/user/manager	0.519s	coverage: 68.1% of statements
ok  	github.com/coreos/dex/email	0.005s	coverage: 42.8% of statements
$

Restarting the Postgres database fixes the error.

closed in #339


DPAT-2026 Establish project structure

Updated devcontainer to include a postgresql , the configuration is in here. Username and password are configured in there and can be changed if desired. Additionally a feature was added to the devcontainer which runs Docker in Docker. From a users perspective this means that postgresql is run in a container inside the devcontainer, and you can see the container running on the standard port 5432. You can connect to the container using the command:
psql -h localhost -U controlpanel

Good starting point 👷♀


Feature request from Micro.blog

Feature request by Khalid.

[x] Being able to change the text would be nice.
[x] Would be good to also have the stats of photos, videos, audio files, posts with titles, posts without titles, etc.
[x] Would be nice to display the stats by year. So you know how your blogging output meandered from year to year.
[x] Similarly, add the number of replies you have made.
[x] Being able to put this into a page (rather than as part of a theme). I would want to create a stats page dedicated to the above.
[ ] Cherry on the cake would be to have a small graph that shows the number of posts and when they went out, across the last year. Similar to something that is given in Feedbin.

All the changes includes other than chart, a separate issue [#3] exists for that. So, closing this issue.


Add licence

If planning to make this open-source I suggest adding a LICENCE.md to make this project used by others.
I think this is awesome!!

@gitirabassi i forgot, thanks for the reminder. adding an MIT license now.


[boost] build failure

Because closed https://github.com/microsoft/vcpkg/issues/20417
I tried to install boost again.
And its failed. Again.
So I again propose to make smoke-test before close issue - lets be a professionals!
Host Environment

OS: Windows
Compiler: latest msvs2019

To Reproduce
Steps to reproduce the behavior:
./vcpkg install boost
Failure logs
-- Downloading https://download.microsoft.com/download/a/5/2/a5207ca5-1203-491a-8fb8-906fd68ae623/msmpisetup.exe -> msmpisetup-10.1.12498.exe...
CMake Error at ports/msmpi/portfile.cmake:59 (message):
    Could not find:
      C:\Program Files/Microsoft MPI/Bin/mpiexec.exe
    Please install the MSMPI redistributable package before trying to install this port.
    The appropriate installer has been downloaded to:
      D:/Tmp/vcpkg/downloads/msmpisetup-10.1.12498.exe

Call Stack (most recent call first):
  scripts/ports.cmake:141 (include)

Error: Building package msmpi:x64-windows failed with: BUILD_FAILED

@yurybura I use clean clone vcpkg from here and just trying to install boost. The ful log:
D:\Tmp>SET currentPath=D:\Tmp\

D:\Tmp>git clone https://github.com/microsoft/vcpkg.git vcpkg
Cloning into 'vcpkg'...
remote: Enumerating objects: 127004, done.
remote: Counting objects: 100% (94/94), done.
remote: Compressing objects: 100% (21/21), done.
remote: Total 127004 (delta 81), reused 73 (delta 73), pack-reused 126910
Receiving objects: 100% (127004/127004), 41.61 MiB | 9.96 MiB/s, done.
Resolving deltas: 100% (78861/78861), done.
Updating files: 100% (8219/8219), done.

D:\Tmp>call D:\Tmp\/vcpkg/bootstrap-vcpkg.bat
Downloading https://github.com/microsoft/vcpkg-tool/releases/download/2021-09-10/vcpkg.exe -> D:\Tmp\vcpkg\vcpkg.exe... done.
Validating signature... done.

Telemetry
---------
vcpkg collects usage data in order to help us improve your experience.
The data collected by Microsoft is anonymous.
You can opt-out of telemetry by re-running the bootstrap-vcpkg script with -disableMetrics,
passing --disable-metrics to vcpkg on the command line,
or by setting the VCPKG_DISABLE_METRICS environment variable.

Read more about vcpkg telemetry at docs/about/privacy.md
Computing installation plan...
The following packages will be built and installed:
    boost[core]:x64-windows -> 1.77.0#1
  * boost-accumulators[core]:x64-windows -> 1.77.0
  * boost-algorithm[core]:x64-windows -> 1.77.0
  * boost-align[core]:x64-windows -> 1.77.0
  * boost-any[core]:x64-windows -> 1.77.0
  * boost-array[core]:x64-windows -> 1.77.0
  * boost-asio[core]:x64-windows -> 1.77.0
  * boost-assert[core]:x64-windows -> 1.77.0
  * boost-assign[core]:x64-windows -> 1.77.0
  * boost-atomic[core]:x64-windows -> 1.77.0
  * boost-beast[core]:x64-windows -> 1.77.0
  * boost-bimap[core]:x64-windows -> 1.77.0
  * boost-bind[core]:x64-windows -> 1.77.0
  * boost-build[core]:x64-windows -> 1.77.0
  * boost-callable-traits[core]:x64-windows -> 1.77.0
  * boost-chrono[core]:x64-windows -> 1.77.0
  * boost-circular-buffer[core]:x64-windows -> 1.77.0
  * boost-compatibility[core]:x64-windows -> 1.77.0
  * boost-compute[core]:x64-windows -> 1.77.0
  * boost-concept-check[core]:x64-windows -> 1.77.0
  * boost-config[core]:x64-windows -> 1.77.0#2
  * boost-container[core]:x64-windows -> 1.77.0
  * boost-container-hash[core]:x64-windows -> 1.77.0
  * boost-context[core]:x64-windows -> 1.77.0
  * boost-contract[core]:x64-windows -> 1.77.0
  * boost-conversion[core]:x64-windows -> 1.77.0
  * boost-convert[core]:x64-windows -> 1.77.0
  * boost-core[core]:x64-windows -> 1.77.0
  * boost-coroutine[core]:x64-windows -> 1.77.0
  * boost-coroutine2[core]:x64-windows -> 1.77.0
  * boost-crc[core]:x64-windows -> 1.77.0
  * boost-date-time[core]:x64-windows -> 1.77.0
  * boost-describe[core]:x64-windows -> 1.77.0
  * boost-detail[core]:x64-windows -> 1.77.0
  * boost-dll[core]:x64-windows -> 1.77.0
  * boost-dynamic-bitset[core]:x64-windows -> 1.77.0
  * boost-endian[core]:x64-windows -> 1.77.0
  * boost-exception[core]:x64-windows -> 1.77.0
  * boost-fiber[core]:x64-windows -> 1.77.0
  * boost-filesystem[core]:x64-windows -> 1.77.0
  * boost-flyweight[core]:x64-windows -> 1.77.0
  * boost-foreach[core]:x64-windows -> 1.77.0
  * boost-format[core]:x64-windows -> 1.77.0
  * boost-function[core]:x64-windows -> 1.77.0
  * boost-function-types[core]:x64-windows -> 1.77.0
  * boost-functional[core]:x64-windows -> 1.77.0
  * boost-fusion[core]:x64-windows -> 1.77.0
  * boost-geometry[core]:x64-windows -> 1.77.0
  * boost-gil[core]:x64-windows -> 1.77.0#1
  * boost-graph[core]:x64-windows -> 1.77.0
  * boost-hana[core]:x64-windows -> 1.77.0
  * boost-heap[core]:x64-windows -> 1.77.0
  * boost-histogram[core]:x64-windows -> 1.77.0
  * boost-hof[core]:x64-windows -> 1.77.0
  * boost-icl[core]:x64-windows -> 1.77.0
  * boost-integer[core]:x64-windows -> 1.77.0
  * boost-interprocess[core]:x64-windows -> 1.77.0
  * boost-interval[core]:x64-windows -> 1.77.0
  * boost-intrusive[core]:x64-windows -> 1.77.0
  * boost-io[core]:x64-windows -> 1.77.0
  * boost-iostreams[bzip2,core,lzma,zlib,zstd]:x64-windows -> 1.77.0#1
  * boost-iterator[core]:x64-windows -> 1.77.0
  * boost-json[core]:x64-windows -> 1.77.0
  * boost-lambda[core]:x64-windows -> 1.77.0
  * boost-lambda2[core]:x64-windows -> 1.77.0
  * boost-leaf[core]:x64-windows -> 1.77.0
  * boost-lexical-cast[core]:x64-windows -> 1.77.0
  * boost-local-function[core]:x64-windows -> 1.77.0
  * boost-locale[core]:x64-windows -> 1.77.0
  * boost-lockfree[core]:x64-windows -> 1.77.0
  * boost-log[core]:x64-windows -> 1.77.0
  * boost-logic[core]:x64-windows -> 1.77.0
  * boost-math[core]:x64-windows -> 1.77.0
  * boost-metaparse[core]:x64-windows -> 1.77.0
  * boost-modular-build-helper[core]:x64-windows -> 1.77.0#1
  * boost-move[core]:x64-windows -> 1.77.0
  * boost-mp11[core]:x64-windows -> 1.77.0
  * boost-mpi[core]:x64-windows -> 1.77.0
  * boost-mpl[core]:x64-windows -> 1.77.0
  * boost-msm[core]:x64-windows -> 1.77.0
  * boost-multi-array[core]:x64-windows -> 1.77.0
  * boost-multi-index[core]:x64-windows -> 1.77.0
  * boost-multiprecision[core]:x64-windows -> 1.77.0
  * boost-nowide[core]:x64-windows -> 1.77.0
  * boost-numeric-conversion[core]:x64-windows -> 1.77.0
  * boost-odeint[core]:x64-windows -> 1.77.0#1
  * boost-optional[core]:x64-windows -> 1.77.0
  * boost-outcome[core]:x64-windows -> 1.77.0
  * boost-parameter[core]:x64-windows -> 1.77.0
  * boost-parameter-python[core]:x64-windows -> 1.77.0
  * boost-pfr[core]:x64-windows -> 1.77.0
  * boost-phoenix[core]:x64-windows -> 1.77.0
  * boost-poly-collection[core]:x64-windows -> 1.77.0
  * boost-polygon[core]:x64-windows -> 1.77.0
  * boost-pool[core]:x64-windows -> 1.77.0
  * boost-predef[core]:x64-windows -> 1.77.0
  * boost-preprocessor[core]:x64-windows -> 1.77.0
  * boost-process[core]:x64-windows -> 1.77.0#2
  * boost-program-options[core]:x64-windows -> 1.77.0
  * boost-property-map[core]:x64-windows -> 1.77.0
  * boost-property-map-parallel[core]:x64-windows -> 1.77.0
  * boost-property-tree[core]:x64-windows -> 1.77.0
  * boost-proto[core]:x64-windows -> 1.77.0
  * boost-ptr-container[core]:x64-windows -> 1.77.0
  * boost-python[core,python3]:x64-windows -> 1.77.0#1
  * boost-qvm[core]:x64-windows -> 1.77.0
  * boost-random[core]:x64-windows -> 1.77.0
  * boost-range[core]:x64-windows -> 1.77.0
  * boost-ratio[core]:x64-windows -> 1.77.0
  * boost-rational[core]:x64-windows -> 1.77.0
  * boost-regex[core]:x64-windows -> 1.77.0
  * boost-safe-numerics[core]:x64-windows -> 1.77.0
  * boost-scope-exit[core]:x64-windows -> 1.77.0
  * boost-serialization[core]:x64-windows -> 1.77.0
  * boost-signals2[core]:x64-windows -> 1.77.0
  * boost-smart-ptr[core]:x64-windows -> 1.77.0
  * boost-sort[core]:x64-windows -> 1.77.0
  * boost-spirit[core]:x64-windows -> 1.77.0
  * boost-stacktrace[core]:x64-windows -> 1.77.0
  * boost-statechart[core]:x64-windows -> 1.77.0
  * boost-static-assert[core]:x64-windows -> 1.77.0
  * boost-static-string[core]:x64-windows -> 1.77.0
  * boost-stl-interfaces[core]:x64-windows -> 1.77.0
  * boost-system[core]:x64-windows -> 1.77.0
  * boost-test[core]:x64-windows -> 1.77.0
  * boost-thread[core]:x64-windows -> 1.77.0
  * boost-throw-exception[core]:x64-windows -> 1.77.0
  * boost-timer[core]:x64-windows -> 1.77.0
  * boost-tokenizer[core]:x64-windows -> 1.77.0
  * boost-tti[core]:x64-windows -> 1.77.0
  * boost-tuple[core]:x64-windows -> 1.77.0
  * boost-type-erasure[core]:x64-windows -> 1.77.0
  * boost-type-index[core]:x64-windows -> 1.77.0
  * boost-type-traits[core]:x64-windows -> 1.77.0
  * boost-typeof[core]:x64-windows -> 1.77.0
  * boost-ublas[core]:x64-windows -> 1.77.0
  * boost-uninstall[core]:x64-windows -> 1.77.0
  * boost-units[core]:x64-windows -> 1.77.0
  * boost-unordered[core]:x64-windows -> 1.77.0
  * boost-utility[core]:x64-windows -> 1.77.0
  * boost-uuid[core]:x64-windows -> 1.77.0
  * boost-variant[core]:x64-windows -> 1.77.0
  * boost-variant2[core]:x64-windows -> 1.77.0
  * boost-vcpkg-helpers[core]:x64-windows -> 1.77.0
  * boost-vmd[core]:x64-windows -> 1.77.0
  * boost-wave[core]:x64-windows -> 1.77.0
  * boost-winapi[core]:x64-windows -> 1.77.0
  * boost-xpressive[core]:x64-windows -> 1.77.0
  * boost-yap[core]:x64-windows -> 1.77.0
  * bzip2[core]:x64-windows -> 1.0.8#2
  * expat[core]:x64-windows -> 2.4.1
  * libffi[core]:x64-windows -> 3.4.2#2
  * liblzma[core]:x64-windows -> 5.2.5#3
  * mpi[core]:x64-windows -> 1#2
  * msmpi[core]:x64-windows -> 10.1.12498#2
  * openssl[core]:x64-windows -> 1.1.1l#1
  * python3[core]:x64-windows -> 3.10.0
  * sqlite3[core]:x64-windows -> 3.36.0#1
  * vcpkg-cmake[core]:x64-windows -> 2021-09-13
  * vcpkg-cmake-config[core]:x64-windows -> 2021-09-27
  * zlib[core]:x64-windows -> 1.2.11#13
  * zstd[core]:x64-windows -> 1.5.0
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
A suitable version of powershell-core was not found (required v7.1.4). Downloading portable powershell-core v7.1.4...
Downloading powershell-core...
  https://github.com/PowerShell/PowerShell/releases/download/v7.1.4/PowerShell-7.1.4-win-x86.zip -> D:\Tmp\vcpkg\downloads\PowerShell-7.1.4-win-x86.zip
Extracting powershell-core...
A suitable version of 7zip was not found (required v19.0.0). Downloading portable 7zip v19.0.0...
Downloading 7zip...
  https://www.7-zip.org/a/7z1900-x64.msi -> D:\Tmp\vcpkg\downloads\7z1900-x64.msi
Extracting 7zip...
Restored 146 packages from C:\Users\AeroSun\AppData\Local\vcpkg\archives in 2.754 s. Use --debug to see more details.
Starting package 1/162: boost-uninstall:x64-windows
Installing package boost-uninstall[core]:x64-windows...
Elapsed time for package boost-uninstall:x64-windows: 9.382 ms
Starting package 2/162: boost-vcpkg-helpers:x64-windows
Installing package boost-vcpkg-helpers[core]:x64-windows...
Elapsed time for package boost-vcpkg-helpers:x64-windows: 5.915 ms
Starting package 3/162: boost-config:x64-windows
Installing package boost-config[core]:x64-windows...
Elapsed time for package boost-config:x64-windows: 399.1 ms
Starting package 4/162: boost-assert:x64-windows
Installing package boost-assert[core]:x64-windows...
Elapsed time for package boost-assert:x64-windows: 14.06 ms
Starting package 5/162: boost-static-assert:x64-windows
Installing package boost-static-assert[core]:x64-windows...
Elapsed time for package boost-static-assert:x64-windows: 10.87 ms
Starting package 6/162: boost-core:x64-windows
Installing package boost-core[core]:x64-windows...
Elapsed time for package boost-core:x64-windows: 77.62 ms
Starting package 7/162: boost-throw-exception:x64-windows
Installing package boost-throw-exception[core]:x64-windows...
Elapsed time for package boost-throw-exception:x64-windows: 12 ms
Starting package 8/162: boost-array:x64-windows
Installing package boost-array[core]:x64-windows...
Elapsed time for package boost-array:x64-windows: 10.27 ms
Starting package 9/162: boost-preprocessor:x64-windows
Installing package boost-preprocessor[core]:x64-windows...
Elapsed time for package boost-preprocessor:x64-windows: 556.6 ms
Starting package 10/162: boost-type-traits:x64-windows
Installing package boost-type-traits[core]:x64-windows...
Elapsed time for package boost-type-traits:x64-windows: 278.2 ms
Starting package 11/162: boost-concept-check:x64-windows
Installing package boost-concept-check[core]:x64-windows...
Elapsed time for package boost-concept-check:x64-windows: 32.51 ms
Starting package 12/162: boost-predef:x64-windows
Installing package boost-predef[core]:x64-windows...
Elapsed time for package boost-predef:x64-windows: 219.6 ms
Starting package 13/162: boost-winapi:x64-windows
Installing package boost-winapi[core]:x64-windows...
Elapsed time for package boost-winapi:x64-windows: 170.5 ms
Starting package 14/162: boost-move:x64-windows
Installing package boost-move[core]:x64-windows...
Elapsed time for package boost-move:x64-windows: 70.38 ms
Starting package 15/162: boost-circular-buffer:x64-windows
Installing package boost-circular-buffer[core]:x64-windows...
Elapsed time for package boost-circular-buffer:x64-windows: 18.39 ms
Starting package 16/162: boost-detail:x64-windows
Installing package boost-detail[core]:x64-windows...
Elapsed time for package boost-detail:x64-windows: 41.09 ms
Starting package 17/162: boost-integer:x64-windows
Installing package boost-integer[core]:x64-windows...
Elapsed time for package boost-integer:x64-windows: 27.83 ms
Starting package 18/162: boost-container-hash:x64-windows
Installing package boost-container-hash[core]:x64-windows...
Elapsed time for package boost-container-hash:x64-windows: 24.72 ms
Starting package 19/162: boost-io:x64-windows
Installing package boost-io[core]:x64-windows...
Elapsed time for package boost-io:x64-windows: 19.98 ms
Starting package 20/162: boost-utility:x64-windows
Installing package boost-utility[core]:x64-windows...
Elapsed time for package boost-utility:x64-windows: 43.43 ms
Starting package 21/162: boost-mpl:x64-windows
Installing package boost-mpl[core]:x64-windows...
Elapsed time for package boost-mpl:x64-windows: 1.397 s
Starting package 22/162: boost-function-types:x64-windows
Installing package boost-function-types[core]:x64-windows...
Elapsed time for package boost-function-types:x64-windows: 112.5 ms
Starting package 23/162: boost-tuple:x64-windows
Installing package boost-tuple[core]:x64-windows...
Elapsed time for package boost-tuple:x64-windows: 17.73 ms
Starting package 24/162: boost-typeof:x64-windows
Installing package boost-typeof[core]:x64-windows...
Elapsed time for package boost-typeof:x64-windows: 79.61 ms
Starting package 25/162: boost-fusion:x64-windows
Installing package boost-fusion[core]:x64-windows...
Elapsed time for package boost-fusion:x64-windows: 1.351 s
Starting package 26/162: boost-smart-ptr:x64-windows
Installing package boost-smart-ptr[core]:x64-windows...
Elapsed time for package boost-smart-ptr:x64-windows: 149.4 ms
Starting package 27/162: boost-conversion:x64-windows
Installing package boost-conversion[core]:x64-windows...
Elapsed time for package boost-conversion:x64-windows: 16.92 ms
Starting package 28/162: boost-optional:x64-windows
Installing package boost-optional[core]:x64-windows...
Elapsed time for package boost-optional:x64-windows: 32.95 ms
Starting package 29/162: boost-iterator:x64-windows
Installing package boost-iterator[core]:x64-windows...
Elapsed time for package boost-iterator:x64-windows: 63.33 ms
Starting package 30/162: boost-numeric-conversion:x64-windows
Installing package boost-numeric-conversion[core]:x64-windows...
Elapsed time for package boost-numeric-conversion:x64-windows: 47.62 ms
Starting package 31/162: boost-bind:x64-windows
Installing package boost-bind[core]:x64-windows...
Elapsed time for package boost-bind:x64-windows: 38.37 ms
Starting package 32/162: boost-type-index:x64-windows
Installing package boost-type-index[core]:x64-windows...
Elapsed time for package boost-type-index:x64-windows: 31.56 ms
Starting package 33/162: boost-function:x64-windows
Installing package boost-function[core]:x64-windows...
Elapsed time for package boost-function:x64-windows: 41.44 ms
Starting package 34/162: boost-mp11:x64-windows
Installing package boost-mp11[core]:x64-windows...
Elapsed time for package boost-mp11:x64-windows: 50.9 ms
Starting package 35/162: boost-parameter:x64-windows
Installing package boost-parameter[core]:x64-windows...
Elapsed time for package boost-parameter:x64-windows: 146.2 ms
Starting package 36/162: boost-build:x64-windows
Installing package boost-build[core]:x64-windows...
Elapsed time for package boost-build:x64-windows: 1.386 s
Starting package 37/162: boost-modular-build-helper:x64-windows
Installing package boost-modular-build-helper[core]:x64-windows...
Elapsed time for package boost-modular-build-helper:x64-windows: 18.83 ms
Starting package 38/162: vcpkg-cmake:x64-windows
Installing package vcpkg-cmake[core]:x64-windows...
Elapsed time for package vcpkg-cmake:x64-windows: 19.39 ms
Starting package 39/162: boost-regex:x64-windows
Installing package boost-regex[core]:x64-windows...
Elapsed time for package boost-regex:x64-windows: 162 ms
Starting package 40/162: boost-range:x64-windows
Installing package boost-range[core]:x64-windows...
Elapsed time for package boost-range:x64-windows: 216.8 ms
Starting package 41/162: boost-endian:x64-windows
Installing package boost-endian[core]:x64-windows...
Elapsed time for package boost-endian:x64-windows: 33.56 ms
Starting package 42/162: boost-foreach:x64-windows
Installing package boost-foreach[core]:x64-windows...
Elapsed time for package boost-foreach:x64-windows: 16.32 ms
Starting package 43/162: boost-proto:x64-windows
Installing package boost-proto[core]:x64-windows...
Elapsed time for package boost-proto:x64-windows: 224.1 ms
Starting package 44/162: boost-phoenix:x64-windows
Installing package boost-phoenix[core]:x64-windows...
Elapsed time for package boost-phoenix:x64-windows: 472.2 ms
Starting package 45/162: boost-pool:x64-windows
Installing package boost-pool[core]:x64-windows...
Elapsed time for package boost-pool:x64-windows: 36.95 ms
Starting package 46/162: boost-exception:x64-windows
Installing package boost-exception[core]:x64-windows...
Elapsed time for package boost-exception:x64-windows: 52.16 ms
Starting package 47/162: boost-intrusive:x64-windows
Installing package boost-intrusive[core]:x64-windows...
Elapsed time for package boost-intrusive:x64-windows: 137.1 ms
Starting package 48/162: boost-container:x64-windows
Installing package boost-container[core]:x64-windows...
Elapsed time for package boost-container:x64-windows: 158.3 ms
Starting package 49/162: boost-unordered:x64-windows
Installing package boost-unordered[core]:x64-windows...
Elapsed time for package boost-unordered:x64-windows: 27.53 ms
Starting package 50/162: boost-algorithm:x64-windows
Installing package boost-algorithm[core]:x64-windows...
Elapsed time for package boost-algorithm:x64-windows: 129.8 ms
Starting package 51/162: boost-align:x64-windows
Installing package boost-align[core]:x64-windows...
Elapsed time for package boost-align:x64-windows: 79.11 ms
Starting package 52/162: boost-atomic:x64-windows
Installing package boost-atomic[core]:x64-windows...
Elapsed time for package boost-atomic:x64-windows: 203.4 ms
Starting package 53/162: boost-rational:x64-windows
Installing package boost-rational[core]:x64-windows...
Elapsed time for package boost-rational:x64-windows: 17.17 ms
Starting package 54/162: boost-ratio:x64-windows
Installing package boost-ratio[core]:x64-windows...
Elapsed time for package boost-ratio:x64-windows: 56.78 ms
Starting package 55/162: boost-system:x64-windows
Installing package boost-system[core]:x64-windows...
Elapsed time for package boost-system:x64-windows: 68.93 ms
Starting package 56/162: boost-chrono:x64-windows
Installing package boost-chrono[core]:x64-windows...
Elapsed time for package boost-chrono:x64-windows: 87.47 ms
Starting package 57/162: boost-lexical-cast:x64-windows
Installing package boost-lexical-cast[core]:x64-windows...
Elapsed time for package boost-lexical-cast:x64-windows: 33.86 ms
Starting package 58/162: boost-tokenizer:x64-windows
Installing package boost-tokenizer[core]:x64-windows...
Elapsed time for package boost-tokenizer:x64-windows: 18.17 ms
Starting package 59/162: boost-date-time:x64-windows
Installing package boost-date-time[core]:x64-windows...
Elapsed time for package boost-date-time:x64-windows: 160.6 ms
Starting package 60/162: boost-thread:x64-windows
Installing package boost-thread[core]:x64-windows...
Elapsed time for package boost-thread:x64-windows: 239.1 ms
Starting package 61/162: boost-variant:x64-windows
Installing package boost-variant[core]:x64-windows...
Elapsed time for package boost-variant:x64-windows: 65.07 ms
Starting package 62/162: boost-spirit:x64-windows
Installing package boost-spirit[core]:x64-windows...
Elapsed time for package boost-spirit:x64-windows: 1.508 s
Starting package 63/162: boost-serialization:x64-windows
Installing package boost-serialization[core]:x64-windows...
Elapsed time for package boost-serialization:x64-windows: 300.8 ms
Starting package 64/162: boost-filesystem:x64-windows
Installing package boost-filesystem[core]:x64-windows...
Elapsed time for package boost-filesystem:x64-windows: 46.12 ms
Starting package 65/162: boost-any:x64-windows
Installing package boost-any[core]:x64-windows...
Elapsed time for package boost-any:x64-windows: 21.04 ms
Starting package 66/162: boost-format:x64-windows
Installing package boost-format[core]:x64-windows...
Elapsed time for package boost-format:x64-windows: 41.22 ms
Starting package 67/162: boost-multi-index:x64-windows
Installing package boost-multi-index[core]:x64-windows...
Elapsed time for package boost-multi-index:x64-windows: 123.6 ms
Starting package 68/162: boost-property-tree:x64-windows
Installing package boost-property-tree[core]:x64-windows...
Elapsed time for package boost-property-tree:x64-windows: 64.48 ms
Starting package 69/162: boost-dynamic-bitset:x64-windows
Installing package boost-dynamic-bitset[core]:x64-windows...
Elapsed time for package boost-dynamic-bitset:x64-windows: 25.49 ms
Starting package 70/162: boost-random:x64-windows
Installing package boost-random[core]:x64-windows...
Elapsed time for package boost-random:x64-windows: 132.7 ms
Starting package 71/162: boost-tti:x64-windows
Installing package boost-tti[core]:x64-windows...
Elapsed time for package boost-tti:x64-windows: 107.3 ms
Starting package 72/162: boost-uuid:x64-windows
Installing package boost-uuid[core]:x64-windows...
Elapsed time for package boost-uuid:x64-windows: 52.2 ms
Starting package 73/162: boost-compute:x64-windows
Installing package boost-compute[core]:x64-windows...
Elapsed time for package boost-compute:x64-windows: 420.2 ms
Starting package 74/162: boost-logic:x64-windows
Installing package boost-logic[core]:x64-windows...
Elapsed time for package boost-logic:x64-windows: 20.54 ms
Starting package 75/162: boost-interval:x64-windows
Installing package boost-interval[core]:x64-windows...
Elapsed time for package boost-interval:x64-windows: 62.46 ms
Starting package 76/162: boost-ublas:x64-windows
Installing package boost-ublas[core]:x64-windows...
Elapsed time for package boost-ublas:x64-windows: 106.8 ms
Starting package 77/162: boost-accumulators:x64-windows
Installing package boost-accumulators[core]:x64-windows...
Elapsed time for package boost-accumulators:x64-windows: 121 ms
Starting package 78/162: boost-context:x64-windows
Installing package boost-context[core]:x64-windows...
Elapsed time for package boost-context:x64-windows: 59.67 ms
Starting package 79/162: boost-coroutine:x64-windows
Installing package boost-coroutine[core]:x64-windows...
Elapsed time for package boost-coroutine:x64-windows: 67.24 ms
Starting package 80/162: openssl:x64-windows
Installing package openssl[core]:x64-windows...
Elapsed time for package openssl:x64-windows: 192.2 ms
Starting package 81/162: boost-asio:x64-windows
Installing package boost-asio[core]:x64-windows...
Elapsed time for package boost-asio:x64-windows: 696.1 ms
Starting package 82/162: boost-ptr-container:x64-windows
Installing package boost-ptr-container[core]:x64-windows...
Elapsed time for package boost-ptr-container:x64-windows: 68.05 ms
Starting package 83/162: boost-assign:x64-windows
Installing package boost-assign[core]:x64-windows...
Elapsed time for package boost-assign:x64-windows: 36.07 ms
Starting package 84/162: boost-beast:x64-windows
Installing package boost-beast[core]:x64-windows...
Elapsed time for package boost-beast:x64-windows: 297.8 ms
Starting package 85/162: boost-lambda:x64-windows
Installing package boost-lambda[core]:x64-windows...
Elapsed time for package boost-lambda:x64-windows: 55.52 ms
Starting package 86/162: boost-bimap:x64-windows
Installing package boost-bimap[core]:x64-windows...
Elapsed time for package boost-bimap:x64-windows: 135.4 ms
Starting package 87/162: boost-callable-traits:x64-windows
Installing package boost-callable-traits[core]:x64-windows...
Elapsed time for package boost-callable-traits:x64-windows: 98.62 ms
Starting package 88/162: boost-compatibility:x64-windows
Installing package boost-compatibility[core]:x64-windows...
Elapsed time for package boost-compatibility:x64-windows: 37.18 ms
Starting package 89/162: boost-contract:x64-windows
Installing package boost-contract[core]:x64-windows...
Elapsed time for package boost-contract:x64-windows: 90.39 ms
Starting package 90/162: boost-math:x64-windows
Installing package boost-math[core]:x64-windows...
Elapsed time for package boost-math:x64-windows: 581.7 ms
Starting package 91/162: boost-convert:x64-windows
Installing package boost-convert[core]:x64-windows...
Elapsed time for package boost-convert:x64-windows: 37.39 ms
Starting package 92/162: boost-coroutine2:x64-windows
Installing package boost-coroutine2[core]:x64-windows...
Elapsed time for package boost-coroutine2:x64-windows: 42.21 ms
Starting package 93/162: boost-crc:x64-windows
Installing package boost-crc[core]:x64-windows...
Elapsed time for package boost-crc:x64-windows: 18.83 ms
Starting package 94/162: boost-describe:x64-windows
Installing package boost-describe[core]:x64-windows...
Elapsed time for package boost-describe:x64-windows: 34.35 ms
Starting package 95/162: boost-dll:x64-windows
Installing package boost-dll[core]:x64-windows...
Elapsed time for package boost-dll:x64-windows: 52.57 ms
Starting package 96/162: boost-fiber:x64-windows
Installing package boost-fiber[core]:x64-windows...
Elapsed time for package boost-fiber:x64-windows: 104.8 ms
Starting package 97/162: boost-interprocess:x64-windows
Installing package boost-interprocess[core]:x64-windows...
Elapsed time for package boost-interprocess:x64-windows: 218.1 ms
Starting package 98/162: boost-flyweight:x64-windows
Installing package boost-flyweight[core]:x64-windows...
Elapsed time for package boost-flyweight:x64-windows: 67.63 ms
Starting package 99/162: boost-functional:x64-windows
Installing package boost-functional[core]:x64-windows...
Elapsed time for package boost-functional:x64-windows: 29.48 ms
Starting package 100/162: boost-multiprecision:x64-windows
Installing package boost-multiprecision[core]:x64-windows...
Elapsed time for package boost-multiprecision:x64-windows: 106.1 ms
Starting package 101/162: boost-polygon:x64-windows
Installing package boost-polygon[core]:x64-windows...
Elapsed time for package boost-polygon:x64-windows: 91.62 ms
Starting package 102/162: boost-qvm:x64-windows
Installing package boost-qvm[core]:x64-windows...
Elapsed time for package boost-qvm:x64-windows: 121 ms
Starting package 103/162: boost-variant2:x64-windows
Installing package boost-variant2[core]:x64-windows...
Elapsed time for package boost-variant2:x64-windows: 19.62 ms
Starting package 104/162: boost-geometry:x64-windows
Installing package boost-geometry[core]:x64-windows...
Elapsed time for package boost-geometry:x64-windows: 1.28 s
Starting package 105/162: boost-gil:x64-windows
Installing package boost-gil[core]:x64-windows...
Elapsed time for package boost-gil:x64-windows: 270.8 ms
Starting package 106/162: boost-property-map:x64-windows
Installing package boost-property-map[core]:x64-windows...
Elapsed time for package boost-property-map:x64-windows: 29.31 ms
Starting package 107/162: boost-xpressive:x64-windows
Installing package boost-xpressive[core]:x64-windows...
Elapsed time for package boost-xpressive:x64-windows: 162.8 ms
Starting package 108/162: boost-graph:x64-windows
Installing package boost-graph[core]:x64-windows...
Elapsed time for package boost-graph:x64-windows: 259.9 ms
Starting package 109/162: boost-hana:x64-windows
Installing package boost-hana[core]:x64-windows...
Elapsed time for package boost-hana:x64-windows: 553.2 ms
Starting package 110/162: boost-heap:x64-windows
Installing package boost-heap[core]:x64-windows...
Elapsed time for package boost-heap:x64-windows: 38.25 ms
Starting package 111/162: boost-histogram:x64-windows
Installing package boost-histogram[core]:x64-windows...
Elapsed time for package boost-histogram:x64-windows: 116.4 ms
Starting package 112/162: boost-hof:x64-windows
Installing package boost-hof[core]:x64-windows...
Elapsed time for package boost-hof:x64-windows: 111.8 ms
Starting package 113/162: boost-icl:x64-windows
Installing package boost-icl[core]:x64-windows...
Elapsed time for package boost-icl:x64-windows: 155.4 ms
Starting package 114/162: bzip2:x64-windows
Installing package bzip2[core]:x64-windows...
Elapsed time for package bzip2:x64-windows: 34.87 ms
Starting package 115/162: vcpkg-cmake-config:x64-windows
Installing package vcpkg-cmake-config[core]:x64-windows...
Elapsed time for package vcpkg-cmake-config:x64-windows: 22 ms
Starting package 116/162: liblzma:x64-windows
Installing package liblzma[core]:x64-windows...
Elapsed time for package liblzma:x64-windows: 57.84 ms
Starting package 117/162: zlib:x64-windows
Installing package zlib[core]:x64-windows...
Elapsed time for package zlib:x64-windows: 34.27 ms
Starting package 118/162: zstd:x64-windows
Installing package zstd[core]:x64-windows...
Elapsed time for package zstd:x64-windows: 43.27 ms
Starting package 119/162: boost-iostreams:x64-windows
Installing package boost-iostreams[bzip2,core,lzma,zlib,zstd]:x64-windows...
Elapsed time for package boost-iostreams:x64-windows: 181.6 ms
Starting package 120/162: boost-json:x64-windows
Installing package boost-json[core]:x64-windows...
Elapsed time for package boost-json:x64-windows: 133.5 ms
Starting package 121/162: boost-lambda2:x64-windows
Installing package boost-lambda2[core]:x64-windows...
Elapsed time for package boost-lambda2:x64-windows: 23.77 ms
Starting package 122/162: boost-leaf:x64-windows
Installing package boost-leaf[core]:x64-windows...
Elapsed time for package boost-leaf:x64-windows: 41.12 ms
Starting package 123/162: boost-scope-exit:x64-windows
Installing package boost-scope-exit[core]:x64-windows...
Elapsed time for package boost-scope-exit:x64-windows: 22.6 ms
Starting package 124/162: boost-local-function:x64-windows
Installing package boost-local-function[core]:x64-windows...
Elapsed time for package boost-local-function:x64-windows: 80.86 ms
Starting package 125/162: boost-locale:x64-windows
Installing package boost-locale[core]:x64-windows...
Elapsed time for package boost-locale:x64-windows: 66.81 ms
Starting package 126/162: boost-lockfree:x64-windows
Installing package boost-lockfree[core]:x64-windows...
Elapsed time for package boost-lockfree:x64-windows: 36.24 ms
Starting package 127/162: boost-log:x64-windows
Installing package boost-log[core]:x64-windows...
Elapsed time for package boost-log:x64-windows: 359.7 ms
Starting package 128/162: boost-metaparse:x64-windows
Installing package boost-metaparse[core]:x64-windows...
Elapsed time for package boost-metaparse:x64-windows: 389.9 ms
Starting package 129/162: boost-msm:x64-windows
Installing package boost-msm[core]:x64-windows...
Elapsed time for package boost-msm:x64-windows: 85.77 ms
Starting package 130/162: boost-multi-array:x64-windows
Installing package boost-multi-array[core]:x64-windows...
Elapsed time for package boost-multi-array:x64-windows: 43.37 ms
Starting package 131/162: boost-nowide:x64-windows
Installing package boost-nowide[core]:x64-windows...
Elapsed time for package boost-nowide:x64-windows: 52.95 ms
Starting package 132/162: boost-units:x64-windows
Installing package boost-units[core]:x64-windows...
Elapsed time for package boost-units:x64-windows: 400.8 ms
Starting package 133/162: boost-odeint:x64-windows
Installing package boost-odeint[core]:x64-windows...
Elapsed time for package boost-odeint:x64-windows: 234.7 ms
Starting package 134/162: boost-outcome:x64-windows
Installing package boost-outcome[core]:x64-windows...
Elapsed time for package boost-outcome:x64-windows: 101.1 ms
Starting package 135/162: expat:x64-windows
Installing package expat[core]:x64-windows...
Elapsed time for package expat:x64-windows: 44.44 ms
Starting package 136/162: libffi:x64-windows
Installing package libffi[core]:x64-windows...
Elapsed time for package libffi:x64-windows: 39.33 ms
Starting package 137/162: sqlite3:x64-windows
Installing package sqlite3[core]:x64-windows...
Elapsed time for package sqlite3:x64-windows: 41.68 ms
Starting package 138/162: python3:x64-windows
Installing package python3[core]:x64-windows...
Elapsed time for package python3:x64-windows: 4.323 s
Starting package 139/162: boost-python:x64-windows
Installing package boost-python[core,python3]:x64-windows...
Elapsed time for package boost-python:x64-windows: 284.1 ms
Starting package 140/162: boost-parameter-python:x64-windows
Installing package boost-parameter-python[core]:x64-windows...
Elapsed time for package boost-parameter-python:x64-windows: 31.04 ms
Starting package 141/162: boost-pfr:x64-windows
Installing package boost-pfr[core]:x64-windows...
Elapsed time for package boost-pfr:x64-windows: 64 ms
Starting package 142/162: boost-vmd:x64-windows
Installing package boost-vmd[core]:x64-windows...
Elapsed time for package boost-vmd:x64-windows: 207.6 ms
Starting package 143/162: boost-type-erasure:x64-windows
Installing package boost-type-erasure[core]:x64-windows...
Elapsed time for package boost-type-erasure:x64-windows: 99.82 ms
Starting package 144/162: boost-poly-collection:x64-windows
Installing package boost-poly-collection[core]:x64-windows...
Elapsed time for package boost-poly-collection:x64-windows: 66.41 ms
Starting package 145/162: boost-process:x64-windows
Installing package boost-process[core]:x64-windows...
Elapsed time for package boost-process:x64-windows: 164.2 ms
Starting package 146/162: boost-program-options:x64-windows
Installing package boost-program-options[core]:x64-windows...
Elapsed time for package boost-program-options:x64-windows: 56.63 ms
Starting package 147/162: msmpi:x64-windows
Building package msmpi[core]:x64-windows...
-- Downloading https://download.microsoft.com/download/a/5/2/a5207ca5-1203-491a-8fb8-906fd68ae623/msmpisdk.msi -> msmpisdk-10.1.12498-b0087dfd.msi...
-- Downloading https://download.microsoft.com/download/a/5/2/a5207ca5-1203-491a-8fb8-906fd68ae623/msmpisetup.exe -> msmpisetup-10.1.12498.exe...
CMake Error at ports/msmpi/portfile.cmake:59 (message):
    Could not find:
      C:\Program Files/Microsoft MPI/Bin/mpiexec.exe
    Please install the MSMPI redistributable package before trying to install this port.
    The appropriate installer has been downloaded to:
      D:/Tmp/vcpkg/downloads/msmpisetup-10.1.12498.exe

Call Stack (most recent call first):
  scripts/ports.cmake:141 (include)

Error: Building package msmpi:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: msmpi:x64-windows
  Vcpkg version: 2021-09-10-2059ef11aa6067e6f59b0d939c5d17e3c5c47d3e

Additionally, attach any relevant sections from the log files above.
Hit ENTER to continue...


SYCL. Add data initialization for training

Hi,
I continue adding of sycl support (https://github.com/dmlc/xgboost/pull/10216, https://github.com/dmlc/xgboost/pull/10174 etc).
By this PR I add the next part of the training-related code for the sycl devices. Here I add data initialization and the related tests.
This PR itself doesn't add any new functional, but I plan to combine all related parts one by one to a launchable sycl-training.

Hi @trivialfis ,
Checks failures are not related to the PR content:
Type and format checks for the Python package:

Build wheel for macosx_x86_64:

Build wheel for macosx_arm64:

Thank you for the heads up. The issue is being fixed I believe: https://github.com/actions/setup-python/issues/850

Hi @trivialfis ,
what is your opinion about this changes?


MXKSoundPlayer

I tried to make MXKSoundPlayer as simple as it could be. It suites for tasks of MXKCallViewController and can be improved in the future. There are problems with background music and MXCallViewController since MXKCallViewController doesn't handle all cases. With my PR there is no such problem. It also fixes 1283 and the problem with sound after MXKCallViewController is dismissed (this problem is reproduced in the last buid from TestFlight. I mentioned about it to you earlier).
NOTE: It works great without CallKit but if you try to add CallKit you will notice that after the call is connected, the sound is gone. I have trying to figure out what the problem is. It's obviously that it's something connected with AVAudioSession but i can't find what is wrong.

Signed-off-by: Denis Morozov<EMAIL_ADDRESS>


is there a way to start with a collapsed listview and then expand on click?

by default you see all the expanded rows and I would like to change this behavior.

for (int i = comments.size(); i > 0; i--) {
            if (mAdapter.getItemAt(i).getChildren().size() > 0) {

                mAdapter.collapseGroup(i);
            }

        }

it will collapse by default


Delete manifests/s/SmartSoft/SmartFTP/10.0.2968.0 directory

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@wingetbot run


fix(athena): Enable use of dataframe type, in athena2pyarrow type

Feature or Bugfix

Bugfix

Detail
Fixing a bug of failing to save a dataframe to parquet files, when the range of the timestamp is outside of the bounds of pyarrows Timestamp[ns]. With this fix the new supported time units (and thus the ranges), are:  ‘s’ [second], ‘ms’ [millisecond], ‘us’ [microsecond], or ‘ns’ [nanosecond] , based on https://arrow.apache.org/docs/python/generated/pyarrow.timestamp.html .
Any other dataframe type will be defaulted to timestamp[ns], similar to current behaviour.
Relates
Bug fix for: https://github.com/aws/aws-sdk-pandas/issues/2950
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 76aef7038bb0f098e876cbf961f7eb45e6ab51ea
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 76aef7038bb0f098e876cbf961f7eb45e6ab51ea
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: b159e3f22574a5ac193ce9fecd7aaff00a8980a1
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: ea43b45014369772dd608db7e5185841ac474f13
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: ea43b45014369772dd608db7e5185841ac474f13
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 2b3a8957f0ab0df2d062d90453c14c6243c86ee9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: ea75b4125d2c253875644cee920a963d446f5ef3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 2b3a8957f0ab0df2d062d90453c14c6243c86ee9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: ea75b4125d2c253875644cee920a963d446f5ef3
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: b071f0b9c93c55762f178a9602394ad5297cb95b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: b071f0b9c93c55762f178a9602394ad5297cb95b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 2bac0245efc6060174a56e80c019280b48e98601
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 2bac0245efc6060174a56e80c019280b48e98601
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@jaidisido thanks for approving and merging the PR. What is the release cadence, in which version this change is expected to be released?


Refine the package to prepare NPM DevOps

This work is a great start for our Lark puppet, thanks for all the efforts from @Roxanne718 !
This PR improves the code base so that it can be easily maintained later.

ping @Roxanne718

ping @Roxanne718


Fix instructions in README about google-services.json

Description
The README instructions for the target of the google-services.json file were incorrect.
Related Issue
n/a
Motivation and Context
It took me a while to figure it out and I wanted to save other people some time.
How Has This Been Tested?
n/a
Screenshots (if appropriate):
Types of changes
README only change
Checklist:
n/a readme only change

@craigsheen thanks for the PR and the reminder. With cordova-android 7 getting released the path needed to deploy the .json file has changed. I updated your PR to add info for cordova-android 6.x as well.


docs(prisma): add required version field in example

Description
When we follow instructions of this page https://turbo.build/repo/docs/handbook/tools/prisma, we got the following error :
yarn install
yarn install v1.22.19
warning package.json: No license field
warning Missing version in workspace at "/xxxxx/packages/database", ignoring.
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 0.12s.

I just have added the required version field to have reproductible steps when we add a Prisma package on our monorepository.
Testing Instructions
No test required

Hey! Sorry for the late reply. I appreciate you taking the time to make this change. I am running CI and have enabled auto-merge so it should go through when tests pass (not expecting any issues but gotta respect the ceremony). Cheers!


P4Pf

I am trying to run the benchmark for this solver but it doesn't work. Could you give me an short code executing the P4Pf giving it some values that I decide?
Btw, I checked the code doing it in issues that are already solved but they do not work for me.

Hey, the example code from the previous issue was indeed a bit out-of-date. I've updated the example below. However, I found some inconsistencies and fixed some things (and updated the interface) in the branch https://github.com/PoseLib/PoseLib/tree/fix_p4pf
This branch should be merged into master soon.
Let me know if anything is still unclear.

Eigen::Vector2d imgA(315, 217);
Eigen::Vector2d imgB(361, 295);
Eigen::Vector2d imgC(392, 660);
Eigen::Vector2d imgD(146, 220);

Eigen::Vector2d pp(280, 420); // principal point
// Vector of image points (with principal point subtracted)
std::vector<Eigen::Vector2d> points2D = { imgA - pp, imgB - pp, imgC - pp, imgD - pp};

// Corresponding 3D points
Eigen::Vector3d a(-20.96, 3.54, 13.86);
Eigen::Vector3d b(-20.96, 3.57, 13.24);
Eigen::Vector3d c(-20.95, 2.01, 13.25);
Eigen::Vector3d d(-21.66, 3.74, 13.86);
std::vector<Eigen::Vector3d> points3D = { a, b, c, d };

// Returns the average of fx and fy as focal length
//std::vector<poselib::CameraPose> output;
//std::vector<double> output_focal;
//int result = poselib::p4pf(points2D, points3D,  &output, &output_focal, true);

// Returns both for fx and fy
std::vector<poselib::CameraPose> output;
std::vector<double> output_fx, output_fy;
int result = poselib::p4pf(points2D, points3D,  &output, &output_fx, &output_fy, true);

for(int k = 0; k < output.size(); ++k) {
    poselib::CameraPose pose = output[k];
    //double focal = output_focal[k];
    double fx = output_fx[k];
    double fy = output_fy[k];
    std::cout << "---------------\n";
    std::cout << pose.R() << "\n";
    std::cout << pose.t << "\n";
    std::cout << fx << " " << fy << "\n";

    for(size_t i = 0; i < 4; ++i) {
        Eigen::Vector3d Z =  pose.R() * points3D[i] + pose.t;
        Eigen::Vector2d proj = Z.hnormalized();
        proj(0) *= fx;
        proj(1) *= fy;

        Eigen::Vector2d res = proj - points2D[i];
        std::cout << "i = " << i << ", res = " << res.norm() << "\n";
    }
}


Issues when using Nuxt UI Pro Themes + Nuxt Scripts

When I used the latest Nuxt UI Pro Docs Theme and added Nuxt Scripts, I encountered some missing icons.
To reproduce:

Clone "Nuxt UI Pro Docs"
Add Nuxt Scripts as dependency
Deploy to Vercel with npx nuxi generate
Find missing Icons

Missing Icons when Client Side Rendering:

Cannot Find icons:

Server Rendered:

Maybe this is also interesting for you @benjamincanac, @harlan-zw

Please provide a minimal reproduction. Thanks.

Why reproduction is required

You find my reproduction repo here
To Reproduce:

Clone reproduction repo, install deps
pnpm nuxi generate
Check output: npx serve .output/public

=> You will find the color mode switcher is missing either the moon or soon icon:


How to get the bounding box of the scene ?

❓ Questions and Help
How to get the bounding box of the scene ?
In world coordinate?

bounds = sim.pathfinder.get_bounds()

You can also compute the cumulative AABB for the SceneGraph:
scene_graph = sim.get_active_scene_graph()
root = scene_graph.get_root_node()
root.compute_cumulative_bb()
scene_bounding_box = root.cumulative_bb


Updates README to add correct poetry command to run the backend server

Update run command to make sure it runs in project env with poetry

Hi @rahilvora,
Thanks for the contribution. Unfortunately I think the docs are incorrect on this part in any case. I just checked them - we should instead have poetry run uvicorn app.server:app --port 8100
I'm closing this but really appreciate you making the PR!

And in the end just make start 🙄 .. well thanks for pointing out that the docs had a problem!


Add a switch or switches for repairing activities

Either static or dynamic when an activity is on, in order to fix devices states if needed.
Maybe with an option has one switch or multiple ones. In this case the number of switch won't be always the same so will need to had / remove them dyamically. In the other hand, if we have only one switch, maybe some devices that don't have distincts power on and off function will have trouble using those options.

Closing, seems to difficult for minimal use.


Fixes some compiler warnings

This seems to happen with LLVM 17 and enabling LTO with  -DCMAKE_INTERPROCEDURAL_OPTIMIZATION=ON.
One of them is legitimately wrong, and the other one is kinda harmless, but seems reasonable to not allow that big of allocations.

The warnings were:
/homer/leif/apache/trafficserver/src/iocore/cache/CacheVC.cc:91: warning: type of ‘cache_config_ram_cache_cutoff’ does not match original declaration [-Wlto-type-mismatch]
   91 | extern int cache_config_ram_cache_cutoff;
      |
/homer/leif/apache/trafficserver/src/iocore/cache/Cache.cc:57: note: type ‘int64_t’ should match type ‘int’
   57 | int64_t cache_config_ram_cache_cutoff          = AGG_SIZE;

(which repeats many times), and
/homer/leif/apache/trafficserver/src/proxy/ControlMatcher.cc: In member function ‘AllocateSpace’:
/homer/leif/apache/trafficserver/src/proxy/ControlMatcher.cc:416:16: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
  416 |   data_array = new Data[num_entries];
      |                ^
/usr/include/c++/11/new:128:26: note: in a call to allocation function ‘operator new []’ declared here

[approve ci]

Yeh, I gave up on the matchers for now at least :/.


Support rerun builds in UI

related: https://github.com/adoptium/aqa-test-tools/issues/770
Signed-off-by: Lan Xia<EMAIL_ADDRESS>

Adoptium test pipeline does not have rerun enabled, so we do not have rerun data in Adoptium TRSS.
Screenshots from the local run:


一个问题

在云端打开/public/install.php时显示红字'Sorry, ./vendor/autoload.php is not existed. Are you sure all dependencies have installed yet?'
是github项目这边遗漏了上传autoload.php吗

run composer install as the guide said. See Installation Step 4. The install.php only process environment files and we recommend following the installation guide instead of using web installer.
Installation Guide

You are more than welcomed to join our QQ Group 668108264 for further tech support.


ReactiveLoadBalancerClientFilter chooses urls being incorrect

I'm using spring cloud 2.2.2 deploying on port 8080.
My discovery service is consul.
I'm deploying two image services with different ports (8200 and 8201). These services are the same.
I'm using load balancing
    @Bean
    public RouteLocator customRouteLocator(RouteLocatorBuilder builder) {
        return builder.routes()
                .route(r -> r.path("/images/**")
                        .filters(f -> f.hystrix(config -> config
                                .setName("hystrix_imageService")
                                .setFallbackUri("forward:/fallback"))
                        )
                        .uri("lb://image-service")
                        .id("imageService"))
                .build();
    }

I set spring.cloud.loadbalancer.ribbon.enabled=false in my application.properties to use ReactiveLoadBalancerClientFilter. (refer to Spring cloud docs)
When i shutdown port 8200, my spring cloud gateway still requests to port 8200.
It should have requested to 8201 instead of 8200 which is shutdown.
If i set  spring.cloud.loadbalancer.ribbon.enabled=true, everything is good. But it's synchronous.
I want to use ReactiveLoadBalancerClientFilter

There are some time lag when dead microservice will be removed from consul.
After this lag dead microservice will be removed from SCG also and SCG will balance traffic to proper instance.
I added retry filter.
So external clients won't see any errors in this test:
while true; do curl http://localhost:8282/foo; sleep 1; done

If you will configure retry filter be aware of bug. Currently it fixed, but fix version still not released.

It works. i appreciate your source code.
The connect-timeout must be less than the timeoutInMilliseconds of hystrix.
Thank you!