ERR_HTTP_HEADERS_SENT with 5.3.0 / 5.3.1 and https-proxy-agent configured

Describe the bug
In 5.3.0 https://github.com/vitejs/vite/commit/7b0a65e added custom logic that utilizes the proxyReq event to set the origin header. This throws an ERR_HTTP_HEADERS_SENT error for me when using using with https-proxy-agent (for example required in setups in which a corporate proxy is in place). I suspect the problem is the same as described in https://github.com/chimurai/http-proxy-middleware/issues/957 and similar / related to the problem described in https://github.com/chimurai/http-proxy-middleware/issues/472 (explanation provided in https://github.com/chimurai/http-proxy-middleware/issues/472#issuecomment-695656240).
When downgrading to 5.2.13 everything works again.
Reproduction
https://stackblitz.com/edit/github-sadccs?file=src%2FApp.vue,vite.config.js
Steps to reproduce
Run npm install
Replace https://example.org with an actual https proxy in vite.config.js (i don't know a public available one, sorry)
Run npm run dev
First click on the "Without proxy agent" button, you should see the expected result then.
Now click on the "With proxy agent" button, the ERR_HTTP_HEADERS_SENT should appear in the console.
System Info
Binaries:
    Node: 18.15.0
    npm: 9.5.0

Used Package Manager
npm
Logs

Click to expand!
node:_http_outgoing:663
    throw new ERR_HTTP_HEADERS_SENT('set');
    ^

Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at new NodeError (node:internal/errors:399:5)
    at ClientRequest.setHeader (node:_http_outgoing:663:11)
    at setOriginHeader (file:///-------/node_modules/vite/dist/node/chunks/dep-BcXSligG.js:61768:16)

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Encountered the same issue.
The exception comes from a commit introduced in<EMAIL_ADDRESS>(https://github.com/vitejs/vite/commit/7b0a65e).
This commit will modify the origin in the proxied request header by default, sometimes it will throw exception Cannot set headers after they are sent to the client.
In my case, I observed that the origin does not exist in the GET request header, and no exception is triggered. However, the origin exists in the POST request header, which triggers an exception.
Modify the origin in request headers is only necessary when the server-side explicitly checks for it. In most other scenarios, it is not required.
Three solutions:

Disable modify of origin by default
Check proxyReq.headersSent before modifying origin
Delete origin before entering the vite proxy

2. Check proxyReq.headersSent before modifying origin

This seems the be the best-fix for me, but I'm not too familiar with the original change.
@johnhunter @sapphi-red do you have thoughts on this?

Option 2 sounds like a good solution. I'll have a proper look when I'm back at my desk.

I'll address this along with https://github.com/vitejs/vite/issues/17562


Wox doesn't find 'camera' app

When I type 'camera', Wox does not display the Windows native app 'Camera'.
Other Windows apps such as Photos do work.
Is there anything that can be done about this?

I noticed this recently as well. Not sure why but will look into it soon.

Hi how's it going. This problem is fixed in version 1.52.24. Simply check for new update and restart to get the fix.


Consider Serilog

Consider replacing NLog with Serilog

Serilog does not, at time of writing, appear to support programatically reading the current configuration of a logger, which makes it difficult to support the current functionality which changes the logger configuration dynamically.


Setup multi-module project structure

Nice Job! I was able to login and test the application. I also really like that you included links with additional information in the Readme 🚀
However what confused me was that during application start the domain call returning a andom numbers was performed twice 😕 . Since this is not relevant to the overall structure this should not block the PR.

From the log you can see, that the devtools RestartClassLoader has been instantiated. I think that's why it gets executed twice. When you compile the application with the Maven production profile, this is not the case.


test_out_file.rb: Fix test failures due to Zlib::DataError.

AppVeyor CI tests are constantly failing due to Zlib-related exceptions
like below:
Error: test: append(FileOutputTest): Zlib::DataError: invalid
distance too far back

This is a very weird error, because the file seems to contain a proper
gzip-compressed data stream. In fact, by inserting the following code
before the failing line, I can confirm that the file itself is NOT
broken:
bytes = File.open(path).read   // Read the file being tested
puts(Zlib::GzipReader.new(StringIO.new(bytes)).read)

The strong suspicion is that Ruby's Zlib wrapper (or its build on
AppVeyor) has a serious bug that corrupts file pointers passed to
GzipReader, thus it ends up reading garbage data.
This patch is my attempt to mitigate the issue by modifying the test
functions to pass bytes (rather than file objects) to GzipReader, and
it should protect zlib from read-time data corruptions.

Related links for the actual error logs:

https://ci.appveyor.com/project/fluent/fluentd/build/3021/job/6gp3tu2f3qimeyhy#L158
https://ci.appveyor.com/project/fluent/fluentd/build/3020/job/k6ad5v0mwfdcmpem#L147
https://ci.appveyor.com/project/fluent/fluentd/build/3019/job/pedwsa74ne4kjfhf#L275

Thx for mitigating weird test failure.


Add Transactions Section

User Story
As a user, I want to be able to view a screen that has a list of all my transactions, purchases, sales, and disputes I am moderating (cases). This screen should let me filter and search my transactions. I should be able to take an action to see the details of a transaction, and take further action if needed (see the requirements for the Transaction Details screen).
Functional Requirements
Tab Bar

[ ] there should be a tab bar at the top of the screen.
[ ] the tab bar should have the viewing user's avatar, name, and other information, identically to the user page tab bar (it may be a good idea to create a small reusable view for both).
[ ] the tab bar should have 3 tabs (Sales, Purchases, Cases). Clicking on a tab will show the transactions associated with that tab.
[ ] each tab should have a number next to it, this number is the total number of transactions for each.

Search and Filters

[ ] there should be a search bar. It is activated by pressing the enter key while it has focus.
[ ] on activation, any text in the search bar is searched for in the transactions type currently active (sales, purchases, cases).
[ ] the search is applied to the order number, title, id, handle, shipping address (name of other party if that's available).
[ ] there are 8 filters, each of which represent one of the possible statuses of a transaction. By default Purchasing (an unfunded order) is unchecked, and the rest are checked.
[ ] the displayed results are filtered by the checked filters (as an OR).

Filter : Status
New order, has not yet been accepted by the vendor (direct pay, offline)
Purchasing, PENDING   = 0;
Vendor has accepted the order and is awaiting payment (direct pay)
Purchasing, CONFIRMED = 1;
Buyer has funded the order
Ready to Process, FUNDED    = 2;
Vendor has shipped the item/sent the digital good
Fulfilled, FULFILLED = 3;
Buyer has completed the order, released the funds, and left a review
Completed, COMPLETE  = 4;
Contract is under active dispute
Disputed, DISPUTED  = 5;
The moderator has resolved the dispute and we are waiting for the winning party to accept the payout.
Dispute Closed (this text should be updated), DECIDED   = 6;
The winning party has accepted the dispute and it is now complete. After the buyer leaves a review the state should be set to COMPLETE.
Dispute Resolved, RESOLVED  = 7;
Vendor refunded the order
Refunded REFUNDED  = 8;
Buyer canceled the order (offline order only)
Completed, CANCELED  = 9;
Vendor declined to confirm the order (offline order only)
Completed, REJECTED  = 10;
List of Transactions

[ ] the currently retrieved transactions are shown in a list.
[ ] clicking on the date header will change the order from ascending to descending by date
[ ] REMOVE: the drop down to change the currency.
[ ] ADD: the price in BTC in parenthesis after the fiat price, if the price is in fiat.
[ ] if the user changes their currency in the settings, this page will show a refresh pop up or refresh the screen.
[ ] if the status of the order has an action required, that action is shown in the status column, with the appropriate buttons.
[ ] if the transaction is marked as unread, it is bold and has a green bar.
[ ] if the transaction has unread messages, a number in a green bubble is shown next to the buyer id/handle.

if the status is PENDING(0), the buyer may cancel the order. The seller must confirm or reject the order.
if the status is CONFIRMED(1), the buyer must fund the order.
if the status is FUNDED(2), the seller must refund the order or fulfill it (this will open the details screen).
if the status is FULFILLED(3), the buyer must complete the transaction (this will open the details screen).
if the status is DECIDED(6), either the buyer or seller must accept the decision (this will open the details modal).

[ ] show pagination controls at the bottom of the page.

Data
The following APIs will be used for this functionality:

ob/purchases
ob/sales
ob/cases

To meet all of the requirements above, the APIs for sales, puchases and cases would need something similar to the following parameters:
ob/[purchases/sales/cases]?
limit: [int],
offsetId: [int],
sortBy: [string], (optional, we may want to just always use date)
descending: [boolean] (if true, sort in descending order, if false ascending)
To meet all of the requirements above, the APIs for sales, purchases, and cases would need to return additional data similar to that below:
total: int
For loading the avatars, we would want an API that allows the client to request an avatar with the peerID and size as parameters (in the url, as a GET). This call should return cache headers so that the results are cached for a long time, to prevent the network from making a large number of calls in a short period of time.

this is done.


Application Hang on Scroll (Axi)

Describe the bug
Application is caught in an endless loop  when reaching bottom of Axis scroll list (with vaueld relics shown)
To Reproduce
Steps to reproduce the behavior:

Go to 'relics'
untick hide vaulted
Click on 'axis'
Scroll down to last row
See error

Expected behavior
idle cpu and not 100% and flashing unresposive UI
Desktop (please complete the following information):

OS: [e.g. W10]
.NET version [e.g. 4.8]
Version [e.g. v9.,3,3]

WS10 reproducable, but i have no idea what can cause this

WS10 reproducable, but i have no idea what can cause this
note : it only freeze the relics window, not the whole software
edit : when trying to re-open the window, WFinfo crashes with these logs : https://pastebin.com/adFz2ts7

just run it on the debugger and it should be easy to figure out.
i dont have this thing set up yet nor looked at the code for more than a second :)

Suposedly fixed in #154


optimization suggestion

Very nice work !
I wondered if you have considered rewriting another version in Python ? Since it is de-facto the programming language when speed is a requirement. I mean, Julia is fine but Python is rock-solid:  fast, and business-safe.
Looking forward for updates 😁

Thank you for your comments. I have not yet planned to port this to Python. You may have a look at https://github.com/emmt/VMLMB/tree/main/python which is an implementation of my VMLMB algorithm in pure Python and with a similar API for vector-like computations.


Burmese appears on Facebook preview in editor view

Reported by Wes in Slack:
https://api.cannabis.ca.gov/licensee-campaign-toolkit/
Logged in

Translates to "your friend family Log in to Facebook to start connecting and sharing with people you know."

Forgot to mention: This happens with any Facebook link, not just Cannabis Dpartment's


Typo error

The following line has typo error (Duplicated Point and Vector types):
Many arguments which might be strongly typed as Point3d, Vector3d, Point3d, Vector3d are weakly typed as XYandZ or XandY.
Revised line would be:
Many arguments that could be strongly typed as Point3d, Vector3d, Point2d, or Vector2d are weakly typed as XYandZ or XandY.

⚠ Do not edit this section. It is required for imodeljs.github.io ➟ GitHub issue linking

LINK: Point-and-Vector-operations---iTwin.js-link-to-docs
TAG: imodeljs-docs-question
SOURCE: https://www.itwinjs.org/learning/geometry/pointvector/

would you like to man an open source contribution? :)


Structures Float on Gravel Beaches

The way gravel beaches seem to work is by removing the top layer, or having it generate as air or something.
Unfortunately, villages and other structures still generate on top of this non-existent surface layer, and so they float slightly off the ground, with doors unreachable by villagers if it so happens to generate on a gravel beach.
Is there anything you can do about this, or is it just an unfortunate side-effect of the way they're done?

Yep, you're correct, it's unfortunately a side effect of how gravel beaches generate.  The topmost layer of a gravel beach is replaced with air (which is why they're always two blocks deep).

I finally found something after a while of searching. There's a stable on a patch of gravel here:
Seed: [-1516676597421523484]
/tp -82853.97 82.57 -75698.72 -234.68 32.24
(The full command was /execute in minecraft:overworld run tp @s -82853.97 82.57 -75698.72 -234.68 32.24, if it's of any use)
I unfortunately couldn't use any of my previous seeds seeing as I used biome and other generation mods in them.
A picture of the stable for reference:

I also ran in to many almost-hits.
This one felt particularly mocking, though:

Apologies for the delay, this was a tricky issue and I got up caught up in other things.  Just fixed with c585fd7.  Unfortunately, the best solution I could think of was to simply give an option to generate gravel beaches at the same height as sand beaches.


httpd: Change 500 into 404 when project doesn't exist

Fixes https://github.com/radicle-dev/heartwood/issues/332

Do you mind adding a small test for this? It's not clear how this change fixes it :)

Cherry picked https://github.com/radicle-dev/heartwood/pull/335/commits/04898f95fc34a2de5733e26ff975f62329374ee0 from the https://github.com/radicle-dev/heartwood/pull/331 and added test.


Extract extension handling

Related to #270 and 3D Tiles serialization. Factoring out the extension handling machinery in CesiumGltfReader for more general use (e.g. 3D tiles).
These are mostly copies of the same-named files in CesiumGltf/CesiumGltfReader up to some renaming. The exceptions are:

Addition of ExtensionContext.cpp/.h, which is the subset of functionality in GltfReader that does extension handling.
Removal of ReaderContext, which was an (unnecessary?) coupling of GltfReader to the extension machinery

The glTF versions can eventually (or now?) be removed and replaced with this common version.

This new library, CesiumJsonExtensions, has two types of things in it:

ExtensibleObject, which has virtually no dependencies except for JsonValue, which is in CesiumUtility.
ExtensionContext, ExtensibleObjectJsonHandler, ExtensionsJsonHandler, and IExtensionJsonHandler, all of which are specific to reading and could go in CesiumJsonReader.

So my feeling is that all the (2) stuff should go in CesiumJsonReader, while ExtensibleObject goes into CesiumUtility. I can also see some wisdom in introducing a CesiumJson library, and moving ExtensibleObject plus JsonValue.h and JsonHelpers.h from CesiumUtility into there instead.
It might also make sense to rename ExtensionContext so that its name captures the fact that it is specific to reading extensions.
I don't think we need a library specific to extensions.

@kring agreed on the reader-only parts and ExtensibleObject - moved those as appropriate. My concern on ExtensionContext is that the 3D Tiles writer PR is going to be adding writer registration to it too - unsure where it would belong at that point.

My concern on ExtensionContext is that the 3D Tiles writer PR is going to be adding writer registration to it too - unsure where it would belong at that point.

I think I would just have a separate ExtensionReaderContext and ExtensionWriterContext. I don't think there's much overlap between them.

Thanks @krupkad, this looks good. Just two requests:

Remove the CesiumGltf versions of this code.
Update CHANGES.md to mention the breaking change of moving these types to their new home.

Unless there's a reason you wanted to do these steps in a separate PR?

@kring thanks,

Unless there's a reason you wanted to do these steps in a separate PR?

Yes, the existing glTF reader classes inherit from CesiumGltfReader::ExtensibleObjectJsonHandler whose constructor takes CesiumGltfReader::ReaderContext which is involved in the GltfReader coupling there. So the changes to do that migration at minimum require touching all of the reader classes, and some light refactoring of the glue code wrapping them.

This looks good to me!


RealSR has no folder basicsr

the inference  inference_diffif.py needs a basic  folder named basicsr

pip install basicsr

the line 13 in inference_diffir.py "from basicsr.archs.S2_arch import DiffIRS2" raises an error " Cannot find reference 'S2_arch' in 'init.py'",  but if I use the DiffIR to replace the basicsr， it seems work

You can check  inference_diffir.py. It seems that line 13 in inference_diffir.py is "from DiffIR.archs.S2_ arch import DiffIRS2".

thank you! it's my typos


0.1beta2 Release

Final PR before publishing second version of Beta release to PyPI.
Changelog

GammaGammaModel Bayesian implementation of Gamma-Gamma model added.
Input validation added to BaseModel class.
Fixed array broadcasting bug in BetaGeoModel.
Revised frequency and monetary value descriptions in User Guide.
Revised SQL code for monetary value calculations in documentation.
Added required dependencies to setup.cfg.

Whoops, wrong repo!


Add API and address config to enable testing bootz service in tests

This pull addresses https://github.com/openconfig/bootz/issues/20. The unit tests will be completed before merge, but before doing  that just want to make sure you agree with the way i am doing it.

I'm not a huge fan of putting test-only code in the Bootz serving code. Is there a way to instead change the public API to return the information we need to do tests?

I'm not a huge fan of putting test-only code in the Bootz serving code. Is there a way to instead change the public API to return the information we need to do tests?

Yes, I agree with you and the pr does that. The test in this pr is just a unit test for the APIs.

I'm not a huge fan of putting test-only code in the Bootz serving code. Is there a way to instead change the public API to return the information we need to do tests?

Yes, I agree with you and the pr does that. The test in this pr is just a unit test for the APIs.

Sorry, what I mean is I don't think we should be adding APIs to the Bootz server that will only be used for testing.
For example, you have added a method to the service that will only ever be used by tests"IsChassisConnected". Is there a way we can test if the chassis is connected by inspecting the response or error of the GetBootstrapData gRPC? Similar applies to getting boot status and resetting the server. IMO these are all things that should be evaluated by looking at the public API, not through a test-only one.

no test has no way to access those info since the test is a separate entity and have no access to the message and logs transferred between the bootzserver and  the router, unless by adding APIs. We can also
(1) create a separate server along tests that only uses entity manager from the bootz repo and include all testing apis.  However, there will lead to duplicate code and impose a risk that test developers may introduce a behaviors that does not comply with the reference implementation.
(2) may use grpc proxy between the router and bootzserevr to inspect the messages between the two, but this will make the testing complicated and probably flaky. Also, not sure how dhcp flow can be validated in this approach.
We can have an offline discussion on this if you want.
@marcushines  what do u suggest?

no, a test has no way to access those info since the test is a separate entity and have no access to the message and logs transferred between the bootzserver and the router, unless by adding APIs. We can also (1) create a separate server along tests that only uses entity manager from the bootz repo and include all testing apis. However, there will lead to duplicate code and impose a risk that test developers may introduce a behaviors that does not comply with the reference implementation. (2) may use grpc proxy between the router and bootzserevr to inspect the messages between the two, but this will make the testing complicated and probably flaky. Also, not sure how dhcp flow can be validated in this approach.
We can have an offline discussion on this if you want.
@marcushines what do u suggest?

Thanks for clarifying. I'll set up another meeting offline for us to discuss this.

will open separate pulls for test apis


WIP: feat: cli output

Landed in https://github.com/metarhia/metasql/commit/5eab1154bbd5abfe0c30092c15e686b5fa824c0e and https://github.com/metarhia/metasql/commit/500cc9bda17fba4fe9ffc9dcf785c4ba655666b1


SPFx 1.12 upgrade getTasks is not defined

Category

[x] Bug ? (Maybe)

Hello,
M365 cli migration tool suggests to add
`
build.rig.getTasks = function () {
var result = getTasks.call(build.rig);
result.set('serve', result.get('serve-deprecated'));

return result;

};
`
to Your gulpfile.js before migration to 1.12. This didn't work for me, I had to use
`
build.rig.getTasks = function () {
var result = this.proto.getTasks.call(build.rig);
result.set('serve', result.get('serve-deprecated'));

return result;

};
`
Hope that helps :)
Have a good one.

Hey @mgwojciech, thanks for reporting. Could you please share the complete gulpfile.js just so that we can double check that everything is in?

Sure,
there are some entries to support fast serve and deal with fs dependency so it's a little bit more than minimal setup but I hope others use fast serve as well :)
`'use strict';
const fs = require('fs');
const build = require('@microsoft/sp-build-web');
build.configureWebpack.mergeConfig({
additionalConfiguration: (generatedConfiguration) => {
generatedConfiguration.node = {
fs: 'empty'
}
fs.writeFileSync("./temp/_webpack_config.json", JSON.stringify(generatedConfiguration, null, 2));
return generatedConfiguration;
}
});
const argv = build.rig.getYargs().argv;
const useCustomServe = argv['custom-serve'];
const workbenchApi = require("@microsoft/sp-webpart-workbench/lib/api");
if (useCustomServe) {
build.tslintCmd.enabled = false;
const ensureWorkbenchSubtask = build.subTask('ensure-workbench-task', function (gulp, buildOptions, done) {
this.log('Creating workbench.html file...');
try {
workbenchApi.default"/workbench";
} catch (e) { }
done();

});
build.rig.addPostBuildTask(build.task('ensure-workbench', ensureWorkbenchSubtask));
}
build.rig.getTasks = function () {
var result = this.proto.getTasks.call(build.rig);
result.set('serve', result.get('serve-deprecated'));

return result;

};
build.initialize(require('gulp'));
`

Thanks for sharing. In the code generated by SPFx v1.12 and suggested by CLI there is one more line that I'm not seeing in your code:
https://github.com/pnp/cli-microsoft365/blob/1760e4a1ab06bcd10f768ea43c518a92c497f50f/src/m365/spfx/commands/project/project-upgrade/rules/FN013002_GULP_serveTask.ts#L23
Could it be that that's causing the issue?

oh yeah, that would make sense. Thanks!

OK to close this issue?

Sure!


Revert "Update cargo to 2015-06-08"

This reverts commit 3aa6608e5b34c1830261c0fb546e8d6078234ae5.

@brson: no appropriate reviewer found, use r? to override

r? @alexcrichton


touchup Tensor.interpolate and Tensor.lerp

rewrite lerp to save one sub and thus flops.
use Tensor.lerp for interpolate and some minor cleanups

nvm the lerp does not help, it's less ops because we count a-b as (a+(-b)) and it doubles the flop now


Use ed25519-consensus instead of ed25519-dalek

Closes #355 (see that issue for more context; ed25519-consensus is a fork of
ed25519-zebra that's Zcash-independent).
This change ensures that tendermint-rs has the same signature verification as
tendermint, which uses the validation criteria provided by the Go
ed25519consensus library.

[x] Referenced an issue explaining the need for the change
[x] Updated all relevant documentation in docs
[x] Updated all code comments where relevant
[x] Wrote tests
[ ] Added entry in .changelog/ I did not do this, because I'm not sure what release to target.

Codecov Report

Merging #1046 (0cf605d) into master (f739e86) will decrease coverage by 0.0%.
The diff coverage is 70.0%.

@@           Coverage Diff            @@
##           master   #1046     +/-   ##
========================================
- Coverage    62.4%   62.4%   -0.1%
========================================
  Files         236     236
  Lines       21321   21301     -20
========================================
- Hits        13325   13297     -28
- Misses       7996    8004      +8

Impacted Files
Coverage Δ

p2p/src/error.rs
0.0% <ø> (ø)

p2p/src/secret_connection/amino_types.rs
0.0% <0.0%> (ø)

pbt-gen/src/time.rs
94.9% <ø> (ø)

proto/src/serializers/timestamp.rs
98.0% <ø> (ø)

tendermint/src/error.rs
0.0% <0.0%> (ø)

tendermint/src/time.rs
98.5% <ø> (ø)

tendermint/src/private_key.rs
56.8% <47.0%> (-2.1%)
:arrow_down:

p2p/src/secret_connection/protocol.rs
59.8% <60.0%> (ø)

tendermint/src/public_key.rs
74.9% <75.0%> (+0.4%)
:arrow_up:

p2p/src/secret_connection.rs
86.3% <78.5%> (-0.2%)
:arrow_down:

... and 17 more

Continue to review full report at Codecov.

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

I did not do this, because I'm not sure what release to target.

I'd say target master (i.e. v0.24.0 of tendermint-rs). If you'd like this to appear in the v0.23.x series then you'd need to submit a separate PR targeting the v0.23.x branch, or make a note of it in #1033 and I'll handle it in the next couple of days.
The changelog entry should probably be listed as a breaking change, right?

Just a changelog entry please and these (hopefully) last few lints, then we can merge.

Updated and superseded by #1067


cst 0.4.1 breaks jscs 3.0.5

The 0.4.0 release of cst has the following deps:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
The 0.4.1 release of cst has the (smaller) dep set:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
This breaks jscs 3.0.5 (see https://github.com/jscs-dev/node-jscs/issues/2278).

Root cause seems to be https://github.com/cst/cst/issues/111, which breaks node < 4.

Okay, three people reported about this, will revert


Implementation of DiskOnTrolleyWithFriction class that represents dynamic system

The #DiskOnTrolleyWithFriction class has been implemented. The code was checked with the following call:
from dynpy.models.mechanics import DiskOnTrolleyWithFriction
from dynpy.utilities.documents.document import DynSysOverviewReport
DynSysOverviewReport(reported_object=DiskOnTrolleyWithFriction());


Questions regarding battery life & 3D print case

Hi there, thanks for sharing the design. They look absolutely interesting. I'm planning to build one for myself.
I have a couple of questions, what is the battery life for the Corne build? Would you able to share the baseplate 3D print file?
Thanks!

Hi! Battery life is really hard to pin down. It really depends on the size of battery that you use. I'm getting at least a couple of weeks with the joycon batteries. That's got a lot to due with the displays being pretty power efficient. If using the OLED displays, it's probably a bit worse. I have some 800 mAh batteries on the one with OLEDs and it's been going for about 2 weeks now. Obviously no displays will get you the best battery life.
I'm working on the case files right now. They are still a work in progress, so I'd put a bit of a caution on those. I'll try to upload them soon.

That's pretty good battery life!
I will order the pcbs, will wait for the 3D files. Thank you for sharing your design, love it!

Case files have been uploaded. They are still a bit of a work in progress though. FYI.

Thank you for share case design. Any chance also share stl for 6col pcb? Thanks.

Unfortunately, I do not have a 6 col version at this time. It won't be too difficult to make one, I just don't have time right now. I might be able to get to it in a few weeks though.

Can I use a corne case instead?

Sorry, missed this. I don't think you can use a corne case. I moved the mount holes and I'm not sure the outline is the same. It would be iffy at best.


[bug] Crash on Assertion failure on macos ventura

Describe the bug
One of our user reported a crash when hitting ESC a lot on Intel mac, Ventura 13.1 (22C65)
❯ RUST_BACKTRACE=full /Applications/Caido.app/Contents/MacOS/Caido
2023-01-17 09:52:07.047 Caido[94074:2731631] *** Assertion failure in -[NSEvent keyCode], NSEvent.m:3003
thread 'main' panicked at 'Uncaught exception <NSException: 0x600001c28270>', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tao-0.15.3/src/platform_impl/macos/event.rs:338:12
stack backtrace:
   0:        0x107226052 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hd2e8cbde22b780fc
   1:        0x10724645a - core::fmt::write::hd6692086cdd356a7
   2:        0x10721ea7c - std::io::Write::write_fmt::h6043124a2486acbb
   3:        0x107227b2b - std::panicking::default_hook::{{closure}}::h87a12b8b06887dd7
   4:        0x107227837 - std::panicking::default_hook::h7f68dad17e0bfaa4
   5:        0x10722814f - std::panicking::rust_panic_with_hook::hd57427cbbfc3717a
   6:        0x107228093 - std::panicking::begin_panic_handler::{{closure}}::h33aab6d04e2bba70
   7:        0x1072264e8 - std::sys_common::backtrace::__rust_end_short_backtrace::h0e7a76f927db9964
   8:        0x107227d5d - _rust_begin_unwind
   9:        0x10726f423 - core::panicking::panic_fmt::hcf6f3c517c6f3cb3
  10:        0x10708012b - core::panicking::panic_display::h4f4ce2dfcd1f5a69
  11:        0x107081fc3 - tao::platform_impl::platform::event::create_key_event::hcc46ee62bbe701ba
  12:        0x1070699e9 - tao::platform_impl::platform::view::cancel_operation::h73473d5ccb497dbf
  13:     0x7ff9076cb51d - <unknown>
  14:     0x7ff907735512 - <unknown>
  15:     0x7ff9077fe862 - <unknown>
  16:     0x7ff907c792c3 - <unknown>
  17:     0x7ff9076db4eb - <unknown>
  18:     0x7ff9078f025e - <unknown>
  19:     0x7ff9076d2e8d - <unknown>
  20:     0x7ff9076cf460 - <unknown>
  21:     0x7ff9076d463d - <unknown>
  22:     0x7ff820db7f6f - <unknown>
  23:     0x7ff820db885a - <unknown>
  24:     0x7ff807139b98 - <unknown>
  25:     0x7ff807139b47 - <unknown>
  26:     0x7ff807139921 - <unknown>
  27:     0x7ff80713859b - <unknown>
  28:     0x7ff807137b80 - <unknown>
  29:     0x7ff810a7c766 - <unknown>
  30:     0x7ff810a7c396 - <unknown>
  31:     0x7ff810a7c2b3 - <unknown>
  32:     0x7ff80a283f33 - <unknown>
  33:     0x7ff80a282db4 - <unknown>
  34:     0x7ff80a2753f7 - <unknown>
  35:        0x106da76c9 - objc_exception::try_no_ret::try_objc_execute_closure::h1b3e62b4774176a9
  36:        0x1070c38c2 - _RustObjCExceptionTryCatch
  37:        0x106db6cad - objc::message::platform::send_unverified::hb74bd746ecde604a
  38:        0x106cba1e9 - tao::platform_impl::platform::event_loop::EventLoop<T>::run::h44acce1761be1b7b
  39:        0x106d69bd3 - tao::event_loop::EventLoop<T>::run::heee933efdc567a5e
  40:        0x106d8648c - <tauri_runtime_wry::Wry<T> as tauri_runtime::Runtime<T>>::run::hccc8ac067e3bfb25
  41:        0x106e6db40 - caido::main::hd646ea77b7c01976
  42:        0x106cf3476 - std::sys_common::backtrace::__rust_begin_short_backtrace::h4e5cd686432cede4
  43:        0x106d9a36c - std::rt::lang_start::{{closure}}::hc26c3dba13a584b3
  44:        0x10721abae - std::rt::lang_start_internal::ha5deaf08dab8765b
  45:        0x106e705ff - _main
  46:     0x7ff806d2b310 - <unknown>

Reproduction
No response
Expected behavior
No response
Platform and versions

Intel mac, Ventura 13.1 (22C65)
tauri: 1.2.0

Stack trace
No response
Additional context
Original issue: https://github.com/caido/caido/issues/345

I am also experiencing the same issue. The stack backtrace is identical.
It can easily be reproduced by just holding down the ESC key for a while.

I got also a different stack trace:
2023-05-11 09:37:25.371 Caido[7541:106674] *** Assertion failure in -[NSEvent keyCode], NSEvent.m:3185
thread 'main' panicked at 'Uncaught exception <NSException: 0x7fe822cc8120>', /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/tao-0.15.3/src/platform_impl/macos/event.rs:338:12
stack backtrace:
   0: rust_begin_unwind
             at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/panicking.rs:142:14
   2: core::panicking::panic_display
             at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/panicking.rs:72:5
   3: tao::platform_impl::platform::event::get_scancode
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/tao-0.15.3/src/platform_impl/macos/event.rs:338:12
   4: tao::platform_impl::platform::event::create_key_event
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/tao-0.15.3/src/platform_impl/macos/event.rs:140:18
   5: tao::platform_impl::platform::view::cancel_operation
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/tao-0.15.3/src/platform_impl/macos/view.rs:892:16
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: <unknown>
  22: <unknown>
  23: <unknown>
  24: <unknown>
  25: <unknown>
  26: <unknown>
  27: <unknown>
  28: <() as objc::message::MessageArguments>::invoke
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/objc-0.2.7/src/message/mod.rs:128:17
  29: objc::message::platform::send_unverified::{{closure}}
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/objc-0.2.7/src/message/apple/mod.rs:27:9
  30: objc_exception::try::{{closure}}
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/objc_exception-0.1.2/src/lib.rs:68:31
  31: objc_exception::try_no_ret::try_objc_execute_closure
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/objc_exception-0.1.2/src/lib.rs:34:9
  32: RustObjCExceptionTryCatch
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/objc_exception-0.1.2/extern/exception.m:10:9
  33: objc_exception::try_no_ret
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/objc_exception-0.1.2/src/lib.rs:44:19
  34: objc_exception::try
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/objc_exception-0.1.2/src/lib.rs:67:9
  35: objc::exception::try
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/objc-0.2.7/src/exception.rs:8:5
  36: objc::message::platform::send_unverified
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/objc-0.2.7/src/message/apple/mod.rs:26:5
  37: objc::message::send_message
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/objc-0.2.7/src/message/mod.rs:178:5
  38: tao::platform_impl::platform::event_loop::EventLoop<T>::run_return
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/tao-0.15.3/src/platform_impl/macos/event_loop.rs:188:16
  39: tao::platform_impl::platform::event_loop::EventLoop<T>::run
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/tao-0.15.3/src/platform_impl/macos/event_loop.rs:155:21
  40: tao::event_loop::EventLoop<T>::run
             at /Users/Sytten/.cargo/registry/src/github.com-1ecc6299db9ec823/tao-0.15.3/src/event_loop.rs:179:5
  41: <tauri_runtime_wry::Wry<T> as tauri_runtime::Runtime<T>>::run
             at /Users/Sytten/.cargo/git/checkouts/dependency-tauri-987ac6e2d82e2314/f73dc64/core/tauri-runtime-wry/src/lib.rs:2129:5
  42: tauri::app::App<R>::run
             at /Users/Sytten/.cargo/git/checkouts/dependency-tauri-987ac6e2d82e2314/f73dc64/core/tauri/src/app.rs:832:5
  43: caido::main
             at ./src/main.rs:61:5
  44: core::ops::function::FnOnce::call_once
             at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/ops/function.rs:248:5

We traced the issue to the fact that if you maintain the ESC and do a mouse activity, it triggers an event that is non-keyboard event so if you call keyCode on it will send an exception as said in the doc: https://developer.apple.com/documentation/appkit/nsevent/1534513-keycode

Further observations:

Gecko flat out decided to not handle the cancelOperation (https://hg.mozilla.org/mozilla-central/log/tip/widget/cocoa/nsCocoaWindow.mm?patch=&linerange=3570:3572) and supposedly that prevents webkit from stealing the CMD+.
The assumptions of that code are now wrong because since sierra ESC also maps to cancelOperation but the code seems to assume its only CMD+. (the referenced eclipse code is 2010, pre-sierra)

Continuing digging, it looks like the most recent version of tao changed something so that now ESC is handled by the on-key down and not the cancelOperation. This most likely fixes the issue but I am unsure what the exact change was, maybe the do_command_by_selector inner code removal. The following snippet was also removed in on key down:
unsafe {
    let responder: id = msg_send![this, nextResponder];
    if !responder.is_null() {
      let () = msg_send![responder, doCommandBySelector: command];
    }
  }

But this only remove the bip sound the OS makes when invalid key is pressed.

So I updated tao to 0.15.8 and wry to 0.22.6 and the issue is gone. So I expect this is due to the fact that the cancel_operation is not called. I can't reproduce the bug with pressing CMD+. and trying to do other mouse events.
Still we should probably add a bit of protection code just to make sure it doesn't come back since it looks like it was a side effect of another piece of code. Most likely in the NSResponder chain if you don't handle the event on key down it might fall back to a cancel operation.

To reproduce the issue use tao 0.15.3 and wry 0.22.0, it might affect other versions but those versions are known to not be working.

The more I dig around it, it does look like having an empty doCommandBySelector (https://developer.apple.com/documentation/appkit/nstextinput/1412853-docommandbyselector) is in fact a hack since it will block the command from being forwarded to the responder chain so the ESC will be treated only as a key down.
It's interesting choice since that means that tao doesn't deal with the quit event anymore (CMD+Q doesn't work on the tao examples), but wry does. This should really be documented in the code otherwise someone is bound to remove that empty method in the future by accident.

Is there a reproduction step for this? Or a single blank tauri window will trigger it?

A blank tauri page should trigger it if you have the right tao and wry versions.
Though we kinda know why this happens, so mostly I would suggest removing the commented code in tao here https://github.com/tauri-apps/tao/blob/dev/src/platform_impl/macos/view.rs#L578-L612 and add a comment to the effect of what I said in my comment above (https://github.com/tauri-apps/tauri/issues/6082#issuecomment-1544324800)

@wusyong It seems like all shutcuts are broken in release mode, dev is working
https://github.com/tauri-apps/tauri/issues/5669


DFYN dual farm apy

@Moonster-BSC it seems we can remove "blockchain-addressbook" and just use tokenSymbol as id


make it optional

not sure this is even any faster

I'll, have a look tomorrow.

see 28ed9bd. I've made it optional, I'll benchmark tomorrow.

I like your version a lot more and suspect it is faster to boot.

closing this in favour of #134


Revamp Snowflake

Describe your changes :

Fixes multiple snowflake issues

Improving the flow
Extraction issues
Fixed Multiple Schema issues

Type of change :

[x] Bug fix
[x] Improvement
[x] New feature
[] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

@open-metadata/ingestion

hi @ayush-shah , I went ahead and did some cleaning. It's basically the same, but please take a look whenever you get the chance. let's merge this on Monday and  close the tickets that this fixes 👍

Let's ignore the sonar bug. We'll clean the full SQLSource in a week


header: move ext header into different package

The purpose of moving Extended header into different package is to avoid cyclic dependency between fraud Service and Syncer:

fraud service(which is from package fraud) is required to get ExtHeader(which is in package header) to verify fraud proof;
Syncer(which is from package header) is required to have Subscription on BEFP;

After discussion with @Wondertan we think that it's the fastest and the easiest solution now.

closed in favour of https://github.com/celestiaorg/celestia-node/issues/322


Erro running bootstrap.bat under Windows

Run log: I want to build the tests so I changed CMakeLists.txt a little bit.
PS C:\work\hid\hid.hpp> git diff
diff --git a/CMakeLists.txt b/CMakeLists.txt
index fcd6c9d..0f5f6b4 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -13,7 +13,7 @@ else ()
 endif()

 ##################################################    Options     ##################################################
-option(BUILD_TESTS "Build tests." OFF)
+option(BUILD_TESTS "Build tests." ON)

 ##################################################    Sources     ##################################################
 file(GLOB_RECURSE PROJECT_HEADERS include/*.h include/*.hpp include/*.ipp)

PS C:\work\hid\hid.hpp> .\bootstrap.bat

C:\work\hid\hid.hpp>if not exist "build" mkdir build

C:\work\hid\hid.hpp>cd build

C:\work\hid\hid.hpp\build>if not exist "vcpkg" git clone https://github.com/Microsoft/vcpkg.git

C:\work\hid\hid.hpp\build>cd vcpkg

C:\work\hid\hid.hpp\build\vcpkg>if not exist "vcpkg.exe" call bootstrap-vcpkg.bat

C:\work\hid\hid.hpp\build\vcpkg>set VCPKG_DEFAULT_TRIPLET=x64-windows

C:\work\hid\hid.hpp\build\vcpkg>vcpkg install --recurse doctest hidapi
Computing installation plan...
The following packages are already installed:
    doctest:x64-windows -> 2.4.11
    hidapi:x64-windows -> 0.14.0
doctest:x64-windows is already installed
hidapi:x64-windows is already installed
Total install time: 1.1 ms
doctest provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(doctest CONFIG REQUIRED)
    target_link_libraries(main PRIVATE doctest::doctest)

hidapi provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(hidapi CONFIG REQUIRED)
    target_link_libraries(main PRIVATE hidapi::hidapi hidapi::winapi hidapi::include)

C:\work\hid\hid.hpp\build\vcpkg>cd ..

C:\work\hid\hid.hpp\build>cmake -DCMAKE_TOOLCHAIN_FILE=./vcpkg/scripts/buildsystems/vcpkg.cmake ..
CMake Error at CMakeLists.txt:3 (project):
  Generator

    Ninja

  does not support platform specification, but platform

    x64

  was specified.

CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!

C:\work\hid\hid.hpp\build>cmake --build . --clean-first --target ALL_BUILD --config Release --parallel 8
CMake Error:
  Generator

    Ninja

  does not support platform specification, but platform

    x64

  was specified.

Removing the -A64 seems to sort out the issue, even with an error message at the end:
ninja: error: unknown target 'ALL_BUILD'

Run-log:
PS C:\work\hid\hid.hpp> git diff
diff --git a/CMakeLists.txt b/CMakeLists.txt
index fcd6c9d..0f5f6b4 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -13,7 +13,7 @@ else ()
 endif()

 ##################################################    Options     ##################################################
-option(BUILD_TESTS "Build tests." OFF)
+option(BUILD_TESTS "Build tests." ON)

 ##################################################    Sources     ##################################################
 file(GLOB_RECURSE PROJECT_HEADERS include/*.h include/*.hpp include/*.ipp)
diff --git a/bootstrap.bat b/bootstrap.bat
index 4fe2ca5..1bc6b0a 100644
--- a/bootstrap.bat
+++ b/bootstrap.bat
@@ -10,6 +10,6 @@ set VCPKG_DEFAULT_TRIPLET=x64-windows
 vcpkg install --recurse doctest hidapi
 cd ..

-cmake -Ax64 -DCMAKE_TOOLCHAIN_FILE=./vcpkg/scripts/buildsystems/vcpkg.cmake ..
+cmake -DCMAKE_TOOLCHAIN_FILE=./vcpkg/scripts/buildsystems/vcpkg.cmake ..
 cmake --build . --clean-first --target ALL_BUILD --config Release --parallel 8
 cd ..

PS C:\work\hid\hid.hpp> .\bootstrap.bat

C:\work\hid\hid.hpp>if not exist "build" mkdir build

C:\work\hid\hid.hpp>cd build

C:\work\hid\hid.hpp\build>if not exist "vcpkg" git clone https://github.com/Microsoft/vcpkg.git
Cloning into 'vcpkg'...
remote: Enumerating objects: 197613, done.
remote: Total 197613 (delta 0), reused 0 (delta 0), pack-reused 197613Receiving objects: 100% (197613/197613), 64.96 MiBReceiving objects: 100% (197613/197613), 72.61 MiB | 17.77 MiB/s, done.

Resolving deltas: 100% (128166/128166), done.
Updating files: 100% (10308/10308), done.

C:\work\hid\hid.hpp\build>cd vcpkg

C:\work\hid\hid.hpp\build\vcpkg>if not exist "vcpkg.exe" call bootstrap-vcpkg.bat
Downloading https://github.com/microsoft/vcpkg-tool/releases/download/2023-06-15/vcpkg.exe -> C:\work\hid\hid.hpp\build\vcpkg\vcpkg.exe... done.
Validating signature... done.

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

Read more about vcpkg telemetry at docs/about/privacy.md
Computing installation plan...
The following packages will be built and installed:
    doctest:x64-windows -> 2.4.11
    hidapi:x64-windows -> 0.14.0
  * vcpkg-cmake:x64-windows -> 2023-05-04
  * vcpkg-cmake-config:x64-windows -> 2022-02-06#1
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
A suitable version of 7zip was not found (required v21.7.0) Downloading portable 7zip 21.7.0...
Downloading 7zip...
https://www.7-zip.org/a/7z2107-extra.7z->C:\work\hid\hid.hpp\build\vcpkg\downloads\7z2107-extra.7z
Downloading https://www.7-zip.org/a/7z2107-extra.7z
Extracting 7zip...
Restored 4 package(s) from C:\Users\xiaof\AppData\Local\vcpkg\archives in 118 ms. Use --debug to see more details.
Installing 1/4 vcpkg-cmake:x64-windows...
Elapsed time to handle vcpkg-cmake:x64-windows: 6.1 ms
Installing 2/4 vcpkg-cmake-config:x64-windows...
Elapsed time to handle vcpkg-cmake-config:x64-windows: 5.08 ms
Installing 3/4 doctest:x64-windows...
Elapsed time to handle doctest:x64-windows: 8.18 ms
Installing 4/4 hidapi:x64-windows...
Elapsed time to handle hidapi:x64-windows: 11.1 ms
Total install time: 31.2 ms
doctest provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(doctest CONFIG REQUIRED)
    target_link_libraries(main PRIVATE doctest::doctest)

hidapi provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(hidapi CONFIG REQUIRED)
    target_link_libraries(main PRIVATE hidapi::hidapi hidapi::winapi hidapi::include)

-- Building for: Ninja
-- The CXX compiler identification is GNU 13.1.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/msys64/mingw64/bin/c++.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done (3.9s)
-- Generating done (0.0s)
-- Build files have been written to: C:/work/hid/hid.hpp/build
[1/1] Cleaning all built files...
Cleaning... 0 files.
ninja: error: unknown target 'ALL_BUILD'

PS C:\work\hid\hid.hpp> cd .\build\

PS C:\work\hid\hid.hpp\build> cmake .
-- Configuring done (0.9s)
-- Generating done (0.0s)
-- Build files have been written to: C:/work/hid/hid.hpp/build
PS C:\work\hid\hid.hpp\build> cmake --build .
[6/6] Linking CXX executable hid_test.exe

The test application seems to be okay.
MINGW64 /c/work/hid/hid.hpp/build
$ ./hid_test.exe
[doctest] doctest version is "2.4.11"
[doctest] run with "--help" for options
################################################################################
version: 0.14.0
version_str: 0.14.0
################################################################################
path: \\?\HID#INTC816#3&d2322f2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x8087
product_id: 0xa1e
serial_number:
release_number: 0x200
manufacturer_string:
product_string:
usage_page: 0x01
usage: 0x0d
interface_number: -1
bus_type: unknown

path: \\?\HID#SYNA7DAB&Col01#5&2f64dfea&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x6cb
product_id: 0xcd40
serial_number: 9999
release_number: 0x501
manufacturer_string: Microsoft
product_string: HIDI2C Device
usage_page: 0x01
usage: 0x02
interface_number: -1
bus_type: i2c

path: \\?\HID#SYNA7DAB&Col02#5&2f64dfea&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x6cb
product_id: 0xcd40
serial_number: 9999
release_number: 0x501
manufacturer_string: Microsoft
product_string: HIDI2C Device
usage_page: 0x0d
usage: 0x05
interface_number: -1
bus_type: i2c

path: \\?\HID#SYNA7DAB&Col03#5&2f64dfea&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x6cb
product_id: 0xcd40
serial_number: 9999
release_number: 0x501
manufacturer_string: Microsoft
product_string: HIDI2C Device
usage_page: 0x0d
usage: 0x0e
interface_number: -1
bus_type: i2c

path: \\?\HID#SYNA7DAB&Col04#5&2f64dfea&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x6cb
product_id: 0xcd40
serial_number: 9999
release_number: 0x501
manufacturer_string: Microsoft
product_string: HIDI2C Device
usage_page: 0xff00
usage: 0x01
interface_number: -1
bus_type: i2c

path: \\?\HID#ConvertedDevice&Col02#5&32cf90e6&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x45e
product_id: 0x00
serial_number:
release_number: 0x00
manufacturer_string:
product_string:
usage_page: 0x0c
usage: 0x01
interface_number: -1
bus_type: unknown

path: \\?\HID#ConvertedDevice&Col03#5&32cf90e6&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x45e
product_id: 0x00
serial_number:
release_number: 0x00
manufacturer_string:
product_string:
usage_page: 0x01
usage: 0x80
interface_number: -1
bus_type: unknown

path: \\?\HID#10251229#3&9d5d338&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0xdeed
product_id: 0xfeed
serial_number:
release_number: 0x101
manufacturer_string: Acer Inc
product_string: Acer Airplane Mode Controller
usage_page: 0x01
usage: 0x0c
interface_number: -1
bus_type: unknown

path: \\?\HID#ConvertedDevice&Col01#5&32cf90e6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\KBD
vendor_id: 0x45e
product_id: 0x00
serial_number:
release_number: 0x00
manufacturer_string:
product_string:
usage_page: 0x01
usage: 0x06
interface_number: -1
bus_type: unknown

path: \\?\HID#VID_1EA7&PID_0064&Col01#6&1bdfd61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x1ea7
product_id: 0x64
serial_number:
release_number: 0x200
manufacturer_string: (Standard system devices)
product_string: 2.4G Mouse
usage_page: 0xffb5
usage: 0x01
interface_number: 0
bus_type: usb

path: \\?\HID#VID_1EA7&PID_0064&Col02#6&1bdfd61d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x1ea7
product_id: 0x64
serial_number:
release_number: 0x200
manufacturer_string: (Standard system devices)
product_string: 2.4G Mouse
usage_page: 0x01
usage: 0x02
interface_number: 0
bus_type: usb

################################################################################
opened device at path: \\?\HID#INTC816#3&d2322f2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

device_info:
path: \\?\HID#INTC816#3&d2322f2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x8087
product_id: 0xa1e
serial_number:
release_number: 0x200
manufacturer_string:
product_string:
usage_page: 0x01
usage: 0x0d
interface_number: -1
bus_type: unknown

serial_number:
manufacturer_string:
product_string:

hid::device::indexed_string(0) failed with error: HidD_GetIndexedString: (0x00000032) The request is not supported.
hid::device::indexed_string(1) failed with error: HidD_GetIndexedString: (0x00000032) The request is not supported.
hid::device::indexed_string(2) failed with error: HidD_GetIndexedString: (0x00000032) The request is not supported.
hid::device::indexed_string(3) failed with error: HidD_GetIndexedString: (0x00000032) The request is not supported.

report_descriptor: 0x05 0x01 0x09 0x0d 0xa1 0x01 0x09 0x0d 0xa1 0x02 0x85 0x1c 0x09 0x81 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x01 0x81 0x02 0x75 0x07 0x95 0x01 0x81 0x03 0x09 0xcb 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x01 0xb1 0x02 0x75 0x07 0x95 0x01 0xb1 0x03 0xc0 0xc0

hid::device::input_report(0) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::input_report(1) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::input_report(2) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::input_report(3) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.

hid::device::feature_report(0) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::feature_report(1) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::feature_report(2) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::feature_report(3) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.

read:
read:
hid::device::write() failed with error: WriteFile: (0x00000001) Incorrect function.
hid::device::send_feature_report() failed with error: HidD_SetFeature: (0x00000057) The parameter is incorrect.
################################################################################
===============================================================================
[doctest] test cases: 1 | 1 passed | 0 failed | 0 skipped
[doctest] assertions: 0 | 0 passed | 0 failed |
[doctest] Status: SUCCESS!

Ah, I think this may be a false alarm. I was not running bootstrap.bat under Developer PowerShell for VS2022 prompt and MSYS2 mingw64 was in the directory -- so cmake picks up MSYS2 mingw64 and not VS2022.
Once I run bootstrap.bat under Developer PowerShell for VS2022, it seems to be all okay.
PS C:\work\hid\hid.hpp> git diff
diff --git a/CMakeLists.txt b/CMakeLists.txt
index fcd6c9d..0f5f6b4 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -13,7 +13,7 @@ else ()
 endif()

 ##################################################    Options     ##################################################
-option(BUILD_TESTS "Build tests." OFF)
+option(BUILD_TESTS "Build tests." ON)

 ##################################################    Sources     ##################################################
 file(GLOB_RECURSE PROJECT_HEADERS include/*.h include/*.hpp include/*.ipp)

PS C:\work\hid\hid.hpp> .\bootstrap.bat

C:\work\hid\hid.hpp>if not exist "build" mkdir build

C:\work\hid\hid.hpp>cd build

C:\work\hid\hid.hpp\build>if not exist "vcpkg" git clone https://github.com/Microsoft/vcpkg.git
Cloning into 'vcpkg'...
remote: Enumerating objects: 197613, done.
remote: Total 197613 (delta 0), reused 0 (delta 0), pack-reused 197613
Receiving objects: 100% (197613/197613), 72.61 MiB | 17.45 MiB/s, done.
Resolving deltas: 100% (128166/128166), done.
Updating files: 100% (10308/10308), done.

C:\work\hid\hid.hpp\build>cd vcpkg

C:\work\hid\hid.hpp\build\vcpkg>if not exist "vcpkg.exe" call bootstrap-vcpkg.bat
Downloading https://github.com/microsoft/vcpkg-tool/releases/download/2023-06-15/vcpkg.exe -> C:\work\hid\hid.hpp\build\vcpkg\vcpkg.exe... done.
Validating signature... done.

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

Read more about vcpkg telemetry at docs/about/privacy.md
Computing installation plan...
The following packages will be built and installed:
    doctest:x64-windows -> 2.4.11
    hidapi:x64-windows -> 0.14.0
  * vcpkg-cmake:x64-windows -> 2023-05-04
  * vcpkg-cmake-config:x64-windows -> 2022-02-06#1
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
A suitable version of 7zip was not found (required v21.7.0) Downloading portable 7zip 21.7.0...
Downloading 7zip...
https://www.7-zip.org/a/7z2107-extra.7z->C:\work\hid\hid.hpp\build\vcpkg\downloads\7z2107-extra.7z
Downloading https://www.7-zip.org/a/7z2107-extra.7z
Extracting 7zip...
Restored 4 package(s) from C:\Users\xiaof\AppData\Local\vcpkg\archives in 112 ms. Use --debug to see more details.
Installing 1/4 vcpkg-cmake:x64-windows...
Elapsed time to handle vcpkg-cmake:x64-windows: 6.26 ms
Installing 2/4 vcpkg-cmake-config:x64-windows...
Elapsed time to handle vcpkg-cmake-config:x64-windows: 4.96 ms
Installing 3/4 doctest:x64-windows...
Elapsed time to handle doctest:x64-windows: 7.06 ms
Installing 4/4 hidapi:x64-windows...
Elapsed time to handle hidapi:x64-windows: 9.68 ms
Total install time: 28.6 ms
doctest provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(doctest CONFIG REQUIRED)
    target_link_libraries(main PRIVATE doctest::doctest)

hidapi provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(hidapi CONFIG REQUIRED)
    target_link_libraries(main PRIVATE hidapi::hidapi hidapi::winapi hidapi::include)

-- Building for: Visual Studio 17 2022
-- Selecting Windows SDK version 10.0.22000.0 to target Windows 10.0.22621.
-- The CXX compiler identification is MSVC 19.35.32217.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: C:/work/hid/hid.hpp/build
MSBuild version 17.5.1+f6fdcf537 for .NET Framework

MSBuild version 17.5.1+f6fdcf537 for .NET Framework

  Checking Build System
  Building Custom Rule C:/work/hid/hid.hpp/CMakeLists.txt
  main.cpp
  test_main.vcxproj -> C:\work\hid\hid.hpp\build\test_main.dir\Release\test_main.lib
  Building Custom Rule C:/work/hid/hid.hpp/CMakeLists.txt
  Building Custom Rule C:/work/hid/hid.hpp/CMakeLists.txt
  Building Custom Rule C:/work/hid/hid.hpp/CMakeLists.txt
  hid_test.cpp
  hid_minimal_test.cpp
  hid_minimal_test.vcxproj -> C:\work\hid\hid.hpp\build\Release\hid_minimal_test.exe
  hid_test.vcxproj -> C:\work\hid\hid.hpp\build\Release\hid_test.exe
  Building Custom Rule C:/work/hid/hid.hpp/CMakeLists.txt

PS C:\work\hid\hid.hpp> .\build\Release\hid_test.exe
[doctest] doctest version is "2.4.11"
[doctest] run with "--help" for options
################################################################################
version: 0.14.0
version_str: 0.14.0
################################################################################
path: \\?\HID#INTC816#3&d2322f2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x8087
product_id: 0xa1e
serial_number:
release_number: 0x200
manufacturer_string:
product_string:
usage_page: 0x01
usage: 0x0d
interface_number: -1
bus_type: unknown

path: \\?\HID#SYNA7DAB&Col01#5&2f64dfea&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x6cb
product_id: 0xcd40
serial_number: 9999
release_number: 0x501
manufacturer_string: Microsoft
product_string: HIDI2C Device
usage_page: 0x01
usage: 0x02
interface_number: -1
bus_type: i2c

path: \\?\HID#SYNA7DAB&Col02#5&2f64dfea&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x6cb
product_id: 0xcd40
serial_number: 9999
release_number: 0x501
manufacturer_string: Microsoft
product_string: HIDI2C Device
usage_page: 0x0d
usage: 0x05
interface_number: -1
bus_type: i2c

path: \\?\HID#SYNA7DAB&Col03#5&2f64dfea&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x6cb
product_id: 0xcd40
serial_number: 9999
release_number: 0x501
manufacturer_string: Microsoft
product_string: HIDI2C Device
usage_page: 0x0d
usage: 0x0e
interface_number: -1
bus_type: i2c

path: \\?\HID#SYNA7DAB&Col04#5&2f64dfea&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x6cb
product_id: 0xcd40
serial_number: 9999
release_number: 0x501
manufacturer_string: Microsoft
product_string: HIDI2C Device
usage_page: 0xff00
usage: 0x01
interface_number: -1
bus_type: i2c

path: \\?\HID#ConvertedDevice&Col02#5&32cf90e6&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x45e
product_id: 0x00
serial_number:
release_number: 0x00
manufacturer_string:
product_string:
usage_page: 0x0c
usage: 0x01
interface_number: -1
bus_type: unknown

path: \\?\HID#ConvertedDevice&Col03#5&32cf90e6&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x45e
product_id: 0x00
serial_number:
release_number: 0x00
manufacturer_string:
product_string:
usage_page: 0x01
usage: 0x80
interface_number: -1
bus_type: unknown

path: \\?\HID#10251229#3&9d5d338&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0xdeed
product_id: 0xfeed
serial_number:
release_number: 0x101
manufacturer_string: Acer Inc
product_string: Acer Airplane Mode Controller
usage_page: 0x01
usage: 0x0c
interface_number: -1
bus_type: unknown

path: \\?\HID#ConvertedDevice&Col01#5&32cf90e6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\KBD
vendor_id: 0x45e
product_id: 0x00
serial_number:
release_number: 0x00
manufacturer_string:
product_string:
usage_page: 0x01
usage: 0x06
interface_number: -1
bus_type: unknown

path: \\?\HID#VID_1EA7&PID_0064&Col01#6&1bdfd61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x1ea7
product_id: 0x64
serial_number:
release_number: 0x200
manufacturer_string: (Standard system devices)
product_string: 2.4G Mouse
usage_page: 0xffb5
usage: 0x01
interface_number: 0
bus_type: usb

path: \\?\HID#VID_1EA7&PID_0064&Col02#6&1bdfd61d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x1ea7
product_id: 0x64
serial_number:
release_number: 0x200
manufacturer_string: (Standard system devices)
product_string: 2.4G Mouse
usage_page: 0x01
usage: 0x02
interface_number: 0
bus_type: usb

################################################################################
opened device at path: \\?\HID#INTC816#3&d2322f2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

device_info:
path: \\?\HID#INTC816#3&d2322f2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
vendor_id: 0x8087
product_id: 0xa1e
serial_number:
release_number: 0x200
manufacturer_string:
product_string:
usage_page: 0x01
usage: 0x0d
interface_number: -1
bus_type: unknown

serial_number:
manufacturer_string:
product_string:

hid::device::indexed_string(0) failed with error: HidD_GetIndexedString: (0x00000032) The request is not supported.
hid::device::indexed_string(1) failed with error: HidD_GetIndexedString: (0x00000032) The request is not supported.
hid::device::indexed_string(2) failed with error: HidD_GetIndexedString: (0x00000032) The request is not supported.
hid::device::indexed_string(3) failed with error: HidD_GetIndexedString: (0x00000032) The request is not supported.

report_descriptor: 0x05 0x01 0x09 0x0d 0xa1 0x01 0x09 0x0d 0xa1 0x02 0x85 0x1c 0x09 0x81 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x01 0x81 0x02 0x75 0x07 0x95 0x01 0x81 0x03 0x09 0xcb 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x01 0xb1 0x02 0x75 0x07 0x95 0x01 0xb1 0x03 0xc0 0xc0

hid::device::input_report(0) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::input_report(1) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::input_report(2) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::input_report(3) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.

hid::device::feature_report(0) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::feature_report(1) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::feature_report(2) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.
hid::device::feature_report(3) failed with error: Get Input/Feature Report DeviceIoControl: (0x00000057) The parameter is incorrect.

read:
read:
hid::device::write() failed with error: WriteFile: (0x00000001) Incorrect function.
hid::device::send_feature_report() failed with error: HidD_SetFeature: (0x00000057) The parameter is incorrect.
################################################################################
===============================================================================
[doctest] test cases: 1 | 1 passed | 0 failed | 0 skipped
[doctest] assertions: 0 | 0 passed | 0 failed |
[doctest] Status: SUCCESS!

This is something I will nevertheless take a look at.
I was assuming that .bat scripts would be ran straight from cmd or by double clicking. If MSYS2 is in the PATH environment variable (which is kinda dangerous - to mix linux into windows shell), cmake may assume it as the system to build for, even in the context of a batch file.
Building in MSYS2 should still work, but you should probably run bootstrap.sh and not bootstrap.bat for it to build correctly (which in fact omits the -Ax64 toggle).

MSYS2 mingw is not Linux but Windows.
This is the build log under MSYS2 mingw64 prompt.
MINGW64 /c/work/hid/hid.hpp
$ ./bootstrap.sh
warning: Starting with the September 2023 release, the default triplet for vcpkg libraries will change from x86-windows to the detected host triplet (x64-windows). To resolve this message, add --triplet x86-windows to keep the same behavior.
Computing installation plan...
The following packages will be built and installed:
    doctest:x86-windows -> 2.4.11
    hidapi:x86-windows -> 0.14.0
Detecting compiler hash for triplet x86-windows...
A suitable version of powershell-core was not found (required v7.2.11) Downloading portable powershell-core 7.2.11...
Downloading powershell-core...
https://github.com/PowerShell/PowerShell/releases/download/v7.2.11/PowerShell-7.2.11-win-x86.zip->C:\work\hid\hid.hpp\build\vcpkg\downloads\PowerShell-7.2.11-win-x86.zip
Downloading https://github.com/PowerShell/PowerShell/releases/download/v7.2.11/PowerShell-7.2.11-win-x86.zip
Extracting powershell-core...
Restored 0 package(s) from C:\Users\xiaof\AppData\Local\vcpkg\archives in 116 us. Use --debug to see more details.
Installing 1/2 doctest:x86-windows...
Building doctest:x86-windows...
-- Downloading https://github.com/doctest/doctest/archive/v2.4.11.tar.gz -> doctest-doctest-v2.4.11.tar.gz...
-- Extracting source C:/work/hid/hid.hpp/build/vcpkg/downloads/doctest-doctest-v2.4.11.tar.gz
-- Using source at C:/work/hid/hid.hpp/build/vcpkg/buildtrees/doctest/src/v2.4.11-2c5d2f15c5.clean
-- Found external ninja('1.11.0').
-- Configuring x86-windows-dbg
-- Configuring x86-windows-rel
-- Building x86-windows-dbg
-- Building x86-windows-rel
-- Installing: C:/work/hid/hid.hpp/build/vcpkg/packages/doctest_x86-windows/share/doctest/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 71.2 ms.
Elapsed time to handle doctest:x86-windows: 4.1 s
Installing 2/2 hidapi:x86-windows...
Building hidapi:x86-windows...
-- Downloading https://github.com/libusb/hidapi/archive/hidapi-0.14.0.tar.gz -> libusb-hidapi-hidapi-0.14.0.tar.gz...
-- Extracting source C:/work/hid/hid.hpp/build/vcpkg/downloads/libusb-hidapi-hidapi-0.14.0.tar.gz
-- Using source at C:/work/hid/hid.hpp/build/vcpkg/buildtrees/hidapi/src/api-0.14.0-e052aaf522.clean
-- Found external ninja('1.11.0').
-- Configuring x86-windows
-- Building x86-windows-dbg
-- Building x86-windows-rel
-- Fixing pkgconfig file: C:/work/hid/hid.hpp/build/vcpkg/packages/hidapi_x86-windows/lib/pkgconfig/hidapi.pc
-- Downloading https://mirror.msys2.org/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst;https://repo.msys2.org/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst;https://mirror.yandex.ru/mirrors/msys2/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst;https://mirrors.tuna.tsinghua.edu.cn/msys2/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst;https://mirrors.ustc.edu.cn/msys2/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst;https://mirror.selfnet.de/msys2/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst -> mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst...
-- Downloading https://mirror.msys2.org/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst;https://repo.msys2.org/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst;https://mirror.yandex.ru/mirrors/msys2/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst;https://mirrors.tuna.tsinghua.edu.cn/msys2/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst;https://mirrors.ustc.edu.cn/msys2/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst;https://mirror.selfnet.de/msys2/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst -> msys2-msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst...
-- Using msys root at C:/work/hid/hid.hpp/build/vcpkg/downloads/tools/msys2/6f3fa1a12ef85a6f
-- Fixing pkgconfig file: C:/work/hid/hid.hpp/build/vcpkg/packages/hidapi_x86-windows/debug/lib/pkgconfig/hidapi.pc
-- Installing: C:/work/hid/hid.hpp/build/vcpkg/packages/hidapi_x86-windows/share/hidapi/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 115 ms.
Elapsed time to handle hidapi:x86-windows: 8.7 s
Total install time: 13 s
doctest provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(doctest CONFIG REQUIRED)
    target_link_libraries(main PRIVATE doctest::doctest)

hidapi provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(hidapi CONFIG REQUIRED)
    target_link_libraries(main PRIVATE hidapi::hidapi hidapi::winapi hidapi::include)

-- Selecting Windows SDK version 10.0.22000.0 to target Windows 10.0.22621.
-- The CXX compiler identification is MSVC 19.35.32217.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done (4.2s)
-- Generating done (0.1s)
-- Build files have been written to: C:/work/hid/hid.hpp/build
MSBuild version 17.5.1+f6fdcf537 for .NET Framework

MSBuild version 17.5.1+f6fdcf537 for .NET Framework
MSBUILD : error MSB1009: Project file does not exist.
Switch: all.vcxproj

And this is the run log under PowerShell (without MSYS2 mingw64 in the path, without VS2022 in the path).
PS C:\work\hid\hid.hpp> .\bootstrap.bat

C:\work\hid\hid.hpp>if not exist "build" mkdir build

C:\work\hid\hid.hpp>cd build

C:\work\hid\hid.hpp\build>if not exist "vcpkg" git clone https://github.com/Microsoft/vcpkg.git
Cloning into 'vcpkg'...
remote: Enumerating objects: 197613, done.
remote: Total 197613 (delta 0), reused 0 (delta 0), pack-reused 197613
Receiving objects: 100% (197613/197613), 72.61 MiB | 14.25 MiB/s, done.
Resolving deltas: 100% (128166/128166), done.
Updating files: 100% (10308/10308), done.

C:\work\hid\hid.hpp\build>cd vcpkg

C:\work\hid\hid.hpp\build\vcpkg>if not exist "vcpkg.exe" call bootstrap-vcpkg.bat
Downloading https://github.com/microsoft/vcpkg-tool/releases/download/2023-06-15/vcpkg.exe -> C:\work\hid\hid.hpp\build\vcpkg\vcpkg.exe... done.
Validating signature... done.

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

Read more about vcpkg telemetry at docs/about/privacy.md
Computing installation plan...
A suitable version of cmake was not found (required v3.25.1) Downloading portable cmake 3.25.1...
Downloading cmake...
https://github.com/Kitware/CMake/releases/download/v3.25.1/cmake-3.25.1-windows-i386.zip->C:\work\hid\hid.hpp\build\vcpkg\downloads\cmake-3.25.1-windows-i386.zip
Downloading https://github.com/Kitware/CMake/releases/download/v3.25.1/cmake-3.25.1-windows-i386.zip
Extracting cmake...
The following packages will be built and installed:
    doctest:x64-windows -> 2.4.11
    hidapi:x64-windows -> 0.14.0
  * vcpkg-cmake:x64-windows -> 2023-05-04
  * vcpkg-cmake-config:x64-windows -> 2022-02-06#1
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
A suitable version of 7zip was not found (required v21.7.0) Downloading portable 7zip 21.7.0...
Downloading 7zip...
https://www.7-zip.org/a/7z2107-extra.7z->C:\work\hid\hid.hpp\build\vcpkg\downloads\7z2107-extra.7z
Downloading https://www.7-zip.org/a/7z2107-extra.7z
Extracting 7zip...
Restored 4 package(s) from C:\Users\xiaof\AppData\Local\vcpkg\archives in 152 ms. Use --debug to see more details.
Installing 1/4 vcpkg-cmake:x64-windows...
Elapsed time to handle vcpkg-cmake:x64-windows: 7.15 ms
Installing 2/4 vcpkg-cmake-config:x64-windows...
Elapsed time to handle vcpkg-cmake-config:x64-windows: 6.03 ms
Installing 3/4 doctest:x64-windows...
Elapsed time to handle doctest:x64-windows: 9.52 ms
Installing 4/4 hidapi:x64-windows...
Elapsed time to handle hidapi:x64-windows: 11.7 ms
Total install time: 35 ms
doctest provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(doctest CONFIG REQUIRED)
    target_link_libraries(main PRIVATE doctest::doctest)

hidapi provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(hidapi CONFIG REQUIRED)
    target_link_libraries(main PRIVATE hidapi::hidapi hidapi::winapi hidapi::include)

'cmake' is not recognized as an internal or external command,
operable program or batch file.
'cmake' is not recognized as an internal or external command,
operable program or batch file.

This is the same as above but with another installation of cmake in the path. This works properly.
PS C:\work\hid\hid.hpp> .\bootstrap.bat

C:\work\hid\hid.hpp>if not exist "build" mkdir build

C:\work\hid\hid.hpp>cd build

C:\work\hid\hid.hpp\build>if not exist "vcpkg" git clone https://github.com/Microsoft/vcpkg.git
Cloning into 'vcpkg'...
remote: Enumerating objects: 197613, done.
remote: Total 197613 (delta 0), reused 0 (delta 0), pack-reused 197613
Receiving objects: 100% (197613/197613), 72.61 MiB | 12.40 MiB/s, done.
Resolving deltas: 100% (128165/128165), done.
Updating files: 100% (10308/10308), done.

C:\work\hid\hid.hpp\build>cd vcpkg

C:\work\hid\hid.hpp\build\vcpkg>if not exist "vcpkg.exe" call bootstrap-vcpkg.bat
Downloading https://github.com/microsoft/vcpkg-tool/releases/download/2023-06-15/vcpkg.exe -> C:\work\hid\hid.hpp\build\vcpkg\vcpkg.exe... done.
Validating signature... done.

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

Read more about vcpkg telemetry at docs/about/privacy.md
Computing installation plan...
A suitable version of cmake was not found (required v3.25.1) Downloading portable cmake 3.25.1...
Downloading cmake...
https://github.com/Kitware/CMake/releases/download/v3.25.1/cmake-3.25.1-windows-i386.zip->C:\work\hid\hid.hpp\build\vcpkg\downloads\cmake-3.25.1-windows-i386.zip
Downloading https://github.com/Kitware/CMake/releases/download/v3.25.1/cmake-3.25.1-windows-i386.zip
Extracting cmake...
The following packages will be built and installed:
    doctest:x64-windows -> 2.4.11
    hidapi:x64-windows -> 0.14.0
  * vcpkg-cmake:x64-windows -> 2023-05-04
  * vcpkg-cmake-config:x64-windows -> 2022-02-06#1
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
A suitable version of 7zip was not found (required v21.7.0) Downloading portable 7zip 21.7.0...
Downloading 7zip...
https://www.7-zip.org/a/7z2107-extra.7z->C:\work\hid\hid.hpp\build\vcpkg\downloads\7z2107-extra.7z
Downloading https://www.7-zip.org/a/7z2107-extra.7z
Extracting 7zip...
Restored 4 package(s) from C:\Users\xiaof\AppData\Local\vcpkg\archives in 131 ms. Use --debug to see more details.
Installing 1/4 vcpkg-cmake:x64-windows...
Elapsed time to handle vcpkg-cmake:x64-windows: 7.33 ms
Installing 2/4 vcpkg-cmake-config:x64-windows...
Elapsed time to handle vcpkg-cmake-config:x64-windows: 5.81 ms
Installing 3/4 doctest:x64-windows...
Elapsed time to handle doctest:x64-windows: 7.79 ms
Installing 4/4 hidapi:x64-windows...
Elapsed time to handle hidapi:x64-windows: 10.6 ms
Total install time: 32.2 ms
doctest provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(doctest CONFIG REQUIRED)
    target_link_libraries(main PRIVATE doctest::doctest)

hidapi provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(hidapi CONFIG REQUIRED)
    target_link_libraries(main PRIVATE hidapi::hidapi hidapi::winapi hidapi::include)

-- Building for: Visual Studio 17 2022
-- Selecting Windows SDK version 10.0.22000.0 to target Windows 10.0.22621.
-- The CXX compiler identification is MSVC 19.35.32217.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: C:/work/hid/hid.hpp/build
MSBuild version 17.5.1+f6fdcf537 for .NET Framework

MSBuild version 17.5.1+f6fdcf537 for .NET Framework

  Checking Build System
  Building Custom Rule C:/work/hid/hid.hpp/CMakeLists.txt
  main.cpp
  test_main.vcxproj -> C:\work\hid\hid.hpp\build\test_main.dir\Release\test_main.lib
  Building Custom Rule C:/work/hid/hid.hpp/CMakeLists.txt
  Building Custom Rule C:/work/hid/hid.hpp/CMakeLists.txt
  Building Custom Rule C:/work/hid/hid.hpp/CMakeLists.txt
  hid_minimal_test.cpp
  hid_test.cpp
  hid_minimal_test.vcxproj -> C:\work\hid\hid.hpp\build\Release\hid_minimal_test.exe
  hid_test.vcxproj -> C:\work\hid\hid.hpp\build\Release\hid_test.exe
  Building Custom Rule C:/work/hid/hid.hpp/CMakeLists.txt

Ah I see. So PowerShell (and probably standard batch) does not see cmake in path.
This is in fact different between our systems as I have it added to local path variable.
Those cmake calls in bootstrap.[sh|bat] should probably point to vcpkg's internal cmake (potentially if a native cmake is not detected). This would avoid the problem right?

Ah I see. So PowerShell (and probably standard batch) does not see cmake in path in the second case.
Those cmake calls in bootstrap.[sh|bat] should probably point to vcpkg's internal cmake (potentially if a native cmake is not detected). This would avoid the problem right?

Yes I think that is the right way to do.


app-bar hide buttons dynamic

In metro-v3 the buttons in an app-bar moved inside a hamburger-menu one-by-one when the screen gets smaller, in metro-v4 all buttons disappear at once on a fixed screen width using media-queries.
The new way is less responsible and lets items overflow outside the screen when the media-query width is set too small.
Would it be possible to move buttons from the appbar to a hamburger menu dynamical on resize?

At this stage, I do not plan to change the behavior of the app-bar in Metro 4. Maybe in later releases.


Port over changes

Pull Request Test Coverage Report for Build 1434

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 75.102%

Totals

Change from base Build 1429:
0.0%

Covered Lines:
2928

Relevant Lines:
3701

💛  - Coveralls

:tada: This PR is included in version 1.14.5 :tada:
Your semantic-release bot :package::rocket:


Update sample.feature

Fix little mistake in scenario where Bob should be used instead of Alice identity

I have used git commit -s but it's still sayed "The sign-off is missing" :/

Fixed! Thanks for your time 😃


CAS1086 - Added 2 new languages to CAS, Farsi and Arabic. Modified UI to...

... include entries for both.

screenshots are attached to the original JIRA entry: https://issues.jasig.org/browse/CAS-1086

Closing CAS1086 to create a new pull request containing only the clean commit.


Datamodel consolidation

Existing data is spread over the following types (*.json files):

agencies
agencyoccupations
agencypeople
documents
employers
images
institutions
inventories
memberships
newspapers
parties
photographers
specialareas

agencies -> Institution, addresses as separate entity connected through hasAddress
agencypeople -> Person
inventories -> Institution
memberships -> Institution
newspapers -> Institution
parties -> Institution
photographers -> Person
specialareas -> ??

MongoDbModel containing the original data as a json field + GenericForeignKey to the instance

agencyoccupations -> ignore; those list 6 "types of occupation", only two of which are referenced in the other json files (each once)

documents: some document instances can be connected to photographers through the oid (but not all)

fields -> lists the labels for the oids that are used in in the photographers.json in the additionalFields list

institutions -> lists the labels for the oids that are used in the photographers.json in the educationlist/institution field

inventories -> lists the labels for the oids that are used in the photographers.json in the inventorylist list

newspapers -> only 5 entries, only one is referenced at two places in images.json and three places in photographers.json; ignore the file for now


Use structured bindings

Description
I found a few places where structured bindings can better express the intent of the code.

SFMLBuildMaster: Build this please.


check if the pullToRefresh is active/refreshing

There some way to check if the pullToRefresh is active/refreshing?
Thanks before and great job anyway!

Hello , for now there's no way to check for it. But as a work around i can suggest you to create a variable and setRefreshing for PullToRefresh with this variable, than simply check is this variable true or false


[IOTDB-5458] Add Session Idle Time Metrics and Upgrade Thrift related Metrics

Add Session Idle Time Metrics: introduce a timer to statistic the distribution of idle time.
Upgrade thrift related metrics from the important level to the core level.
Fix some code smells.


User must not be logged in if token expires

PR approval required https://github.com/fredsonchaves07/movie-catch-api/pull/181 and https://github.com/fredsonchaves07/movie-catch-api/pull/182

This question will not be integrated as an authentication rule as there is already logic and specific validation for all tokens that are generated


Output template which uses markdown tables

Related: #69, https://github.com/bazelbuild/skydoc/issues/183
There's much inconsistency with how skydoc deals with escaping and formatting -- we should at the very least provide a basic set of output templates which circumvent the HTML table mess, and thus use pure markdown for all display.

@blossommojekwu @kendalllaneee This might be a great thing to incorporate into a "using custom templates" tutorial, as it would have real use aside from the purpose of being an example.

Tables render really wide on small screens. Why use them at all?
I guess for rules_nodejs we'll make this new template now. Here I have each rule as a level 4 header
https://github.com/alexeagle/rules_nodejs/blob/master/tools/stardoc/templates/rule.vm
On github it looks like
https://github.com/bazelbuild/rules_nodejs/wiki/scratch
And in github pages
https://alexeagle.github.io/rules_nodejs/Stylus.html

I'm glad you've crafted custom templates that work for you :) Certainly an approach that avoids tables is great.
I still propose that it would be nice to have an alternative to the default html-tables templates which uses a purer markdown approach.
We might also consider incorporating such options into the stardoc rule of stardoc.bzl. Currently this rule takes a format string attribute, which can be markdown or proto. (Lets ignore the fact that presently the markdown format is actually markdown with HTML tables).
We could provide an additional "pure markdown" option, which automatically points to a pure-markdown-tables solution.
(We could also incorporate your "markdown-no-tables" solution, as well)
Food for thought. Obviously we don't want to be in the business of providing too many options (as it becomes a support burden), but 2-3 different alternatives might work well.

I think fewer first-party-maintained options is better. Why keep the tables one at all?
Of course Most important is confirming whether docs should be authored in markdown or html.


Overwritten html files when two items of the same type but different case exist and the file system is case insensitive

Search terms
ignore case, case, caseless, overwritten, html
Expected Behavior
Given:

Two exported items of the same kind (e.g. functions) that only vary in case (e.g. 'model' and 'Model')
It should generate a suffix if the generated html files would clash in a case insensitive file system (e.g. Windows or OsX) (e.g. functions/model.html, functions/Model-1.html)

Actual Behavior

The model.html file gets overwritten, so only one of those documents can be accessed in case insensitive file systems.

Environment

Typedoc version: 0.23.8
TypeScript version: 4.7.4
Node.js version: 16.16.0
OS: OSX 12.5

Excellent! Thanks 👍


using weak cryptography algorithms like MD5 or SHA-1

Using weak cryptography algorithms like MD5 or SHA-1 for sensitive operations such as hash generation, password storage, or secret storage can result in well-known attacks, potentially leading to unauthorized access and data compromise.
https://github.com/oracle/oci-native-ingress-controller/blob/main/vendor/github.com/google/uuid/hash.go

@Dris7 Native Ingress controller does not have any encryption functionality. The only place hash are being used is to generate backend set names which are not cryptographically sensitive.


[language] Use transaparent address and salt to represent EventKey.

Motivation
This PR will replace the old event key (which is a hash of an address concatenated with a salt) with its unhashed version. The main reason for pushing this change is because we want to provide a default subscriber for the pub/sub use case. The address in the key will naturally give the block explorer some sense of which account this event is related to.
Have you read the Contributing Guidelines on pull requests?
Yes

LGTM storage-wise

:umbrella: The latest upstream changes (presumably f14cbad4c403760e8da82c7e134dad2cc4cccf01) made this pull request unmergeable. Please resolve the merge conflicts.

Things lgtm, other than the ordering of functions

@bors-libra  r=tnowacki

:pushpin: Commit 8737b09 has been approved by tnowacki

:hourglass: Testing commit 8737b092a3388cc1ccb6d6bfcee26fcc15dbfa20 with merge 8d2c9703a0136b4dba243a8932a4e7fb7373e88a...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: tnowacki
Pushing 8d2c9703a0136b4dba243a8932a4e7fb7373e88a to master...


fixed: action build fail

Thanks for contribution! Seems that it is not the reason why the build failed, but it does make sense.
And sorry for the delay. This project is in lack of maintainers that deal with the code.


Working on first installation, tried again and now it's stopped working.

I'm using the Cisco AnyConnect VPN. Trying to ssh results in temporary failure in name resolution when running WSL 2 on Ubuntu and Linux.
So I went ahead and followed the readme using the latest release of wsl-vpnkit. It ended up working, but when I tried to walk it through with two others, I still had temporary failure in name resolution errors.
I figured I'd go ahead and start with a clean slate myself and run through the same steps again, but now it doesn't work. I feel as though I'm missing some essential step that I did the first time around. Anyone have a clue?
Some details:
I unregistered the wsl-vpnkit distribution, basically just followed the uninstallation steps on the readme. Went through the installation again, but when I start the distribution, it seems that startup.sh doesn't print anything to the terminal. Additionally, when I start the service and try to start it again, I don't get the message about the service already running. Before reinstallation, these messages would show on the terminal window.

I also experienced a similar issue with wsl-vpnkit not working. I think this happens if you start the wsl2 distro before connecting to the vpn. My solution is to enable the vpn and then close all open wsl2 windows/terminals and open them again.
I also have this at the very top of my .zshrc to start the wsl-vpnkit service if it has not been started already:
if [[ -z $(wsl.exe -d wsl-vpnkit ps | grep wsl-vm) ]]; then
    wsl.exe -d wsl-vpnkit service wsl-vpnkit start
fi


llama3 instruct template will have different outputs depending on system tokens

What is the issue?
Issue:
The absense or presence of a system token produces different outputs, based on my findings:
https://github.com/ggerganov/llama.cpp/issues/7062#issuecomment-2100500582
This is even more important for fine tunes on the instruct models as it can break everything.
Official ollama - llama3 template removes tokens if no system message is present:
https://github.com/ollama/ollama/blob/main/docs/modelfile.md
https://ollama.com/library/llama3:instruct/blobs/8ab4849b038c
The corrected template should be:
TEMPLATE """<|start_header_id|>system<|end_header_id|> {{ .System }} <|eot_id|>{{ if .Prompt }} <|start_header_id|>user<|end_header_id|> {{ .Prompt }} <|eot_id|>{{ end }} <|start_header_id|>assistant<|end_header_id|> {{ .Response }} <|eot_id|>"""
Edit:
I've made an official thread and awaiting response:
https://github.com/meta-llama/llama3/issues/203

So meta just changed the template page without answering my issue :) Atleast give some credit where credit is due.


Minor documentation editorial changes

Add quotation marks to configuration.md on scala version
Add a screencap of the assumed directory layout for source / test files when setting up VS Code
As requested into stable and one commit.

Thank you @Quafadas!


Change module structure

rust-analyzer cannot jump to the sys definitons from async-rdma codebase.
To fix the problem, we need to change the module structure in rdma-sys.

Request review @pwang7 @rogercloud


Question on generalization study on Uni3D

In Table 8 of Uni3D, generalization study is conducted by evaluating zero-shot detection accuracy on KITTI. Since two separate detection heads are trained and a dual-BN is leveraged for nuscenes and waymo during pre-training, what are the implementation details for conducting zero-shot detection on KITTI and which detection head is used?

@wangyubin04
Hi, thanks for your question.
Note that Table 8 in Uni3D reports the AP_{BEV} and AP_{3D} of the car category at IoU = 0.7. The experiment setting follows that of ST3D, where the baseline model is trained on source domain (e.g., Waymo) and tested on target domain (e.g. KITTI). For example, the first and fourth rows represent the results of the PV-RCNN model pre-trained on Waymo but evaluated on KITTI (only car category). Similarly, we can use Uni3D to perform the joint training on Waymo and nuScenes, and then directly test on the KITTI dataset, which is shown in the third row of Table 8.


Cisco Shipped Closed

It looks like Cisco Shipped has closed.  Anyone know of a alternative?

It would be possible to host it on any PaaS, that supports SQLite.

@renet123 it would be possible to host it on https://www.openshift.com/, would that work?

Added Red Hat OpenShift support https://www.openshift.com/
How-To => https://github.com/robertcsapo/cisco-meraki-cmx-api-app/tree/openshift/openshift


What am I doing wrong with opening a compute engine?

On pascal:
[justin@pascal83:help]$ visit -nowin -cli
Running: cli3.4.1 -nowin
Running: viewer3.4.1 -nowin -noint -host <IP_ADDRESS> -port 5600
>>> OpenComputeEngine("localhost", ("-np", "16", "-nn", "2"))
Running: mpirun -np 16 -ppn 16 /usr/gapps/visit/3.4.1/linux-x86_64/bin/engine_par -plugindir /g/g20/justin/.visit/3.4.1/linux-x86_64/plugins:/usr/gapps/visit/3.4.1/linux-x86_64/plugins -visithome /usr/gapps/visit/3.4.1 -visitarchhome /usr/gapps/visit/3.4.1/linux-x86_64 -host pascal83 -port 5600
ERROR:  Can't launch using mpirun. No such file or directory

On lassen:
[justin@lassen708:help]$ visit -nowin -cli
Running: cli3.4.1 -nowin
Running: viewer3.4.1 -nowin -noint -host <IP_ADDRESS> -port 5600
>>> OpenComputeEngine("localhost", ("-np", "16", "-nn", "2"))
Running: mpirun -np 16 -ppn 16 /usr/gapps/visit/3.4.1/linux-intel/bin/engine_par -plugindir /g/g20/justin/.visit/3.4.1/linux-intel/plugins:/usr/gapps/visit/3.4.1/linux-intel/plugins -visithome /usr/gapps/visit/3.4.1 -visitarchhome /usr/gapps/visit/3.4.1/linux-intel -host lassen708 -port 5600
/usr/tce/packages/spectrum-mpi/ibm/spectrum-mpi-rolling-release/bin/mpirun: Error: unknown option "-ppn"
Type '/usr/tce/packages/spectrum-mpi/ibm/spectrum-mpi-rolling-release/bin/mpirun --help' for usage.

Try adding -l srun and -p pbatch or -p pvis for pascal.

would you happen to know what to add for lassen?

would you happen to know what to add for lassen?

Looking at the host profile, the launcher command is bsub, partitions are pdebug and pbatch

Thanks. Looks like I need a bank there.

Well, full launch method is bsub/mpirun, so I'm not certain which of those you put for -l.
Pascal's host profile shows sbatch/srun but simply using srun worked for me.
As for bank, do you have wbronze ?

I do have it, but is wbronze on lassen?

It's the default bank listed in the host profile, but I haven't run on lassen in awhile.


SAK-48144 - Reduce the occurrence of the warnings from ComponentManagerShim

Dang @ern why can't I just take @botimer changes?  Noah - I gently disagree with refactoring the three to one.  Whilst I am not expert in this code - it might be nice to know which of the three call patterns each error was caused by to help chasing them back

Hey @botimer - could you take another look?   I accepted all your suggestions (I think).  Thanks.