🐛 Bug Report:

👟 Reproduction steps
launch(Dispatchers.IO) {
    try {
        val client = Client()
            .setEndpoint("http://<IP_ADDRESS>/v1")
            .setProject("619505812e4d0")
            .setKey("94c9dad4e9041994a7470289b01c69......d87bd7d4d27a5ea30c804cae865")
            .setSelfSigned(true)

        val database = io.appwrite.services.Database(client)

        for (i in 0..10000) {
            val response = database.createDocument(
                collectionId = "6195069ccabcf",
                data = mapOf(
                    "userId" to<EMAIL_ADDRESS>                    "premiumStatus" to true,
                    "expiredTo" to 123456
                ),
            )
            val json = response.isSuccessful
            log.info("res $i is $json")
            delay(10)
        }

    } catch (e: Exception) {
        log.error("Exception: ", e)
    } catch (er: AppwriteException) {
        log.error("AppwriteException: ", er)
    }
}

👍 Expected behavior
All this was done for the sake of verification.
It was expected that all documents (data) will be successfully created or the server will not hang from this.
👎 Actual Behavior
The service is now unavailable and does not restart.
Restarting Docker, containers gave no results.
🎲 Appwrite version
Version 0.10.x
💻 Operating system
Windows
🧱 Your Environment
I use WSL2
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Hey @tequilaonelove what do you see in your Appwrite logs?

@tequilaonelove, would you please update the issue title to include a descriptive summary?
Also, are you suggesting the problem is with the Kotlin SDK? I suspect your appwrite instance might be locking up because it isn't able to handle the load (Docker containers don't perform as well in WSL).
Btw, I ran the equivalent in Python and it finished fine:
import logging
import time

from appwrite.client import Client
from appwrite.services.database import Database

logging.basicConfig(level=logging.DEBUG)

try:
    # Initialise the Appwrite client
    client = Client()
    client.set_endpoint('https://my_domain/v1') # Your API Endpoint
    client.set_project('my_project') # Your project ID
    client.set_key('my_key') # Your secret API key

    # Initialize the database SDK with the client object
    database = Database(client)

    # Perform your task
    for i in range(0, 10000):
        result = database.create_document(
            "collection_id",
            {
                "number": i
            },
            ["*"],
            ["*"]
        )
        logging.info("res %d is %s", i, result)
        time.sleep(10/1000)
except Exception as err:
    logging.exception(err)

Im dont close connections in code: response.body?.close().

Im dont close connections in code: response.body?.close().

@tequilaonelove, are you asking if you need to call close? I don't think you need to.
Also, again, would you please update the issue title to be more descriptive? And perhaps you can provide the appwrite logs?

Closing this issue, as there's been no new update and it lacks proper information to help resolve the issue. Feel free to reopen with more information if the issue still exist.


Provide JSDoc

Just for keeping track of this.

I'm on board but let's wait for some conclusion on #87.
Should we annotate types both in Flow and in JSDoc? What's the usual approach here?

I haven't used Flow yet, so I can't really say what's the best approach. I think it also depends if you just want JSDoc in the source code or use it to actually generate a documentation website or something like it.

This was done via #300.


[Papercut][SW-16211] resolve double negatives by offering config type boolean-reverse

Description
Please describe your pull request:

Why is it necessary? Labels of config fields use double negatives to describe the effect. This is confusing. The consequence of changing the wording without negatives would be the necessity to  refactor every condition where the boolean value is queried.
What does it improve? By using the config element typ boolean-reverse the wording can be changed so no negatives are used without the need to refactor every condition elsewhere. It just changes the label for false values to "Yes" and respectively the value of true values to "No".
Does it have side effects? None so far.

Questions
Answers

BC breaks?
no

Tests pass?
yes

Related tickets?
https://issues.shopware.com/issues/SW-16211#/issues/SW-16211

How to test?
Set Config Form Element  with type boolean-reverse "Yes" should be false "No" should be true

Thanks for your PR!
Unfortunately, we won't implement this new xtype in near future, because it is not absolutely necessary at the moment.
This ticket will be solved by changing the misleading labels.


[feature request] ability to disable dismiss by vertically swiping

Currently we have a dismissDragDistance argument to adjust the swiping distance to dismiss image gallery, but I prefer disable it and only offer a way that allow user dismiss image gallery via the overlay.
And I also have another feature request that adjust the gallery direction (PageView's scrollDirection) to vertical instead of horizontal. It's sort of related to this request since currently we hardcoded the swiping guesture as vertical swipe. Let me know if it's acceptable and/or if I need to create another issue for that request.
Thanks!

Hey @BLumia! That's a great request I believe, I have implemented both full-on vertical support and a way to disable drag-to-dismiss.
You can check out v0.9.0. You can let me know if you have any issues 🚀


Change json format of timelines

The old timeline json format had an extra level of nesting that doesn't seem to serve any purpose. This nesting is no longer there in the new backend code.
Old:
 "items": [
       {
            node:  {
            "title": "SIGNED UP",
            "date": "2020-03-10",
            "event_type": "NODE",
            "sub_title": "You started reporting!",
            "summary": null,
            "route_name": null,
            "route_text": null,
            "external_link": null,
            "external_link_text": null,
            "ongoing": null,
            "progress": null,
            "your_contribution": null
        },
    },
]

New:
 "items": [
        {
            "title": "SIGNED UP",
            "date": "2020-03-10",
            "event_type": "NODE",
            "sub_title": "You started reporting!",
            "summary": null,
            "route_name": null,
            "route_text": null,
            "external_link": null,
            "external_link_text": null,
            "ongoing": null,
            "progress": null,
            "your_contribution": null
        },
]

Cool, this bothered me from the start! :)

Ben, I'd personally like to invite you to be braver about saying so - you have good instincts for this :-)


[DRAFT] BREAKING CHANGE: Update options defaults for v1beta1

Fixes #N/A
Description
This PR implements a planned breaking change for the v0.33 beta upgrade which involves setting the following new defaults for the beta version while also dropping the settings merge logic:

The Drift feature gate is now enabled by default.
The webhooks are now disabled by default.
The global log level is now set to info by default if not overridden in the log configuration file

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.05%) to 80.057%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/disruption/expiration.go
2
84.38%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
8217

Relevant Lines:
10264

💛  - Coveralls

/lgtm


Nameplate changes width to fit name and uses different font

This pull request implements two improvements to rendering:

First, instead of being a static size, the nameplate box now adjusts its width to fit the name of whoever is speaking.
Second, it tries to use the nameplate font recreation discussed in issue #22 before falling back to the other fonts.

To do the dynamic nameplate sizing, I did my best to recreate the dialogue box based on screenshots from the original DS games.
Here is a screenshot of a quick test dialogue before the pull request:

And this is what the same dialogue looks like with these changes:

In order for this to work, some additional assets will need to be added to the assets folder. This zip file includes:

ace_name - folder with the font discussed in #22 for the nameplates
textbox - folder with the PNGs for the text box and nameplate parts
AA dialogue box recreation.afphoto - the raw Affinity Photo document with the dialogue box. If you'd like it in another format like PSD, I can certainly export it, but I don't know if any data will be lost.

They should just need to be placed in the assets folder (with the exception of the .afphoto file; it's just there so we can edit it later :) )
I've tested this with the example.py file as well as a few of my own short scripts, and it seems to be working well, but of course it'd be great to have other checks done before merging so it doesn't break anything.
Thanks so much!

This seems fine.
I'll give a test and merge if it's working good

And done.
Thanks a lot, the bots are going to look so much better thanks to your work :)


Common tools(systematics, correction, scripts to output correctionlib)

[ ] HLT prescale
[ ]  change top reweight: https://twiki.cern.ch/twiki/bin/viewauth/CMS/TopPtReweighting#TOP_PAG_corrections_based_on_dat
[ ] B Frag weight: https://twiki.cern.ch/twiki/bin/viewauth/CMS/MLReweighting
[ ] Hdamp weight: https://twiki.cern.ch/twiki/bin/viewauth/CMS/MLReweighting
[ ] other corrections : https://github.com/lenzip/BTagAnalysis/blob/master/BTagAnalyzerSelector.C
[ ] histo-> correctionlib https://gitlab.cern.ch/cms-nanoAOD/jsonpog-integration/-/blob/master/misc/LUM/makePUReWeightJSON.py
[ ] csv->correctionlib https://gitlab.cern.ch/cms-btv/btv-scale-factors

more info about weights
Hi,

If you are thinking on using SV mass as a fitting variable , then you might need a correction for the appropriate modelling of c-jets (like Luca is doing on ptrel): I have computed it already using 2016 data (see slide 3 of [https://indico.cern.ch/event/661833/contributions/2702217/attachments/1513845/2362113/btv280817-jpfr-ctemplatestudies.pdf](https://indico.cern.ch/event/661833/contributions/2702217/attachments/1513845/2362113/btv280817-jpfr-ctemplatestudies.pdf) ) in case you want to give it a try ( see the P.D.)

 But probably this is already second order. Anyway, as I said already, it is there in case you want to give it a try it.

 Best,
  Juan Pablo

P.D.: The correction to apply is as follows :

Here I am providing :

 A - Prototype correction function (sorry, what matters are just the parameters but I prefer to include some details)

 B - eps, root and C files  with the fit (= correction function) including the confidence interval.

 A : double svmassReweight(double rw);

 // way to use it

if (typeofjet == "c")  weight = weight\*svmassReweight(yoursvmass);

double svmassReweight(double rw){

  double a = 1.04340e+00;
  double b = -4.44267e-01;
  double c = 4.81803e-01;
  double d = -1.20184e-01;

  double rwt = a+b\*rw+c\*rw\*rw+d\*rw\*rw\*rw;
  if (rw > 2.5) rwt = 1.0;
  if (rw < 0.) rwt = 1.0;
  return rwt;

 }
 // FCN=8.70425 FROM MIGRAD    STATUS=CONVERGED      87 CALLS 88 TOTAL
 //                    EDM=5.25834e-15    STRATEGY= 1      ERROR MATRIX ACCURATE
 // EXT PARAMETER                                   STEP FIRST
 // NO.   NAME      VALUE            ERROR          SIZE DERIVATIVE
 //  1  p0           1.04340e+00   1.24107e-02   9.35186e-06 -6.06073e-06
 //  2  p1          -4.44267e-01   9.45840e-02   1.44238e-05 4.34457e-06
 //  3  p2           4.81803e-01   1.20232e-01   1.04365e-05 9.68263e-06
 //  4  p3          -1.20184e-01   3.83756e-02   6.05908e-06 1.87564e-05

The sources and motivations of other systematics uncertainties that I use in the code are in this AN
par 2.4.2 of http://cms.cern.ch/iCMS/jsp/openfile.jsp?tp=draft&files=AN2017_018_v9.pdf


Where can I found my S3_ENDPOINT in docker setup? have error: Artifact not found

Hi, I am not sure which S3_ENDPOINT you are refer to ? where can I find it at aws?
aws bucket name: turbo-repo
my .env config
NODE_ENV=production
PORT=3000
TURBO_TOKEN=yourToken
LOG_LEVEL=info
STORAGE_PROVIDER=s3
STORAGE_PATH=turbo-repo
AWS_ACCESS_KEY_ID=<aws secret  id>
AWS_SECRET_ACCESS_KEY=<aws secret key>
AWS_REGION=ap-southeast-1
S3_ENDPOINT=http://turbo-repo.s3.ap-southeast-1.amazonaws.com

I get some error in my docker logs.. not sure what Artifact means..
{"severity":"WARNING","level":40,"time":1662821516456,"pid":7,"hostname":"7467bd81768e","reqId":"oEKrAxmVR0K3hrHPnmpmcA-1","data":{},"isBoom":true,"isServer":false,"output":{"statusCode":404,"payload":{"statusCode":404,"error":"Not Found","message":"Artifact not found"},"headers":{}},"stack":"/home/app/node/src/plugins/remote-cache/routes/get-artifact.ts:29\n      throw notFound(`Artifact not found`, err)\n                    ^\n\nError: Artifact not found\n    at Object.handler (/home/app/node/src/plugins/remote-cache/routes/get-artifact.ts:29:21)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)","type":"Error","message":"Artifact not found"}
{"severity":"INFO","level":30,"time":1662821516458,"pid":7,"hostname":"7467bd81768e","reqId":"oEKrAxmVR0K3hrHPnmpmcA-1","res":{"statusCode":404},"responseTime":53.324764251708984,"message":"request completed"}
{"severity":"INFO","level":30,"time":1662821516696,"pid":7,"hostname":"7467bd81768e","reqId":"oEKrAxmVR0K3hrHPnmpmcA-2","req":{"method":"POST","url":"/v8/artifacts/events?teamId=team_pingspace_wcs","hostname":"turborepo-cache.pingspace.co","remoteAddress":"<IP_ADDRESS>","remotePort":37378},"message":"incoming request"}
{"severity":"INFO","level":30,"time":1662821516702,"pid":7,"hostname":"7467bd81768e","reqId":"oEKrAxmVR0K3hrHPnmpmcA-2","res":{"statusCode":200},"responseTime":4.817142486572266,"message":"request completed"}

I am pretty sure that my aws access id and secret is able to upload .env file to bucket
aws s3api put-object --bucket turbo-repo --key .env --body .env

If you use AWS_REGION, you can remove S3_ENDPOINT. Only one of two is mandatory. Let me know if it works.
FYI, the warning (404  error) you see is standard since the server couldn't find the artifact. An artifact is a remotely cached version of your local turborepo command execution.

If you use AWS_REGION, you can remove S3_ENDPOINT. Only one of two is mandatory. Let me know if it works.
FYI, the warning (404 error) you see is standard since the server couldn't find the artifact. An artifact is a remotely cached version of your local turborepo command execution.

I removed S3_ENDPOINT at .env file..
but it still show Artifact not found.. I still don't understand An artifact is a remotely cached version of your local turborepo command execution. mean? I checked my s3 bucket.. still empty

my latest logs from docker
{"severity":"INFO","level":30,"time":1663637003773,"pid":7,"hostname":"c2fb30aceb5c","message":"Server listening at http://<IP_ADDRESS>:3000"}
{"severity":"INFO","level":30,"time":1663637021482,"pid":7,"hostname":"c2fb30aceb5c","reqId":"teYalIleSSyeUY1zjbBq6A-0","req":{"method":"POST","url":"/v8/artifacts/events?slug=team_pingspace_wcs&teamId=team_pingspace_wcs","hostname":"turborepo-cache.pingspace.co","remoteAddress":"<IP_ADDRESS>","remotePort":49408},"message":"incoming request"}
{"severity":"INFO","level":30,"time":1663637021501,"pid":7,"hostname":"c2fb30aceb5c","reqId":"teYalIleSSyeUY1zjbBq6A-0","res":{"statusCode":200},"responseTime":16.02419662475586,"message":"request completed"}
{"severity":"INFO","level":30,"time":1663637021503,"pid":7,"hostname":"c2fb30aceb5c","reqId":"teYalIleSSyeUY1zjbBq6A-1","req":{"method":"GET","url":"/v8/artifacts/70476cc6f96f028a?slug=team_pingspace_wcs&teamId=team_pingspace_wcs","hostname":"turborepo-cache.pingspace.co","remoteAddress":"<IP_ADDRESS>","remotePort":49410},"message":"incoming request"}
{"severity":"INFO","level":30,"time":1663637021551,"pid":7,"hostname":"c2fb30aceb5c","reqId":"teYalIleSSyeUY1zjbBq6A-2","req":{"method":"GET","url":"/v8/artifacts/21fb2254ce4d2f9c?slug=team_pingspace_wcs&teamId=team_pingspace_wcs","hostname":"turborepo-cache.pingspace.co","remoteAddress":"<IP_ADDRESS>","remotePort":49414},"message":"incoming request"}
{"severity":"WARNING","level":40,"time":1663637021609,"pid":7,"hostname":"c2fb30aceb5c","reqId":"teYalIleSSyeUY1zjbBq6A-1","data":{},"isBoom":true,"isServer":false,"output":{"statusCode":404,"payload":{"statusCode":404,"error":"Not Found","message":"Artifact not found"},"headers":{}},"stack":"/home/app/node/src/plugins/remote-cache/routes/get-artifact.ts:29\n      throw notFound(`Artifact not found`, err)\n                    ^\n\nError: Artifact not found\n    at Object.handler (/home/app/node/src/plugins/remote-cache/routes/get-artifact.ts:29:21)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)","type":"Error","message":"Artifact not found"}
{"severity":"INFO","level":30,"time":1663637021615,"pid":7,"hostname":"c2fb30aceb5c","reqId":"teYalIleSSyeUY1zjbBq6A-1","res":{"statusCode":404},"responseTime":111.70306777954102,"message":"request completed"}
{"severity":"WARNING","level":40,"time":1663637021618,"pid":7,"hostname":"c2fb30aceb5c","reqId":"teYalIleSSyeUY1zjbBq6A-2","data":{},"isBoom":true,"isServer":false,"output":{"statusCode":404,"payload":{"statusCode":404,"error":"Not Found","message":"Artifact not found"},"headers":{}},"stack":"/home/app/node/src/plugins/remote-cache/routes/get-artifact.ts:29\n      throw notFound(`Artifact not found`, err)\n                    ^\n\nError: Artifact not found\n    at Object.handler (/home/app/node/src/plugins/remote-cache/routes/get-artifact.ts:29:21)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)","type":"Error","message":"Artifact not found"}
{"severity":"INFO","level":30,"time":1663637021620,"pid":7,"hostname":"c2fb30aceb5c","reqId":"teYalIleSSyeUY1zjbBq6A-2","res":{"statusCode":404},"responseTime":65.06990432739258,"message":"request completed"}
{"severity":"INFO","level":30,"time":1663637022204,"pid":7,"hostname":"c2fb30aceb5c","reqId":"teYalIleSSyeUY1zjbBq6A-3","req":{"method":"POST","url":"/v8/artifacts/events?slug=team_pingspace_wcs&teamId=team_pingspace_wcs","hostname":"turborepo-cache.pingspace.co","remoteAddress":"<IP_ADDRESS>","remotePort":49422},"message":"incoming request"}
{"severity":"INFO","level":30,"time":1663637022206,"pid":7,"hostname":"c2fb30aceb5c","reqId":"teYalIleSSyeUY1zjbBq6A-3","res":{"statusCode":200},"responseTime":2.208415985107422,"message":"request completed"}
^C

Update:
I finally found out the problem.. I am using nginx to do the reverse proxy to https domain.. but turn out it can't work.. I am not sure why.. I am using pure ip address .. then it work well..


Empty normalSuffix breaks rendering.

Hi.
I use Netlify with their Pretty URLs option. With the config below generic pages are broken: you can't access them directly (only through index page) or refresh it, instead of that you'll get a bunch of HTML.
    'clean-urls': {
      normalSuffix: '',
      indexSuffix: '/'
    }

Example: https://5cd6eabef6fef10008c3538f--innerequestria.netlify.com/how/gitea
Now I use the next config, which allows me to use clean links.
    'clean-urls': {
      normalSuffix: '.html',
      indexSuffix: '/'
    }

Example: https://5cd7059a66b8b3000c5d83e6--innerequestria.netlify.com/how/gitea

Same here.
When I tried use normalSuffix: '' or normalSuffix: '/', headers from Netlify were same
⫸  curl -I https://hypersignal.xyz/experience
HTTP/2 200
accept-ranges: bytes
cache-control: public, max-age=0, must-revalidate
content-length: 13564
content-type: text/plain; charset=UTF-8
date: Sun, 16 Jun 2019 08:18:08 GMT


Changed import for sawtooth-sdk

In the migration to @restroom-mw/sawtooth-sdk, we haven't changed imports in the code. There are still warning on the types declarations.

:tada: This PR is included in version 1.9.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Possible error in project start docs

The "Install your new package" section of the Starting a new project page starts with this:
>> cd {{project_name}}

I believe that is incorrect. It should be:
>> cd {{project directory}}

That is, the project's directory is not (necessarily) the same as the project_name defined during the copier session defining the project.
At the top of the Starting a new project page is this copier command:
>> copier gh:lincc-frameworks/python-project-template <path/to/destination>

It's that <path/to/destination> where the cd command should aim to place the user.
In the case of my first project, my directory takes the name of the software project I'm working on (from a third part): SOAP-GPU (an acronym). That's not even a possible project_name (because caps are forbidden from project names).

Great catch, and you're absolutely correct. We'll get this updated shortly!

We have a PR waiting for review right now that will correct this.


fixReducedOffersV1: curtail the occurrence of order books that are blocked by reduced offers

High Level Overview of Change
The goal of this amendment is to curtail the occurrence of order books that are blocked by reduced offers.
This commit identifies three ways in which offers can be reduced:

A new offer can be partially crossed by existing offers, so the new offer is reduced when placed in the ledger.

An in-ledger offer can be partially crossed by a new offer in a transaction.  So the in-ledger offer is reduced by the new offer.

An in-ledger offer may be under-funded.  In this case the in-ledger offer is scaled down to match the available funds.

Reduced offers can block order books if the effective quality of the reduced offer is worse than the quality of the original
offer (from the perspective of the taker).  It turns out that, for small values, the quality of the reduced offer can be significantly affected by the rounding mode used during scaling computations.
This commit adjusts some rounding modes so that the quality of a reduced offer is always at least as good (from the taker's perspective) as the original offer.
These rounding changes are on an amendment because they will affect transaction outcomes.  The amendment is titled fixReducedOffersV1 because additional ways of producing reduced offers may come to light.  So there may be a future need for a V2 amendment.
Context of Change
Occasional blocked order books have been a long-standing low-level irritant with the DEX.  There has been at least one patch that helped to manage the problem.  But the patch did not really make the problem go away.  This pull request goes to the root of these blockages and just makes them go away.
First, it's important to recognize that both XRP and IOUs have finite representations in the ledger.  For example, it is not possible to represent fractions of drops.  IOUs also have a finite representation that becomes apparent with very small or very large numbers.  So when a number cannot be precisely represented in XRP or by an IOU it must be rounded.
This pull request changes the rounding mode that is used when calculating a reduced offer.  The rounding is changed so that the quality of the reduced offer is always the same or better than the quality of the original offer (viewing the offer's quality from the taker's perspective).
Note that this change affects the values that offers in the ledger contain.  However the change in representation is at most either...

One drop of XRP or
1e-81 of an IOU.

As the values in offers get tiny, rounding effects can have an outsize influence on the quality of an offer.  But the offers are only being adjusted by minute amounts of actual funds.
Type of Change

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Tests (tests for the changes are included in this pull request)
[x] Documentation Updates

I'm calling this a breaking change because outcomes on the DEX are affected.  People who care deeply about the specifics of DEX corner cases would do well to understand the consequences of this pull request.  The pull request also includes an amendment, which can cause amendment blockage.
I'm unsure whether the Doc team will want to include discussion of the details of this change.  But they should be aware of the change and decide for themselves.
Interactions with Number
It turns out that this pull request interacts with the new Number integration with STAmount.  There are three specific things to note:
STAmount::canonicalize rounding  The rounding characteristics of STAmount::canonicalize() changed when Number was integrated.  The new default canonicalize rounding interacted badly with the rounding that fixReducedOffersV1 requires.  Fortunately, Number provides a way to remotely control its rounding mode.  This pull request uses that capability.
Number Rounding Modes  The rounding modes that Number provides do not align precisely with the rounding that STAmount operations use.  STAmount uses a bool named roundUp.  But, what that bool really means is roundAwayFromZero.  So the rounding direction reverses for negative numbers.  If the bool is true STAmount rounds away from zero, and false rounds toward zero.
Number provides a towards_zero rounding mode.  So that's covered.  But Number does not provide an away_from_zero rounding mode.  So I faked this with Number's upward rounding mode.  This should usually work.  And it works in all of my tests because STAmount values are usually positive.
But it would be nice if Number provided an away_from_zero rounding mode.  That would remove the compromise of faking it with upward.
Number::RoundModeGuard.  As I was surgically controlling the Number rounding mode to get the behavior I wanted out of STAmount::canonicalize() I introduced a bug.  I wanted a way to change the Number rounding mode only while I was in a scope and have that mode revert when I left scope.  I thought that Number provided that precise tool with saveNumberRoundMode.  But I was wrong.  I did not read the code carefully enough and made assumptions about the behavior.  So I misused saveNumberRoundMode and @HowardHinnant set me right.
@HowardHinnant ended up implementing NumberRoundModeGuard to give me exactly the behavior that I wanted.  You can see that (almost trivial) implementation in STAmount.cpp of this pull request.
In general I personally think NumberRoundModeGuard is exactly the tool that folks should reach for when surgically adjusting the rounding mode.  I'd like to suggest that it should be a permanent fixture in Number.
Number Request Summary  Here are the changes I'm hoping for:

Add an away_from_zero rounding mode to Number.
Make Number::RoundModeGuard a part of the Number implementation similar to saveNumberRoundMode.

I'll be curious what @gregtatcam and @HowardHinnant think regarding these requests.
I'm requesting @gregtatcam and @HowardHinnant as reviewers since they have the most experience with Number.  I'm hoping that @seelabs will also take a gander since these changes are integrated into the payment engine.

There are compiler warnings on OSX M1 Ventura 13.3.1(a), clang 14.03:
src/ripple/beast/container/detail/aged_unordered_container.h:197:23: warning: 'binary_function<ripple::base_uint<256>, beast::detail::aged_unordered_container<false, true, ripple::base_uint<256>, ripple::HashRouter::Entry, std::chrono::steady_clock, ripple::hardened_hash<>, std::equal_to<ripple::base_uint<256>>, std::allocator<std::pair<const ripple::base_uint<256>, ripple::HashRouter::Entry>>>::element, bool>' is deprecated [-Wdeprecated-declarations]
          public std::binary_function<Key, element, bool>

I don't see these warnings on develop. I assume it just needs to be merged with the latest develop?

I just looked at the latest develop.  I see this commit which I think fixes the compiler warning you are seeing: https://github.com/XRPLF/rippled/commit/8d482d3557fb206eab5c7bbfc57216238b516d14
This pull request hasn't picked up that particular commit yet.
I can rebase if you'd like, as long as it wouldn't mess up @HowardHinnant's review.

I just looked at the latest develop. I see this commit which I think fixes the compiler warning you are seeing: 8d482d3 This pull request hasn't picked up that particular commit yet.
I can rebase if you'd like, as long as it wouldn't mess up @HowardHinnant's review.

I checked that the rebase fixes this warning. No need to rebase now.

Should we consider including in this PR a fix for the related issue: https://ripplelabs.atlassian.net/browse/RXL-226? The fix is to pass the limitQuality to the limitStepOut() and if the quality of the adjusted offer is less than the limitQuality then re-calculate the offer with the roundUp set to false.

We could consider including that fix.  My current inclination is to put that fix on a separate amendment.  These three fixes are useful and have thorough unit tests.  At the least we'd need to add unit tests for the new fix.  With those tests I'd hope to learn whether we can set roundUp to false in that location unconditionally.  There may be additional things we learn while wringing out that additional change.
Beyond that, I heard a report recently that the the tfFillOrKill flag on OfferCreate transactions is not working as expected.  That may (or may not) be yet another problem with ledger rounding.  That problem report could be investigated (and possibly fixed) in the separate amendment.

The topmost commit addresses comments by @HowardHinnant.
In terms of adding a new Number::away_from_zero rounding mode, I'm requesting it in an effort to make the most recent change more correct.  It's probably not critical because it will only affect a divRound call that has a negative result.  I think those are very uncommon today.
This is the situation:
    STAmount result = [&]() {
        // If appropriate, tell Number the rounding mode we are using.
        MightSaveRound const savedRound(
            roundUp ? Number::upward : Number::towards_zero);
        return STAmount(issue, amount, offset, resultNegative);
    }();

The variable roundUp is a bool.  Even though it's called roundUp, the implementation seems to treat it as...

true: round away from zero
false: round toward zero.

Here I'm using Number::upward as a stand-in.  And it's the right choice as long as resultNegative == false.  But if resultNegative == true I'll get the wrong behavior.
Since I'm looking at this harder, I happen to have enough information to synthesize the behavior that I want:
    STAmount result = [&]() {
        // If appropriate, tell Number the rounding mode we are using.
        // Note that "roundUp == true" actually means "round away from zero".
        // Otherwise round toward zero.
        MightSaveRound const savedRound(
            roundUp ^ resultNegative ? Number::upward : Number::downward);
        return STAmount(issue, amount, offset, resultNegative);
    }();

I guess I'm inclined to use this work around, since it's the only place in the code that would use the new Number::away_from_zero rounding mode, at least for now.
Thoughts?

@gregtatcam, do you want a last opportunity to look over this pull request before I mark it Passed?  Thanks.

@gregtatcam, do you want a last opportunity to look over this pull request before I mark it Passed? Thanks.

I'll review tonight.

Thanks, looks good!

PING, this issue happens more frequently at the moment. Issue has been dormant for over a month.


test framework?

https://www.npmjs.com/package/mocha ?
https://github.com/Steve-Fenton/tsUnit
https://github.com/mmanela/chutzpah
jasmine
https://github.com/jasmine/jasmine
https://github.com/chaijs/chai
http://jonnyreeves.co.uk/2015/hello-typescript-and-mocha/
http://dinozafirakos.com/2014/07/21/testing-with-mocha-chai-and-typescript/
http://ciplogic.com/index.php/blog/100-typescript-unit-testing-with-mocha

Mocha + Chai


App refuses to transfer files with question marks in them

Versions:

Android 11 (May Security Patch) on my Pixel 5
OpenMTP Version 3.1.5 (3.1.5) on Legacy MTP mode

If you attempt to transfer a file with a question mark in the filename, the app chokes and never finishes the transfer.

Interesting. I will check this.

You can add " (quotation mark) to the same list. Transfer stops when there's a " in the filename.
Il sure come back if I find any other problematic character.

@Voreball I was able to reproduce this issue. But the situation is a tad more complication. I could easily fix this by sanitizing the filenames but the same gets a complicated for directories.
I need more time on this issue as I need to make sure that I dont break anything

A vote for not just sanitizing filenames, because that can lead to data loss. Properly encapsulating Unicode all the way through your internal file name handling can be a real pain, but it's worth it.


Item update code is simplified

Q
A

Bug fix?
no

New feature?
no

New sample?
no

Related issues?
no

What's in this Pull Request?
react-field-slider: code to update field value has been optimized

@AJIXuMuK,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

thx Alex, sorry for the small delay...

No worries - everyone needs a vacation :)


Determine if we can extract bindings from engine and template code and have them exist as standalone repos and cocoapods/aars

Determine if we can extract bindings from engine and template code and have them exist as standalone repos and cocoapods/aars

Closing this as won't do. Any extraction of platform bindings from other engine code is unlikely, but at a minimum is a non-priority for the foreseeable future.


docs: indicates readability comment fix

Signed-off-by: Ryan Russell<EMAIL_ADDRESS>What problem are we solving?
grep -r indictes
wdclient/resource_pool/managed_handle.go:	// This indictes a user is done with the handle and releases the handle
wdclient/net2/managed_connection.go:	// This indictes a user is done with the connection and releases the

How are we solving the problem?
indictes -> indicates
Notes for merger
Feel free to let me know if you prefer these small, specific PR's, or would rather me lump comment readability things into a more signficant PR.
Best,
Ryan

Smaller PRs is better.


Remove blank line

genius

Thanks, but this comes down to more of a preference in visibility of code structure


fix: incorrect default backend in local dev

This is probably not the best solution. We should probably look in the configuration to determine where the backend is located. At least this fixes the plugin against the default local backstage setup. This likely fixes #174 too.

@zeeraw Thanks for your effort. Unfortunately we can't accept this PR, as it breaks our Backstage deployment. We use port 7000 for backend.
Are you able to make the changes for it to find the port from the app-config?


Problem with kernel 4.13

This is 4x RX580 GPU system, AMD 970 motherboard, booting from USB flash.
On a fresh Ubuntu 16.04 LTS I am trying to install ROCM per this manual:
https://rocm.github.io/ROCmInstall.html
Since it suggests installing kernel 4.13, I decided to do so. After kernel installs and I reboot, I am getting lots of amd-vi completion-wait loop timed out messages. The system boots, however I cannot ssh to it (connection refused), I cannot login locally either: after I type in my username, I get the Login: prompt again w/o asking for password. So, I cannot reboot and I force power off. After that I cannot boot at all, I get the grub error "unknown file system" (not even getting to grub boot menu).
I did it 3 times, and it's always the same. With 4.4.0-116 I can boot normally. This setup also runs with amdgpu-pro w/o any problems under 4.4.0-116. Any ideas, please?

AMD 970? As in an AM3 or AM3+ consumer board?
If that is the case, please note that ROCm 1.8 requires a chipset with PCIe gen 3 with atomics support, as per the first section of the ROCm README file. We have relaxed this support on gfx9-generation GPUs, such as Vega 10. This limitation still exists on gfx8-generation GPUs such as your RX580, however.

To give a bit more info to this: I have a test system where the motherboard does not support PCIe gen 3 atomics. It's an AMD 890FX. However, It has a FirePro W9100 in it, which is a "Hawaii"-based GPU (gfx701) that does not require PCIe gen 3 w/ atomics to work in ROCm.
I installed Ubuntu 16.04.0 (Linux 4.4.0-21) and tried installing ROCm 1.8.1 on top of it. It worked for me, and I was able to run test applications successfully.
I then purged rocm-dkms, manually upgraded to Linux 4.13.0-32, and reinstalled rocm-dkms. This also worked, and I was able to run test applications successfully.
Honestly (and yes, the documentation should likely be upgraded to say this), you can also just install to the latest 16.04 release (e.g. 16.04.4) and upgrade to the latest kernel release. I have a separate system running 4.15.0-29 at the moment, for instance.
Note that the only GPUs we support without PCIe gen 3 atomics are Hawaii (gfx701) and Vega 10 (gfx900). Your RX580 GPUs require gen 3 atomics and I strongly suspect that is why you are running into problems installing ROCm. This requirement does not exist in amdgpu-pro.


Include subpages in filtered page results

Short description

This PR is to fix the problem that subpages are not shown when the filter is applied.
Proposed changes

Subpages are now shown too
Pages are shown even when their root page and/or parent page is filterd out.

Resolved issues

Fixes: #934

Please wait with merging this PR until I squashed all commits, thanks!

@MizukiTemma Thank for you PR, you can now merge it :tada:
For the future: Please use the command git rebase develop instead of git merge develop when you want to include the recent changes of the develop branch in your feature branch like described in our documentation. This makes the git history a bit cleaner and makes it easier to squash the commits later on.
Also, please change the subjects of your commit messages so that they describe the solution to the problem, not the problem itself. E.g., If the problem is that the subpages are not shown, the commit that fixes that issue should be named "Include subpages in filtered page results" or similar.

@MizukiTemma This exactly what I'm talking about, please don't merge the develop branch into your feature branch, but use rebasing instead :slightly_smiling_face:
I will rebase this branch now again before merging.


Updates to LTX-video model

LTX has uploaded the bf16 model for version 0.9.1.
https://huggingface.co/Lightricks/LTX-Video/tree/main
Thank you very much for making the gguf models!
Now, we just need an update for the latest version.

Nevermind.
I just realised that the updated vae model has not been released.


{Packaging} Not build Mariner RPM on PullRequest CI

Description
Mariner 2.0 has rpmbuild 4.17.0 which is very slow while building the RPM, same as UBI 8 (https://github.com/Azure/azure-cli/pull/21655) and CentOS Stream 8 (https://github.com/Azure/azure-cli/pull/20918). The CI job BuildRpmPackageMariner takes ~40min.
Turning on -vv (verbose) for rpmbuild shows the process got stuck at these steps for a very long time:
D:      execv(/usr/lib/rpm/pythondeps.sh) pid 4341
D:      waitpid(4341) rc 4341 status 0
D:      execv(/usr/lib/rpm/pythondistdeps.py) pid 4346
D:      waitpid(4346) rc 4346 status 0
D:      execv(/usr/lib/rpm/pythondeps.sh) pid 4347
D:      waitpid(4347) rc 4347 status 0
D:      execv(/usr/lib/rpm/pythondistdeps.py) pid 4352
D:      waitpid(4352) rc 4352 status 0
D:      execv(/usr/lib/rpm/pythondeps.sh) pid 4353
D:      waitpid(4353) rc 4353 status 0

htop shows the same:

Email: azure-cli FIPS compliance

/azp run

Packaging


Usage guide for Explore page

It would be good to have a detailed guide with screenshots showing and explaining the various functions on the explore page.
It should cover:

switching scopes
selecting points (click, lasso)
searching

using different embeddings to search

clusters
tags

I've built some documentation over here https://github.com/enjalot/latent-scope-observable-examples
which is deployed here: https://enjalot.github.io/latent-scope/explore-and-curate


openni2 build fail due to #1926

I am on Windows 10, VS2015,.
vcpkg install openni2
and here is the error message
Starting package 1/1: openni2:x64-windows
Building package openni2:x64-windows...
-- CURRENT_INSTALLED_DIR=C:/dev/vcpkg/installed/x64-windows
-- DOWNLOADS=C:/dev/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/dev/vcpkg/packages/openni2_x64-windows
-- CURRENT_BUILDTREES_DIR=C:/dev/vcpkg/buildtrees/openni2
-- CURRENT_PORT_DIR=C:/dev/vcpkg/ports/openni2/.
-- Using cached C:/dev/vcpkg/downloads/OpenNI2-2.2-beta.zip
-- Testing integrity of cached file...
-- Testing integrity of cached file... OK
-- Extracting done
-- Applying patch C:/dev/vcpkg/ports/openni2/upgrade_projects.patch
-- Applying patch failed. This is expected if this patch was previously applied.
-- Applying patch C:/dev/vcpkg/ports/openni2/upgrade_projects.patch done
-- Applying patch C:/dev/vcpkg/ports/openni2/inherit_from_parent_or_project_defaults.patch
-- Applying patch failed. This is expected if this patch was previously applied.
-- Applying patch C:/dev/vcpkg/ports/openni2/inherit_from_parent_or_project_defaults.patch done
-- Applying patch C:/dev/vcpkg/ports/openni2/replace_environment_variable.patch
-- Applying patch failed. This is expected if this patch was previously applied.
-- Applying patch C:/dev/vcpkg/ports/openni2/replace_environment_variable.patch done
-- Building C:/dev/vcpkg/buildtrees/openni2/src/OpenNI2-2.2-beta2/OpenNI.sln for Release
-- Building C:/dev/vcpkg/buildtrees/openni2/src/OpenNI2-2.2-beta2/OpenNI.sln for Debug
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/Android-Arm/OniPlatformAndroid-Arm.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/Driver/OniDriverAPI.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/Driver/OniDriverTypes.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/Linux-Arm/OniPlatformLinux-Arm.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/Linux-x86/OniPlatformLinux-x86.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/MacOSX/OniPlatformMacOSX.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/Win32/OniPlatformWin32.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/OniCAPI.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/OniCEnums.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/OniCProperties.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/OniCTypes.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/OniEnums.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/OniPlatform.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/OniProperties.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/OniVersion.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/OpenNI.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/PrimeSense.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/PS1080.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/include/openni2/PSLink.h
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/lib/OpenNI2.lib
-- Installing: C:/dev/vcpkg/packages/openni2_x64-windows/debug/lib/OpenNI2.lib
CMake Error at ports/openni2/portfile.cmake:142 (file):
  file INSTALL cannot find
  "C:/dev/vcpkg/buildtrees/openni2/src/OpenNI2-2.2-beta2/Bin/x64-Release/OpenNI2/Drivers/Kinect.dll".
Call Stack (most recent call first):
  scripts/ports.cmake:72 (include)

Error: Building package openni2:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: openni2:x64-windows
  Vcpkg version: 0.0.90-2017-09-28-450cb8591a5023f762b4b928cb36ca632d0fe7b3

Additionally, attach any relevant sections from the log files above.

C:\dev\vcpkg>

The patch has not been applied.
-- Applying patch C:/dev/vcpkg/ports/openni2/upgrade_projects.patch
-- Applying patch failed. This is expected if this patch was previously applied.
-- Applying patch C:/dev/vcpkg/ports/openni2/upgrade_projects.patch done
-- Applying patch C:/dev/vcpkg/ports/openni2/inherit_from_parent_or_project_defaults.patch
-- Applying patch failed. This is expected if this patch was previously applied.
-- Applying patch C:/dev/vcpkg/ports/openni2/inherit_from_parent_or_project_defaults.patch done
-- Applying patch C:/dev/vcpkg/ports/openni2/replace_environment_variable.patch
-- Applying patch failed. This is expected if this patch was previously applied.
-- Applying patch C:/dev/vcpkg/ports/openni2/replace_environment_variable.patch done

Please remove buildtrees/openni2 directory.
Then, Please change charactor code to UTF-8 using chcp 65001.
And, try again install openni2 port.
Remove-Item C:\dev\vcpkg\buildtrees\openni2 -Recurse
chcp 65001
vcpkg install openni2:x64-windows

Now it shows up a new error. Please see log file
    "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\EventBasedRead\EventBasedRead.vcxproj.metaproj" (Rebuild target) (14) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\EventBasedRead\EventBasedRead.vcxproj" (Rebuild target) (34) ->
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\EventBasedRead\EventBasedRead.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\EventBasedRead\EventBasedRead.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\EventBasedRead\EventBasedRead.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\EventBasedRead\EventBasedRead.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MultiDepthViewer\MultiDepthViewer.vcxproj.metaproj" (Rebuild target) (7) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MultiDepthViewer\MultiDepthViewer.vcxproj" (Rebuild target) (37) ->
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MultiDepthViewer\MultiDepthViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MultiDepthViewer\MultiDepthViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MultiDepthViewer\MultiDepthViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member (compiling source file main.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MultiDepthViewer\MultiDepthViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member (compiling source file Viewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MultiDepthViewer\MultiDepthViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member (compiling source file main.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MultiDepthViewer\MultiDepthViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member (compiling source file Viewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MultiDepthViewer\MultiDepthViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member (compiling source file main.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MultiDepthViewer\MultiDepthViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member (compiling source file Viewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MultiDepthViewer\MultiDepthViewer.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj.metaproj" (Rebuild target) (6) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj" (Rebuild target) (36) ->
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member (compiling source file Device.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member (compiling source file Capture.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member (compiling source file Device.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member (compiling source file Capture.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member (compiling source file Device.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member (compiling source file Capture.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         Device.cpp(278): warning C4456: declaration of 'rc' hides previous local declaration [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member (compiling source file Draw.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member (compiling source file Draw.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member (compiling source file Draw.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\ThirdParty\PSCommon\XnLib\Include\XnMath.h(38): warning C4244: 'return': conversion from 'double' to 'XnFloat', possible loss of data (compiling source file MouseInput.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\ThirdParty\PSCommon\XnLib\Include\XnMath.h(51): warning C4244: 'return': conversion from 'double' to 'XnFloat', possible loss of data (compiling source file MouseInput.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member (compiling source file NiViewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member (compiling source file NiViewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member (compiling source file NiViewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\ThirdParty\PSCommon\XnLib\Include\XnMath.h(38): warning C4244: 'return': conversion from 'double' to 'XnFloat', possible loss of data (compiling source file Draw.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\ThirdParty\PSCommon\XnLib\Include\XnMath.h(51): warning C4244: 'return': conversion from 'double' to 'XnFloat', possible loss of data (compiling source file Draw.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]
         Draw.cpp(1289): warning C4456: declaration of 'chars' hides previous local declaration [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Wrappers\java\OpenNI.jni\OpenNI.jni.vcxproj.metaproj" (Rebuild target) (18) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Wrappers\java\OpenNI.jni\OpenNI.jni.vcxproj" (Rebuild target) (30) ->
         org_openni_NativeMethods.cpp(720): warning C4311: 'type cast': pointer truncation from 'OniRecorderHandle' to 'long' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Wrappers\java\OpenNI.jni\OpenNI.jni.vcxproj]
         org_openni_NativeMethods.cpp(732): warning C4311: 'type cast': pointer truncation from 'OniDeviceHandle' to 'long' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Wrappers\java\OpenNI.jni\OpenNI.jni.vcxproj]
         org_openni_NativeMethods.cpp(743): warning C4311: 'type cast': pointer truncation from 'OniDeviceHandle' to 'long' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Wrappers\java\OpenNI.jni\OpenNI.jni.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PSLink\PSLinkConsole\PSLinkConsole.vcxproj.metaproj" (Rebuild target) (17) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PSLink\PSLinkConsole\PSLinkConsole.vcxproj" (Rebuild target) (32) ->
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PSLink\PSLinkConsole\PSLinkConsole.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PSLink\PSLinkConsole\PSLinkConsole.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PSLink\PSLinkConsole\PSLinkConsole.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MWClosestPoint\MWClosestPoint.vcxproj.metaproj" (Rebuild target) (11) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MWClosestPoint\MWClosestPoint.vcxproj" (Rebuild target) (35) ->
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MWClosestPoint\MWClosestPoint.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleViewer\SimpleViewer.vcxproj.metaproj" (Rebuild target) (5) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleViewer\SimpleViewer.vcxproj" (Rebuild target) (38) ->
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleViewer\SimpleViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleViewer\SimpleViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleViewer\SimpleViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member (compiling source file Viewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleViewer\SimpleViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member (compiling source file Viewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleViewer\SimpleViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member (compiling source file Viewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleViewer\SimpleViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member (compiling source file main.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleViewer\SimpleViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member (compiling source file main.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleViewer\SimpleViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member (compiling source file main.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleViewer\SimpleViewer.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleRead\SimpleRead.vcxproj.metaproj" (Rebuild target) (2) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleRead\SimpleRead.vcxproj" (Rebuild target) (31) ->
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleRead\SimpleRead.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleRead\SimpleRead.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleRead\SimpleRead.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\SimpleRead\SimpleRead.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\DummyDevice\DummyDevice.vcxproj.metaproj" (Rebuild target) (4) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\DummyDevice\DummyDevice.vcxproj" (Rebuild target) (29) ->
       (ResourceCompile target) ->
         C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\stdio.h(321): warning RC4011: identifier truncated to '_CRT_USE_WINAPI_FAMILY_DESKTOP_' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\DummyDevice\DummyDevice.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj.metaproj" (Rebuild target) (6) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj" (Rebuild target) (36) ->
         C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\stdio.h(321): warning RC4011: identifier truncated to '_CRT_USE_WINAPI_FAMILY_DESKTOP_' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Tools\NiViewer\NiViewer.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PS1080\PS1080.vcxproj.metaproj" (Rebuild target) (8) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PS1080\PS1080.vcxproj" (Rebuild target) (28) ->
         C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\stdio.h(321): warning RC4011: identifier truncated to '_CRT_USE_WINAPI_FAMILY_DESKTOP_' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PS1080\PS1080.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\ClosestPointViewer\ClosestPointViewer.vcxproj.metaproj" (Rebuild target) (13) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\ClosestPointViewer\ClosestPointViewer.vcxproj" (Rebuild target) (39) ->
       (ClCompile target) ->
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\ClosestPointViewer\ClosestPointViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\ClosestPointViewer\ClosestPointViewer.vcxproj]
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\ClosestPointViewer\ClosestPointViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member (compiling source file Viewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\ClosestPointViewer\ClosestPointViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member (compiling source file Viewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\ClosestPointViewer\ClosestPointViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member (compiling source file Viewer.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\ClosestPointViewer\ClosestPointViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member (compiling source file main.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\ClosestPointViewer\ClosestPointViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member (compiling source file main.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\ClosestPointViewer\ClosestPointViewer.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member (compiling source file main.cpp) [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\ClosestPointViewer\ClosestPointViewer.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MWClosestPointApp\MWClosestPointApp.vcxproj.metaproj" (Rebuild target) (12) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MWClosestPointApp\MWClosestPointApp.vcxproj" (Rebuild target) (40) ->
         cl : Command line warning D9002: ignoring unknown option '/arch:SSE2' [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Samples\MWClosestPointApp\MWClosestPointApp.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PS1080\PS1080Console\PS1080Console.vcxproj.metaproj" (Rebuild target) (19) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PS1080\PS1080Console\PS1080Console.vcxproj" (Rebuild target) (41) ->
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionX' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PS1080\PS1080Console\PS1080Console.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(278): warning C4458: declaration of 'resolutionY' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PS1080\PS1080Console\PS1080Console.vcxproj]
         C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Include\OpenNI.h(290): warning C4458: declaration of 'fps' hides class member [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\PS1080\PS1080Console\PS1080Console.vcxproj]

       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\OpenNI.sln" (Rebuild target) (1) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\Kinect\Kinect.vcxproj.metaproj" (Rebuild target) (16) ->
       "C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\Kinect\Kinect.vcxproj" (Rebuild target) (25) ->
       (ClCompile target) ->
         c:\dev\vcpkg\buildtrees\openni2\src\openni2-2.2-beta2\source\drivers\kinect\BaseKinectStream.h(7): fatal error C1083: Cannot open include file: 'NuiApi.h': No such file or directory [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\Kinect\Kinect.vcxproj]
         c:\dev\vcpkg\buildtrees\openni2\src\openni2-2.2-beta2\source\drivers\kinect\BaseKinectStream.h(7): fatal error C1083: Cannot open include file: 'NuiApi.h': No such file or directory [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\Kinect\Kinect.vcxproj]
         c:\dev\vcpkg\buildtrees\openni2\src\openni2-2.2-beta2\source\drivers\kinect\BaseKinectStream.h(7): fatal error C1083: Cannot open include file: 'NuiApi.h': No such file or directory [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\Kinect\Kinect.vcxproj]
         c:\dev\vcpkg\buildtrees\openni2\src\openni2-2.2-beta2\source\drivers\kinect\BaseKinectStream.h(7): fatal error C1083: Cannot open include file: 'NuiApi.h': No such file or directory [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\Kinect\Kinect.vcxproj]
         c:\dev\vcpkg\buildtrees\openni2\src\openni2-2.2-beta2\source\drivers\kinect\KinectDriver.h(7): fatal error C1083: Cannot open include file: 'NuiApi.h': No such file or directory [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\Kinect\Kinect.vcxproj]
         c:\dev\vcpkg\buildtrees\openni2\src\openni2-2.2-beta2\source\drivers\kinect\BaseKinectStream.h(7): fatal error C1083: Cannot open include file: 'NuiApi.h': No such file or directory [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\Kinect\Kinect.vcxproj]
         c:\dev\vcpkg\buildtrees\openni2\src\openni2-2.2-beta2\source\drivers\kinect\BaseKinectStream.h(7): fatal error C1083: Cannot open include file: 'NuiApi.h': No such file or directory [C:\dev\vcpkg\buildtrees\openni2\src\OpenNI2-2.2-beta2\Source\Drivers\Kinect\Kinect.vcxproj]

    407 Warning(s)
    7 Error(s)

Time Elapsed 00:00:22.24

This error has occurred because the patch has not been applied.
I think need change character code to UTF-8.
Did you try this commands https://github.com/Microsoft/vcpkg/issues/1927#issuecomment-334497986?

I deleted the buildtree, and then run chcp 65001 and then run vcpkg install openni2 and then this error shows up.
I am on default windows command prompt instead of powershell if it matters

Hmmm, I think that your problem is caused by patches not being applied.
But, I don't know why patches are not applied to OpenNI2 files in your environment.
This problem can't be reproduced in my environment. I have no ideas...
 (I tried again, But I can't reproduce this problem in my environment.)
Does anyone know how to resolve this problem?

I tested on 3 computers and it all return the same error message. This is quite confusing.
@UnaNancyOwen Are you on VS2015 or VS2017?

I confirmed using Visual Studio 2017.
I tried it in a clean installation environment, but that problem didn't reproduce.
The latest OpenNI2 port no longer uses disable_kinect.patch in port file.
(Sorry, I forgot to remove it.)
OpenNI2 port is setting path to Kinect SDK 1.x (that installed by using Kinect SDK 1.x port) using replace_environment_variable.patch.
Your problem is caused by patches not being applied in your environment. (I think it is no doubt.)
But, I don't understand why not being applied it.
PS C:\vcpkg> .\vcpkg install openni2:x64-windows
The following packages will be built and installed:
  * kinectsdk1:x64-windows
    openni2:x64-windows
Additional packages (*) will be installed to complete this operation.
Starting package 1/2: kinectsdk1:x64-windows
Building package kinectsdk1:x64-windows...
A suitable version of cmake was not found (required v3.9.3). Downloading portable cmake v3.9.3...
A suitable version of git was not found (required v2.14.1). Downloading portable git v2.14.1...
-- CURRENT_INSTALLED_DIR=C:/vcpkg/installed/x64-windows
-- DOWNLOADS=C:/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/vcpkg/packages/kinectsdk1_x64-windows
-- CURRENT_BUILDTREES_DIR=C:/vcpkg/buildtrees/kinectsdk1
-- CURRENT_PORT_DIR=C:/vcpkg/ports/kinectsdk1/.
-- Downloading https://download.microsoft.com/download/E/1/D/E1DEC243-0389-4A23-87BF-F47DE869FC1A/KinectSDK-v1.8-Setup.exe...
-- Downloading https://download.microsoft.com/download/E/1/D/E1DEC243-0389-4A23-87BF-F47DE869FC1A/KinectSDK-v1.8-Setup.exe... OK
-- Testing integrity of downloaded file...
-- Testing integrity of downloaded file...
Installing package kinectsdk1:x64-windows... done
Elapsed time for package kinectsdk1:x64-windows: 7.257 min
Starting package 2/2: openni2:x64-windows
Building package openni2:x64-windows...
-- CURRENT_INSTALLED_DIR=C:/vcpkg/installed/x64-windows
-- DOWNLOADS=C:/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/vcpkg/packages/openni2_x64-windows
-- CURRENT_BUILDTREES_DIR=C:/vcpkg/buildtrees/openni2
-- CURRENT_PORT_DIR=C:/vcpkg/ports/openni2/.
-- Downloading https://github.com/OpenNI/OpenNI2/archive/2.2-beta2.zip...
-- Downloading https://github.com/OpenNI/OpenNI2/archive/2.2-beta2.zip... OK
-- Testing integrity of downloaded file...
-- Testing integrity of downloaded file...
Installing package openni2:x64-windows... done
Elapsed time for package openni2:x64-windows: 1.415 min
Total time taken: 8.671 min

I think I just figured out the problem by looking at the replace_environment_variable.patch. I am actually using a custom triplet x64-windows-jasjuang specifying everything as dynamic but only glew as static for my own purposes. I omit it when I was reporting issues just to avoid confusion, but this time it ends up being the root cause. The patch is patching the 4 default triplets only. Is it possible to fix it so it actually is able to detect the current active triplet and patch it properly? My kinectsdk1 is in C:\vcpkg\packages\kinectsdk1_x64-windows-jasjuang and not C:\vcpkg\packages\kinectsdk1_x64-windows

Can you provide a custom triplets file?

Create a file called x64-windows-jasjuang.cmake in C:\vcpkg\triplets and fill in
set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE dynamic)

if(PORT STREQUAL "glew")
  set(VCPKG_LIBRARY_LINKAGE static)
else()
  set(VCPKG_LIBRARY_LINKAGE dynamic)
endif()

Please try test again after replace this file to following.
ports/openni2/replace_environment_variable.patch.in
diff --git a/Source/Drivers/Kinect/Kinect.vcxproj b/Source/Drivers/Kinect/Kinect.vcxproj
index 08a49fe..7fd8620 100644
--- a/Source/Drivers/Kinect/Kinect.vcxproj
+++ b/Source/Drivers/Kinect/Kinect.vcxproj
@@ -101,7 +101,7 @@
     <ClCompile>
       <WarningLevel>Level3</WarningLevel>
       <Optimization>Disabled</Optimization>
-      <AdditionalIncludeDirectories>..\..\..\Include;..\..\..\ThirdParty\PSCommon\XnLib\Include;$(KINECTSDK10_DIR)\inc;</AdditionalIncludeDirectories>
+      <AdditionalIncludeDirectories>..\..\..\Include;..\..\..\ThirdParty\PSCommon\XnLib\Include;@NATIVE_VCPKG_ROOT_DIR@\packages\kinectsdk1_@TARGET_TRIPLET@\include</AdditionalIncludeDirectories>
       <PreprocessorDefinitions>_WINDLL;%(PreprocessorDefinitions);_WINDOWS</PreprocessorDefinitions>
       <DisableLanguageExtensions>false</DisableLanguageExtensions>
       <TreatWarningAsError>false</TreatWarningAsError>
@@ -109,7 +109,7 @@
     <Link>
       <GenerateDebugInformation>true</GenerateDebugInformation>
       <AdditionalDependencies>Kinect10.lib;XnLib.lib;%(AdditionalDependencies)</AdditionalDependencies>
-      <AdditionalLibraryDirectories>$(SolutionDir)Bin\$(Platform)-$(Configuration)\;$(KINECTSDK10_DIR)\lib\x86;</AdditionalLibraryDirectories>
+      <AdditionalLibraryDirectories>$(SolutionDir)Bin\$(Platform)-$(Configuration)\;@NATIVE_VCPKG_ROOT_DIR@\packages\kinectsdk1_@TARGET_TRIPLET@\debug\lib</AdditionalLibraryDirectories>
       <TreatLinkerWarningAsErrors>true</TreatLinkerWarningAsErrors>
     </Link>
   </ItemDefinitionGroup>
@@ -117,7 +117,7 @@
     <ClCompile>
       <WarningLevel>Level3</WarningLevel>
       <Optimization>Disabled</Optimization>
-      <AdditionalIncludeDirectories>..\..\..\Include;..\..\..\ThirdParty\PSCommon\XnLib\Include;$(KINECTSDK10_DIR)\inc;</AdditionalIncludeDirectories>
+      <AdditionalIncludeDirectories>..\..\..\Include;..\..\..\ThirdParty\PSCommon\XnLib\Include;@NATIVE_VCPKG_ROOT_DIR@\packages\kinectsdk1_@TARGET_TRIPLET@\include</AdditionalIncludeDirectories>
       <PreprocessorDefinitions>_WINDLL;%(PreprocessorDefinitions);_WINDOWS</PreprocessorDefinitions>
       <DisableLanguageExtensions>false</DisableLanguageExtensions>
       <TreatWarningAsError>false</TreatWarningAsError>
@@ -125,7 +125,7 @@
     <Link>
       <GenerateDebugInformation>true</GenerateDebugInformation>
       <AdditionalDependencies>Kinect10.lib;XnLib.lib;%(AdditionalDependencies)</AdditionalDependencies>
-      <AdditionalLibraryDirectories>$(SolutionDir)Bin\$(Platform)-$(Configuration)\;$(KINECTSDK10_DIR)\lib\amd64;</AdditionalLibraryDirectories>
+      <AdditionalLibraryDirectories>$(SolutionDir)Bin\$(Platform)-$(Configuration)\;@NATIVE_VCPKG_ROOT_DIR@\packages\kinectsdk1_@TARGET_TRIPLET@\debug\lib</AdditionalLibraryDirectories>
       <IgnoreSpecificDefaultLibraries>
       </IgnoreSpecificDefaultLibraries>
       <IgnoreAllDefaultLibraries>
@@ -139,7 +139,7 @@
       <Optimization>MaxSpeed</Optimization>
       <FunctionLevelLinking>true</FunctionLevelLinking>
       <IntrinsicFunctions>true</IntrinsicFunctions>
-      <AdditionalIncludeDirectories>..\..\..\Include;..\..\..\ThirdParty\PSCommon\XnLib\Include;$(KINECTSDK10_DIR)\inc;</AdditionalIncludeDirectories>
+      <AdditionalIncludeDirectories>..\..\..\Include;..\..\..\ThirdParty\PSCommon\XnLib\Include;@NATIVE_VCPKG_ROOT_DIR@\packages\kinectsdk1_@TARGET_TRIPLET@\include</AdditionalIncludeDirectories>
       <TreatWarningAsError>false</TreatWarningAsError>
     </ClCompile>
     <Link>
@@ -147,7 +147,7 @@
       <EnableCOMDATFolding>true</EnableCOMDATFolding>
       <OptimizeReferences>true</OptimizeReferences>
       <AdditionalDependencies>Kinect10.lib;XnLib.lib;%(AdditionalDependencies)</AdditionalDependencies>
-      <AdditionalLibraryDirectories>$(SolutionDir)Bin\$(Platform)-$(Configuration)\;$(KINECTSDK10_DIR)\lib\x86;</AdditionalLibraryDirectories>
+      <AdditionalLibraryDirectories>$(SolutionDir)Bin\$(Platform)-$(Configuration)\;@NATIVE_VCPKG_ROOT_DIR@\packages\kinectsdk1_@TARGET_TRIPLET@\lib</AdditionalLibraryDirectories>
       <TreatLinkerWarningAsErrors>true</TreatLinkerWarningAsErrors>
     </Link>
   </ItemDefinitionGroup>
@@ -157,7 +157,7 @@
       <Optimization>MaxSpeed</Optimization>
       <FunctionLevelLinking>true</FunctionLevelLinking>
       <IntrinsicFunctions>true</IntrinsicFunctions>
-      <AdditionalIncludeDirectories>..\..\..\Include;..\..\..\ThirdParty\PSCommon\XnLib\Include;$(KINECTSDK10_DIR)\inc;</AdditionalIncludeDirectories>
+      <AdditionalIncludeDirectories>..\..\..\Include;..\..\..\ThirdParty\PSCommon\XnLib\Include;@NATIVE_VCPKG_ROOT_DIR@\packages\kinectsdk1_@TARGET_TRIPLET@\include</AdditionalIncludeDirectories>
       <TreatWarningAsError>false</TreatWarningAsError>
     </ClCompile>
     <Link>
@@ -165,7 +165,7 @@
       <EnableCOMDATFolding>true</EnableCOMDATFolding>
       <OptimizeReferences>true</OptimizeReferences>
       <AdditionalDependencies>Kinect10.lib;XnLib.lib;%(AdditionalDependencies)</AdditionalDependencies>
-      <AdditionalLibraryDirectories>$(SolutionDir)Bin\$(Platform)-$(Configuration)\;$(KINECTSDK10_DIR)\lib\amd64;</AdditionalLibraryDirectories>
+      <AdditionalLibraryDirectories>$(SolutionDir)Bin\$(Platform)-$(Configuration)\;@NATIVE_VCPKG_ROOT_DIR@\packages\kinectsdk1_@TARGET_TRIPLET@\lib</AdditionalLibraryDirectories>
       <TreatLinkerWarningAsErrors>true</TreatLinkerWarningAsErrors>
     </Link>
   </ItemDefinitionGroup>

It might be a good idea to add integrate install option (vcpkg integrate install) to vcpkg_build_msbuild().

@ras0219-msft @alexkaratarakis Currently, The solution/projects that need build using msbuild is no way to refer to libraries installed by vcpkg, except to rewrite vcxproj files.
It might be a good idea to add integrate option (like a vcpkg integrate install) to vcpkg_build_msbuild().

@UnaNancyOwen Your new replace_environment_variable.patch.in solves it for me! Can you please submit a PR?

OK, I will send a Pull Request.

Solved by #1937


"Airplane mode" for unit tests

This removes unintended usage of topology (due to unit tests not reseting their original state) and allows nearly every unit test run without network connectivity (exception is the S3 unit test).
One aspect of this causing the most code churn is deferring the lookup of federation metadata until it is needed.  This allows various simple client invocations to succeed (think: pelican help and similar -- anything where the client config is initialized but not needed) and avoiding failures in the corresponding unit tests.

@joereuss12 - you test on Windows, right?  Can you take a look at the failing unit test?  I suspect it's something simple (basically, it looks like the unit test isn't fully shut down before cleanup) but it's really tough to debug without Windows access.


WIP: Initial aarch64-apple-darwin20 GCC/PlatformSupport shards

Adds the first public GCC/PlatformSupport shards for Apple Silicon. For reference, see https://github.com/JuliaPackaging/Yggdrasil/pull/2436
Should I remove the PlatformSupport-aarch64-apple-darwin20.v2020.11.6.x86_64-linux-musl.* entries which contain no download?

I believe I'm missing something. With these changes I'm still seeing:
  Downloaded artifact: PlatformSupport-aarch64-apple-darwin20.v2020.11.6.x86_64-linux-musl.unpacked
ERROR: LoadError: Cannot automatically install 'PlatformSupport-aarch64-apple-darwin20.v2020.11.6.x86_64-linux-musl.unpacked'; no download section in '/home/omus/.julia/dev/BinaryBuilderBase/Artifacts.toml'

When attempting to build other JLLs

I believe I'm missing something. With these changes I'm still seeing:
  Downloaded artifact: PlatformSupport-aarch64-apple-darwin20.v2020.11.6.x86_64-linux-musl.unpacked
ERROR: LoadError: Cannot automatically install 'PlatformSupport-aarch64-apple-darwin20.v2020.11.6.x86_64-linux-musl.unpacked'; no download section in '/home/omus/.julia/dev/BinaryBuilderBase/Artifacts.toml'

When attempting to build other JLLs

Worked around this. I realized I needed to update ps_build to use the new PlatformSupport version. Unfortunately I didn't make a PlatformSupport build for x86_64-linux-musl as well which is problematic. I worked around this by modifying the 2020.11.6 Artifact entries to use the ones created here.
Lesson learned

Worked around this. I realized I needed to update ps_build to use the new PlatformSupport version. Unfortunately I didn't make a PlatformSupport build for x86_64-linux-musl as well which is problematic. I worked around this by modifying the 2020.11.6 Artifact entries to use the ones created here.
Lesson learned

Looks like I need to change the commit we use for GCC: https://github.com/JuliaPackaging/Yggdrasil/pull/2439#issuecomment-766839222

Looks like I need to change the commit we use for GCC: https://github.com/JuliaPackaging/Yggdrasil/pull/2439#issuecomment-766839222

This PR is partially replaced by https://github.com/JuliaPackaging/BinaryBuilderBase.jl/pull/109.

Rebase please, and we can merge this!

I'm going to re-deploy the GCCBootstrap@11-IainS for aarch64-apple-darwin20 as during my experimentation it's possible I build against another than ccc57f4ed3feed697f17d3230786389b1b410af9.
Something I discovered while experimenting with this is that using --deploy can overwrite uploaded release assets. This seems to occur since detected previous release is done by looking inspecting the download sections of BinaryBuilderBase's Artifacts.toml. Since GCCBootstrap@11-IainS never had a download section then the deployment just assumes it's the first build.

I've redeployed the GCCBootstrap shards for aarch64-apple-darwin20 and this PR is now ready to go.

Awesome, thanks Curtis!


Verify and fix permissions

Resolves issue #769.

Perhaps I misinterpreted the spec. Let me check the email.

Nope, the email is just as spartan. @akeym: Could you clarify what's meant by "RW" in the permissions spec you emailed us in December? Does it include creation and deletion, or just updating?

read write implies any read or write operation
On Mon, Jan 5, 2015 at 1:05 PM, drkitty<EMAIL_ADDRESS>wrote:

Nope, the email is just as spartan. @akeym https://github.com/akeym:
Could you clarify what's meant by "RW" in the permissions spec you emailed
us in December? Does it include creation and deletion, or just updating?
—
Reply to this email directly or view it on GitHub
https://github.com/OSU-Net/cyder/pull/812#issuecomment-68781152.

Since that's cleared up, this is ready for merge.


Accompanying paper citations

Hello, I find the CFF idea great! For using it in our own software (SModelS, https://smodels.github.io) there is, however, a small hurdle: we would like to have several papers cited with the software, not just the paper that accompanies the latest release. While this is doable by adding several identifiers, the format of the identifiers (and choice of types) is not very convenient for this. I think this is a rather common problem, as there can be several relevant publications, in particular if there is a published manual plus a paper describing only the new features and/or relevant physics case.
I'd therefore like to suggest to have one identifier, or set of identifiers, for the actual software, and another one for the papers (=journal publications) to be cited with the software.  NB this is different from both the the 'preferred-citation' and the 'references' keys. Perhaps 'paper-publications' or 'articles' would be a suitable key. The possible items of this key should include authors, title, doi, arXiv, other id/link to document server.
Finally, is there a tool for exporting CFF to bibtex?
Thanks for the great work, cheers, Sabine

Hello, @sabinekraml, and Happy New Year! :fireworks: :tada:
Regarding your request to refer to multiple papers related to the software, I would like to suggest to add them as references in addition to the preferred-citation which refers to the latest release.  This solution worked for another situation, as well; see #436.
As I am just a CFF user and not a maintainer of this standard, I cannot help you regarding your feature request for a new field, I am sorry.  But I support your idea as I know some projects myself which could make great use of this feature. :+1:
Concerning the conversion tool, I prefer cffconvert which is written in Python 3 and suffices for my use cases.  If you are used to Ruby, you can also have a look at ruby-cff which is the library used by GitHub to generate the "Cite this repository" blob on a project's landing page.  Further conversion tools are listed in the Tooling Table in the "Conversion" column.  If none of these should work for your use case, please create me an issue such that I can implement a tool which suits your needs -- I am looking forward to your feature request! :wrench:
Does this information answer at least some of your questions?

Thanks Sabine for making the issue and thanks Kevin for this helpful overview. In addition to what Kevin wrote, it may be useful to know that items from identifiers take a description which may be used to describe its role (e.g. you could have a type: doi with description: The manual for version 12.3). See https://github.com/citation-file-format/citation-file-format/blob/1.2.0/schema-guide.md#identifiers. Note that identifiers deliberately has but a few keys --this is to avoid duplication of metadata. Tooling should be used (or built) to retrieve additional metadata from identifiers if need be.
Final note: the next version 1.3.0 of the CFF schema will likely have formal, machine-readable relation qualifiers similar to how Zenodo/DataCite are doing it with for example IsReferencedBy, HasPart, Documents, etc. The relevant PR is here: https://github.com/citation-file-format/citation-file-format/pull/459


Add Arxiv article link in Citation section in Readme

For reference, please consider adding the link to the corresponding Arxiv article into the Citation section in the Readme. The link is:
https://arxiv.org/abs/2205.09328

Thanks for your advice. Has been added to ReadMe.


Reduce barskill height

Hi! Here is just a small proposal, which I think would make a better looking. It's okay if you find this unnecessary.
What I think is the width(or height) of the skill bar is too big, which looks bolder than the text above them. So I tried to decrease the size of them to half. Shown as below(ignore differences in fonts and other things).
Thanks for taking the time to view this. 😃

I like you version better. We should make that the default. But why not make it adjustable? :wink:
It should not be much of a change. I see if I can find some time in between.

Good idea! I'm not sure how to make that change, so I'll leave it to you. 😺

So, finally found some time for this. As I said, not much of a change -- took like 2min :wink:
Thanks again for the suggestion!

So, finally found some time for this. As I said, not much of a change -- took like 2min :wink:
Thanks again for the suggestion!

That's great! 😆 Thank you for your works.

That's great! 😆 Thank you for your works.


WRKLDS-1421: Add required labels in dockerfile

This adds the commit https://github.com/openshift/cli-manager/pull/98/commits/52558c956a32c94317b8037672450d2671093a6d in release-4.17 branch to main branch in order to stay in sync.

/override ci/prow/e2e-aws-operator


corrects cursor position when hitting space

This fixes the cursor position to stay as it was before hitting space
This is relevant when:

editing something in the middle of the message and pressing space would move the cursor to the end of the message

Are you using osx ? because i can't reproduce. I can edit message in the middle, hit space, and the cursor does not jump to the end of the message.

I can reproduce.  This only seems to come into play when there is an emoji short code at the end of the line that hasn't been replaced yet, e.g. (with | as the cursor):
The quick brownfox jumps over the lazy dog :)|

Move the cursor to the middle of the line:
The quick brown|fox jumps over the lazy dog :)

Press space to fix the typo and the cursor jumps after the emoji:
The quick brown fox jumps over the lazy dog 😄 |

In my system (linux with yakyak/yakyak/master checked out) it always moves to the end (with | as cursor)
The quick brownfox :)|jumps over the lazy dog

Press space
The quick brownfox 😃 jumps over the lazy dog|

Indeed that also triggers it.

ohhhh, my bad!! this is specific to emojis, it was so obvious when I was writing the pull request that I forgot to write it in the title/body

I trust you, i merge.


fix: Infer and scan BSON files from file path

Fixes #2409

can you add a test case to the pytest?

I'd be down for a point release once these fixes go in

Added test case.

=========================== short test summary info ============================
FAILED tests/tests/test_bson.py::test_read_bson - psycopg2.errors.InternalError_: Error during planning: unable to infer how to handle file extension: bson
========================= 1 failed, 7 passed in 3.90s ==========================

Binary not being rebuilt?

Binary not being rebuilt?

yeah, the cache is apparently by cargo.lock hash not the current run...
slt-in-main fixes this.

The build problem should be resolved by the ci changes in #2401


Add call hierarchy support for TypeScript 3.8

This adds Call Hierarchy support for TypeScript 3.8 and is the other half of https://github.com/microsoft/TypeScript/pull/35176.
Related: https://github.com/microsoft/vscode/issues/16110, https://github.com/microsoft/TypeScript/issues/31863
cc: @mjbvz, @jrieken

🕺 this is soo exciting

We only ship stable TS versions in stable VS Code. That means that we can't update this until TS 3.8 is released in mid February.

I'll update the PR shortly, that's actually how I had it set up before creating the PR.

Thanks! We'll ship VS Code 1.42 with support for call hierarchy support but users will still need to update to TS 3.8
Once we pick up TS 3.8 with VS code 1.43, it will be available to everyone.  I'll also remove the copied over protocol types at that point


Pulsar 1.1.4 - building from sources - regression

Hi guys,
You have a regression when trying to build from sources with 1.1.4
wget https://github.com/PulsarCoin/Pulsar-Coin-Cryptocurrency/archive/refs/tags/v1.1.4.tar.gz
tar -xvf v1.1.4.tar.gz
cd Pulsar-Coin-Cryptocurrency-1.1.4/
cd depends/
make -j8 NO_QT=1
make: ./config.guess: Permission denied
make: ./config.guess: Permission denied
make: ./config.guess: Permission denied
make: ./config.sub: Permission denied
make: ./config.guess: Permission denied
make: ./config.sub: Permission denied
/bin/sh: 1: Makefile: not found
/bin/sh: 1: Syntax error: "|" unexpected
/bin/sh: 1: Makefile: not found
/bin/sh: 1: Syntax error: "|" unexpected
/bin/sh: 1: Makefile: not found
/bin/sh: 1: Syntax error: "|" unexpected
/bin/sh: 1: Makefile: not found
/bin/sh: 1: Syntax error: "|" unexpected
/bin/sh: 1: Makefile: not found
/bin/sh: 1: Syntax error: "|" unexpected
/bin/sh: 1: Makefile: not found
/bin/sh: 1: Syntax error: "|" unexpected
/bin/sh: 1: Syntax error: "|" unexpected
/bin/sh: 1: Syntax error: "|" unexpected
/bin/sh: 1: Syntax error: "|" unexpected
/bin/sh: 1: Syntax error: "|" unexpected
/bin/sh: 1: Syntax error: "|" unexpected
/bin/sh: 1: Syntax error: "|" unexpected
make: config.site.in: No such file or directory
/bin/sh: 1: Syntax error: "|" unexpected
make: config.site.in: No such file or directory
/bin/sh: 1: Syntax error: "|" unexpected
Makefile:74: builders/.mk: No such file or directory
make: *** No rule to make target 'builders/.mk'.  Stop.

fixed


Clicking on speaker session, do not lead to the respective session

Actual Behaviour

go to speakers page
click on speaker photo
click on the associated speaker session

Expected Behaviour
it should lead to the tracks page showing the sessions detail.

@aayusharora Currently it leads to the respective session in tracks page.

Can you please check the mobile version

@aayusharora  In mobile it does not navigate anywhere.

@sumedh123 Are you working on this?

@geekyd  I am taking a look. Still if you want, you can go ahead :+1:

@sumedh123 Almost done with the fix. Thanks.


Non-URL stories show incorrect markup on mobile for title

On mobile, story links that don't have a URL (for example, Ask HN stories) show the HTML markup instead of just the title text.

I think I fixed this in #33 (commit 458525ac76b9e3efcd4b4f65739f17b42b108049)

Oh you did! Awesome thanks so much, I just realized you fixed the typo on that file.


fixed bugs on teamPage

Improved the manageTeam section.

Before:-

After:-

fixed button inconsistency.

Removed unused CSS

Minified the JS Code.

@smaranjitghose have a look :)

Please have a look at the current codebase and give a PR, there are merge conflicts

@smaranjitghose done


Container API errors should still throw exceptions

Concerning this: https://github.com/docker-php/docker-php/blob/cac4840d1d43966a5e0802e24469d806f18e08ac/generated/1.33/Resource/ContainerResource.php#L96-L107
And some others.
Client error should throws exception. This is the goal of exception: to manage not wanted stated. ;-)
Example: https://github.com/KnpLabs/php-github-api/tree/master/lib/Github/Exception
Most of the API sdk work like this. Plus, this permit to have a cleaner end user code, focused on the logic process, then managing exception with a try/catch.

Another use case: On 1.24 branch, if I want my command to simply fail if the container creation return 500 error code, I have nothing to do because the exception is just raised. Plus, I can manage only some cases of the exception (400, 404...) and throw it away if the error should not be managed.
Here, I'm forced to manage all error and create exception myself.

Another idea related to #262 why not specify the api version on file generation? No need to worry about which version to handle anymore on we will have only one namespace.

It's ok in 2.0, Jane now generate exception for 400 / 500 status code

It's ok in 2.0

Well, the issue was telling about the missing exception on 2.0. It is working on 1.24. Did you recently fix this?

Don't understand there is no exception on 1.24 ?