Update britive-tutorial.md

Updated info based on changes in Britive Platform.

@hwan-britive
Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request. Thanks!

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@microsoft-github-policy-service agree [company="Britive"]
Thank you.
Harry
From: microsoft-github-policy-service[bot] @.>
Date: Wednesday, September 6, 2023 at 8:06 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Harry Wan @.>, Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update britive-tutorial.md (PR #114369)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
@hwan-britivehttps://github.com/hwan-britive please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.orghttp://www.opensource.org/).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/114369#issuecomment-1708560525, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AV6XS2D7WEAR3TB4PWI27Z3XZCGOFANCNFSM6AAAAAA4NPRIME.
You are receiving this because you were mentioned.Message ID: @.***>

@microsoft-github-policy-service agree company="Britive"
From: microsoft-github-policy-service[bot] @.>
Date: Wednesday, September 6, 2023 at 8:05 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Harry Wan @.>, Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update britive-tutorial.md (PR #114369)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
@hwan-britivehttps://github.com/hwan-britive please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.orghttp://www.opensource.org/).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/114369#issuecomment-1708558573, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AV6XS2GXHHMQLLIRA4R6KOTXZCGL7ANCNFSM6AAAAAA4NPRIME.
You are receiving this because you were mentioned.Message ID: @.***>

@jeevansd

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@hwan-britive @jeevansd - Note that image files must be hosted in the repo. Also, instead of "click" or "click on" the preferred instruction style is to use "select".

@Jak-MS @jeevansd Can you let me know if latest commit address image hosting location and "select" instead of "click" or "click on"?  Thanks.

@hwan-britive, we're creating a separate PR for your changes in our private repo for better content validation, the changes will merge within 2-3 working days.
#please-close


get function does not work in context scope

When doing context.get, the returned value is undefined. Verified that context.set writes the value into Redis.
global and flow contexts work as expected.
I'm guessing something about keys is not matching between set and get in the context scope.
[{"id":"ff717bc4.01b6f8","type":"function","z":"b5b1f0dd.44fdb","name":"test Redis context write","func":"\n\ncontext.set("newPayload", msg.payload, "redis");\n\nreturn msg;\n","outputs":1,"noerr":0,"x":2190,"y":960,"wires":[["9e6ce691.4b1ae8"]]},{"id":"a7c4a692.06ef88","type":"inject","z":"b5b1f0dd.44fdb","name":"","topic":"","payload":"{"val1":123,"val2":234}","payloadType":"json","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":1940,"y":960,"wires":[["ff717bc4.01b6f8"]]},{"id":"9e6ce691.4b1ae8","type":"function","z":"b5b1f0dd.44fdb","name":"test Redis context read","func":"\n\ncontext.get("newPayload", "redis", function(err, newPayload) {\n   if (err) {\n        node.error(err, msg);\n    } else {\n        node.warn(newPayload);\n    }\n});\n","outputs":1,"noerr":0,"x":2180,"y":1040,"wires":[["938f296c.c16e38"]]},{"id":"938f296c.c16e38","type":"debug","z":"b5b1f0dd.44fdb","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":2390,"y":1040,"wires":[]}]

Hi - thanks for raising the issue. Please note you are raising an issue against code in a PR that has not been reviewed or tested by the project yet (which is long overdue admittedly), so there may be issues we don't know about yet.
I don't know if @HirokiUchikawa is available to look at this or if he has moved on to other things. If you are in any position to debug this, then adding any comments to the relevant bit of #1 would certainly be helpful.

Are there any news about this issue? As far as i know the async function works and return values.


Added Exchange Rate Calculator

Developer Checklist

[ ] Followed guidelines mentioned in the readme file.
[ ] Followed directory structure. (e.g. ProjectName/{USERNAME}/...yourfiles)
[ ] Starred ⭐ the Repo (Optional)

Summary
add a summary here
This project is about finding exchange rate, for example: 1 USD ~ 82 Rs.
Screenshot
attach screenshots/gifs here

Live Project Link
add a working project link here
https://exchange-rate-blue.vercel.app/

Hi @Arpit045-boop, pleasd Rename project to CurrencyConverter from Exchange Rate.

Hi @PBJI good work so far :rocket:,
I guess this MR is inactive, we will check it for 4-5 days and then close it if no response is provided.

@thinkswell, yess I was thinking the same but I had 7 days in mind though.


Link to pricing doesn't have the information referenced

This link referenced in this line does not have this information - please update
Go to the Azure Virtual Desktop pricing page and look for the "Apps" and "Apps + Desktops" prices for your region.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1dd1d77c-598c-edef-7de9-b6ae843171e4
Version Independent ID: 928851a2-0361-cd4e-24ef-8977267e7f82
Content: Estimate per-user app streaming costs for Azure Virtual Desktop - Azure
Content Source: articles/virtual-desktop/remote-app-streaming/streaming-costs.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@msftcloudgeek Thank you for bringing this to our attention!  I'm going to assign this to the document author for review as there have been some recent updates that we'll need to reflect in the documentation.

@Heidilohr I think this issue has been fixed. Now that we're out of promotional pricing, the Azure Virtual Desktop Pricing page has been updated with the non-promotional pricing details. I now see "Desktops + apps $10 / Apps $5.50"
(There's one section of the Pricing page that still describes the promotional pricing, but that's getting fixed as well.)

Thanks @rick-man. I have tweaked the link in the AVD article to go straight to the table to make it easier to find and altered "Apps + Desktops" to be "Desktops + Apps" to match the pricing page.
#please-close


[DOC-3723] Update proxy provisioning - autostopping

Update proxy provisioning - autostopping in What's supported
For reviewers, a preview is available.
What's supported
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

LGTM.


MACs not cycing (El Capitan 10.11.1)

Hi.
I've been back to RelayMyHome today after several months. Always worked perfectly on Yosemite. I've downloaded the latest update to use it on El Capitan.
I launch the script as usual, only it doesn't actually cycle between addresses. This is the line I get:
Spoofing en0 to 4E:53:50:4F:4F:00 for 90 seconds
over and over again. It never changes MAC. Tried with quick and full mode. The first time I launched it I got my Streetpasses all right, so the script is working as intended... except it always relays me to the same MAC address.
Any solution to this? Thanks.

Im in the same boat as you Spoofing en1 to 4E:53:50:4F:4F:00 over and over again... Hope there is a fix here soon..

@taintedzodiac have you seen this? It appears that the script only returns one from that list of mac addresses, and it's not random.

I had the same issue, and fixed on my local copy. I will create a pull request for that this weekend.

Can confirm the gist @stepquick shared fixes the script for me on El Capitan 10.11.4.

@markcerqueira @taintedzodiac also confirming @stepquick share fixes the issue in El Captain 10.11.4, and that this issue is still open.

Thanks for the confirmations, all. Merged and closed!


Uncaught TypeError: "time" is read-only

Lightweight Charts Version: 3.8.0
Steps/code to reproduce:
data:
[{
close: 42218.58338925

date: "2022-01-17"

high: 43196.74354075

low: 41516.3831187

open: 43091.22186576

time: "2022-01-17"

volume: 67541.86482800724
}]

Uncaught TypeError: "time" is read-only
    convertStringToBusinessDay lightweight-charts.esm.development.js:10927
    convertStringsToBusinessDays lightweight-charts.esm.development.js:10931
    _internal_setSeriesData lightweight-charts.esm.development.js:10998
    _internal_applyNewData lightweight-charts.esm.development.js:12009
    setData lightweight-charts.esm.development.js:11369
    CandleStickChart candlestick.chart.js:23
    React 5
    unstable_runWithPriority scheduler.development.js:468
    React 3
    workLoop scheduler.development.js:417
    flushWork scheduler.development.js:390
    performWorkUntilDeadline scheduler.development.js:157
    js scheduler.development.js:180
    js scheduler.development.js:645
    factory react refresh:6
    Webpack 20

time is 'string', so when i click the error line, it tries to reassign a value to itself.
function convertStringToBusinessDay(value) {
    if (isString(value.time)) {
        value.time = stringToBusinessDay(value.time);
    }
}

Actual behavior:

Expected behavior:

Screenshots:

CodeSandbox/JSFiddle/etc link:
            candlestickSeries.setData([...data]);

answer:
i was defining 'time' variable by using 'Object.defineProperty' so it was a read-only property.
thats why its messed up.
anyway i would expect that it shouldnt broke.


Fixes FN011008. Closes #1509

Fixes FN011008. Closes #1509

Coverage remained the same at 100.0% when pulling d7e821655586b85e1e26bbd065e6866c3662f530 on appieschot:feature/fix_FN011008 into 454dff361882c32350a4d490d75e4bf1155979b4 on pnp:dev.

Merged manually. Thanks! 🚀


Unable to install

I have a VueJS project built with vue-cli that I'm struggling to use data-forge-js in. I did the following:
npm install --save data-forge
and added this import to my component:
import dataForge from 'data-forge';
In my component I attempt to create a simple DataFrame:
const dataFrame = new dataForge.DataFrame({         columnNames: ['Col1'],         values: [           [1],           [5],           [10],         ],       });
Upon executing npm run dev I see the following errors and warning (there are many, I've posted a subset):
WARNING in ./node_modules/require_optional/index.js
82:18-42 Critical dependency: the request of a dependency is an expression
 @ ./node_modules/require_optional/index.js
 @ ./node_modules/mongodb-core/lib/auth/gssapi.js
 @ ./node_modules/mongodb-core/index.js
 @ ./node_modules/promised-mongo/index.js
 @ ./node_modules/data-forge/src/dataframe.js
 @ ./node_modules/data-forge/src/series.js
 @ ./node_modules/data-forge/src/concat-series.js
 @ ./node_modules/data-forge/index.js
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/TrainerHome.vue
 @ ./src/components/TrainerHome.vue
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/MemberHome.vue
 @ ./src/components/MemberHome.vue
 @ ./src/router/index.js
 @ ./src/main.js
 @ multi ./build/dev-client ./src/main.js

WARNING in ./node_modules/require_optional/index.js
90:20-44 Critical dependency: the request of a dependency is an expression
 @ ./node_modules/require_optional/index.js
 @ ./node_modules/mongodb-core/lib/auth/gssapi.js
 @ ./node_modules/mongodb-core/index.js
 @ ./node_modules/promised-mongo/index.js
 @ ./node_modules/data-forge/src/dataframe.js
 @ ./node_modules/data-forge/src/series.js
 @ ./node_modules/data-forge/src/concat-series.js
 @ ./node_modules/data-forge/index.js
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/TrainerHome.vue
 @ ./src/components/TrainerHome.vue
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/MemberHome.vue
 @ ./src/components/MemberHome.vue
 @ ./src/router/index.js
 @ ./src/main.js
 @ multi ./build/dev-client ./src/main.js

...

I've been able to install and import many other npm packages without an issue. I've done a lot of searching for these errors and warnings but, thus far, I've been unable to get it to work. I'd really like use data-forge-js in my project. Any assistance provided would be much appreciated.

Hi, thanks for logging an issue.
I don't recognise the problem.  Are you able to provide an example that I can debug? If you have your project on Github already please give me a link to it.

Hey, thanks for the fast response! Let me see if I can construct an example. My project is in gitlab and is private. I could potentially get you access if I can't create an example. Thanks again!

Even just a small example and I can have a look at it today.

I'll see what I can put together this evening (my time) after putting my kid to bed :)

If you have a gitlab account I'd be open to granting you access to the repo there.

Sorry haven't signed up for it.

No problem, I'll work on getting you an example or access to the git
repository. Thank you again!
On Feb 26, 2018 5:57 PM, "Ashley Davis"<EMAIL_ADDRESS>wrote:

Sorry haven't signed up for it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/data-forge/data-forge-js/issues/9#issuecomment-368719441,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZ3GVSt31U1wEW77uCK2PjAYybODOd77ks5tY2EGgaJpZM4SUOPV
.

I created a quick, if not simple, example that demonstrates the problem.
https://github.com/cberthiaume/data-forge-js-test
I started by using vue-cli version 2.9.3 to create a default project:
vue init webpack data-forge-js-test
Following the instructions in the README I can load the default page locally by running npm run dev. Next, I added the reference to data-forge and created a DataFrame in the mounted lifecycle hook. Now, when I run npm run dev I receive this error:
Failed to compile.

./node_modules/harmony-proxy/index.js
Module not found: Error: Can't resolve './lib-cov' in 'C:\Users\chris\data\work\move2thrive\data-forge-js-test\node_modules\harmony-proxy'
 @ ./node_modules/harmony-proxy/index.js 2:4-24
 @ ./node_modules/promised-mongo/index.js
 @ ./node_modules/data-forge/index.js
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/HelloWorld.vue
 @ ./src/components/HelloWorld.vue
 @ ./src/router/index.js
 @ ./src/main.js
 @ multi (webpack)-dev-server/client?http://localhost:8081 webpack/hot/dev-server ./src/main.js

You can see the change I made to the default in this commit.
I hope this helps. Let me know if I can add anything further.

I think I've fixed your problem.
Before I publish though can I please get you to test it with your project?
First uninstall your existing version:
npm uninstall --save data-forge
Then install the latest version directly from the repo:
npm install --save https://github.com/data-forge/data-forge-js
Please let me know if it works for you now, if so I'll publish it.

That did it! The application builds now and I can see the console output of the DataFrame.
Thank you so much for looking into this so quickly!

Ok no worries. It's getting late here so I'll probably publish tomorrow. I'll let you know when it's done.
You might be interested to know that data-forge-ts (the TypeScript port) is on it's way. Please jump over to the new repo and add a star ;)
https://github.com/data-forge/data-forge-ts

Done!

I attempted to use the latest version directly from the repo in my actual project, as opposed to the example, and I'm seeing these errors:
ERROR in ./node_modules/babyparse/babyparse.js
Module not found: Error: Can't resolve 'fs' in 'C:\Users\chris\data\work\move2thrive\move2thrive_web\node_modules\babyparse'
 @ ./node_modules/babyparse/babyparse.js 41:16-29
 @ ./node_modules/data-forge/index.js
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/TrainerHome.vue
 @ ./src/components/TrainerHome.vue
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/MemberHome.vue
 @ ./src/components/MemberHome.vue
 @ ./src/router/index.js
 @ ./src/main.js
 @ multi ./build/dev-client ./src/main.js

ERROR in ./node_modules/data-forge/index.js
Module not found: Error: Can't resolve 'fs' in 'C:\Users\chris\data\work\move2thrive\move2thrive_web\node_modules\data-forge'
 @ ./node_modules/data-forge/index.js 213:14-27 239:14-27 278:13-26 294:13-26
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/TrainerHome.vue
 @ ./src/components/TrainerHome.vue
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/MemberHome.vue
 @ ./src/components/MemberHome.vue
 @ ./src/router/index.js
 @ ./src/main.js
 @ multi ./build/dev-client ./src/main.js

ERROR in ./node_modules/data-forge/src/dataframe.js
Module not found: Error: Can't resolve 'fs' in 'C:\Users\chris\data\work\move2thrive\move2thrive_web\node_modules\data-forge\src'
 @ ./node_modules/data-forge/src/dataframe.js 1038:13-26 1059:12-25 1089:13-26 1110:12-25
 @ ./node_modules/data-forge/index.js
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/TrainerHome.vue
 @ ./src/components/TrainerHome.vue
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/MemberHome.vue
 @ ./src/components/MemberHome.vue
 @ ./src/router/index.js
 @ ./src/main.js
 @ multi ./build/dev-client ./src/main.js

If you're interested I could send you a zip of the repo to email address. I'd prefer not to post it publicly though.

That's strange.
Can you think  of any difference been your example and your real app that would manifest the problem?
If you can make the problem happen with your example I'm sure I'll be able to fix it quickly.

Feel free to email the repo to<EMAIL_ADDRESS>I won't share it and I'll delete it once wee have fixed the problem.

I think I see the difference. In my example, which apparently was initialized with a different version of vue-cli than my project, webpack.base.conf.js includes this block:
node: {
    // prevent webpack from injecting useless setImmediate polyfill because Vue
    // source contains it (although only uses it if it's native).
    setImmediate: false,
    // prevent webpack from injecting mocks to Node native modules
    // that does not make sense for the client
    dgram: 'empty',
    fs: 'empty',
    net: 'empty',
    tls: 'empty',
    child_process: 'empty'
  },

Adding that to the same file in my actual project remedies the problem and the application seems to work correctly. It also lines up with what I see when searching for that error on the web.
Thanks again for all the help!

No problem. Glad to see it sorted. I hope to publish the updated version today or tomorrow.
If you are interested in working with data in JavaScript, I'm actually I'm writing a book on the subject!
It's available now on Manning early access (to be printed in the coming months):
https://www.manning.com/books/data-wrangling-with-javascript
If you want to support my efforts please let your colleagues and networks know about the book!

Thanks, I'll likely buy a copy myself and will spread the word!

I've published version 0.6.0 of DataForge. Please uninstall the repo and reinstall from npm. Let me know if it still works as expected!

0.6.0 working correctly. Thanks again!


The talkconv_cuda.py

I can't find the talkconv_cuda.py in the code. Where is it?

I assume you are getting an error when trying to import this line. You have to compile and install the custom CUDA library as described here in order to use TaLK convolutions.


Incorrect stereo configuration when writing file causes unhelpful error message (especially if not using NumPy)

Imagine the array configuration of the input to SoundFile.write is incorrect. For example, I triggered this by passing in interleaved stereo data where SoundFile.write expects an array of 2-element arrays. The error message was an exception thrown from two layers deep inside SoundFile, reading "Invalid shape: (960,)". Later, after understanding this was incorrect but while still a little confused, I tried. This got the error "Invalid shape: (2, 480)".
There are a few problems with this error message which make it less helpful than it could be.

It is not clear that this is related to an function parameter, or if it is, which parameter. When I first saw this it appeared to be an internal error in the library. The documentation very clearly explains the correct format, but I did not go looking at the documentation because I thought it was a library error and instead wound up reading the source. A message with less information like "parameter 1 incorrectly formatted" would have maybe been more helpful for this reason.
There are three different conditions that can trigger this single error, but which one is not indicated.
Most importantly, the error is described in terms of numpy semantics instead of library semantics. The error is that the dimension of the input array does not match the current (mono, stereo) value. But instead of talking about mono vs stereo, it gives the numpy multidimensional array shape. It may be a numpy user would immediately know what "shape (960,)" means, but I am not using numpy, so it was not obvious to me what "shape" referred to.

My expected behavior would be that this would read like "Stereo data expected (got data with shape: (960,)" or "Mono data expected (got data with shape: (480,2)".
Exact error message

Repro
I have a repro but it is not very convenient. You can check out https://github.com/mcclure/analogue-core-template-amaranth and check out revision 1e31ea635bdb880c411a79dedf107c51b9be16f0 . You will want to install "pdm" with pip, and probably want to edit src/fpga/amaranth_core/pyproject.toml to include "soundfile" instead of "pysoundfile", then you can run with (cd src/fpga/amaranth_core && python.exe -m pdm install && python.exe -m pdm capture_wav). It will take some time to complete.
The part that uses python-soundfile is here.

Thank you for the bug report. I agree that error messages could be improved.
Would you like to contribute a pull request with better error messages?


Prefetch not working on GH Pages

Prefetch functionality is not working on GH Pages deploys. The requests are returning 301's. I can investigate a little but the default will be to disable since this functionality was not in the scope.

Actually, I think it best to wait to see if this is resolved once the domain is switched


Need to test token against lowercase for stopwords

inside of stemmer.js there needs to be a test of the token.toLowerCase to the stopword (which is lowercase):
new Tokenizer().tokenize(text).forEach(function(token) {
var test = token.toLowerCase();
if(keepStops || stopwords.words.indexOf(test) == -1) {
// now add the actual token
stemmedTokens.push(stemmer.stem(token));
}
});

sorry to leave this one hanging, its a quick fix im just on the home stretch of what im currently working on. Would be glad to merge it in a PR otherwise i should have this out soon

Just noticed this one now - I believe this was addressed in https://github.com/NaturalNode/natural/pull/235.

yes thanks for pointing that out!


multi-training

Why using your code multi graphics card training is as fast as single-card training (2x3090)？

Hi, i'm not sure what your question is. Isn't it natural that multi-GPU DDP training costs around the same time per iteration as single GPU training?

n

Yes,The eta of multi-GPU is the same as single gpu for 17 days

In the config we set the total number of training iterations, so changing the number of GPUs will only affect the total number of epochs but not the training time.
And btw, the initial eta is an unreliable overestimate.

I see.that means if i change the total_iters to be half in multi-GPU training，we can get the same result as single-GPU training？I remember only 6 days for multi-GPU training in your paper

There's no need to change the schedule, the 17 days eta is simply wrong.

okay，I see.

If i use 4-gpus，can i change the total_iters to be half（500k） to get the simlar result as 1000k with 2-gpus？


Readme update

Modulus Pull Request
Description

Checklist

[ ] I am familiar with the Contributing Guidelines.
[ ] New or existing tests cover these changes.
[ ] The documentation is up to date with these changes.
[ ] The CHANGELOG.md is
up to date with these changes.

Dependencies

/blossom-ci

/blossom-ci


咨询下，该报错怎么解决？

../models/google/inception3_spg.py:137: UserWarning: nn.init.xavier_uniform is now deprecated in favor of nn.init.xavier_uniform_.
nn.init.xavier_uniform(m.weight.data)
=> loading checkpoint '../models/inception_v3_google-1a9a5a14.pth'
KeyError
Traceback (most recent call last):
File "../utils/Restore.py", line 24, in restore
args.current_epoch = checkpoint['epoch'] + 1
KeyError: 'epoch'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "train_frame.py", line 194, in
train(args)
File "train_frame.py", line 98, in train
model, optimizer= get_model(args)
File "train_frame.py", line 88, in get_model
restore(args, model, optimizer, including_opt=False)
File "../utils/Restore.py", line 38, in restore
_model_load(model, checkpoint)
File "../utils/Restore.py", line 51, in _model_load
if model_dict.keys()[0].startswith('module.'):
TypeError: 'odict_keys' object is not subscriptable

The checkpoint is not correctly loaded. Place the checkpoint at the right location or change the path to the checkpoint.


Add target to web site projects for <ServiceProjectMetadata> metadata retrieval

Is this a Bug or Feature request?:
Feature request that's part of the #7947 big rock
Steps to reproduce (preferably a link to a GitHub repo with a repro project):
Once our tool (see #8211) is ready, need to minimize the amount of hard-coded metadata included in consuming projects. Consuming project or the #8211 tool should be able to execute a target in the web site project to determine that information.
Some of the metadata comes from well-known project properties e.g. $(TargetFileName). The provider should make other information e.g. the ServiceName and Method or Path (relative URI of the document) available.
Description of the problem:
Ideally, authors of consuming projects (where generated C# or TypeScript files live) would only need to know the relative path to the Swagger- or OpenApi-enabled web site project.
Note that, as Swashbuckle is implemented, the client project author will need to provide the document name in even the best case.
More generally, providers may choose to make only default metadata available and generation tool must handle overrides. (For example, user may choose to host API documentation at a non-default URI.) To provide more than default metadata, providers would need a tool that inspects the web site and likely executes it, minimizing the benefit of the #8211 tool.
Version of Microsoft.AspNetCore.Mvc or Microsoft.AspNetCore.App or Microsoft.AspNetCore.All:
All released versions

Done as part of client-side generation prototype (#8211).


support tasks

Are there any usage examples? @Ed-XCF

How to use:
-----main.py or web.py-----
from bali.tasks import add_background_tasks
from fastapi import FastAPI
add_background_tasks(app)
-----tasks.py-----
from bali.tasks import run_every
@run_every(30)
def check_half_payment_status():
pass

Is it work well when the app running in multi workers or multi pods in K8S?

Is it work well when the app running in multi workers or multi pods in K8S?

There is an idea to reduce the possibility of synchronous startup of tasks through mathematical statistics, but users must be concerned about concurrency and locking

I'll closed it as there's no update for a long time for this PR.


Create release guide for LM and Watcher

Description
Have a release guide document to describe each necessary step to release LM and Watcher components.
The goal is for each developer, who follows this guide can release LM or Wather component to landscape without questions.
Things to concern:

how to do GitHub release: if git tag required, how to create release PR...
how to release on Internal repo.
troubleshooting section to collect unhappy path scenarios, can be empty in the first version.

AC

[x] release guide documented in internal team wiki

See "Release Process" in internal wiki.

Re. promotion to stage, I confirmed the following with SRE

for promotion to stage, a semantic version MUST be provided (it is NOT possible to provide a commit hash)
the provided semver MUST be a version core (major.minor.patch)
it MUST be a version core (MAJOR.MINOR.PATCH), suffixes like pre-releases are not allowed

So for our canary verification process, we have two options:
1. we pile up all solved tickets until the end of the sprint (sprint review) in canary verification, create the release and promote it to stage (Tuesdays). Then we would have 3 days to verify the changes before they get promoted to further to prod
2. for each solved ticket that needs verification, we create a release, promote it to stage and verify it directly. On the following Monday, the changes would then be further promoted to prod.
Major problem with 1.:  Goes against continuous integration. It may be troublesome to verify all changes at once since they may interfere with each other. (a bit of a mitigation may be to test the single changes more thoroughly on dev before a final overall test on stage)
Major problem with 2.: We don't have an explicit release decision for the sprint. Each ticket is an entity that may be promoted all the way to prod individually.

Updated version in "Release Process" in internal wiki.


load_weights gives ValueError: You are trying to load a weight file containing 1 layers into a model with 2 layers

Problem: I am trying to save weights of a model and load the weights after creating the same network used during training. It seems like save_weights always saves 1 layer. I must be doing something wrong but can't figure it out. (Note: I can save the architecture to a json and it might work then but I don't want that). Any help is highly appreciated.
Here is a dummy script to reproduce the error:
def euclidean_distance(vects):
	x, y = vects
	sum_square = K.sum(K.square(x - y), axis=1, keepdims=True)
	return K.sqrt(K.maximum(sum_square, K.epsilon()))

def eucl_dist_output_shape(shapes):
	shape1, shape2 = shapes
	return (shape1[0], 1)

def create_base_network(input_shape, train_mode=True):
	input = Input(shape=input_shape)
	x = Flatten()(input)
	x = Dense(1024, activation='relu')(x)
	x = Dense(1024, activation='relu')(x)
	return Model(input, x)

def test_train():
	tr_pairs = np.array(np.zeros((10, 2, 128, 128, 3)))
	tr_y = np.array(np.zeros((10,)))
	te_pairs = np.array(np.zeros((11, 2, 128, 128, 3)))
	te_y = np.array(np.zeros((11,)))
	input_shape = tr_pairs.shape[2:]
	input_a = Input(shape=input_shape)
	input_b = Input(shape=input_shape)
	base_net = create_base_network(input_shape)
	processed_a = base_net(input_a)
	processed_b = base_net(input_b)
	distance = Lambda(euclidean_distance, output_shape=eucl_dist_output_shape)([processed_a, processed_b])
	model = Model([input_a, input_b], distance)
	rms = RMSprop(lr=0.001)
	model.compile(loss=cosine_proximity, optimizer=rms)
	model.fit([tr_pairs[:, 0], tr_pairs[:, 1]], tr_y,
			  batch_size=48,
			  epochs=2,
			  validation_data=([te_pairs[:, 0], te_pairs[:, 1]], te_y))

	model.save_weights(model_save_path)

def load_test_weights(input_shape):
	weights_path = model_save_path
	model = create_base_network(input_shape)
	model.load_weights(weights_path)
	return model

if __name__ == '__main__':
	model_save_path = 'path/test.h5'
	test_train()
	model = load_test_weights((128, 128, 3))
	print('model loaded woohoo')

Did some digging, it appears that when I do model = Model([input_a, input_b], distance) in test_train() function, keras creates a new model which appears to have a single layer with the name model_1. And this in turn raises the error in saving.py. How can I tackle this problem? Since I am training a siamese network, essentially there is a single CNN as defined in  create_base_network and it would be redundant to save two copies of the same thing. Also during inference if I only want to get the embeddings of a test image, there is no point in loading the base network twice. Am I correct?


Master build - version numbers

Looking at the latest build of master - why would it be producing beta version numbers?
https://ci.appveyor.com/project/GitTools/gittools-testing/branch/master

Oh gees.. I missed this: https://github.com/GitTools/GitTools.Testing/blob/master/GitVersionConfig.yaml#L4

Should we change that so that master produces stable numbers? The only model I am really used to working with is git flow - so having master produce beta packages has thrown me.. What's the reasoning behind this - how do we produce new stable versions with this in place?

I see no reason having this in place, seeing how stable builds of dependent libraries like GitVersion exist. This library has been proven stable enough to remove that beta tag, imo.


Model plugin namespaces and tf prefixes to support multiple model instances

I am setting up some multi-robot simulations and was having issues with the different instances of the Laser, ModelTfPublisher, and DiffDrive plugin colliding on topics and TF transform broadcasters.
I made some changes to these plugins to support prefixing topic names and frame IDs with the model name so that multiple instances play nicely with each other.  I made equivalent changes to TricycleDrive as I did to DiffDrive so you can test it out with the 'cleaner' model.  To test it myself, I just made a second copy of the cleaner model in the default world file so there were two models: cleaner1 and cleaner2.
In the Laser, DiffDrive, and TricycleDrive plugins, I added a boolean YAML parameter 'use_namespace'.  If false, then they behave the same as before.  If true, the model name is prefixed on the necessary topic names and frame IDs.
In the ModelTfPublisher plugin, I added a boolean YAML parameter 'use_tf_prefix', which behaves in a similar fashion to 'use_namespace' in the other plugins.
These two new parameters default to false, so everything will behave as normal by default.

Sorry, somehow I didn't notice the 'namespace' parameter in the parent model plugin! I just tried it out and it works fine for my application.
At the moment I am going to continue using TF 1 and haven't considered future-proofing for ROS 2 at all, since my primary objective is integrating Flatland into the curriculum of the ROS-based class I teach before it starts in early January.  I will probably do an overhaul of the code and lecture materials once ROS 2 is more mainstream, but that doesn't seem to be very soon.
Sorry again for the pointless PR, I will RTFM more thoroughly next time!

No problem. The feature wasn't in there when we talked at iROS, or when you last submitted code (it was added as a result of our discussion). It hasn't seen a lot of use yet, so let me know if there's anything that doesn't work.


Route handlers lose type when middleware is defined inline

Running into a weird problem where the UserRouteHandler type is lost if you use middlewares with the route handler e.g:
import { Router } from "hyper-express";

let router = new Router();

router.get('/hello', (req, res) => {
  // req and res types are inferred fine
})

router.get('/hello', (_1, _2, next) => { next() }, (req, res) => {
  // middleware param types are fine, but the final handler has implicit anys for req and res
})

req and res are of type any, while the middleware function type is inferred correctly, I peeked at the type definition for router[method] functions and they're correctly typed, so not sure why this is happening 🤔
reproduced here

Hey, this bug has been fixed in the recent v6.4.11 release. It seemed to have to do with the MiddlewareHandler being spread inside of the original spread syntax.


python310Packages.pyunifiprotect: 4.1.7 -> 4.1.8

Description of changes
https://github.com/briis/pyunifiprotect/releases/tag/v4.1.8

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 188463 run on x86_64-linux 1

4 packages built:

home-assistant-component-tests.unifiprotect
python310Packages.pyunifiprotect
python39Packages.pyunifiprotect
unifi-protect-backup


Move selector from EntityRule to Spec level

The goal of the selector is to select what hosts to apply the policy to,
not to specify source addresses for matching packets.
Description
It appears there is a mistake in the "Apply policy to Kubernetes node ports" documentation where the allow-cluster-internal-ingress-only policy sets a selector field in the entityrule for source address selection rather than setting it at the spec level to decide what nodes should apply the rules.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Deploy preview for calico ready!
Built with commit b724c0c10722c720618354cdf57f1f7b344c94a5
https://deploy-preview-2874--calico.netlify.com

Thank you for submitting this.
This looks correct to me. Would you be able to make this change to the previous versions too. See https://github.com/projectcalico/calico/blob/master/CONTRIBUTING_DOCS.md#how-to-quickly-apply-changes-in-master-to-a-previous-release for help doing that (or you could just make the change manually since this is so small).

@tmjd I have added a second commit modifying the two versions where I could find kubernetes-node-ports.md


Preparation for second order

Constructing the right extras becomes very tricky when different inner/outer backends must be called in various ways on closure functions

So here's where I'm at. The typical structure of a second-order operator is:
function second_order_operator(f, backend::SecondOrder, x)
    function inner_operator_closure(z)
        inner_extras = prepare_inner_operator(f, inner(backend), z)
        return inner_operator(f, inner(backend), z, inner_extras)
    end
    outer_extras = prepare_outer_operator(inner_operator_closure, outer(backend), x)
    return outer_operator(inner_operator_closure, outer(backend), x, outer_extras)
end

It's hard to prepare the extras because

the inner operator is called on a variable z generated during the outer operator, so it may not have the same type as x. Typically, it might be a vector of Duals instead of a vector of numbers.
in one case (reverse-over-forward HVP), the inner operator closure closes over the vector v in addition to the rest, so the preparation signature may need to look different

My current suggested workflow for preparation:

Define a function wrapper InputCopier which deepcopies and stores the first thing on which it is called, so that we can see what z is like inside the outer operator
Define the inner operator closure
Wrap it in an InputCopier
Call the outer operator on this, now we have the type of z
Prepare the inner operator closure with z
Prepare the outer operator on the prepared inner operator closure

Actually this will not work because

some backends don't even call the underlying function as-is
some only call it during their own preparation step

Partially solved by #135 where the outer differentiation is prepared, but not the inner one. I think it is close to optimal

I see how it is difficult for us to provide default fallbacks for the inner preparation.
How about allowing people to manually deal with the inner preparation by adding an inner_XYZ_extras field to the HVPExtras and defaulting to NoXYZExtras?

Possibly but that would be a very advanced use, and my take is that plenty of things will fail when people first try out the HVP, so optimizing performance that way is not high-priority for me.
Besides, for reverse mode backends which do not require preparation and work out of place (Zygote, Tracker), this is already optimal

In the end I think the easiest approach is to have a mutable extras prepared on the first run, like so: https://discourse.julialang.org/t/second-order-autodiff-which-combinations-should-work/114892/12

This sounds reasonable to me. To play the devil's advocate: on which backends are mutable extras doable and more performant?

I really can't think of any scenario where modifying a field of a mutable struct is more costly than essentially re-creating that field from scratch

Sure, but for which backends is it possible?
(And while it might not be more costly, it should be strictly less costly to warrant the increase in code complexity.)

Mutable extras are doable on all backends. It's not the extras itself you mutate, it's just a field from a wrapper. Here's an example:
mutable struct InnerGradientWrapper{F,B}
    const f::F
    const backend::B
    extras::Union{Nothing,GradientExtras}  # type-unstable
end

function (igw::InnerGradientWrapper)(x::AbstractVector)
    if isnothing(igw.extras)
        igw.extras = prepare_gradient(igw.f, igw.backend, x)
    end
    return gradient(igw.f, igw.backend, x, igw.extras9
end

Tried it in #291 but the problem is that changing this extras object modifies the inner state of our gradient closure. As a result, outer preparation becomes invalid

I'm just wondering how much the type instability will hurt us here

How about the following?
mutable struct InnerGradientWrapper{F,B,E<:Union{Nothing,GradientExtras}}
    const f::F
    const backend::B
    extras::E
end

Tried it in #291 but the problem is that changing this extras object modifies the inner state of our gradient closure. As a result, outer preparation becomes invalid

Could you give an example? This is not clear to me from reading the diff in #291 and the PR contains no further comments.

It's the same discussion that we have had for SparseConnectivityTracer and in #252. The InnerGradientWrapper is a closure that changes its inner state, so preparation is impossible.

In ForwardDiff-over-ReverseDiff, let g be the gradient closure.
I need the exact type of g to tag the duals for the pushforward.
I need the duals to prepare g and get extras.
I need the extras to have the exact type of g because it closes over them.


Can support for  Open in new tab ?

For details, please click to seeing to 👇
https://github.com/Mottie/GitHub-userscripts/issues/123

hotkey simply calls click, so this is not its concern. Where a link is opened should be handled by the element it clicks on, for example, <a target="_blank">.
https://github.com/github/hotkey/blob/0691586c0eca5d198b5619b7321594706f5cc194/src/utils.ts#L16-L22

Thank you very much for your reply!


Post Android 11 fix to v5 branch

Related to this commit: https://github.com/mCodex/react-native-sensitive-info/commit/89dab8495821fb8d0a6169639fb068d81283c4a4
While v6 is in alpha stage, can you please port this (and others if necessary) to v5 version / branch please?
Related PR: https://github.com/mCodex/react-native-sensitive-info/pull/251

Hi!
Of course! Done! Closing this issue for now :)


Unauthentified image request on Safari, iOS and PC

When the initial image is loaded, the request to get its content does not contain the authentication information that my server needs. It may be due to the way the img element is created.
A simple solution may be to have the img element in the Vue template.

v0.1.5 now supports passing an Image object to initial-image prop.
see this demo:

https://jsfiddle.net/zhanziyang/02cLhjkn/2/
https://jsfiddle.net/zhanziyang/02cLhjkn/3/

Running on the second link in Safari iOS gave me those errors and did not show the image.

The first error is a bug within croppa. I will fix it.
But I'm not sure about the second one. I think it is caused by the same problem asked here.
Please help me test it: https://jsfiddle.net/zhanziyang/02cLhjkn/5/ (I added "?v=0.0.1" at the end of the image url so that safari will not using the cached image)

If I remove the css, the loaded image is shown below Croppa, but not inside Croppa.

This is intended. In the seonde demo, croppa uses image outside of it as initial image. Usually you would like to hide it using css.

This is intended. In the seonde demo, croppa uses image outside of it as initial image. Usually you would like to hide it using css.

I wanted to emphasize that the image was still loading correctly.

Oh, I see. The external image does not need canvas, so there is no CORS restrition, thus it can load successfully.
Have you tried https://jsfiddle.net/zhanziyang/02cLhjkn/5/? Is the initial image shown correctly?

I may be able to test tomorrow.

I tested and the problem is still exactly the same.

This fixed the issue for me. I'm using     "vue-croppa": "^1.2.0",
Thanks for this lib!


Master65016 oct

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[ ] All unit tests pass on CircleCi.
[ ] I ran all tests locally and they pass.

verified that the test cases are passing on <IP_ADDRESS> but failing on <IP_ADDRESS> load 9 build


Prepended-input + Uneditable-input not working

At the moment, these two (as above) aren't working together.

             $
             500.00

I don't think the span2 works on it as well.

you have to add the disabled property to the uneditable input... so:

             $
             500.00

Should be open issue - disabled does noting in v1.4.0, span does not work and there is no margin/padding between add-on and uneditable-input


Add support for MFA signup and login flow

What kind of change does this PR introduce?
This pull request adds support for the multi factor authentication flow. I've tested all the methods through the Example application. Please let me know if I need to add/change anything.

@michaelschattgen this is an awesome PR - thank you for your efforts! Code / implementation all looks solid to me, really appreciate the comments and clarity.
Any chance you'd be willing to include tests too? That's about the only thing I see missing.

Thank you! I expect to add tests somewhere in the upcoming days. 😌

I've added the tests for both the StatelessClient and the GotrueClient. I've decided to just combine all MFA calls into 1 test since they all overlap, they all rely on a working Enroll, Verify and Challenge. Alongside these complete flow tests I've also added a couple failure tests.
Please let me know if this is sufficient!

Splendid work, seriously. Thanks for being so thorough - Happy to merge this featureset!


Complete zip() when any of its input signal completes.

Fix for https://github.com/ReactiveKit/ReactiveKit/issues/139

Many thanks! I should have fixed this myself

Nope, you gave me a good chance to contribute!

This has a bug. I'm fixing now... Please wait.

Current coverage is 67.67% (diff: 94.73%)

Merging #140 into master will increase coverage by 1.14%

@@             master       #140   diff @@
==========================================
  Files            19         19
  Lines          1912       1924    +12
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1272       1302    +30
+ Misses          640        622    -18
  Partials          0          0

Powered by Codecov. Last update b8fcb8f...db9c858

I'm now confident!

Looking good @jechol! Thanks a lot :)


New Hue products and their expanded color gamuts

Hi Ben,
First of all - great work on this converter script.  I see it used all over the place in various Hue apps including mine, so I think it's safe to say your code here facilitates a lot of third party Hue development and I'm grateful to you for that.
I've had a couple of users suggest that my app (which takes an RGB value and converts to Hue CIE via your module) is potentially producing unexpected colors on the newer generation Hue hardware.  I know the new stuff has potentially different color gamuts, but I have no way to verify this in practice as I'm still on a bunch of Gen 1 stuff.
So I just wanted to quickly ask you if you can envision this kind of thing being a problem for your module, or if my user is possibly missing something or misunderstanding the color that was produced.
Thanks!

Hey @kershner there's a good chance the conversion code here doesn't apply well to the newer hue lights which have different gamuts.
When I have some time I'll dig into this more and see if there's any updated code provided by Philips.
This looks relevant: http://www.developers.meethue.com/documentation/hue-xy-values

As I recall there used to be a README somewhere buried in the Philips iOS SDK repo but I don't see it anymore.  They used to have a step-by-step implementation guide for converting from RGB to XY color.  That must have been back when there was only one gamut to consider.  Now it appears there are 3.

I have proposed a fix in PR #3.  Once I have a chance to test and verify it's working correctly I'll merge it.

Awesome!  I really appreciate you taking the time to investigate this.

Haven't had the time to implement the new changes into my own application but the issue has been addressed very nicely with your recent updates.  If there are any issues with the new implementation I will be sure to raise them.  Thanks for the quick resolution.


UserInfo Endpoint Call Got Blocked

Hi, I meet an blocked call to userInfo endpoint issue when using oidc-client. In my code, i call signinRedirect (internally calling authorize endpoint) and then signinRedirectCallback in another async step (internally calling token and userInfo endpoint). The calls to authorize endpoint and token endpoint looks successfully and tokens got returned. But for some reason, the login workflow always stops in the call to userInfo endpoint which does not show any error but does show the call blocked transferred for OPTIONS and GET method userInfo in the network development tool without any specific reason. Then it goes into another round of authentication starting from calling authorize endpoint again (I think the reason to go through these workflow interatively because this user does not finish authentication and the workflow gets redirected into the login url which will call the authorize endpoint). Would you know why it happened? Any help i would really appreciate.
I pasted the console logs below. Most of them came from the oidc-client library.
UserManager._signinStart: got navigator window handle index.js:123:2134
OidcClient.createSigninRequest index.js:123:2134
MetadataService.getMetadataProperty for: authorization_endpoint index.js:123:2134
MetadataService.getMetadata: Returning metadata from settings index.js:123:2134
MetadataService.getMetadataProperty: metadata recieved index.js:123:2134
OidcClient.createSigninRequest: Received authorization endpoint https://scm-ui-rrrr-beta.auth.us-west-2.amazoncognito.com/oauth2/authorize index.js:123:2134
SigninState.toStorageString index.js:123:2134
WebStorageStateStore.set bb722153825243238697e0201bf03b5b index.js:123:2134
UserManager._signinStart: got signin request index.js:123:2134
UserManager.signinRedirect: successful index.js:123:2261
OidcClient.processSigninResponse index.js:123:2134
OidcClient.readSigninResponseState index.js:123:2134
WebStorageStateStore.remove 0b0c23a02fb4479c9a0666224c090f9e index.js:123:2134
SigninState.fromStorageString index.js:123:2134
OidcClient.processSigninResponse: Received state from storage; validating response index.js:123:2134
ResponseValidator.validateSigninResponse index.js:123:2134
ResponseValidator._processSigninParams: state validated index.js:123:2134
ResponseValidator.validateSigninResponse: state processed index.js:123:2134
ResponseValidator._validateTokens: Validating code index.js:123:2134
MetadataService.getMetadataProperty for: token_endpoint index.js:123:2134
MetadataService.getMetadata: Returning metadata from settings index.js:123:2134
MetadataService.getMetadataProperty: metadata recieved index.js:123:2134
TokenClient.exchangeCode: Received token endpoint index.js:123:2134
JsonService.postForm, url:  https://scm-ui-rrrr-beta.auth.us-west-2.amazoncognito.com/oauth2/token index.js:123:2134
Navigated to https://scm-ui-rrrr-beta.auth.us-west-2.amazoncognito.com/oauth2/authorize?client_id=2vl9bg8gbh8lfsjoblvqm4ssa8&redirect_uri=https%3A%2F%2Fdev-dsk-rrrr-scm-portal-beta-pdx.aka.amazon.com%2F&response_type=code&scope=openid email profile&state=bb722153825243238697e0201bf03b5b&code_challenge=uPgHdbnu5XGn8HKGy-146RDUIgaR0ERqOUfVdY14gks&code_challenge_method=S256&response_mode=query
JsonService.postForm: HTTP response received, status 200 index.js:123:2134
TokenClient.exchangeCode: response received index.js:123:2134
ResponseValidator._processCode: token response successful, processing id_token index.js:123:2134
MetadataService.getMetadataProperty for: issuer index.js:123:2134
MetadataService.getMetadata: Returning metadata from settings index.js:123:2134
MetadataService.getMetadataProperty: metadata recieved index.js:123:2134
ResponseValidator._validateIdTokenAttributes: Validaing JWT attributes; using clock skew (in seconds) of:  300 index.js:123:2134
JoseUtil.parseJwt index.js:123:2134
ResponseValidator.validateSigninResponse: tokens validated index.js:123:2134
ResponseValidator._processClaims: response is OIDC, processing claims index.js:123:2134
ResponseValidator._filterProtocolClaims, incoming claims:
Object { at_hash: "j-UHdfqHvv4jaqz3VdxIAQ", sub: "ea6d668e-7e51-4712-842e-2c9c81aeb1a0", iss: "https://cognito-idp.us-west-2.amazonaws.com/us-west-2_kF8R4cfO3", "custom:user_id": "rrrr", "cognito:username": "Amazon_rrrr", given_name: "rrrr", nonce: "0g_sEATaDqU-WnXcIzDz2bEKR6wO5o19f451dsNaben4B_Dwt9msiXs5_GEhjtJ5tY-XjyMlBgFnFg6wzkJP-Z3Ef0fyBMtyuO3A9vT6poA0MgDYoWjcTLSYwe0xArcmki-UsOpb3fH61Dj8cskLTwxWB2CPdxh1LQruUp1ts", … }
index.js:123:2134
ResponseValidator._filterProtocolClaims: protocol claims filtered {...} index.js:123:2134
ResponseValidator._processClaims: loading user info index.js:123:2134
MetadataService.getMetadataProperty for: userinfo_endpoint index.js:123:2134
MetadataService.getMetadata: Returning metadata from settings index.js:123:2134
MetadataService.getMetadataProperty: metadata recieved index.js:123:2134
UserInfoService.getClaims: received userinfo url https://scm-ui-rrrr-beta.auth.us-west-2.amazoncognito.com/oauth2/userInfo index.js:123:2134
JsonService.getJson, url:  https://scm-ui-rrrr-beta.auth.us-west-2.amazoncognito.com/oauth2/userInfo index.js:123:2134
JsonService.getJson: token passed, setting Authorization header
Regards

Why does the call to userinfo fail? You will need to debug more into that.

I have the same issue when trying to sign in to Azure AD with loadUserInfo set to true in UserManagerSettings. It works fine with Okta. Thankfully I don't need the user info, but I thought I should mention it here in case it's of any use.

IIRC AAD does not allow CORS on the discovery document endpoints. Maybe that's changed, but I don't know.


Omit deep-equal

we want to remove deep-equal from @textlint/kernel.
Because<EMAIL_ADDRESS>is large
(It support ES3, but we not need to support ES3)
Options:

planttheidea/fast-equals: A blazing fast equality comparison, either shallow or deep

https://bundlephobia.com/package/<EMAIL_ADDRESS>deep-equal deps is large.

https://github.com/textlint/textlint/blob/c3e28a5a721cca843a4631a6eb39ca4e2c984550/packages/textlint/package.json#L62
It can be removed

https://bundlephobia.com/package/<EMAIL_ADDRESS>
18kb :down:


Bug: After zooming the start offset time is not correct anymore

Can you explain better?

If you zoom-in then scroll up, you end up at for example 10am, not 6am anymore.

That's exactly what I was trying to explain to you earlier, the problem with having two levels of zoom. There is no easy fix.


Support normalization like in PyTorch

When we run NewFeatureExtractionPipeline with model sentence-transformers/all-mpnet-base-v2 the result is not normalized. Please refer to https://huggingface.co/sentence-transformers/all-mpnet-base-v2
What we get from pipeline is exactly like sentence_embeddings after mean_pooling and then need to run F.normalize - only after normalization the embeddings are equivalent to result of encode() from SentenceTransformer python package.
I searched myself for implementation of such normalization in Go packages and unfortunately didn't find any, the most closest stuff was in https://github.com/sugarme/gotch with their rich tensor functionality (but still normalize function is missing there). So I implemented it myself based on algorithm provided here:
https://pytorch.org/docs/stable/_modules/torch/nn/functional.html#normalize
The code is not long but required a lot of reverse engineering and debugging, so I will be glad to save time of other developers.
Please let me know if you want to add this functionality, either as new normalize function, or directly as output from NewFeatureExtractionPipeline (maybe with boolean param if to normalize).

sounds good! do you want me to send you this function or how to proceed?

Either works for me, can submit a draft pr or just post the code here?

Hi @sedletsky-f5 can you push to a branch on your own github repo, and then start a pull request to our repo via the github interface?  I dont think github is set up for open pushes, and it doesnt seem to like me adding permissions to your specific user.

@RJKeevil , I followed the regular procedure with github - cloned the repo, made a change and committed it but when I tried to push it, I got above error. it is a matter of permissions that you can give me in this repo via Settings -> Access -> Collaborators and teams (URL path /settings/access). Please give me Role: Write, it should be enough to push and then you can review and approve. Thanks

Hi, i've invited you for write access. I think normally its better if you push to your own repo/fork ala https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request but for this its all good, just please make sure you push to a branch and not to main. Thanks again.

thanks @RJKeevil , yes I am familiar with collaboration in github/gitlab :-)
created PR https://github.com/knights-analytics/hugot/pull/21 - please review

I am just wondering how to explain all dependencies and installation details for the used gotch package. You can see how they did it in another package using it: https://github.com/sugarme/transformer/
Please suggest and I will document it.

and another question is about pipeline - do you have in this repo and if so, how to trigger it to test no regression?

yep we have a full suite, take a look at hugot_test and github actions  - run tests workflow. I'll get back to you tomorrow on the rest, 1am for me here :)

I had issues with pipeline and it looked very complicated to update Dockerfile to always support this option, so I decided to solve it with conditional build (only those ones interested in normalization should use -tags GOTCH after all pre-requisites are installed like in my case). Running now pipeline again to see it is not impacted by this PR.

Ok great, looking good. We can take it from here, we'll see if we can replicate just what we need from gotch in native go before merging.  That will help keep complexity down for users, and should avoid another round of the C tax.

Thanks @RJKeevil , just let me know when you plan to merge so I will see if to use it or external normalization function in my current project.

Will do, aiming for a merge this week

@sedletsky-f5 I have added a new commit for normalization that simplifies things somewhat, now it normalizes the onnxruntime output vectors in native go by implementing the formula at https://pytorch.org/docs/stable/generated/torch.nn.functional.normalize.html without need for gotch. I tested it against your previous gotch implementation and sentence transformers and it provides identical results.
It's less general than your gotch implementation of course but i think it makes sense to implement the special case here, and then eventually if we see that we want to move to tensor operations maybe rewrite it in gonum or gotch if we need a pytorch backend.

It is really a great improvement, @riccardopinosio and I will try now with my example (to see the results are the same). Also I added 1 review comment for your commit. Thanks

@sedletsky-f5 I answered your comment :) let me know if it's clear. Also if this works for you, maybe you can squash the commits, so when I merge it's your contribution.

@RJKeevil and @riccardopinosio can we advance with the merge (all comments are resolved) and tag? It would remove the complexity of gotch in my project.

Perhaps if you can complete your testing of the 1.20 PR today, Riccardo and I can look at running the tests and releasing v0.1.1 tomorrow with both included?

I found more places to fix for v1.20 and it might take some time. So maybe it would be better to not make dependency between these 2 efforts (and release already working normalization). While waiting for pipeline, I can make context switch to the second one :-) thanks

Merged to main


Add ARM64 support with MSVC

Tested with Visual Studio 2022 on a Snapdragon 850 running Windows 11.

Thank you for your contributions.


Adds rerun to cgo docker build

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

/approve

/lgtm
/approve

/unhold


CorrelationIdGenerator uses string.Create and avoids bounds-checks

Description
For netcoreapp2.1 string.Create is used instead of a stack allocation and then copying to the string.
The bound-checks are removed for both targetframeworks.
Benchmarks

BenchmarkDotNet=v0.10.14, OS=Windows 10.0.17134
Intel Core i7-7700HQ CPU 2.80GHz (Kaby Lake), 1 CPU, 8 logical and 4 physical cores
Frequency=2742192 Hz, Resolution=364.6718 ns, Timer=TSC
.NET Core SDK=2.1.300-rc1-008673
  [Host] : .NET Core 2.1.0-rc1 (CoreCLR 4.6.26426.02, CoreFX 4.6.26426.04), 64bit RyuJIT
  Clr    : .NET Framework 4.7.1 (CLR 4.0.30319.42000), 64bit RyuJIT-v4.7.3101.0
  Core   : .NET Core 2.1.0-rc1 (CoreCLR 4.6.26426.02, CoreFX 4.6.26426.04), 64bit RyuJIT

Method
Job
Runtime
Mean
Error
StdDev
Scaled
Gen 0
Allocated

Default
Clr
Clr
30.55 ns
0.3343 ns
0.2610 ns
1.00
0.0178
56 B

StringCreate
Clr
Clr
30.72 ns
0.3675 ns
0.3437 ns
1.01
0.0178
56 B

StringCreateSpanUnsafe
Clr
Clr
29.00 ns
0.1565 ns
0.1463 ns
0.95
0.0178
56 B

Default
Core
Core
38.56 ns
0.7330 ns
0.6498 ns
1.00
0.0178
56 B

StringCreate
Core
Core
29.07 ns
0.1224 ns
0.1022 ns
0.75
0.0178
56 B

StringCreateSpanUnsafe
Core
Core
24.21 ns
0.1273 ns
0.1129 ns
0.63
0.0178
56 B

Default is the current implementation in dev.
StringCreate is for reference when just string.Create is used (only applyable for netcoreapp2.1.
StringCreateSpanUnsafe is this PR.

I just saw some other places where the bounds-check could be avoided in the same way, like
https://github.com/aspnet/KestrelHttpServer/blob/8da5f55832acf0386682726925112ebd411db60c/src/Kestrel.Core/Internal/Http/ChunkWriter.cs#L24-L33
Shall I do this? (if so, in this PR or a new one?)

Thanks! This is a nice improvement on Core without regressing Desktop or complicating the code too much.
In addition to eliminating bounds checks ChunkWriter.BeginChunkBytes, you might also want to look at StringUtilities.ConcatAsHexSuffix.
Before you spend too much more time, I'd like some feedback from @benaadams who's responsible for the majority of the unsafe code in Kestrel. LGTM though.

you might also want to look at

I'll have a look over the place. Thx.

StringUtilities.ConcatAsHexSuffix

BenchmarkDotNet=v0.10.14, OS=Windows 10.0.17134
Intel Core i7-7700HQ CPU 2.80GHz (Kaby Lake), 1 CPU, 8 logical and 4 physical cores
Frequency=2742192 Hz, Resolution=364.6718 ns, Timer=TSC
.NET Core SDK=2.1.300-rc1-008673
  [Host] : .NET Core 2.1.0-rc1 (CoreCLR 4.6.26426.02, CoreFX 4.6.26426.04), 64bit RyuJIT
  Clr    : .NET Framework 4.7.1 (CLR 4.0.30319.42000), 64bit RyuJIT-v4.7.3101.0
  Core   : .NET Core 2.1.0-rc1 (CoreCLR 4.6.26426.02, CoreFX 4.6.26426.04), 64bit RyuJIT

Method
Job
Runtime
Mean
Error
StdDev
Scaled
ScaledSD
Gen 0
Allocated

Default
Clr
Clr
31.33 ns
0.6917 ns
0.8748 ns
1.00
0.00
0.0228
72 B

StringCreateSpanUnsafe
Clr
Clr
30.18 ns
0.2140 ns
0.1897 ns
0.96
0.03
0.0228
72 B

Default
Core
Core
29.77 ns
0.2383 ns
0.2112 ns
1.00
0.00
0.0228
72 B

StringCreateSpanUnsafe
Core
Core
24.77 ns
0.1765 ns
0.1651 ns
0.83
0.01
0.0229
72 B

Other places I've found, but don't know how relevant they are (and didn't try anything so far, just a search in VS):
https://github.com/aspnet/KestrelHttpServer/blob/27799b5acb59523889a3a52a39d606e795b81c50/src/Kestrel.Core/Internal/Http2/HPack/Huffman.cs#L380
https://github.com/aspnet/KestrelHttpServer/blob/27799b5acb59523889a3a52a39d606e795b81c50/src/Kestrel.Core/Internal/Http2/Http2Frame.cs#L20

HTTP/2 isn't supported yet and I expect it will undergo a lot of churn in 2.2. I'd leave it as is for now. I'll keep in mind that it's a possible avenue for improving HTTP/2 perf.

I'll keep in mind that it's a possible avenue for improving HTTP/2 perf.

@halter73 fine, thx. In case of let me know if I can help.

CorrelationIdGenerator.GetNextId w/o lookup (PR not updated yet)

BenchmarkDotNet=v0.10.14, OS=Windows 10.0.17134
Intel Core i7-7700HQ CPU 2.80GHz (Kaby Lake), 1 CPU, 8 logical and 4 physical cores
Frequency=2742192 Hz, Resolution=364.6718 ns, Timer=TSC
.NET Core SDK=2.1.300-rc1-008673
  [Host] : .NET Core 2.1.0-rc1 (CoreCLR 4.6.26426.02, CoreFX 4.6.26426.04), 64bit RyuJIT
  Clr    : .NET Framework 4.7.1 (CLR 4.0.30319.42000), 64bit RyuJIT-v4.7.3101.0
  Core   : .NET Core 2.1.0-rc1 (CoreCLR 4.6.26426.02, CoreFX 4.6.26426.04), 64bit RyuJIT

Method
Job
Runtime
Mean
Error
StdDev
Scaled
ScaledSD
Gen 0
Allocated

Default
Clr
Clr
32.91 ns
0.6418 ns
0.6004 ns
1.00
0.00
0.0178
56 B

StringCreate
Clr
Clr
31.06 ns
0.4951 ns
0.4631 ns
0.94
0.02
0.0178
56 B

StringCreateSpanUnsafe
Clr
Clr
28.88 ns
0.3857 ns
0.3608 ns
0.88
0.02
0.0178
56 B

NoLookup
Clr
Clr
32.77 ns
0.4607 ns
0.4309 ns
1.00
0.02
0.0178
56 B

NoLookupBranchless
Clr
Clr
35.48 ns
0.1829 ns
0.1428 ns
1.08
0.02
0.0178
56 B

Default
Core
Core
38.00 ns
0.2891 ns
0.2705 ns
1.00
0.00
0.0178
56 B

StringCreate
Core
Core
29.55 ns
0.3055 ns
0.2858 ns
0.78
0.01
0.0178
56 B

StringCreateSpanUnsafe
Core
Core
24.50 ns
0.2452 ns
0.2294 ns
0.64
0.01
0.0178
56 B

NoLookup
Core
Core
27.75 ns
0.4264 ns
0.3780 ns
0.73
0.01
0.0178
56 B

NoLookupBranchless
Core
Core
28.91 ns
0.4621 ns
0.4322 ns
0.76
0.01
0.0178
56 B

               Default is the current implementation in dev.
          StringCreate is for reference when just string.Create is used (only applyable for netcoreapp2.1.
StringCreateSpanUnsafe is this PR so far.
              NoLookup w/o lookup, Unsafe only on buffer
    NoLookupBranchless w/o lookup and branchless (for reference)
So StringCreateSpanUnsafe is the current state of this PR.
NoLookup would be the update. Perf regresses a bit (both Core and Desktop). I would stick to StringCreateSpanUnsafe, but shall I update to NoLookup?

StringUtilities.ConcatAsHexSuffix w/o lookup (PR not updated yet)

BenchmarkDotNet=v0.10.14, OS=Windows 10.0.17134
Intel Core i7-7700HQ CPU 2.80GHz (Kaby Lake), 1 CPU, 8 logical and 4 physical cores
Frequency=2742192 Hz, Resolution=364.6718 ns, Timer=TSC
.NET Core SDK=2.1.300-rc1-008673
  [Host] : .NET Core 2.1.0-rc1 (CoreCLR 4.6.26426.02, CoreFX 4.6.26426.04), 64bit RyuJIT
  Clr    : .NET Framework 4.7.1 (CLR 4.0.30319.42000), 64bit RyuJIT-v4.7.3101.0
  Core   : .NET Core 2.1.0-rc1 (CoreCLR 4.6.26426.02, CoreFX 4.6.26426.04), 64bit RyuJIT

Method
Job
Runtime
Mean
Error
StdDev
Scaled
ScaledSD
Gen 0
Allocated

Default
Clr
Clr
31.14 ns
0.3393 ns
0.3173 ns
1.00
0.00
0.0228
72 B

StringCreateSpanUnsafe
Clr
Clr
30.45 ns
0.5382 ns
0.5034 ns
0.98
0.02
0.0228
72 B

NoLookup
Clr
Clr
33.77 ns
0.4602 ns
0.4304 ns
1.08
0.02
0.0228
72 B

NoLookupBranchless
Clr
Clr
33.81 ns
0.4356 ns
0.3861 ns
1.09
0.02
0.0228
72 B

Default
Core
Core
34.12 ns
0.7521 ns
0.7386 ns
1.00
0.00
0.0228
72 B

StringCreateSpanUnsafe
Core
Core
26.85 ns
0.4039 ns
0.3778 ns
0.79
0.02
0.0228
72 B

NoLookup
Core
Core
26.77 ns
0.3949 ns
0.3694 ns
0.79
0.02
0.0228
72 B

NoLookupBranchless
Core
Core
28.02 ns
0.3557 ns
0.3328 ns
0.82
0.02
0.0228
72 B

               Default is the current implementation in dev.
StringCreateSpanUnsafe is this PR so far.
              NoLookup w/o lookup, Unsafe only on charBuffer
    NoLookupBranchless w/o lookup and branchless (for reference)
So StringCreateSpanUnsafe is the current state of this PR.
NoLookup would be the update. On Core perf is equal, on Desktop perf regresses. I would update the PR to use NoLookup. Shall I?

We’re closing this PR because we don’t feel that this change is a good fit for the product at this time - we don't want to add more unsafe code to Kestrel.
We thank you for the contribution and look forward to collaborating more in the future.


Seeding - Add support for type specification

Actual Behaviour
When defining the seed data, you can't specify whether you need an array or a set.
Expected Behaviour
Although this should keep working as it is, it should also allow to define the type of the field.
Define an attribute with all elements of the same type, it will be converted to a list.

This could either support the DynamoDB type notation: {"SS": ["foo", "bar"]} for a StringSet.

Or could set up a flag per table to indicate if the objects should be marshaled or not, using for instance, this library: https://www.npmjs.com/package/dynamodb-marshaler

Steps to reproduce it
NA
LogCat for the issue
NA
Screenshots of the issue
NA
Would you like to work on the issue?
I'm afraid I'm not enough skilled for this :S

+1
Also doesn't work if your value is a number, only works with strings or objects.
This works:
[{"id": "foo","length":"1"},{"id": "bar","length":"7"}]
This doesn't:
[{"id": "foo","length":1},{"id": "bar","length":7}]

@AshanFernando friendly ping 😄

@marksteele @rajikaimal I just checked the seeder.js and its currently using DynamoDBDocument Client which don't expect the data type. However, it seems like the numbers don't support because the line number 115 in seeder.js users require(location) to load the seed file which will expect in JSON format.
My guess is if we can use JSON.parse(fs.readFileSync(location, 'utf8')); it should work for numbers like "length": 7.
@marksteele Will you be able to replace this line in your code inside node-modules/serverless-dynamodb-local/src/seeder.js?

@rajikaimal @AshanFernando
Here's the fix to get numeric values from the JSON to work, had to change the unmarshalBuffer to guard against undefined value in the loop.
`
/**

Transform all selerialized Buffer value in a Buffer value inside a json object

@param {json} json with serialized Buffer value.
@return {json} json with Buffer object.
*/
function unmarshalBuffer(json) {
_.forEach(json, function(value, key) {
if (value !== undefined && value.type==="Buffer") {
json[key]= new Buffer(value.data);
}
});
return json;
}
`

This is now released in 0.2.30. Please close the issue.

Thanks, @vkarponen for the implementation.


Turn ./app/views/issues/_form into tailwind

Bit by bit making progress! A lot harder than it looked.


App relaunch on notification click.

Issue
When the app is not killed, tapping on either background or foreground notifications relaunches the app on Android. I have used postLocalNotification() for showing foreground notifications.
Library version
"react-native-notifications": "^5.0.0"
"react": "18.2.0",
"react-native": "0.71.6",

Manifest changes
<activity
            android:name=".MainActivity"
            android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|screenSize|smallestScreenSize|uiMode"
            android:exported="true"
            android:label="@string/app_name"
            android:launchMode="singleTask"
            android:requestLegacyExternalStorage="true"
            android:screenOrientation="portrait"
            android:windowSoftInputMode="adjustResize">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>

Expected behavior
The app shouldn't be relaunched when it is already open or running in the background (Recents)
Step to reproduce

Open the app
Put it in the recents
send the push notification
click on it, and the app will relaunch.

@vishaledkey did you find a solution?

any solutions for this?

Same issue here after updating the app to latest 5.1.0

@vishaledkey did you find a solution?

I'm using the Notifee library to handle the local notifications for now.

@aoligama  @ersel I ended up patching v5.1.0, here is my patch that works fine https://gist.github.com/ilight/be7141f45f15e39b6fccfe46ca6e3829

I have thwe same issue too please help


pull request for e2e test at 01/28/2017 14:26:35

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


Create RFC for bundling local images in rustdoc output

rendered

I fixed the links and added the explanation for cross-crate inlined images.


Enhancements for parity with primitives

For parity with primitives and other standard types, the following features would be amazing

[ ] core::ops::Not and std::ops::Not for BigUint
[ ] Checked operations for BigUint, e.g. checked_add
[ ] BigInt/BigUint with_capacity plus a method to determine the current int's capacity

Additionally, none of the checked_ operation variants are implemented for BigUint

core::ops::Not and std::ops::Not for BigUint

What would you want this to do with leading zeros? For a fixed-width size, that's no problem, just make them all ones, but BigUint is semantically infinite. We do have Not for BigInt because we can use negative values as-if it were 2's complement, with an infinite prefix of ones. There's prior art for this in Python bitwise operators, where ~x is -x - 1.
Another option to ignore leading zeros and just flip up to the most-significant bit, but that means the round trip !!x won't return to the same value. We could also flip the bits of whatever big-digits are currently allocated, but that exposes the internal digit size which may be different on some targets. We also have an invariant to never have 0 in the most-significant digit, but that would again break the !!x round trip if we trim that.

Checked operations for BigUint, e.g. checked_add

It does implement the trait CheckedAdd etc., but it just doesn't have the same inherent methods that you can use without importing the trait, like BigInt does. They're mostly useless except for checked_div dividing by 0, although I guess checked_sub also avoids negative cases for BigUint. For addition and multiplication, the only reason to have these is for generic code taking T: CheckedAdd, which doesn't need the inherent method at all.

BigInt/BigUint with_capacity plus a method to determine the current int's capacity

This doesn't fit the subject of "parity with primitives"...
I have thought about adding capacity methods, sort of related to #98. I would want this to be either in bits or bytes though, not exposing the internal digit size.

Sorry it took me so long to respond, I've been busy.

What would you want this to do with leading zeros?

I honestly didn't think this would have been as complex of a task as it turned out to be, but (forgive me if this is just plain stupid) couldn't iterating over the internal digits and applying Not to them suffice?
Ex.
for digit in self.data.iter_mut() {
    *digit = !*digit;
}

It does implement the trait CheckedAdd etc.

I'm sorry, I didn't see those!

This doesn't fit the subject of "parity with primitives"...

Forgive me, I was trying to make a title that fit the more general scope of the issue

I have thought about adding capacity methods [..] not exposing the internal digit size.

However it's exposed is fine, as long as there's a way to pre-allocate another Big{U}Int
Thank you for taking the time to respond!

couldn't iterating over the internal digits and applying Not to them suffice?

In the current master branch, the internal digit size varies by target for efficient computation, u32 on 32-bit targets and u64 on 64-bit, and this is considered an implementation detail that may yet change. But even as-is, that means !BigUint::one() as you suggest would return 0xfffffffe on 32-bit targets and 0xfffffffffffffffe on 64-bit. That seems bad.
We also don't keep any leading zeros, so BigUint::zero() is completely empty. Thus, if we just applied Not to all digits, !BigUint::zero() would still be zero!
For the round-trip problem, take a concrete example like let x = (BigUint::one() << 256) - 1u32 -- in binary that's 256 ones, and in digits that will be a size-dependent number of 0xff...ff digits. If we Not this digit-by-digit, they would all turn zero, and then for our no-leading-zeros invariant we'd trim it to an empty vector. If we Not it again, there are no digits left to change, so it remains zero. That means we have x != !!x, which would be pretty surprising.


pandoc document conversion failed with error 137

I ran the pipeline and everything worked up until til the leaflet generation which failed with pandoc document conversion failed with error 137 , any idea what this could be about?
Seems like it was the actual export of the Cloropleth.html file the errored
  Loading Biodiverse results
  ..Observed indices
  ..SES-scores
  ..P-values
  Preparing data for CANAPE analysis
  ..Running the CANAPE analysis
  ...Inferring endemism type
  Estimating sampling redundancy
  ..Loading a file with the total number of GBIF-records per H3-cell
  ..Adding N records to the main table
  ..Estimating the index
  Exporting the data table
  Preparing gridcell polygons
  ..Adding diversity estimates to polygons
  ..Adding H3 cell names
  ..Fixing antimeridian issue
  Creating leaflet map
  ..Generating polygon labels
  ..Building basemap
  ..Preparing color palettes
  ..Adding polygons
  ...  RICHNESS_ALL
  ...  PD
  ...  SES_PD
  ...  PD_P
  ...  ENDW_WE
  ...  SES_ENDW_WE
  ...  PE_WE
  ...  SES_PE_WE
  ... CANAPE
  ... Redundancy
  ..Adding variable selector
  ..Hiding variables
  ..Exporting the results
Command error:
  Killed
  Error: pandoc document conversion failed with error 137
  Execution halted

Memory issue?

Hello Thomas! In the results, there should be a folder pipeline_info, which contains the execution trace and report. Could you please check how much memory this process used? It shouldn't be large, although it can consume >16GB RAM (depends on the number of grid cells in the dataset).

When I lowered h3resolution to 2 , the pipeline succeeded. I was running it with Joes Acacia tree on a GBIF download of all australian Fabaceae data.

Could you please send me the entire folder (wd/be/eeb65c...)? There should be input data, log files, and the command itself.
Please note that there are hidden files and symlinks inside.


Undeclared Variables

Hi, I ran into a
Uncaught ReferenceError: assignment to undeclared variable angleSpeed
I'll submit a PR.

Nice find.  Thank you!


Stop algorithm build

HKube micro-service
dashboard
Describe the bug
trying to stop an algorithm build fails
To Reproduce
Steps to reproduce the behavior:

build an algorithm, and while its building press on the stop button
the build isn't stopping and an error is shown

Screenshots

Additional context
Add any other context about the problem here.

Bug not related to Dashboard, you hadn't connected to API-Server on that moment.