Call With Shawn @ Pluarlity

Meeting set for Thursday at 11:00 PST via Shawns scheduling app

https://discord.com/channels/1057785182347853905/1137421257663598722/1174827137207894026
@Jord @BOILΞR(Chris)  Boiler a few things to fill you in on from the discussion w/Shawn, but one is the KYC/KYB. They only want 1 of us to fill it out and then that's the "customer" as far as Arbitrum is concerned.  Jord and I were thinking it would be better to have my LLC do KYB in that case. It's a bit more work up front and it would be me and my partner scanning our faces, but then I can contract us and make that an expense for the LLC, so we don't get hit with a big up front tax which is what would happen if one of us did it as an individual.  That's something we all need to be on board with, so we can discuss at our meeting.

This led into a conversation about making an entity for DAO Masons to handle the 90K when it comes, because it would be trickier to finesse that through the LLC.

Also bookmark: We're on the hook for KYC/KYB with Grant Ships after they hand off funds to us, we have decisions to make on that, but if we do it we likely put that on the Ships themselves.

Other notes:
He suggested we frontload the pay more, so I updated Exhibit A so we get a bigger bulk before year end (ARB price is likely to dip in January).
Green lights on promo opportunities, and looks like we're really tapped in to a big audience with this one so let's be ready for attention.
There's a 2 week turn around on pay, and if there's a week of KYB we are 3 weeks away from first paycheck, followed by 2nd paycheck soon.


Are you f***ing kidding me? In the process of dropping O365

Even if somehow this is somehow not considered a malwareish way of doing things, its unethical, we have just made the switch to another office solution.

The guy who downvoted this is a Microsoft employee


Minor bug in preprocess_rollout.py

When re-running preprocess_rollout.py, if the library file specified in default_training.yml exists and library_headers doesn't include 'template_code' then it fails in _save_unique_templates because in this case template_code would be set in _filter_dataset which isn't called and when the library is read in we have 'names=config["library_headers"]', so the template_code column isn't read even if it's present. The workaround is obviously to delete the library file whenever I edit the raw library file and re-run; but if I forget, the error is only caught after the three preceding steps, which take some time on a large raw library.

Thanks for the feedback.
Just to get it right: you are defining your own library_headers that does not include the "template_code"? Why can't you add it to the library_headers?  Then the template codes would be read in when you are re-running the script.
Another solution, would be to add a check for the template_code column in the library file and if it isn't there, re-compute it. But I would prefer that the "template_code" is in library_headers, if it is possible - because then the template codes only need to be computed once.

Yes, I see now. I left it out because the online docs indicated to modify library_headers to match the columns in the raw template library and I didn't have this column (which I now see is generated when creating the template library). One alternative is to leave "template_code" out of library headers, modify names in _filter_dataset at line 28 of preprocess_rollout.py and add "template_code" to names at line 74.


wrong for increasing hidden_dim,emb_dim

Sorry for bothering you.
In the early training, I set the 'hidden_dim' as 64, and set the 'emb_dim' as 32. Then ,when i increase them as '256' and '128'. it has an error. It seems that the shape of parameter generated by training in the early training is not fit for the later training. How can i deal with it.

You can't (easily) increase those things. You've been training a model that is performing matrix transformations on hidden vectors of size 64. You can't use that model to handle hidden vectors of size 256. You'd need different shaped weight matrices for that.
Perhaps you're confused because you can increase max number of encoder steps and max number of decoder steps. That's because increasing those things just means unrolling the RNN for more steps.


fix: Ensure the current filters are applied when executing bulk actions

Updates the executeBulkAction on the frontend to send along the currently applied filters inside the POST body
Update the InvokeActionController to pull and use the refined query from the table instead of the table's model's generic query. This will automatically apply the supplied filters from the POST body.

I couldn't find any tests for these pieces, but please point me in the right direction if there are some.

Looks pretty good. Will review next week and add test myself. Thanks!

Thanks Owen!


Add simple fixed size stack/static allocator

Comes with a set of helper objects that take a std container, the
container types, and the fixed container width.
Added documentation about how to use containers.
Removed ETL library. Style prefers using standard libraries whenever
possible vs 3rd party libraries.
Resolves #689

Coverage increased (+0.8%) to 76.791% when pulling b24eae9db17410e0ce72e4b46c912d5f799cff9b on allocators into 3affc6879f1dafa3f8d1bfa0bb5a6e5e20bf0d11 on master.


Rename Ignition to Gazebo

Ignition Gazebo was renamed to Gazebo. This project is not still renamed.
Is there any plans to rename it ? Probably gazebo should be gazebo-classic and ignition should be gazebo.

Done in #483


Reducer in useRowSelect relies on external state

Pulled out of #2120, because this should be fixed even if 2120 is solved in another way or ends up being unrelated.
Describe the bug
The handler of toggleRowSelected action type reads isSelected from row objects:

useRowSelect.js:126

As a result, when multiple selection changes happen within the same reducer run, toggleRowSelected uses the initial row selection state, regardless of whether another action updated it earlier in the same run.
Provide an example via Codesandbox!
Sorry I did not make one. The idea is just to do this:
assert(someRow.isSelected); // the bug shows only if row is selected

toggleAllRowsSelected(false) ;
someRow.toggleRowSelected(true);

What happens then is this:

The reducer handles toggleAllRowsSelected.

It clears selectedRowIds.
At this point, the isSelected property of rows has not been updated.

The reducer handles toggleRowSelected.

It sees it should select the row.
It looks at row.isSelected. It is true, because react did not yet recompute it.
It skips the update.
Therefore the row is not added back to selectedRowIds.

At last, react recomputes selectedFlatRows, which updates isSelected as a side effect (see #2170).

It is hard to make a minimal example, because this triggers observable bugs depending on when exactly React chooses to recompute selectedFlatRows, which is further obfuscated by #2170.
Expected behavior
Reducers should never access any information outside of previousState. Otherwise they no longer are predictable.
Replacing row.isSelected by id in state.selectedRowIds or something similar should work I believe.

Yeah, I think you're right. This particular situation is further mitigated in the next branch, too where we have a new state management paradigm that gets around the stale state issue with reducers. There's a lot of places in React Table right now that could suffer from this same problem, so it seemed fitting that we move to something a bit safer.

What's the status on this issue? Is there a workaround?

@fparga no fix yet. I haven't seen an overwhelming amount of noise on this issue, so it doesn't seem to affect many right now. I currently have my sights set on v8 where this class of issue won't exist at all (by nature of some new architecture decisions). I would be happy to accept a PR to fix this issue in v7 and even offer any guidance on it.

@fparga a workaround is to

avoid useRowSelect, or
use it in controlled state mode (so, avoiding selection state update logic), or
use selectedRowIds directly, ignoring helper methods and isSelected attribute.
It is an annoyance, but at least you can use all other parts of react-table normally.

Looking forward to v8 though :)

+1 to add some noise.  I spent a couple hours integrating/debugging inconsistency bugs before finding this issue and tossing out the code to roll our own implementation.  The design/spec looks great so I'm hopeful it's more stable in v8 🤞


Add rpc call from BCI to get neighbor's info

Add rpc call from BCI to get neighbor's info.
#31

Add requests module into README.md

Requests is in python standard library.

I made a mistake, requests is auto installed by conada. 😭

Ref this and (this)[https://www.liaoxuefeng.com/wiki/1016959663602400/1183249464292448] make sure in (this)[https://docs.python-requests.org/en/latest/user/quickstart/#make-a-request], this package may be installed in Anaconda or other environment but it is not in python standard library.


Move source code into src directory

The bot's source code should be in a designated src directory. For this, there should be an npm script in the package.json file and the README should be adjusted.

I'll be working on this.
After moving the sorce code to src changing the npm script dev to "cd src && nodemon index.js" and start to "cd src && node index.js" should be enough

Thanks @ErickJoestar
I've assigned the Issue to you. It may be a good a idea to add nodemon as a dev-dependency as not everyone has it installed globally.


EVM-C: Rework "get code" callback

@chfast lets focus this week on merging this.

This is a lot of focus for this week :D

We've discussed on Friday the reasons behind all these options and so far the original proposal seems to be the best for two reasons:

the VM itself usually is able to provide a pointer into the destination memory
if the memory of the client is passed around, then the client needs to maintain its lifecycle, and this could easily be a DoS vector

Implementation in #170 and https://github.com/ethereum/evmjit/pull/172.

@chfast can we close this?


How to change parameter in findModules()???

Hi,
thanks for your pyWGCNA tools. But I have some problems.
I want to know how to set the parameter in functions?
I did not find in the Tutorials.
Thanks

Hi,
Thank you for using PyWGCNA :)
for more depth in analysis, I would suggest you look at your interesting function in the API documentation.
I would say, most of the main parameters should be defined when you initiate your WGCNA object. look at here
But if there are any specific parameters that you are looking for and aren’t able to find in the API documentation, feel free to reopen this issue.
Thanks


Add required property to defineConditionKeys to be used for serviceResolvedConditionKeys

Background

What do these changes do?

Adds a required property to the IAM trait defineConditionKeys.
Updates the IAM trait documentation.

Why are they important?

Defines whether a service resolved condition key is required. Not applicable to request resolved condition keys as the native @required trait must be used on the field directly.
Testing

How did you test these changes?

Smithy test files.
Java test class to check required is set correctly.

Links

Links to additional context, if necessary
Issue #, if applicable (see here for a list of keywords to use for linking issues)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Resolving in favor of #2288


ResourceOwnerPassword grant loses authentication details (like remote IP)

curl -i --basic -u client_id:secret -d 'grant_type=password&username=someuser&password=somepass'  localhost:8080/auth/oauth/token

in TokenEndpoint.getAccessToken principal.getDetails() has remoteIp
but this information is lost by ResourceOwnerPasswordTokenGranter.getOAuth2Authentication()
which creates a UsernamePasswordAuthenticationToken that is passed to
my custom implementation of AuthenticationProvider.
I require access to the incoming requests details (remoteIp for example) during the authentication procedure.

Maybe you just need to use a TokenEndpointAuthenticationFilter?

Ping. Did you try that?

I ended up using SecurityContextHolder.getContext().getAuthentication() to get access to the WebAuthenticationDetails


Customizable left click withdraw amounts

I understand this can be quite a lot of work, and I'm not sure if it's considered in scope, but I had the following idea. I think it would be convenient if we could configure for each item slot in the bank tag layout the default quantity that gets withdrawn on left click.
For example, I have the following bit in my herb run tab:

It would be nice if it would be possible to set the default left click withdraw amount of Volcanic Ash to 50, since that's exactly
how much I use during a herb run and would free up an inventory slot after using it. Similarly it would be nice to set the withdraw amount of the seeds to some large number so I can withdraw enough without needing to shift-click.
If this were possible I could gear up for a run simply by left clicking each item once and get exactly the right quantities of each item.

As a proposal for implementation, I would add a new (shift) right click menu entry "Set default withdraw quantity". This would open a new dialog where you can enter a number. A missing or non-positive number would be interpreted as "no override", meaning a left click respects your default quantity settings:

However, if a positive number gets entered then this takes priority over your default left click settings, and withdraws the specified amount on left click instead. This override would be stored on a per 'bank tag layout slot' basis, so if I have a duplicate item on my bank tag layout I would be able to set a different custom left click withdraw amount to each of them, and different bank tag layouts can have different withdraw amounts (for the same item).

Will not add this. I've seen it discussed in the Runelite discord and it seems pretty clear that the devs are not willing to allow a feature like this.
Furthermore, Runelite doesn't offer any API for custom quantities (only menu swapping existing Withdraw-<quantity> menu entries) and it wouldn't surprise me if the base client itself can't easily do this.
However, you might get some use out of one of my other plugins, Hotkeyable Menu Swaps. It lets you set a different key to swap each withdraw quantity in a bank item's right-click menu. While this doesn't allow anything beyond 1/5/10/all/your current withdraw-x quantity, it's better than nothing.

Will not add this. I've seen it discussed in the Runelite discord and it seems pretty clear that the devs are not willing to allow a feature like this.

Alright, fair enough. If it's not allowed then that's the end of it.

However, you might get some use out of one of my other plugins, Hotkeyable Menu Swaps.

I already use and love it :)

Adam says it's probably ok


feat(Order/SuccPred/Limit): extra lemmas

These are trivial variations on already proven results.

bors r+


Possibly incorect definition of checked_result::operaotr<=

Maybe this was in fact intended, but looks unsymmetrical.
Also, using tribool for relational operators is tricky, as I think, the semantic requirements of strict weak order are not satisfied.

merged in


docs(samples): enable/disable bucket's versioning sample

PR contains below samples:

Enable bucket versioning (storage_enable_versioning)
Disable bucket versioning (storage_disable_versioning)

LGTM, but making sure @frankyn or @JesseLovelace have a chance to take a look :)

@JesseLovelace can you take a look  into this and other Samples PR.

Gentle ping @JesseLovelace


Error when connection to remote Redshift cluster

Describe the bug
(A clear and concise description of what the bug is.)
When attempting to connect to a remote Redshift cluster, I receive the following exception:
odd-collector_1          | Traceback (most recent call last):
odd-collector_1          |   File "/app/odd_collector/adapters/redshift/adapter.py", line 90, in __connect
odd-collector_1          |     self.__connection = psycopg2.connect(self._data_source)
odd-collector_1          |   File "/usr/local/lib/python3.9/site-packages/psycopg2/__init__.py", line 122, in connect
odd-collector_1          |     conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
odd-collector_1          | psycopg2.OperationalError: could not translate host name "my.redshift.cluster" to address: Name or service not known

Set up
(How do you run the app?
Which version of the app are you running? Provide either docker image version or check commit hash at the top left corner. We won't be able to help you without this information.)
I followed the instructions here.
My collector_config.yaml file looks like this:
default_pulling_interval: 1
token: "MGnOJf0ni9fZW4wHkzOxoaOtkYt5op8vts567pTX"
plugins:
  - type: postgresql
    name: postgresql-step2-test
    host: !ENV ${SAMPLE_POSTGRES_HOST}
    port: 5432
    database: !ENV ${SAMPLE_POSTGRES_DATABASE}
    user: !ENV ${SAMPLE_POSTGRES_USER}
    password: !ENV ${SAMPLE_POSTGRES_PASSWORD}
  - type: redshift
    name: My Redshift Cluster
    description: "" # Optional string
    database: prod
    host: my.redshift.cluster
    port: 8192
    user: username
    password: password

Steps to Reproduce
Steps to reproduce the behavior:
I followed the instructions here.
Expected behavior
(A clear and concise description of what you expected to happen)
A connection to the cluster is opened successfully and the meta data is populated.
Screenshots
(If applicable, add screenshots to help explain your problem)
NA.
Additional context
(Add any other context about the problem here)

Hey @jasonstrimpel!
It seems that the place in which you run the collector can't resolve my.redshift.cluster hostname. Please double check if this place (whether this is a K8S pod or a local machine) can actually reach Redshift via this URL. If not, please let us know so we could start investigating this on our side


Does the GitHub fetch library have to be used in HTTP Sources?

...or can I use a different HTTP request library? If I do, will I loose the hook functionality?

The provided methods call into the fetch global. How would you use a different library? If you e.g. override HttpStateSource#request, then you would indeed lose the hooks.

OK, so what you are saying is that it is ill advised to use a different library, and the github/fetch and matthew-andrews/isomorphic-fetch libraries are pretty hard dependencies of the Marty framework.

As mentioned on Gitter, you're not directly using they - they get pulled in as dependencies by Marty, and e.g. this.get and this.post on HttpStateSource internally use a fetch polyfill.
If needed, you can override HttpStateSource#request, but otherwise you won't be directly calling fetch.


Broken image link on the README.md

Jun 2020 now. Not solved yet hhh.

Non-Image content-type returned

Jun 2020 now. Not solved yet hhh.

Feb 2021 now. Not solved yet hhh.

Apr 28 2021 now. Not solved yet hhh

Dec 2021 now. Not solved yet hhh

March 2022 now. Not solved yet hhh

Apr 2022 now. Not solved yet hhh

May April 2022 now. Not solved yet hhh

Sep 2022 now. Not solved yet hhh

At this point, who even cares about the broken image link? :|

Jan 2023. Still...

July 2024 now😂


Updated dev endpoint URL

Looks good. Once we've tested the new endpoint for ClaimService in dev we can update all of them in dev and then move the changes into the other environments.


purge?

is cache purge functionality available?

It isn't right now, mainly because each cache implementation has different ways of doing this, if they have any way at all.

maybe you should letting implementations functionality to implement this?

Sorry, I'm not sure what you mean.

i have elaborated my question.

Oh, I guess we do have a purge function, called reset: https://github.com/BryanDonovan/node-cache-manager/blob/master/lib/caching.js#L165
It isn't guaranteed that a third-party engine would implement it though. (see also: https://github.com/BryanDonovan/node-cache-manager/issues/73)


pthread blockage on CMake build

vcpkg install pthreads:x64-windows
Computing installation plan...
The following packages will be built and installed:
pthreads[core]:x64-windows -> 3.0.0#13
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\jk\AppData\Local\vcpkg\archives in 141 us. Use --debug to see more details.
Installing 1/1 pthreads:x64-windows...
Building pthreads[core]:x64-windows...
-- Using cached pthreads4w-code-v3.0.0.zip.
-- Cleaning sources at F:/vcpkg/buildtrees/pthreads/src/49e541b66c-6b4ff17b62.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source F:/vcpkg/downloads/pthreads4w-code-v3.0.0.zip
-- Applying patch fix-arm-macro.patch
-- Applying patch fix-arm64-version_rc.patch
-- Applying patch use-md.patch
-- Applying patch fix-pthread_getname_np.patch
-- Applying patch fix-install.patch
-- Using source at F:/vcpkg/buildtrees/pthreads/src/49e541b66c-6b4ff17b62.clean
-- Found external ninja('1.11.0').
-- Getting CMake variables for x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
Command failed: "C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
Working Directory: F:/vcpkg/buildtrees/pthreads/x64-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
F:\vcpkg\buildtrees\pthreads\get-cmake-vars-x64-windows-dbg-CMakeCache.txt.log
F:\vcpkg\buildtrees\pthreads\get-cmake-vars-x64-windows-rel-CMakeCache.txt.log
F:\vcpkg\buildtrees\pthreads\get-cmake-vars-x64-windows-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:310 (vcpkg_execute_required_process)
scripts/cmake/z_vcpkg_get_cmake_vars.cmake:18 (vcpkg_configure_cmake)
scripts/cmake/vcpkg_build_nmake.cmake:46 (z_vcpkg_get_cmake_vars)
scripts/cmake/vcpkg_install_nmake.cmake:52 (vcpkg_build_nmake)
ports/pthreads/portfile.cmake:44 (vcpkg_install_nmake)
scripts/ports.cmake:147 (include)
error: building pthreads:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+pthreads
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[pthreads]+Build+error&body=Copy+issue+body+from+F%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

https://github.com/microsoft/vcpkg/issues/new?title=[pthreads]+Build+error&body=Copy+issue+body+from+F%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

See https://github.com/microsoft/vcpkg/issues/30604

Package: pthreads[core]:x64-windows -> 3.0.0#13
Host Environment

Host: x64-windows
Compiler: MSVC 19.35.32216.1
vcpkg-tool version: 2023-03-29-664f8bb619b752430368d0f30a8289b761f5caba
vcpkg-scripts version: 69efe9cc2 2023-03-31 (30 hours ago)

To Reproduce
vcpkg install pthreads:x64-windows
Failure logs
-- Using cached pthreads4w-code-v3.0.0.zip.
-- Cleaning sources at F:/vcpkg/buildtrees/pthreads/src/49e541b66c-6b4ff17b62.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source F:/vcpkg/downloads/pthreads4w-code-v3.0.0.zip
-- Applying patch fix-arm-macro.patch
-- Applying patch fix-arm64-version_rc.patch
-- Applying patch use-md.patch
-- Applying patch fix-pthread_getname_np.patch
-- Applying patch fix-install.patch
-- Using source at F:/vcpkg/buildtrees/pthreads/src/49e541b66c-6b4ff17b62.clean
-- Found external ninja('1.11.0').
-- Getting CMake variables for x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: "C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
    Working Directory: F:/vcpkg/buildtrees/pthreads/x64-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      F:\vcpkg\buildtrees\pthreads\get-cmake-vars-x64-windows-dbg-CMakeCache.txt.log
      F:\vcpkg\buildtrees\pthreads\get-cmake-vars-x64-windows-rel-CMakeCache.txt.log
      F:\vcpkg\buildtrees\pthreads\get-cmake-vars-x64-windows-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:310 (vcpkg_execute_required_process)
  scripts/cmake/z_vcpkg_get_cmake_vars.cmake:18 (vcpkg_configure_cmake)
  scripts/cmake/vcpkg_build_nmake.cmake:46 (z_vcpkg_get_cmake_vars)
  scripts/cmake/vcpkg_install_nmake.cmake:52 (vcpkg_build_nmake)
  ports/pthreads/portfile.cmake:44 (vcpkg_install_nmake)
  scripts/ports.cmake:147 (include)

F:\vcpkg\buildtrees\pthreads\get-cmake-vars-x64-windows-dbg-CMakeCache.txt.log
# This is the CMakeCache file.
# For build in directory: f:/vcpkg/buildtrees/pthreads/x64-windows-dbg
# It was generated by CMake: D:/system applications/cmake/bin/cmake.exe
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//No help, variable specified on the command line.
BUILD_SHARED_LIBS:UNINITIALIZED=ON

//Path to a program.
CMAKE_AR:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/lib.exe

//Choose the type of build, options are: None Debug Release RelWithDebInfo
// MinSizeRel ...
CMAKE_BUILD_TYPE:STRING=Debug

CMAKE_CROSSCOMPILING:STRING=OFF

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe

CMAKE_CXX_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP '

CMAKE_CXX_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

CMAKE_CXX_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//C compiler
CMAKE_C_COMPILER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe

CMAKE_C_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP '

CMAKE_C_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

//Flags used by the C compiler during MINSIZEREL builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=/O1 /Ob1 /DNDEBUG

CMAKE_C_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//Flags used by the C compiler during RELWITHDEBINFO builds.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/Zi /O2 /Ob1 /DNDEBUG

//Libraries linked by default with all C applications.
CMAKE_C_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//No help, variable specified on the command line.
CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION:UNINITIALIZED=ON

//Flags used by the linker during all build types.
CMAKE_EXE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during DEBUG builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during MINSIZEREL builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during RELWITHDEBINFO builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=

//No help, variable specified on the command line.
CMAKE_EXPORT_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY:UNINITIALIZED=ON

//Value Computed by CMake.
CMAKE_FIND_PACKAGE_REDIRECTS_DIR:STATIC=F:/vcpkg/buildtrees/pthreads/x64-windows-dbg/CMakeFiles/pkgRedirects

//No help, variable specified on the command line.
CMAKE_INSTALL_BINDIR:STRING=bin

//No help, variable specified on the command line.
CMAKE_INSTALL_LIBDIR:STRING=lib

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=F:/vcpkg/packages/pthreads_x64-windows/debug

//No help, variable specified on the command line.
CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP:UNINITIALIZED=TRUE

//Path to a program.
CMAKE_LINKER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/link.exe

//make program
CMAKE_MAKE_PROGRAM:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe

//Flags used by the linker during the creation of modules during
// all build types.
CMAKE_MODULE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of modules during
// DEBUG builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during the creation of modules during
// MINSIZEREL builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during the creation of modules during
// RELEASE builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during the creation of modules during
// RELWITHDEBINFO builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

CMAKE_MSVC_RUNTIME_LIBRARY:STRING=MultiThreaded$<$<CONFIG:Debug>:Debug>$<$<STREQUAL:dynamic,dynamic>:DLL>

//Path to a program.
CMAKE_MT:FILEPATH=CMAKE_MT-NOTFOUND

//Value Computed by CMake
CMAKE_PROJECT_DESCRIPTION:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_HOMEPAGE_URL:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=get_cmake_vars

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=rc

CMAKE_RC_FLAGS:STRING=-c65001 /DWIN32

//Flags for Windows Resource Compiler during DEBUG builds.
CMAKE_RC_FLAGS_DEBUG:STRING=-D_DEBUG

//Flags for Windows Resource Compiler during MINSIZEREL builds.
CMAKE_RC_FLAGS_MINSIZEREL:STRING=

//Flags for Windows Resource Compiler during RELEASE builds.
CMAKE_RC_FLAGS_RELEASE:STRING=

//Flags for Windows Resource Compiler during RELWITHDEBINFO builds.
CMAKE_RC_FLAGS_RELWITHDEBINFO:STRING=

//Flags used by the linker during the creation of shared libraries
// during all build types.
CMAKE_SHARED_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of shared libraries
// during DEBUG builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during the creation of shared libraries
// during MINSIZEREL builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during the creation of shared libraries
// during RELWITHDEBINFO builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Flags used by the linker during the creation of static libraries
// during all build types.
CMAKE_STATIC_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of static libraries
// during DEBUG builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during MINSIZEREL builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during the creation of static libraries
// during RELEASE builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during RELWITHDEBINFO builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

CMAKE_SYSTEM_NAME:STRING=Windows

CMAKE_SYSTEM_PROCESSOR:STRING=AMD64

CMAKE_SYSTEM_VERSION:STRING=10.0.22621

//The CMake toolchain file
CMAKE_TOOLCHAIN_FILE:FILEPATH=F:/vcpkg/scripts/buildsystems/vcpkg.cmake

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=ON

//Automatically copy dependencies into the output directory for
// executables.
VCPKG_APPLOCAL_DEPS:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_CHAINLOAD_TOOLCHAIN_FILE:UNINITIALIZED=F:/vcpkg/scripts/toolchains/windows.cmake

//No help, variable specified on the command line.
VCPKG_CRT_LINKAGE:UNINITIALIZED=dynamic

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_RELEASE:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_RELEASE:UNINITIALIZED=

//The directory which contains the installed libraries for each
// triplet
VCPKG_INSTALLED_DIR:PATH=F:/vcpkg/installed

//Languages to enables for this project
VCPKG_LANGUAGES:STRING=C;CXX

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_RELEASE:UNINITIALIZED=

//The path to the vcpkg manifest directory.
VCPKG_MANIFEST_DIR:PATH=

//Use manifest mode, as opposed to classic mode.
VCPKG_MANIFEST_MODE:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_OUTPUT_FILE:PATH=F:/vcpkg/buildtrees/pthreads/cmake-vars-x64-windows-dbg.cmake.log

//No help, variable specified on the command line.
VCPKG_PLATFORM_TOOLSET:UNINITIALIZED=v143

//Appends the vcpkg paths to CMAKE_PREFIX_PATH, CMAKE_LIBRARY_PATH
// and CMAKE_FIND_ROOT_PATH so that vcpkg libraries/packages are
// found after toolchain/system libraries/packages.
VCPKG_PREFER_SYSTEM_LIBS:BOOL=OFF

//Enable the setup of CMAKE_PROGRAM_PATH to vcpkg paths
VCPKG_SETUP_CMAKE_PROGRAM_PATH:BOOL=ON

//No help, variable specified on the command line.
VCPKG_SET_CHARSET_FLAG:UNINITIALIZED=ON

//No help, variable specified on the command line.
VCPKG_TARGET_ARCHITECTURE:UNINITIALIZED=x64

//Vcpkg target triplet (ex. x86-windows)
VCPKG_TARGET_TRIPLET:STRING=x64-windows

//Trace calls to find_package()
VCPKG_TRACE_FIND_PACKAGE:BOOL=OFF

//Enables messages from the VCPKG toolchain for debugging purposes.
VCPKG_VERBOSE:BOOL=OFF

//(experimental) Automatically copy dependencies into the install
// target directory for executables. Requires CMake 3.14.
X_VCPKG_APPLOCAL_DEPS_INSTALL:BOOL=OFF

//(experimental) Add USES_TERMINAL to VCPKG_APPLOCAL_DEPS to force
// serialization.
X_VCPKG_APPLOCAL_DEPS_SERIALIZED:BOOL=OFF

//No help, variable specified on the command line.
Z_VCPKG_ROOT_DIR:UNINITIALIZED=F:/vcpkg

//The directory which contains the installed libraries for each
// triplet
_VCPKG_INSTALLED_DIR:PATH=F:/vcpkg/installed

//No help, variable specified on the command line.
_VCPKG_ROOT_DIR:UNINITIALIZED=F:/vcpkg

//Value Computed by CMake
get_cmake_vars_BINARY_DIR:STATIC=F:/vcpkg/buildtrees/pthreads/x64-windows-dbg

//Value Computed by CMake
get_cmake_vars_IS_TOP_LEVEL:STATIC=ON

//Value Computed by CMake
get_cmake_vars_SOURCE_DIR:STATIC=F:/vcpkg/scripts/get_cmake_vars

########################
# INTERNAL cache entries
########################

//ADVANCED property for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=f:/vcpkg/buildtrees/pthreads/x64-windows-dbg
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=26
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=2
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=D:/system applications/cmake/bin/cmake.exe
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=D:/system applications/cmake/bin/cpack.exe
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=D:/system applications/cmake/bin/ctest.exe
//ADVANCED property for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_STANDARD_LIBRARIES
CMAKE_C_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=D:/system applications/cmake/bin/cmake-gui.exe
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Ninja
//Generator instance identifier.
CMAKE_GENERATOR_INSTANCE:INTERNAL=
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Source directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=F:/vcpkg/scripts/get_cmake_vars
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MT
CMAKE_MT-ADVANCED:INTERNAL=1
//number of local generators
CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=1
//Platform information initialized
CMAKE_PLATFORM_INFO_INITIALIZED:INTERNAL=1
//noop for ranlib
CMAKE_RANLIB:INTERNAL=:
//ADVANCED property for variable: CMAKE_RC_COMPILER
CMAKE_RC_COMPILER-ADVANCED:INTERNAL=1
CMAKE_RC_COMPILER_WORKS:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS
CMAKE_RC_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_DEBUG
CMAKE_RC_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_MINSIZEREL
CMAKE_RC_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELEASE
CMAKE_RC_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELWITHDEBINFO
CMAKE_RC_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=D:/system applications/cmake/share/cmake-3.26
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_TOOLCHAIN_FILE
CMAKE_TOOLCHAIN_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Install the dependencies listed in your manifest:
//\n    If this is off, you will have to manually install your dependencies.
//\n    See https://github.com/microsoft/vcpkg/tree/master/docs/specifications/manifests.md
// for more info.
//\n
VCPKG_MANIFEST_INSTALL:INTERNAL=OFF
//ADVANCED property for variable: VCPKG_VERBOSE
VCPKG_VERBOSE-ADVANCED:INTERNAL=1
//Making sure VCPKG_MANIFEST_MODE doesn't change
Z_VCPKG_CHECK_MANIFEST_MODE:INTERNAL=OFF

F:\vcpkg\buildtrees\pthreads\get-cmake-vars-x64-windows-rel-CMakeCache.txt.log
# This is the CMakeCache file.
# For build in directory: f:/vcpkg/buildtrees/pthreads/x64-windows-rel
# It was generated by CMake: D:/system applications/cmake/bin/cmake.exe
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//No help, variable specified on the command line.
BUILD_SHARED_LIBS:UNINITIALIZED=ON

//Path to a program.
CMAKE_AR:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/lib.exe

//Choose the type of build, options are: None Debug Release RelWithDebInfo
// MinSizeRel ...
CMAKE_BUILD_TYPE:STRING=Release

CMAKE_CROSSCOMPILING:STRING=OFF

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe

CMAKE_CXX_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP '

CMAKE_CXX_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

CMAKE_CXX_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//C compiler
CMAKE_C_COMPILER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe

CMAKE_C_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP '

CMAKE_C_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

//Flags used by the C compiler during MINSIZEREL builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=/O1 /Ob1 /DNDEBUG

CMAKE_C_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//Flags used by the C compiler during RELWITHDEBINFO builds.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/Zi /O2 /Ob1 /DNDEBUG

//Libraries linked by default with all C applications.
CMAKE_C_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//No help, variable specified on the command line.
CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION:UNINITIALIZED=ON

//Flags used by the linker during all build types.
CMAKE_EXE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during DEBUG builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during MINSIZEREL builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during RELWITHDEBINFO builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=

//No help, variable specified on the command line.
CMAKE_EXPORT_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY:UNINITIALIZED=ON

//Value Computed by CMake.
CMAKE_FIND_PACKAGE_REDIRECTS_DIR:STATIC=F:/vcpkg/buildtrees/pthreads/x64-windows-rel/CMakeFiles/pkgRedirects

//No help, variable specified on the command line.
CMAKE_INSTALL_BINDIR:STRING=bin

//No help, variable specified on the command line.
CMAKE_INSTALL_LIBDIR:STRING=lib

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=F:/vcpkg/packages/pthreads_x64-windows

//No help, variable specified on the command line.
CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP:UNINITIALIZED=TRUE

//Path to a program.
CMAKE_LINKER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/link.exe

//make program
CMAKE_MAKE_PROGRAM:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe

//Flags used by the linker during the creation of modules during
// all build types.
CMAKE_MODULE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of modules during
// DEBUG builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during the creation of modules during
// MINSIZEREL builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during the creation of modules during
// RELEASE builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during the creation of modules during
// RELWITHDEBINFO builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

CMAKE_MSVC_RUNTIME_LIBRARY:STRING=MultiThreaded$<$<CONFIG:Debug>:Debug>$<$<STREQUAL:dynamic,dynamic>:DLL>

//Path to a program.
CMAKE_MT:FILEPATH=CMAKE_MT-NOTFOUND

//Value Computed by CMake
CMAKE_PROJECT_DESCRIPTION:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_HOMEPAGE_URL:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=get_cmake_vars

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=rc

CMAKE_RC_FLAGS:STRING=-c65001 /DWIN32

//Flags for Windows Resource Compiler during DEBUG builds.
CMAKE_RC_FLAGS_DEBUG:STRING=-D_DEBUG

//Flags for Windows Resource Compiler during MINSIZEREL builds.
CMAKE_RC_FLAGS_MINSIZEREL:STRING=

//Flags for Windows Resource Compiler during RELEASE builds.
CMAKE_RC_FLAGS_RELEASE:STRING=

//Flags for Windows Resource Compiler during RELWITHDEBINFO builds.
CMAKE_RC_FLAGS_RELWITHDEBINFO:STRING=

//Flags used by the linker during the creation of shared libraries
// during all build types.
CMAKE_SHARED_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of shared libraries
// during DEBUG builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during the creation of shared libraries
// during MINSIZEREL builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during the creation of shared libraries
// during RELWITHDEBINFO builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Flags used by the linker during the creation of static libraries
// during all build types.
CMAKE_STATIC_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of static libraries
// during DEBUG builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during MINSIZEREL builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during the creation of static libraries
// during RELEASE builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during RELWITHDEBINFO builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

CMAKE_SYSTEM_NAME:STRING=Windows

CMAKE_SYSTEM_PROCESSOR:STRING=AMD64

CMAKE_SYSTEM_VERSION:STRING=10.0.22621

//The CMake toolchain file
CMAKE_TOOLCHAIN_FILE:FILEPATH=F:/vcpkg/scripts/buildsystems/vcpkg.cmake

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=ON

//Automatically copy dependencies into the output directory for
// executables.
VCPKG_APPLOCAL_DEPS:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_CHAINLOAD_TOOLCHAIN_FILE:UNINITIALIZED=F:/vcpkg/scripts/toolchains/windows.cmake

//No help, variable specified on the command line.
VCPKG_CRT_LINKAGE:UNINITIALIZED=dynamic

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_RELEASE:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_RELEASE:UNINITIALIZED=

//The directory which contains the installed libraries for each
// triplet
VCPKG_INSTALLED_DIR:PATH=F:/vcpkg/installed

//Languages to enables for this project
VCPKG_LANGUAGES:STRING=C;CXX

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_RELEASE:UNINITIALIZED=

//The path to the vcpkg manifest directory.
VCPKG_MANIFEST_DIR:PATH=

//Use manifest mode, as opposed to classic mode.
VCPKG_MANIFEST_MODE:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_OUTPUT_FILE:PATH=F:/vcpkg/buildtrees/pthreads/cmake-vars-x64-windows-rel.cmake.log

//No help, variable specified on the command line.
VCPKG_PLATFORM_TOOLSET:UNINITIALIZED=v143

//Appends the vcpkg paths to CMAKE_PREFIX_PATH, CMAKE_LIBRARY_PATH
// and CMAKE_FIND_ROOT_PATH so that vcpkg libraries/packages are
// found after toolchain/system libraries/packages.
VCPKG_PREFER_SYSTEM_LIBS:BOOL=OFF

//Enable the setup of CMAKE_PROGRAM_PATH to vcpkg paths
VCPKG_SETUP_CMAKE_PROGRAM_PATH:BOOL=ON

//No help, variable specified on the command line.
VCPKG_SET_CHARSET_FLAG:UNINITIALIZED=ON

//No help, variable specified on the command line.
VCPKG_TARGET_ARCHITECTURE:UNINITIALIZED=x64

//Vcpkg target triplet (ex. x86-windows)
VCPKG_TARGET_TRIPLET:STRING=x64-windows

//Trace calls to find_package()
VCPKG_TRACE_FIND_PACKAGE:BOOL=OFF

//Enables messages from the VCPKG toolchain for debugging purposes.
VCPKG_VERBOSE:BOOL=OFF

//(experimental) Automatically copy dependencies into the install
// target directory for executables. Requires CMake 3.14.
X_VCPKG_APPLOCAL_DEPS_INSTALL:BOOL=OFF

//(experimental) Add USES_TERMINAL to VCPKG_APPLOCAL_DEPS to force
// serialization.
X_VCPKG_APPLOCAL_DEPS_SERIALIZED:BOOL=OFF

//No help, variable specified on the command line.
Z_VCPKG_ROOT_DIR:UNINITIALIZED=F:/vcpkg

//The directory which contains the installed libraries for each
// triplet
_VCPKG_INSTALLED_DIR:PATH=F:/vcpkg/installed

//No help, variable specified on the command line.
_VCPKG_ROOT_DIR:UNINITIALIZED=F:/vcpkg

//Value Computed by CMake
get_cmake_vars_BINARY_DIR:STATIC=F:/vcpkg/buildtrees/pthreads/x64-windows-rel

//Value Computed by CMake
get_cmake_vars_IS_TOP_LEVEL:STATIC=ON

//Value Computed by CMake
get_cmake_vars_SOURCE_DIR:STATIC=F:/vcpkg/scripts/get_cmake_vars

########################
# INTERNAL cache entries
########################

//ADVANCED property for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=f:/vcpkg/buildtrees/pthreads/x64-windows-rel
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=26
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=2
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=D:/system applications/cmake/bin/cmake.exe
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=D:/system applications/cmake/bin/cpack.exe
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=D:/system applications/cmake/bin/ctest.exe
//ADVANCED property for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_STANDARD_LIBRARIES
CMAKE_C_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=D:/system applications/cmake/bin/cmake-gui.exe
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Ninja
//Generator instance identifier.
CMAKE_GENERATOR_INSTANCE:INTERNAL=
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Source directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=F:/vcpkg/scripts/get_cmake_vars
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MT
CMAKE_MT-ADVANCED:INTERNAL=1
//number of local generators
CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=1
//Platform information initialized
CMAKE_PLATFORM_INFO_INITIALIZED:INTERNAL=1
//noop for ranlib
CMAKE_RANLIB:INTERNAL=:
//ADVANCED property for variable: CMAKE_RC_COMPILER
CMAKE_RC_COMPILER-ADVANCED:INTERNAL=1
CMAKE_RC_COMPILER_WORKS:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS
CMAKE_RC_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_DEBUG
CMAKE_RC_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_MINSIZEREL
CMAKE_RC_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELEASE
CMAKE_RC_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELWITHDEBINFO
CMAKE_RC_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=D:/system applications/cmake/share/cmake-3.26
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_TOOLCHAIN_FILE
CMAKE_TOOLCHAIN_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Install the dependencies listed in your manifest:
//\n    If this is off, you will have to manually install your dependencies.
//\n    See https://github.com/microsoft/vcpkg/tree/master/docs/specifications/manifests.md
// for more info.
//\n
VCPKG_MANIFEST_INSTALL:INTERNAL=OFF
//ADVANCED property for variable: VCPKG_VERBOSE
VCPKG_VERBOSE-ADVANCED:INTERNAL=1
//Making sure VCPKG_MANIFEST_MODE doesn't change
Z_VCPKG_CHECK_MANIFEST_MODE:INTERNAL=OFF

F:\vcpkg\buildtrees\pthreads\get-cmake-vars-x64-windows-out.log
[1/2] "D:/system applications/cmake/bin/cmake.exe" -E chdir ".." "D:/system applications/cmake/bin/cmake.exe" "F:/vcpkg/scripts/get_cmake_vars" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=F:/vcpkg/packages/pthreads_x64-windows" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=F:/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=F:/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=F:/vcpkg" "-DZ_VCPKG_ROOT_DIR=F:/vcpkg" "-D_VCPKG_INSTALLED_DIR=F:/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-DVCPKG_OUTPUT_FILE:PATH=F:/vcpkg/buildtrees/pthreads/cmake-vars-x64-windows-rel.cmake.log"
FAILED: ../CMakeCache.txt
"D:/system applications/cmake/bin/cmake.exe" -E chdir ".." "D:/system applications/cmake/bin/cmake.exe" "F:/vcpkg/scripts/get_cmake_vars" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=F:/vcpkg/packages/pthreads_x64-windows" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=F:/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=F:/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=F:/vcpkg" "-DZ_VCPKG_ROOT_DIR=F:/vcpkg" "-D_VCPKG_INSTALLED_DIR=F:/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-DVCPKG_OUTPUT_FILE:PATH=F:/vcpkg/buildtrees/pthreads/cmake-vars-x64-windows-rel.cmake.log"
-- The C compiler identification is MSVC 19.35.32216.1
-- The CXX compiler identification is MSVC 19.35.32216.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe - broken
CMake Error at D:/system applications/cmake/share/cmake-3.26/Modules/CMakeTestCCompiler.cmake:67 (message):
  The C compiler

    "C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: F:/vcpkg/buildtrees/pthreads/x64-windows-rel/CMakeFiles/CMakeScratch/TryCompile-jbo784

    Run Build Command(s):C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe -v cmTC_bbaf4 && [1/2] C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1435~1.322\bin\Hostx64\x64\cl.exe  /nologo   /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP   /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -MDd /showIncludes /FoCMakeFiles\cmTC_bbaf4.dir\testCCompiler.c.obj /FdCMakeFiles\cmTC_bbaf4.dir\ /FS -c F:\vcpkg\buildtrees\pthreads\x64-windows-rel\CMakeFiles\CMakeScratch\TryCompile-jbo784\testCCompiler.c
    [2/2] cmd.exe /C "cd . && "D:\system applications\cmake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_bbaf4.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1435~1.322\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_bbaf4.dir\testCCompiler.c.obj  /out:cmTC_bbaf4.exe /implib:cmTC_bbaf4.lib /pdb:cmTC_bbaf4.pdb /version:0.0 /machine:x64  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    FAILED: cmTC_bbaf4.exe
    cmd.exe /C "cd . && "D:\system applications\cmake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_bbaf4.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1435~1.322\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_bbaf4.dir\testCCompiler.c.obj  /out:cmTC_bbaf4.exe /implib:cmTC_bbaf4.lib /pdb:cmTC_bbaf4.pdb /version:0.0 /machine:x64  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    RC Pass 1: command "rc /fo CMakeFiles\cmTC_bbaf4.dir/manifest.res CMakeFiles\cmTC_bbaf4.dir/manifest.rc" failed (exit code 0) with the following output:
    The system cannot find the file specified
    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:15 (project)

-- Configuring incomplete, errors occurred!
[2/2] "D:/system applications/cmake/bin/cmake.exe" -E chdir "../../x64-windows-dbg" "D:/system applications/cmake/bin/cmake.exe" "F:/vcpkg/scripts/get_cmake_vars" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=F:/vcpkg/packages/pthreads_x64-windows/debug" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=F:/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=F:/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=F:/vcpkg" "-DZ_VCPKG_ROOT_DIR=F:/vcpkg" "-D_VCPKG_INSTALLED_DIR=F:/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-DVCPKG_OUTPUT_FILE:PATH=F:/vcpkg/buildtrees/pthreads/cmake-vars-x64-windows-dbg.cmake.log"
FAILED: ../../x64-windows-dbg/CMakeCache.txt
"D:/system applications/cmake/bin/cmake.exe" -E chdir "../../x64-windows-dbg" "D:/system applications/cmake/bin/cmake.exe" "F:/vcpkg/scripts/get_cmake_vars" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=F:/vcpkg/packages/pthreads_x64-windows/debug" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=F:/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=F:/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=F:/vcpkg" "-DZ_VCPKG_ROOT_DIR=F:/vcpkg" "-D_VCPKG_INSTALLED_DIR=F:/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-DVCPKG_OUTPUT_FILE:PATH=F:/vcpkg/buildtrees/pthreads/cmake-vars-x64-windows-dbg.cmake.log"
-- The C compiler identification is MSVC 19.35.32216.1
-- The CXX compiler identification is MSVC 19.35.32216.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe - broken
CMake Error at D:/system applications/cmake/share/cmake-3.26/Modules/CMakeTestCCompiler.cmake:67 (message):
  The C compiler

    "C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: F:/vcpkg/buildtrees/pthreads/x64-windows-dbg/CMakeFiles/CMakeScratch/TryCompile-2sehcz

    Run Build Command(s):C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe -v cmTC_2c4e5 && [1/2] C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1435~1.322\bin\Hostx64\x64\cl.exe  /nologo   /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP   /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -MDd /showIncludes /FoCMakeFiles\cmTC_2c4e5.dir\testCCompiler.c.obj /FdCMakeFiles\cmTC_2c4e5.dir\ /FS -c F:\vcpkg\buildtrees\pthreads\x64-windows-dbg\CMakeFiles\CMakeScratch\TryCompile-2sehcz\testCCompiler.c
    [2/2] cmd.exe /C "cd . && "D:\system applications\cmake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_2c4e5.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1435~1.322\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_2c4e5.dir\testCCompiler.c.obj  /out:cmTC_2c4e5.exe /implib:cmTC_2c4e5.lib /pdb:cmTC_2c4e5.pdb /version:0.0 /machine:x64  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    FAILED: cmTC_2c4e5.exe
    cmd.exe /C "cd . && "D:\system applications\cmake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_2c4e5.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1435~1.322\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_2c4e5.dir\testCCompiler.c.obj  /out:cmTC_2c4e5.exe /implib:cmTC_2c4e5.lib /pdb:cmTC_2c4e5.pdb /version:0.0 /machine:x64  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    RC Pass 1: command "rc /fo CMakeFiles\cmTC_2c4e5.dir/manifest.res CMakeFiles\cmTC_2c4e5.dir/manifest.rc" failed (exit code 0) with the following output:
    The system cannot find the file specified
    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:15 (project)

-- Configuring incomplete, errors occurred!
ninja: build stopped: subcommand failed.

Additional context

Please install the windows SDK :)


fix: path_display set to truncate

When path_display is changed in telescope's default setup, (in the following image to "smart"), file browser is also affected, which I don't really know if it makes any sense...
Actual behavior:

Desired (?) behavior:

(path_display is set to truncate = 3 because otherwise when in folder-browser, we cannot see the end of the path correctly)

Ok, I agree. Don't know where to start but I'll try to take a look soon. Tranks!

I've made "tails" the default for path_display in file_browser and allowed user configs in folder_browser again.
Still, with "smart" path display in folder_browser, there seems to be something odd ("/telescope-file-browser.nvim" is common in every entry and therefore shouldn't be showing):

Could this be because we are using require"telescope.utils".transform_path(...) incorrectly in make_entry.lua or is it because of an upstream error?
Also, in folder_browser mode, the title seems too long. I'm thinking of applying there also user's path_display. What do you think?

Just skimming. Are the changes related to titles fix ups for #40? That should go into a separate PR.
I'm ok merging the tail for file_browser as a band-aid with a TODO comment. I'll have to refactor the entry maker stuff eventually in larger scope. As mentioned, it's quite brittle.

Not just fixing #40 but other actions that weren't updating the titles correctly, and I'm also truncating long titles.
I can move it to a new PR if you want, I just thought this may be related...
Apart from that, do you have any idea why this is happening? Is this because of an upstream issue?

Still, with "smart" path display in folder_browser, there seems to be something odd ("/telescope-file-browser.nvim" is common in every entry and therefore shouldn't be showing):

Just a heads up, I plan on looking into this next week. Probably enough file browser for me this week, it was quite some work tonight :sweat_smile:

Sorry, this is all pretty new to me... :)


remove en-us metadata from links

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-overview.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@Saisang looks good. Please sign off when you are ready to have this pr merged.
@arob98


[BUG] st_read fails to read Excel file from an http URL

In duckdb v0.9.2, the following code fails (where it succeeded in 0.9.1):
import duckdb

conn = duckdb.connect(database=':memory:')
conn.execute('SET s3_endpoint="localhost:8333";')
conn.execute('SET s3_url_style="path";')
conn.execute('SET s3_use_ssl=false;')
conn.execute('INSTALL spatial; LOAD spatial;')
r = conn.execute(
    "SELECT * FROM st_read('http://localhost:8333/appdata/global/sba_sample.xlsx', layer='sba_sample')"
)

print(r.fetchdf())

In this case, http://localhost:8333 is a local seaweedfs container compliant with the S3 API (and sba_sample.xlsx exists at that path).
With this exception:
Traceback (most recent call last):
  File "tmp/excel_example.py", line 7, in <module>
    r = conn.execute(
duckdb.duckdb.IOException: IO Error: Unknown file type

I'll note that this was working in duckdb 0.9.1 and it has been our work-around due to the other failure mentioned in #182.
Thanks in advance for your help!

I suspect this may have something to do with #168, given that the error message matches.

Hi! I think this has been fixed in https://github.com/duckdb/duckdb_spatial/pull/187.
Note: for XLSX in particular using DuckDB's filesystem with httpfs has a slower initial load time than /vsis3/ or /vsicurl/. Im aware of the issue and will look into improving it more in the future.
In a couple of hours (when the CI finishes) you should be able to install the extension with this fix for 0.9.2 by running:
FORCE INSTALL spatial FROM 'http://nightly-extensions.duckdb.org';

Thanks @Maxxen - Can fix be made available in the default 0.9.2 spatial extension or in a 0.9.3 fix release?

We may eventually replace the default 0.9.2 install version with this fixed version, but I can't give a timeline. If more issues occur it may be delayed further.


Show Rails error page for a morph reload

I noticed that in contrast to the :replace reload method, :morph will not display the Rails error page if an updated page raises an error. It will only print an error to the browser's console.
I changed the MorphReloader to morph the complete <html> document, to handle the different <head>s between the Rails error page and the app's layout. This would theoretically also fix that a change to an app's layout would not get picked up by the :morph method currently.
While the tests are green, my PR is broken, because after morphing from error page to a fixed version, I get the following browser error: An import map is added after module script load was triggered. and Stimulus controllers run twice.
I decided to open up the PR anyways, to start a discussion about a potential implementation or if someone has an idea how to approach the morph error page. I'll probably take another stab tomorrow and try to use Turbo for the Morph Reloader but I ran out of ideas for today.

Thank you for taking a look.
I can see your point about showing the full error page being too disruptive, especially on fast and small iterative changes. I personally always liked the instant feedback of an error screen similar to e.g. the react error overlay and I always missed a similar feature in the typical Rails setup.
I'll take a look if I can align the :replace method, with a similar error behavior to the :morph method 👍


[SPARK-49359][TESTS][FOLLOWUP][3.5] Fix compilation to rename util.Map to jutil.Map

What changes were proposed in this pull request?
This PR is a follow-up of the following and aims to fix compilation failures of branch-3.5 by renaming util.Map to jutil.Map

https://github.com/apache/spark/pull/47848

Why are the changes needed?
To recover the compilation on branch-3.5.

https://github.com/apache/spark/actions/runs/10544835250/job/29214315896

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @cloud-fan and @HyukjinKwon

Thank you, @HyukjinKwon .

Merged to branch-3.5.

thanks for fixing it!


Map is broken

Map is currently totally broken on the site. There's just a white space where it should be.
Will comment with screenshots in a few minutes.

Pretty sure it's that first 404 that's breaking things. Chances are updating the gmaps4rails gem will fix this.

As of right now I don't think it the gem is working: https://travis-ci.org/apneadiving/Google-Maps-for-Rails/builds/129553203

@MaxWofford figured it out and closed it in #235.


Worker timeout -> 502 bad gateway

The queryset manager isn't working with some large querysets. The service dies with a weird error message, which results in an annoying 502 for the users.

From the logs
storefront_1           | <IP_ADDRESS> - - [02/Jul/2021:07:33:42 +0000] "GET /querysets/querysets HTTP/1.0" 200 258 "-" "python-requests/2.25.1" "-"
queryset-manager_1     | [2021-07-02 07:34:26 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:9)
storefront_1           | 2021/07/02 07:34:26 [error] 37#37: *90 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: , request: "GET /querysets/data/severity_history_queryset HTTP/1.0", upstream: "http://<IP_ADDRESS>:80/data/severity_history_queryset", host: "<IP_ADDRESS>:4000"
storefront_1           | <IP_ADDRESS> - - [02/Jul/2021:07:34:26 +0000] "GET /querysets/data/severity_history_queryset HTTP/1.0" 502 158 "-" "python-requests/2.25.1" "-"
queryset-manager_1     | [2021-07-02 07:34:26 +0000] [1] [WARNING] Worker with pid 9 was terminated due to signal 6

Seems to only affect one of the querysets?
The failing queryset is severity_history_queryset

Relevant SO https://stackoverflow.com/questions/10855197/gunicorn-worker-timeout-error

The service network is able to handle requests locally, but not remotely.

This is definitely just a Gunicorn timeout. The simple solution is to just increase the timeout duration, but this issue has highlighted the need for more sophisticate monitoring.

Relevant article about Nginx -> Gunicorn issues: https://www.datadoghq.com/blog/nginx-502-bad-gateway-errors-gunicorn/#collect-apm-data-from-your-web-stack

Fixed by increasing timeout for Gunicorn.
The fix is implemented by the creation of a new base image, which centralizes Gunicorn configuration, making it much easier to solve issues like these in the future:
https://github.com/prio-data/uvicorn_deployment


ISPN-9352 Add nanoseconds stats for read/write/remove averages

https://issues.jboss.org/browse/ISPN-9352

Also fixed the Simple Cache stats to now really report milliseconds instead of nanos...

@ryanemerson added another commit to use correct types in the netty transport stats (an artifact of the Scala code)

Ok. CI is better now


Adding CCD method, including tests.

Description
Adding CCD as an initial test of new refactor.
Todos

[ ] Add CCD method to ccwfn.py and test case with CCD energy from CFOUR.
[ ] Add CCD method to cchbar.py and cclambda.py with test case with CCD pseudoenergy from CFOUR.
[ ] Add CCD method to ccdensity.py with test case reproducing CCD energy.

Status

[ ] Ready to go

Codecov Report

Merging #17 (6b965b1) into main (aeddde2) will decrease coverage by 1.74%.
The diff coverage is 84.69%.


Out of memory at the start of stage 3 of training

Is a Titan Xp insufficient for training this model? How much VRAM does RPM-Net require? Are there recommended ways to reduce the memory usage with the least impact on quality?

Hi, we train the RPM-Net using 4 GPUs, and each of them has 32GB of memory.
A direct way to reduce the GPU memory cost is setting a smaller batch size, also, you can try to reduce the output frames number (num_frame).
Thanks!


Make podcasts available to Plex

What this PR does / why we need it:
Make podcasts available to Plex
Which issue (if any) this PR fixes:
Fixes # n/a
Any other useful info:

👍 awesome!


Bugfix in integration test for Build Plan

Description
The integration test for the build plan was not possible to test the appliance error. After reimaging the appliance, the test was performed and errors were found due to object search that did not exist.
Issues Resolved
#174
Check List

[ ] New functionality includes testing.

[x] All tests pass ($ rake test).

[ ] New functionality has been documented in the README if applicable.

[ ] New functionality has been thoroughly documented in the examples (please include helpful comments).

[x] Changes are documented in the CHANGELOG.

@aalexmonteiro  don't you think this attribute missing in the integration test shouldn't be also highlighted on the examples ?

@thiago, you're right. Good hint. :)

@tmiotto , I added the example with custom attributes.


Any pypi package for this toolkit?

You can see pypi Package dependencies list in https://github.com/open-compass/VLMEvalKit/blob/main/requirements.txt

You can see pypi Package dependencies list in https://github.com/open-compass/VLMEvalKit/blob/main/requirements.txt

I mean, is this tool installable?

You can install it by this
git clone https://github.com/open-compass/VLMEvalKit.git
cd VLMEvalKit
pip install -e .

and use it by this
from vlmeval import *
model_name = 'llava_v1.5_13b'  # for example
model = supported_VLM[model_name]() if isinstance(model_name, str) else model_name
model.generate('hello') # only text
model.generate(['./assets/apple.jpg', 'Please describe this image.'])  # text + image

Furthermore, we more recommend using the VLMEvalKit repository for one-click evaluation of multimodal models and benchmarks.

You can install it by this
git clone https://github.com/open-compass/VLMEvalKit.git
cd VLMEvalKit
pip install -e .

and use it by this
from vlmeval import *
model_name = 'llava_v1.5_13b'  # for example
model = supported_VLM[model_name]() if isinstance(model_name, str) else model_name
model.generate('hello') # only text
model.generate(['./assets/apple.jpg', 'Please describe this image.'])  # text + image

Furthermore, we more recommend using the VLMEvalKit repository for one-click evaluation of multimodal models and benchmarks.

Ok, I initially thought it had a Python package in PYPI like https://pypi.org/project/opencompass.


add --bundledir param so that you can debug what files get bundled

Sometimes you might want to debug (or export) the files that actually get put into the binary snapshot. This adds a flag to let you do just that.

I really appreciate your help, but i have another plan for this feature. Particularly, i plan to implement json output. So that --json and --debug together will give you the list of files. Another project (mine or community-driven) parses the json and copies files as you describe.

@igorklopov That seems like a reasonable plan. I'll just use my fork for now, so feel free to close/reject this PR if you want. Also feel free to reuse any of the above code in the simple "other project" that can parse and copy the files if you find it helpful.

I would absolutely love some feature like this! Is there an alternative to this pull request yet?


Fix #393

As mentioned in https://github.com/swaywm/wlroots/issues/393 keybinds
did't trigger / were checked with "odd" keys and modifiers.
This commit sends the keycode through two paths, one to get the keycode
and modifiers after xkb handles them, a secondary path to get a "raw"
keysym without modifiers and then add the modifiers rootston knows
about.
This will result in the [Alt]+[Shift]+2 combination I mention earlier
going through the keybind detection twice.

[Alt]+[at]
[Alt]+[Shift]+2

When either combination is found, the appropriate keybind is executed.
The xkb handled version will be prefered over the "raw" version.
Edit: oh right, test-plan
Bind something to [Alt]+[Shift]+2 and check whether the keybind is found.

I would prefer leaving wlr_keyboard as is and do all changes in rootston.

The only file this changes rootston/keyboard.c. There's no need to touch wlr_keyboard for this.
Maybe I worded things a bit badly. Both paths go branch off in the key handler in rootston.
It's just that one gets the keysym over the full xkb_state while the other goes over xkb_keymap (from wlr_keyboard->keymap) and only uses the state to get the xkb_layout_index_t from the state.
Btw. IMO this is ready for review.

LGTM

Thanks!


Create LICENSE.md

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 20.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
12

Relevant Lines:
60

💛  - Coveralls


Requirejs

Just discovered an aesthetic problem: most of the  tags below the filter input widgets in browseData.html now get stripped away for reasons I couldn't figure out yet..


Add PV info and consolidate/simplify playload specification

Hi @brownd1978,
You have proposed changes to files in these packages:

JobConfig

which require these tests: build.
@Mu2e/fnalbuild-users, @Mu2e/write have access to CI actions on main.
:hourglass: The following tests have been triggered for d1e642bbdf1104315ec17a7132a5e3b5442d46a6: build  (Build queue is empty)
About FNALbuild. Code review on Mu2e/Offline.

This is draft because I haven't yet tested all the affected scripts.

:sunny: The build tests passed at d1e642bbdf1104315ec17a7132a5e3b5442d46a6.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged d1e642bbdf1104315ec17a7132a5e3b5442d46a6 at d7718e254427e8bbe8209019ac8b602779505fc9

build (prof)
:white_check_mark:
Log file. Build time: 08 min 31 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at d1e642bbdf1104315ec17a7132a5e3b5442d46a6 after being merged into the base branch at d7718e254427e8bbe8209019ac8b602779505fc9.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

:memo: The HEAD of main has changed to 4e3453fc9752133ae62be8640be7f8ad2faf2161. Tests are now out of date.

Tests finished. The PVInfo payload is now visible in the dts outputs:
PRINCIPAL TYPE: SubRun
PROCESS NAME... | MODULE LABEL......... | PRODUCT INSTANCE NAME | DATA PRODUCT TYPE...................................... | PRODUCT FRIENDLY TYPE...... | SIZE
MuBeamResampler | compressPVTargetStops | ..................... | std::vector<cet::map_vectormu2e::PhysicalVolumeInfo > | mu2e::PhysicalVolumeInfomvs | ...2
MuBeamResampler | compressPVIPAStops... | ..................... | std::vector<cet::map_vectormu2e::PhysicalVolumeInfo > | mu2e::PhysicalVolumeInfomvs | ...2
MuBeamResampler | genCounter........... | ..................... | mu2e::GenEventCount.................................... | mu2e::GenEventCount........ | ...-

@FNALbuild run build test

:hourglass: The following tests have been triggered for 7f5e1901efd0b0647bbab945950e35effebf34a4: build  (Build queue is empty)

:sunny: The build tests passed at 7f5e1901efd0b0647bbab945950e35effebf34a4.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 7f5e1901efd0b0647bbab945950e35effebf34a4 at 90562b2ef41137420d2459e8869ed17b7df68a85

build (prof)
:white_check_mark:
Log file. Build time: 04 min 16 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 7f5e1901efd0b0647bbab945950e35effebf34a4 after being merged into the base branch at 90562b2ef41137420d2459e8869ed17b7df68a85.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

Looks good to me. Thanks Dave.


Swap AppSync with API Gateway + Lambda + Serverless Express

Please ensure all pull requests are made against the master branch.
Issue #, if available:
Description of changes:
Checklist

[x] Tests have been added and are passing
[x] Documentation has been updated

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


In Theaters

Specto menu items still not working.  In theaters, is dead.
Any news as to when the links will be restored, or is there anything can can be done via client options?
Thanks for a great add-on, and hope your discover the issue.
If anyone has any ideas, pls share,

Fixed, try new version.


Remove MBEDTLS_SSL_EXPORT_KEYS

Remove the configuration option MBEDTLS_SSL_EXPORT_KEYS, making it always on.
We can do this in a minor version since its absence is not an observable aspect of the API.
Rationale
The option MBEDTLS_SSL_EXPORT_KEYS only gates the ability to set a callback. It does not change the behavior of the code.
Its impact on security is negligible: in order to introduce a vulnerability or facilitate exploitation, the application has to actively use the functionality. (The added function pointer in the SSL context is just one of many, so this does not facilitate exploitation to a non-negligible extent.)
The impact on code size is small: about 80B on an M0+ build, including the configuration function that doesn't get called unless the callback is used.
While we do test with the option disabled, this only happens in test-ref-configs.pl. Our testing missed at least one bug that happened in production: https://github.com/ARMmbed/mbedtls/issues/3998.

I strongly object to this issue, because of code-size.
"Because of 80B? Are you joking?"
No, I'm not: Removing options and saying that it doesn't matter because each one of them saves only - say - 80B, is like stepping into the rain saying "A single raindrop doesn't get me wet!"
Put 10 of those changes together and you have a code-size impact which does matter for highly constrained devices.
I agree that there's a challenge with testing many options, and we will never get around combinatorial explosion, but removing options is the wrong way. We should instead put more thought in the choice of configurations that we test.
This is really a choice of what Mbed TLS is as a product (ping @daverodgman): If we want to be serious embedded TLS library, we can't afford having those changes creep in - which should much rather go the other way, just as we did for the baremetal branch, were we challenged every byte of code. That's in fact what we should strive for: Mbed TLS should be configurable so that if you do it correctly, the final binary should have nothing in it that you don't need.

@hanno-arm You have unrealistic expectations about Mbed TLS. Manuel compiled a list of improvements from the baremetal branch that we could take. Making export optional would be about 5th from the bottom, i.e. far below the threshold that we'll ever get around to doing. And that's accounting for the whole cost of the option, not taking into account the code that the compiler can eliminate.
Combinatorial explosion of testing is a problem that you can't just solve by “putting more thought” into it. We have over a hundred boolean options. The total number of combinations is in the cryptographic range. It's literally infeasible to test them all. The fewer obscure combinations there are, the more of a chance we have to be able to reason about them all, let alone cover by testing.
We've put more than 80B of code in redundant checks that we want to have for security or maintainability. Oh, this function can't fail now, but it returns int in case a failure mode was added later — well, we need to put if( ret != 0 ) goto cleanup after it. This variable on the stack in a low-level internal function is realistically never going to remain live until it can be observed — but we still zeroize it. Mbed TLS is a security product, and it's portable. This limits what can be done to reduce the code size. You could write the functionality in assembly and fit it into far fewer kilobytes, but you'd have to say goodbye to maintainability and to security reviews.

Combinatorial explosion of testing is a problem that you can't just solve by “putting more thought” into it. We have over a hundred boolean options. The total number of combinations is in the cryptographic range. It's literally infeasible to test them all. The fewer obscure combinations there are, the more of a chance we have to be able to reason about them all, let alone cover by testing.

That's what I said: You will never get around the combinatorial explosion, there must be thought into which configurations are worth testing. That being the case anyway, I don't see the grounds for removing worthwhile configuration options ("worthwhile" here being := guarding something that is not normally used, and which cannot be removed by the compiler or LTO if it's not used).
Mbed TLS must remain highly configurable, or, in the words of a contributor, maintain its "stellar customizability". Yes, testing is hard, and yes, perhaps some people are overwhelmed by the number of options. But the solution to neither of them is the removal of configuration options, in my view.

While I agree with both sides of this discussion, I don't see a general trend in removing configurable options, so (hopefully) a rain of small codesize increases should not happen. This option, in combination with others, resulted in an untested behaviour (reported by me here: https://github.com/ARMmbed/mbedtls/issues/3998), so I'll prepare a quick preview PR for removing it, and we can discuss further from that point.