Update view-account-license-and-service-details-with-microsoft-365-po…

…wershell.md
Replaced subpar script with very good script with output to csv showing all users and all skus and service plans in a format that is manageable for large enterprises.

Thank you for the contribution @Smartboss88. Can you please review and sign the Contributor License Agreement?

Not sure what info you need?  My work address is<EMAIL_ADDRESS>Sent from Mail for Windows From: microsoft-github-policy-service[bot]Sent: Thursday, September 14, 2023 1:48 PMTo: MicrosoftDocs/microsoft-365-docsCc: Smartboss88; MentionSubject: Re: [MicrosoftDocs/microsoft-365-docs] Update view-account-license-and-service-details-with-microsoft-365-po… (PR<EMAIL_ADDRESS>please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following<EMAIL_ADDRESS>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<EMAIL_ADDRESS>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<EMAIL_ADDRESS>agree company="Microsoft"Contributor License Agreement Contribution License AgreementThis 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 Yourcontributions to Microsoft open source projects. This Agreement is effective as of the latest signaturedate 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 licenseapproved by the Open Source Initiative (www.opensource.org).“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to anyProject, including but not limited to communication on electronic mailing lists, source code controlsystems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose ofdiscussing and improving that Project, but excluding communication that is conspicuously marked orotherwise designated in writing by You as “Not a Submission.”“Submission” means the Code and any other copyrightable material Submitted by You, including anyassociated comments and documentation.Your Submission. You must agree to the terms of this Agreement before making a Submission to anyProject. This Agreement covers any and all Submissions that You, now or in the future (except asdescribed 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 separatelyto the Project if You (a) retain all copyright and license information that was in the materials as Youreceived them, (b) in the description accompanying Your Submission, include the phrase “Submissioncontaining materials of a third party:” followed by the names of the third party and any licenses or otherrestrictions of which You are aware, and (c) follow any other instructions in the Project’s writtenguidelines concerning Submissions.Your Employer.  If YourSubmission is made in the course of Your work for an employer or Your employer has intellectualproperty rights in Your Submission by contract or applicable law, You must secure permission from Youremployer to make the Submission before signing this Agreement. In that case, the term “You” in thisAgreement will refer to You and the employer collectively. If You change employers in the future anddesire to Submit additional Submissions for the new employer, then You agree to sign a new Agreementand secure permission from the new employer before Submitting those Submissions.Licenses.Copyright License. You grant Microsoft, and those who receive the Submission directly orindirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in theSubmission to reproduce, prepare derivative works of, publicly display, publicly perform, and distributethe Submission and such derivative works, and to sublicense any or all of the foregoing rights to thirdparties.Patent License. You grant Microsoft, and those who receive the Submission directly orindirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license underYour patent claims that are necessarily infringed by the Submission or the combination of theSubmission with the Project to which it was Submitted to make, have made, use, offer to sell, sell andimport 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) aregranted by implication, exhaustion, estoppel or otherwise.Representations and Warranties. You represent that You are legally entitled to grant the abovelicenses. You represent that each of Your Submissions is entirely Your original work (except as You mayhave disclosed under Section 3). You represent that You have secured permission from Your employer tomake the Submission in cases where Your Submission is made in the course of Your work for Youremployer or Your employer has intellectual property rights in Your Submission by contract or applicablelaw. If You are signing this Agreement on behalf of Your employer, You represent and warrant that Youhave 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. UNLESSREQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIESEXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT ISPROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OFNONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of whichYou later become aware that would make Your representations in this Agreement inaccurate in anyrespect.Information about Submissions. You agree that contributions to Projects and information aboutcontributions may be maintained indefinitely and disclosed publicly, including Your name and otherinformation that You submit with Your Submission.Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, andthe 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 toexclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive alldefenses of lack of personal jurisdiction and forum non-conveniens.Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, andsupersedes any and all prior agreements, understandings or communications, written or oral, betweenthe parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>
I just linked my microsoft account to my personal account.  That should do it right?Account link | Microsoft Open Source Management Sent from Mail for Windows From: Smart KamolratanapiboonSent: Thursday, September 14, 2023 2:31 PMTo: MicrosoftDocs/microsoft-365-docs; MicrosoftDocs/microsoft-365-docsCc: MentionSubject: RE: [MicrosoftDocs/microsoft-365-docs] Update view-account-license-and-service-details-with-microsoft-365-po… (PR #12796) Not sure what info you need?  My work address is<EMAIL_ADDRESS>Sent from Mail for Windows From: microsoft-github-policy-service[bot]Sent: Thursday, September 14, 2023 1:48 PMTo: MicrosoftDocs/microsoft-365-docsCc: Smartboss88; MentionSubject: Re: [MicrosoftDocs/microsoft-365-docs] Update view-account-license-and-service-details-with-microsoft-365-po… (PR<EMAIL_ADDRESS>please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following<EMAIL_ADDRESS>agree [company="{your company}"]Options:1.       (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<EMAIL_ADDRESS>agree1.       (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<EMAIL_ADDRESS>agree company="Microsoft"Contributor License Agreement Contribution License AgreementThis 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 Yourcontributions to Microsoft open source projects. This Agreement is effective as of the latest signaturedate 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 licenseapproved by the Open Source Initiative (www.opensource.org).“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to anyProject, including but not limited to communication on electronic mailing lists, source code controlsystems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose ofdiscussing and improving that Project, but excluding communication that is conspicuously marked orotherwise designated in writing by You as “Not a Submission.”“Submission” means the Code and any other copyrightable material Submitted by You, including anyassociated comments and documentation.Your Submission. You must agree to the terms of this Agreement before making a Submission to anyProject. This Agreement covers any and all Submissions that You, now or in the future (except asdescribed 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 separatelyto the Project if You (a) retain all copyright and license information that was in the materials as Youreceived them, (b) in the description accompanying Your Submission, include the phrase “Submissioncontaining materials of a third party:” followed by the names of the third party and any licenses or otherrestrictions of which You are aware, and (c) follow any other instructions in the Project’s writtenguidelines concerning Submissions.Your Employer.  If YourSubmission is made in the course of Your work for an employer or Your employer has intellectualproperty rights in Your Submission by contract or applicable law, You must secure permission from Youremployer to make the Submission before signing this Agreement. In that case, the term “You” in thisAgreement will refer to You and the employer collectively. If You change employers in the future anddesire to Submit additional Submissions for the new employer, then You agree to sign a new Agreementand secure permission from the new employer before Submitting those Submissions.Licenses.Copyright License. You grant Microsoft, and those who receive the Submission directly orindirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in theSubmission to reproduce, prepare derivative works of, publicly display, publicly perform, and distributethe Submission and such derivative works, and to sublicense any or all of the foregoing rights to thirdparties.Patent License. You grant Microsoft, and those who receive the Submission directly orindirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license underYour patent claims that are necessarily infringed by the Submission or the combination of theSubmission with the Project to which it was Submitted to make, have made, use, offer to sell, sell andimport 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) aregranted by implication, exhaustion, estoppel or otherwise.Representations and Warranties. You represent that You are legally entitled to grant the abovelicenses. You represent that each of Your Submissions is entirely Your original work (except as You mayhave disclosed under Section 3). You represent that You have secured permission from Your employer tomake the Submission in cases where Your Submission is made in the course of Your work for Youremployer or Your employer has intellectual property rights in Your Submission by contract or applicablelaw. If You are signing this Agreement on behalf of Your employer, You represent and warrant that Youhave 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. UNLESSREQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIESEXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT ISPROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OFNONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of whichYou later become aware that would make Your representations in this Agreement inaccurate in anyrespect.Information about Submissions. You agree that contributions to Projects and information aboutcontributions may be maintained indefinitely and disclosed publicly, including Your name and otherinformation that You submit with Your Submission.Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, andthe 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 toexclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive alldefenses of lack of personal jurisdiction and forum non-conveniens.Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, andsupersedes any and all prior agreements, understandings or communications, written or oral, betweenthe parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

<!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h3
	{mso-style-priority:9;
	mso-style-link:"Heading 3 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:13.5pt;
	font-family:"Calibri",sans-serif;
	font-weight:bold;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
code
	{mso-style-priority:99;
	font-family:"Courier New";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	font-size:10.0pt;
	font-family:"Courier New";}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 3";
	font-family:"Calibri",sans-serif;
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:238637366;
	mso-list-template-ids:-1;}
@list l1
	{mso-list-id:238909508;
	mso-list-template-ids:-1;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2
	{mso-list-id:1296443824;
	mso-list-template-ids:-1;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3
	{mso-list-id:1457604835;
	mso-list-template-ids:-1;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l3:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4
	{mso-list-id:1840846954;
	mso-list-template-ids:-1;}
@list l4:level1
	{mso-level-start-at:6;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
<EMAIL_ADDRESS>agree company="Microsoft"  Sent from Mail for Windows From: microsoft-github-policy-service[bot]Sent: Thursday, September 14, 2023 2:21 PMTo: MicrosoftDocs/microsoft-365-docsCc: Smartboss88; MentionSubject: Re: [MicrosoftDocs/microsoft-365-docs] Update view-account-license-and-service-details-with-microsoft-365-po… (PR<EMAIL_ADDRESS>please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following<EMAIL_ADDRESS>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<EMAIL_ADDRESS>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<EMAIL_ADDRESS>agree company="Microsoft"Contributor License Agreement Contribution License AgreementThis 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 Yourcontributions to Microsoft open source projects. This Agreement is effective as of the latest signaturedate 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 licenseapproved by the Open Source Initiative (www.opensource.org).“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to anyProject, including but not limited to communication on electronic mailing lists, source code controlsystems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose ofdiscussing and improving that Project, but excluding communication that is conspicuously marked orotherwise designated in writing by You as “Not a Submission.”“Submission” means the Code and any other copyrightable material Submitted by You, including anyassociated comments and documentation.Your Submission. You must agree to the terms of this Agreement before making a Submission to anyProject. This Agreement covers any and all Submissions that You, now or in the future (except asdescribed 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 separatelyto the Project if You (a) retain all copyright and license information that was in the materials as Youreceived them, (b) in the description accompanying Your Submission, include the phrase “Submissioncontaining materials of a third party:” followed by the names of the third party and any licenses or otherrestrictions of which You are aware, and (c) follow any other instructions in the Project’s writtenguidelines concerning Submissions.Your Employer.  If YourSubmission is made in the course of Your work for an employer or Your employer has intellectualproperty rights in Your Submission by contract or applicable law, You must secure permission from Youremployer to make the Submission before signing this Agreement. In that case, the term “You” in thisAgreement will refer to You and the employer collectively. If You change employers in the future anddesire to Submit additional Submissions for the new employer, then You agree to sign a new Agreementand secure permission from the new employer before Submitting those Submissions.Licenses.Copyright License. You grant Microsoft, and those who receive the Submission directly orindirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in theSubmission to reproduce, prepare derivative works of, publicly display, publicly perform, and distributethe Submission and such derivative works, and to sublicense any or all of the foregoing rights to thirdparties.Patent License. You grant Microsoft, and those who receive the Submission directly orindirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license underYour patent claims that are necessarily infringed by the Submission or the combination of theSubmission with the Project to which it was Submitted to make, have made, use, offer to sell, sell andimport 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) aregranted by implication, exhaustion, estoppel or otherwise.Representations and Warranties. You represent that You are legally entitled to grant the abovelicenses. You represent that each of Your Submissions is entirely Your original work (except as You mayhave disclosed under Section 3). You represent that You have secured permission from Your employer tomake the Submission in cases where Your Submission is made in the course of Your work for Youremployer or Your employer has intellectual property rights in Your Submission by contract or applicablelaw. If You are signing this Agreement on behalf of Your employer, You represent and warrant that Youhave 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. UNLESSREQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIESEXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT ISPROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OFNONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of whichYou later become aware that would make Your representations in this Agreement inaccurate in anyrespect.Information about Submissions. You agree that contributions to Projects and information aboutcontributions may be maintained indefinitely and disclosed publicly, including Your name and otherinformation that You submit with Your Submission.Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, andthe 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 toexclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive alldefenses of lack of personal jurisdiction and forum non-conveniens.Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, andsupersedes any and all prior agreements, understandings or communications, written or oral, betweenthe parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>
@JohanFreelancer9

@microsoft-github-policy-service agree company="Microsoft"
On Tue, Sep 26, 2023 at 6:46 AM microsoft-github-policy-service[bot] <
@.***> wrote:

@Smartboss88 https://github.com/Smartboss88 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.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 GitHub
https://github.com/MicrosoftDocs/microsoft-365-docs/pull/12796#issuecomment-1735287453,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALOZKNJDOVO5ZHLRTJTACFDX4KW6TANCNFSM6AAAAAA4X5VY4Y
.
You are receiving this because you were mentioned.Message ID:
@.***>

@kelleyvice-msft Please merge this PR. Thanks

@kelleyvice-msft Gentle reminder.


AVRO-1969: Add schema compatibility checker for Ruby

This change introduces a module Avro::SchemaCompatibility to perform a full compatibility check between two schemas in Ruby. This compatibility check extends the existing schema matching implemented in Avro::IO::DatumReader.match_schemas. The implementation of the .match_schemas class method has been moved to the new module and is called as part of the full compatibility check.
#read?, #be_read? and #mutual_read? methods have been added to Avro::Schema as a way to invoke the new compatibility checks. A #default? method has been added to Field to determine if a field has a default.
Tests for the new module were based on the test cases from:

lang/java/avro/src/test/java/org/apache/avro/io/parsing/TestResolvingGrammarGenerator2.java
lang/java/avro/src/test/java/org/apache/avro/TestSchemaCompatibility.java

Additional fixes included:

support for empty records and empty unions in Ruby (these were useful to demonstrate test parity for compatibility checking)
schema promotion between bytes and strings in .match_schemas
schema promotion within complex types in .match_schemas, e.g. an array of ints promoted to an array of longs

JIRA issue: https://issues.apache.org/jira/browse/AVRO-1969

@spacharya I noticed that you recently looked at another Ruby PR to potentially be merged soon. Would you mind taking a look at this one too? We've also been running with this change in production.

Sorry, not sure why I marked this as good to go but then didn't push the change. Note to myself / whoever pushes this: the commit message needs to be updated to include the JIRA key. Otherwise looks good to go.

I'll look at resolving the conflicts on this tomorrow and will update the commit message to include the JIRA key at that time.

Rebased on current master and commit message updated with JIRA key.


libcudart.so.9.0: cannot open shared object file: No such file or directory

Trying to recreate the example and get the following error when importing from blocksparse.matmul import BlocksparseMatMul
---------------------------------------------------------------------------
NotFoundError                             Traceback (most recent call last)
<ipython-input-1-1dea216b89b0> in <module>()
----> 1 from blocksparse.matmul import BlocksparseMatMul
      2 import tensorflow as tf
      3 import numpy as np

~/anaconda/lib/python3.6/site-packages/blocksparse/matmul.py in <module>()
     11 from tensorflow.python.framework import ops
     12 from tensorflow.python.ops.init_ops import Initializer
---> 13 import blocksparse.ewops as ew
     14
     15 data_files_path = tf.resource_loader.get_data_files_path()

~/anaconda/lib/python3.6/site-packages/blocksparse/ewops.py in <module>()
     15
     16 data_files_path = tf.resource_loader.get_data_files_path()
---> 17 _op_module = tf.load_op_library(os.path.join(data_files_path, 'blocksparse_ops.so'))
     18 # for x in dir(_op_module):
     19 #     print(x)

~/anaconda/lib/python3.6/site-packages/tensorflow/python/framework/load_library.py in load_op_library(library_filename):
     54   """
     55   with errors_impl.raise_exception_on_not_ok_status() as status:
---> 56     lib_handle = py_tf.TF_LoadLibrary(library_filename, status)
     57
     58   op_list_str = py_tf.TF_GetOpList(lib_handle)

~/anaconda/lib/python3.6/site-packages/tensorflow/python/framework/errors_impl.py in __exit__(self, type_arg, value_arg, traceback_arg)
    471             None, None,
    472             compat.as_text(c_api.TF_Message(self.status.status)),
--> 473             c_api.TF_GetCode(self.status.status))
    474     # Delete the underlying status object from memory otherwise it stays alive
    475     # as there is a reference to status from this from the traceback due to

NotFoundError: libcudart.so.9.0: cannot open shared object file: No such file or directory

I believe I have all the prerequisites:

Python 3.6.2
CUDA Version 8.0.61 (from /usr/local/cuda/version.txt)
tensorflow-gpu (1.4.1)
Ubuntu 16.04

I am running an AWS p2.xlarge instance; it uses a single Kepler GPU (K80).
Edit:
Tried this again on another instance that uses Maxwell architecture, since it is recommended (GPU+ at paperspace.com).
Apart from different GPU, the only other difference on that instance is Python 3.6.3.
Still get the same error.

Same issue. Tensorflow alone is working.  Running:

Ubuntu 16.04
Python 3.5.4
CUDA 8.0.44
cudnn 6.0
tf 1.4.1
GPU: 1080ti

Next time I should read before asking. Solved the issue by following instruction in Development section

@LawnboyMax This is probably too late to be useful, but this problem can be addressed by adding the path to the file to your LD_LIBRARY_PATH:
export LD_LIBRARY_PATH=/usr/local/cuda/lib64:$LD_LIBRARY_PATH

Some issue. CUDA 8.0 don't match GCC 5.You can try install GCC 4.

Some issue. CUDA 8.0 don't match GCC 5.4.You can try install GCC 4.


neural blocked because of pipes-zlib using out of bounds pipes

pipes-4.3.5 (Gabriel Gonzalez<EMAIL_ADDRESS>@Gabriel439) is out of bounds for:

[ ] pipes-zlib-<IP_ADDRESS> (>=4.0 && < 4.3). No maintainer. @githubuser @k0001. Used by: library, test-suite

This blocks neural from entering Stackage.

Opened an issue on pipes-zlib. https://github.com/k0001/pipes-zlib/issues/32


Function Discovery

See https://github.com/GoogleContainerTools/kpt/issues/2009#issuecomment-867259380

@pitta issue for tracking discoverability.

Oh wow! Awesome.
If this is the preferred place for this stuff and discussion going forward I'm happy to do that here in the future. Slack just seemed more informal and exploratory .


CLI support for ignoring rules

Is your feature request related to a problem? Please describe.
I'm seeing some false positives after attempting an upgrade to v8.0.2.
Example: https://github.com/moov-io/infra/pull/233
{
	"Description": "Generic API Key",
	"StartLine": 133,
	"EndLine": 133,
	"StartColumn": 18,
	"EndColumn": 49,
	"Context": "                key = \"transit-local-base64-key\"",
	"Secret": "key = \"transit-local-base64-key\"",
	"File": "modules/customers/deployment.tf",
	"Commit": "",
	"Entropy": 3.8553886,
	"Author": "",
	"Email": "",
	"Date": "",
	"Message": "",
	"Tags": [],
	"RuleID": "generic-api-key"
}

Describe the solution you'd like
A solution like shared config files could work, but it would also work to support CLI arguments when ignoring default rules.
Describe alternatives you've considered
generic-api-key could be made a bit more robust. I could also ignore some *.tf files, but that could expose secrets in the future.
cc @zricethezav

@adamdecaf as a stop-gap I removed the generic rule in https://github.com/zricethezav/gitleaks/releases/tag/v8.0.5. I left it commented in the default config in case folks want to enable it.

Sounds good, thanks!


flynn dashbord

when i login in the dashbord,it always show this
Install CA certificate to continue?
but i have installed the flynn-ca.cer.
how should i do，any one can help me?

like this:

@SolarisYan What browser and version of Windows are you using?

@jvatic i use win 10 and the browser is chrome,but i change the firefox all is ok,thx

@SolarisYan Did you try restarting Chrome after installing the cert?

@jvatic ofcoure i restart it,now the issue is like follow:

and the same to IE

@SolarisYan try going to http://dashboard.demo.flynn.com instead of https.

I have the same problem after successfully installing the cert on one machine I've tried to install on another and now can't get past the install cert page. The http:// version loads but doesn't show any apps.

I am unable to reproduce this. Please make sure you're following the installation steps exactly for the certificate (and that there aren't any security exceptions created for it in your browser).

Closing this issue for now. Please open a new issue with the browser/version OS/version and steps to reproduce if encountered again.


custom floating point type (default constructible)

Add support for custom floating point type with these specific conditions:

the type is default constructible (i.e. this will not work with arbitrary precision or arbitrary size floating point classes)
the type T can be constructed with T(0.0)
the type T can be converted to and from NumberIntegerType and NumberUnsignedType
...

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 8 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 98.621%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
5547

Relevant Lines:
5547

💛  - Coveralls


ETL - Update output (from previous input) when changes are made on web site

When a user inputs an excel spreadsheet to an experiment, and then changes the experiment, update the output to reflect the changes.

[x] add excel spreadsheet in upload
[x] detect change delete existing process; add new process
[x] detect change delete existing attributes (parameter/measurement); add new attribute
[x] detect changes values
[ ] detect adding removing/files
[ ] update file-list
[x] update changed values
[x] remove dropped attributes
[x] add new attributes
[x] remove dropped processes
[x] add new processes

Note. Competed, except for files. Separate issue: #1253.


when using mender and xavier nx rootfs is too large

For my image I'm running out of space
ERROR: core-image-tern-1.0-r0 do_image_mender: Size of rootfs is greater than the calculated partition space<PHONE_NUMBER>2 ><PHONE_NUMBER>). This image won't fit on a device with the current storage configuration. Try reducing IMAGE_OVERHEAD_FACTOR if it is higher than 1.0, or raise MENDER_STORAGE_TOTAL_SIZE_MB if the device in fact has more storage.

I've tried increasing it with TEGRAFLASH_SDCARD_SIZE or MENDER_STORAGE_TOTAL_SIZE_MB but both result in parse errors that I seem unable to track down.
Does anyone have a hint what variable might work? My SD card is 256G so it's not a physical space problem ;)

The ROOTFSPART_SIZE variable (from the machine conf file) controls the size of the rootfs partition.  That's the value that gets written out as APPSIZE in the flash layout XML file during flashing. The mender-tegra integration should key everything off that value, too.

@madisongh oh, good tip. So, xavier-nx.inc has ROOTFSPART_SIZE set to 14G and jetson-xavier-nx-devkit.conf has TEGRAFLASH_SDCARD_SIZE set to 16G.
Should I override both in my local.conf? So, if my SD card is actually 32G in my local.conf
TEGRAFLASH_SDCARD_SIZE = "32G"
ROOTFSPART_SIZE = "32212254720"

where<PHONE_NUMBER>0 is 30G
Or, do I just need ROOTFSPART_SIZE?

Right, sorry, I forgot that with Mender in the mix, this gets more complicated...  tegra-mender-setup.bbclass will try to calculate ROOTFSPART_SIZE for you based on TEGRAFLASH_SDCARD_SIZE  and the MENDER-prefixed variables that specify the sizes of the non-rootfs partitions.
So setting TEGRAFLASH_SDCARD_SIZE to 32G should get you a more suitable rootfs partition size.  Try it and check the output of bitbake -e core-image-<whatever> to see if the settings look more reasonable to you.
Taking the suggestion in the error message of changing IMAGE_OVERHEAD_FACTOR might help, too - it defaults to 1.3, where 1.1 might work better for really large rootfs partitions.

fwiw, here is the tail or the error when I change TEGRAFLASH_SDCARD_SIZE
| [   1.7687 ] Copying signatures
| [   1.7694 ] tegrahost_v2 --chip 0x19 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
| [   2.5433 ]
| [   2.5442 ] tegraparser_v2 --generategpt --pt flash.xml.bin
| [   2.5448 ] End sector for APP_b, expected at: 33554398, actual: 59203367
| [   2.5455 ]
| Error: Return value 4
| Command tegraparser_v2 --generategpt --pt flash.xml.bin
| WARNING: exit code 1 from a shell command.

One thing I've done in my builds to bypass all the mender calculation is to use an override, for example:
ROOTFSPART_SIZE_jetson-xavier-nx-devkit = "8589934592"

to get an 8GiB partition size. That overrides the setting in the bbclass, and should take.

hmm, similar parse error
in local.conf
ROOTFSPART_SIZE_jetson-xavier-nx-devkit = "8589934592"

then
| [   2.5133 ] tegraparser_v2 --generategpt --pt flash.xml.bin
| [   2.5139 ] End sector for APP_b, expected at: 33554398, actual: 34563879
| [   2.5149 ]
| Error: Return value 4
| Command tegraparser_v2 --generategpt --pt flash.xml.bin
| WARNING: exit code 1 from a shell command.

@dwalkes ROOTFSPART_SIZE_jetson-xavier-nx-devkit works for you with tegra-demo-distro on the xavier nx?
for me I get
| [   2.5321 ] tegraparser_v2 --generategpt --pt flash.xml.bin
| [   2.5327 ] End sector for APP_b, expected at: 33554398, actual: 34563879
| [   2.5334 ]
| Error: Return value 4
| Command tegraparser_v2 --generategpt --pt flash.xml.bin
| WARNING: exit code 1 from a shell command.

@arrow53 yes I'm using ROOTFSPART_SIZE with a custom machine type, not sure what would be different about your case.  Are you on the dunfell branch?
I just kicked off
source setup-env -m jetson-xavier-nx-devkit -d testdistro-mender
bitbake core-image-base

on https://github.com/OE4T/tegra-demo-distro/tree/dunfell-l4t-r32.4.3 to see if I can reproduce.

wow, thanks @dwalkes I really appreciate the effort. Just knowing it works for you is very helpful.
I am using that exact workflow. I'll be curious what you find but seems I need to slowly add things from core-image-base (I have my own recipe) until it breaks.

I can reproduce, I see there's a problem here with specifying TEGRAFLASH_SDCARD_SIZE=32G in conf/local.conf with no other changes.

not sure what would be different about your case

One difference is the machine I'm using is based on the emmc version.
deploy log for kernel-bup-payload at https://drive.google.com/file/d/1a9DSxL3UbBBV9SC3s_I3PNyMKjGVE1hM/view?usp=sharing and flash.xml from build/tmp/work/jetson_xavier_nx_devkit-oe4t-linux/kernel-bup-payload/1.0-r0/bup-payload/flash.xml at https://drive.google.com/file/d/1KO1ueO3Lj8u_i1YYx5vSAQ6CwRPOiFOz/view?usp=sharing - nothing jumps out at me for either one of these at first glance.

@arrow53  @dwalkes Check the flash layout XML file you are using for this line:
<device type="sdcard" instance="0" sector_size="512" num_sectors="33554432">

That  num_sectors field is set for a 16GB SDcard in the stock XML file for the Xavier NX.  Update that value for your larger card.  You can get the number of sectors with sgdisk <DEVICENAME> --print or parted <DEVICENAME> unit s print (with sudo if needed). For my 32GB card, I get 623333952 sectors.

Ah yes that would do it.  I think we should start a page about customizing root filesystem size for mender on tegra at https://github.com/OE4T/tegra-demo-distro/wiki.  @arrow53 if you can verify this works and want to get it started please do.

Yeah, I'd forgotten about that detail, even though I ran into the exact same problem some time back...  of course, I never got around to writing it down.
We could perhaps add a build-time check to make sure that the size in the XML file matches the TEGRAFLASH_SDCARD_SIZE setting, or maybe even modify the XML based on the variable setting, at least for some common SDcard sizes.

@dwalkes @madisongh I think it's fair to assume sector_size is always 512 (I think that's standard for SD/emmc) so then I think the size is just sector_size * num_sectors / 1024 / 1024 / 1024 GBs.
So num_sectors = TEGRAFLASH_SDCARD_SIZE * 1024 * 1024 * 1024 / sector_size
I get a different value than @madisongh got with partd so not sure if mine is right. Seems bad to argue with partd. Mine did build.
At any rate, the two options seem to be some awk'ing PARTITION_LAYOUT_TEMPLATE or adding a note to the wiki about creating one's own or hand touching the existing one.
Do you guys have a preference? Personally, I think just having the user patch kernel-bup-payload would be fine and making a note in the wiki about it. Lemme know if that's cool and I'll do that and close.

The "G" in the SDcard size is power-of-10, not power-of-2, so use 1000 for your multiplier.   There's also some overhead reserved on the card, which reduces the available number of sectors a bit further.  Using what parted or sgdisk reports (which is also in sysfs) gives you an accurate number, but as long as the count isn't too far off from actual, it should work OK for SDcard builds.  It's more important for the number to be accurate if you're flashing via USB.
A note on the wiki for now would be fine with me.

I made a page https://github.com/OE4T/tegra-demo-distro/wiki/Customization-of-Xavier-NX

Thanks @arrow53 !

I wouldn't be very grateful. it's not a great page. I basically just referred back to here as honestly while it works I'm still confused a bit.

I've updated the page with a generic title and linked to the location where the flash.xml files can be customized can now be found at https://github.com/OE4T/tegra-demo-distro/wiki/Customization-of-Storage-Size-on-Mender-Builds.
See similar question at https://hub.mender.io/t/nvidia-tegra-jetson-xavier-nx/2615/3

Thanks @dwalkes.  I added a bit more on the specifics of what needs to change in the XML file so folks won't have to click through the links.


Intercept CoAP generated payload for printing/storing

Hi!
When enabled debug/trace logs I see generated payload - however it is truncated.
I've checked code, method org.eclipse.californium.core.coap.Message#getPayloadTracingString -- and truncation's there.
Is there a way to intercept the payload for eg. writing to file?
For example I'd like to see what's generated for such sequence:
ExecuteRequest request = new ExecuteRequest(objectId, objectInstanceId, resourceId, argList);  leshanServer.send(registration, request, responseCallback, errorCallback);
Using version 1.3.2
Thank you!

Is there a way to intercept the payload for eg. writing to file?

Maybe using a MessageInterceptor from Californium :thinking:
Looking at this issue you should find a way to do that : https://github.com/eclipse/leshan/issues/696

Should we close this issue ?


laravel mix documentation is lacking an early reference to where the configuration is

webpack.mix.js appears only way down in the documentation at
https://laravel.com/docs/5.4/mix
found me googling 'where is the laravel mix configuration'

We'll make this more clear with the 1.0 release. Thanks.


redub ignores targetName parameter in dub.sdl while dub respects it

It appears that redub does not respect the targetName parameter specified in the dub.sdl file, whereas dub correctly uses this parameter to set the output target name.
Steps to Reproduce:

Set targetName in the dub.sdl configuration file.
Run redub to build the project.
Observe the output file name.

Expected Behavior: redub should respect the targetName parameter and produce an output file with the specified name, similar to how dub handles it.
Actual Behavior: redub ignores the targetName parameter, resulting in an incorrectly named output file.

Fixed in v1.13.6

thank you very much


Add unit tests

E.g. For filters and effects. Start with something simple.

Added just a few unit tests. Need another ticket for further unit testing additions in 8Beat.


Rename chart controller to chartconfig

Towards https://github.com/giantswarm/giantswarm/issues/4949

Closing. Outdated.


1353 steps modal

Implements modal dialog window with the detailed information on the steps.
Fixes https://github.com/whamcloud/integrated-manager-for-lustre/issues/1353

This change is

Some feedback found while testing our manually

If a modal is opened and a step is opened and then closed, the step cannot be expanded again (see GIF below)
When jobs / steps are first loading there should be a spinner to indicate to the user that they are being fetched

I think we should do away with the steps area and just nest it directly under a job like this:

It can be expanded / contracted by clicking on the job (should probably add a chevron as well like the top command).

Do I get it right, that the user cannot "select" multiple commands? Is it possible to have multiple commands? Even if not, I think I could bring a general model :)

We build a tree as we get the data (commands, jobs, step). No matter in which order. We just build a tree that can be displayed to the user. And yes, we need to just store all the commands, jobs, steps as we receive them from the backend. We display as much valid tree as we can.
The user clicks on items he wants to  see, we store user's choices
When displaying the tree, we walk over it and display taking user's choices into account.

For example, initially user has not made any choice and we only show the commands is any.
For the point 2 we in fact need a relational table: (cmd_id: u32, job_id: Option<u32> , step_id: Option<u32>). Implementation may from trivial to some indexed set, with some optimizations in between these edge cases.
So when we are about to show a command, we look up the table of user's choices: if there are entries for that command, we show the command's details (jobs). When we are about to show a job,  we look up the table of user's choices: if there are entries for that job, we show the jobs's details (steps). And so on.
So user's choices act as a filter to the tree.
Here is some trivial implementation => https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=996a4737827b83e011977e4111e9c9c3 :)
Only that user's choice table would need some tests ;-)

Do I get it right, that the user cannot "select" multiple commands? Is it possible to have multiple commands? Even if not, I think I could bring a general model :)

Yes, selecting different commands impossible, this is the restriction brought by Select type. Let me take a look at your code tomorrow.

When jobs / steps are first loading there should be a spinner to indicate to the user that they are being fetched

Omg, at the time I checked that, I had set up a proxy to simulate delays and had verified that it works smooth without any spinners before I realized today, that I customized the proxy in the wrong way and the requests are not delayed. :oops:
Now I have fixed the proxy and see the problem. I'll add the spinners tomorrow, I expect it to be pretty easy.

 Is it possible to have multiple commands? Even if not, I think I could bring a general model :)

The user can possibly "select" multiple commands in the future. I.E. consider the usecase that there are multiple commands in flight and we show a notification regarding them. The user clicks the notification and the command modal pops up to show both commands within it.

Looks like docker test compilation is failing with this patch: https://build.whamcloud.com/job/manager-for-lustre/300/

The iconography for the steps should mirror the jobs and command, i.e.

check for success
ban sign for failure
grey ban sign for cancel
spinner for in progress

Hm, it seems that cancel is not possible to get for steps:

state: One of incomplete, failed, success

So, you propose to forget about (+) and (-) and use the check/ban/spinner icons for them, right?

The layout of these steps seem strange to me:

I would have expected more depth as there are some non-shallow wait_for items:

localhost.har.zip
localhost.har.zip

The iconography for the steps should mirror the jobs and command, i.e.

check for success
ban sign for failure
grey ban sign for cancel
spinner for in progress

In addition, it looks like there are lot's of things being written to the log:

Ugh. Probably I need to make some machinery to avoid such debugging scaffolding from committing.

Hm, it seems that cancel is not possible to get for steps:
state: One of incomplete, failed, success
So, you propose to forget about (+) and (-) and use the check/ban/spinner icons for them, right?

I don't think that description is accurate... I'm pretty sure there is a cancelled state as well.
https://github.com/whamcloud/GUI/blob/0cbf30d7ab36746619a3b53617c1a14a8e8d8622/source/iml/command/step-modal.js#L40-L44
I'd try it out, but it looks like ability to cancel jobs is not part of this patch.
https://github.com/whamcloud/GUI/blob/0cbf30d7ab36746619a3b53617c1a14a8e8d8622/source/iml/command/command-modal.js#L101-L125

We should also show the log / backtrace if there is one on error.

The layout of these steps seem strange to me:
I would have expected more depth as there are some non-shallow wait_for items:

Resolved:


New design time freezing

Resolves #71. Resolves #85.

In simulation problems, we have always one stage, and
problem_options.impose_terminal_phyisical_time = 1;
problem_options.stagewise_clock_constraint = 1;
lead to the very same result, but we may have the same terminal constraint twice (also one relaxed, other as hard, depending on the relaxation settings, hence once we run the integrator, problem_options.stagewise_clock_constraint should always be false.

A small example with two contacts (either simulation or some disc manipulation ocp) would be helpful to check and verify the correctness of the multi contact implementation.

Looks fine except the few minor aestetics comments. As mentioned earlier, having a minimal two contacts example (like the OCP with two discs, described in some of the examples) would be helpful to verify correctness.

I added the three cart problem as a test of the multicontact implementation. It seems to work.

In simulation problems, we have always one stage, and problem_options.impose_terminal_phyisical_time = 1; problem_options.stagewise_clock_constraint = 1; lead to the very same result, but we may have the same terminal constraint twice (also one relaxed, other as hard, depending on the relaxation settings, hence once we run the integrator, problem_options.stagewise_clock_constraint should always be false.

Yep this is now checked in Options.preprocess

Thanks for addressing all my comments. We are almost ready to merge.
I have a few final comments:

simulation: Gauss Legendre leads to infeasible problems both with Stewart and Heaviside and both elastic and inelastic impacts, with GL size of algebraic e.g. theta and t_grid not consistent.
on discs example Heaviside not-lifted much slower than lifted (are the initializations consistent - if yes, then just the nonlinearity makes the difference)
disc example Heaviside with n_s = 1 breaks the plotting for some reason.
tf_simulation example and inelastic impacts, the plots of the the algebraic variables is quite strange (I tried Radau, as it converges)

simulation: Gauss Legendre leads to infeasible problems both with Stewart and Heaviside and both elastic and inelastic impacts, with GL size of algebraic e.g. theta and t_grid not consistent.

The bug that was causing infeasibility is fixed however size mismatch is expected as we do not include the rhs theta/alpha as a variable in the mpcc.

on discs example Heaviside not-lifted much slower than lifted (are the initializations consistent - if yes, then just the nonlinearity makes the difference)

Initialization for $\alpha$ is consistent between both.

disc example Heaviside with n_s = 1 breaks the plotting for some reason.

With heuristic step equilibration the solver finds a solution where each other h is zero. This breaks our plotting code.

tf_simulation example and inelastic impacts, the plots of the the algebraic variables is quite strange (I tried Radau, as it converges)

Does not seem strange to me. the theta multipliers and beta seem to be correct.


link to eye-tracking overview is broken

link is on this page: https://www.jspsych.org/extensions/jspsych-ext-webgazer/
and goes here https://www.jspsych.org/overview/eye-tracking.md (but this shows 404 - not found)

Thanks @tobiasgerstenberg! @jodeleeuw ok for me to fix this and redeploy the docs?

Yes, thanks!

Should be fixed now 👍


feat: add cli script to run from command line

I generated this script by asking Claude 3.5 Sonnet to generate a CLI from the shiny app code.
I then of course reviewed and fixed the few bugs.
In the future, it'd be easy to also optionally take a fasta file, run nextclade and use nextclade results as mutation input.
As an overview, here is what I added to the README, reproduced for convenience:
CLI
A command line interface (CLI) is available for this application. The CLI is a Python script. You can install the necessary packages with conda using the following command:
conda env create -f environment.yaml

Here is an example of how to run the CLI with a list of mutations and the output you can expect:
$ python covid_mutation_distribution/cli.py "C241T, C3037T, A23403G, G28881A, G28882A, G28883C"
Number of mutations: 6
Transition/Transversion ratio: 5.00

Log Likelihoods:
  chronic: -11.04
  total chronic: -11.50
  deer: -12.92
  total deer: -12.11

Best fit distribution: (np.float64(-11.040868182380382), 'global_pre-VoC')
(1.58 times more likely than the global Omicron distribution)

Mutator lineage analysis:
  No mutator lineage detected

Full usage information can be found by running:
usage: cli.py [-h] [--bin-size {genes_split,gene,500,1000}] [--output {text,json}] [--plot] [--plot-output PLOT_OUTPUT] [--color-palette {plasma,viridis,inferno,seaborn}] [--verbose] mutations

SARS-CoV-2 Mutation Distribution Profiler (SMDP) CLI

positional arguments:
  mutations             Comma-separated list of mutations or path to a file containing mutations

options:
  -h, --help            show this help message and exit
  --bin-size {genes_split,gene,500,1000}
                        Bin size for analysis (default: gene)
  --output {text,json}  Output format (default: text)
  --plot                Generate a plot of mutation distribution
  --plot-output PLOT_OUTPUT
                        Output file for the plot (default: mutation_distribution.png)
  --color-palette {plasma,viridis,inferno,seaborn}
                        Color palette for the plot (default: plasma)
  --verbose             Print detailed information during analysis

Currently, the CLI only supports a single query at a time.
Resolves #13

You're awesome - thank you! As noted on the slack Erin is on vacation now, but we'll be in touch later re more!


Soda bread for tea sandwiches?

The effectiveness of the motorload sandwiches at Tal-y-Tara has inspired me.

Too moist - tasty, but not the right thing.


Seeing revocation in OCSP response should trigger ACME renewal

Perhaps subject to configuration, when the mod_md OCSP client observes that a monitored certificate is revoked,
it should attempt to request a new certificate for the managed domain.
Additionally, mod_md could/should generate a new keypair, especially when the OCSP response specifies the keyCompromise revocation reason.
This feature enables hosts to automatically and promptly recover when certificates are revoked.  It would be especially useful in situations where a CA revokes en masse due to some discovered misconfiguration, misissuance, or compromise.  Such situations have occured for publicly trusted ACME CAs including Let's Encrypt, and it should be assumed that events of this kind will continue to occur.  Examples:

https://community.letsencrypt.org/t/2022-01-25-issue-with-tls-alpn-01-validation-method/170450
https://community.letsencrypt.org/t/2023-06-15-certificate-policies-extension-mismatch/200155

Something like #330 ?

I suppose this can be closed, now that the related PRs were merged v2.4.26 was released.


Remove visible caret - iOS always visible

Update Styling Properties in OTPInput Component to Remove Caret.
Partially resolve https://github.com/guilhermerodz/input-otp/issues/32 UI Issue
Update:

This pull request introduces updates to the styling properties of the OTPInput component within the input.tsx file.
The changes aim to enhance the component's visual appearance and consistency with the overall design system to reduce internal styling.
The changes prevent the caret from displaying on the screen when all the inputs are filled in on iOS.
Users are not forced to auto-submit or blur when all characters/digits are filled in.

Changes:

Removed the font-family: 'monospace' property.
Added box-sizing: 'border-box' property.

Rationale:
The removal of the monospace font family from the OTPInput component is motivated by a desire to maintain visual consistency throughout the application. As most components utilize the default system font, aligning the OTPInput component with this standard enhances the cohesive appearance of the interface and reduces the internal styling of the components.
Before

After

The introduction of the box-sizing: 'border-box' property addresses layout challenges encountered with the component's sizing. By including padding and borders in the component's dimensions, we can avoid unexpected layout shifts and provide a more stable and predictable interface for users.
Before

After

Result

Impact:

These changes are expected to improve the visual consistency of the OTPInput component and preventing the caret from displaying.
No major impacts on functionality or existing layouts are anticipated, as the adjustments are primarily aesthetic and pertain to internal component spacing.

hi @codercodingthecode thank you for tackling this issue!
however, this issue is bigger than what we all initially thought...
if the visible caret isn't visible, then it negatively impacts the position where the iOS' long-press context menu will pop. that's why I had to leave a single pixel width caret for iOS, so that it at leasts know where to show.
https://github.com/guilhermerodz/input-otp/assets/10366880/251e886b-3cfe-422e-ba82-1e744355dd30
regarding the monospace font choice:

enforcing monospace font hasn't been an issue as it really doesn't affect anything in appearance when JS is enabled on the page. haven't had any reports about the monospace choice yet.
enforcing monospace helps with consistent spacing per-character, as input-otp implementation is currently "hacky" and needs some predictability/tests.

@guilhermerodz Is there any way to fix caret showing up on iOS then?

can we set  opacity to 0.01 to remove the caret

can we set opacity to 0.01 to remove the caret

that would be so cool! however, iOS does not play well when selecting invisible text 😢

Closing this as it's no longer active. Thanks for helping me out with this!


Design Seller page

Design Seller page
This page has been created and is found in the pages folder to route to the page is '/seller' and the design template is found at
https://demo.activeitzone.com/ecommerce/shop/Filon-Asset-Store-2

I'd like to work on this issues

@ShedrachJonah11  it has already been merged


Consistency issue

As salam alaykoum,
Surah Al Baqarah doesn't contain the audio file for "بِسْمِ اللَّهِ الرَّحْمَٰنِ الرَّحِيم" but Al 'Imran does contain it.

'alaikumsalam
hi @arnaud-zad
I just updated & reformatted audio files https://github.com/semarketir/quranjson/pull/30
I will close this issue
thank you 🙇♂


[topgen,bazel] Add missing source files for topgen py_library

They are part of the dependent modules for util/topgen.py, so they need to be added to the //util/topgen py_library.

@timothytrippel Could you please review this as well? It is the similar support in https://github.com/lowRISC/opentitan/commit/aecb97536e28afbd44be5573bbf3f9e041e430d2 and https://github.com/lowRISC/opentitan/commit/5e93fb3ce6c0b786fbfbfba7a29f73be63c85047

Thanks @timothytrippel ! Could you please help merging the PR?


LUN-253: Change discipline item onPress behavior

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword LUN.

Will do this for exercises and similar in a separate PR.

Please test this if this feels smooth for you.

Wrong branch name, will reopen.


front end homework difficulty

So, I think there is a consensus on the difficulty of this project being too easy.
I've built tools on top of githubs API before, angular + ionic + cordova  ...
One thing that kind of through me off (though I was admittedly junior) was repo navigation. Basically you need to account for N deep files nested in folders recursively.
Maybe we could incorporate a project view in the homework? I feel like a public github viewer is almost cliche at this point
Thoughts? @ghigo @nickick @klaymon @Techwraith

I really like that we start simple with the homework and ramp up the
difficulty in the in person coding session. Whatever we do, we should make
sure that we leave some things open for candidates to implement in person
with us.
On Fri, Feb 24, 2017 at 10:26 AM Jack Hanford<EMAIL_ADDRESS>wrote:

So, I think there is a consensus on the difficulty of this project being
too easy.
I've built tools on top of githubs API before, angular + ionic + cordova
https://github.com/hanford/Mobile-Github-Client ...
One thing that kind of through me off (though I was admittedly junior) was
repo navigation. Basically you need to account for N deep files nested in
folders recursively.
Maybe we could incorporate a project view in the homework? I feel like a
public github viewer is almost cliche at this point
Thoughts? @ghigo https://github.com/ghigo @nickick
https://github.com/nickick @klaymon https://github.com/klaymon
@Techwraith https://github.com/Techwraith
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eaze/homework-front-end/issues/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIVbu9Z0oJd_44OQs2uJWZJGX8zWO32ks5rfyDIgaJpZM4MLhkt
.

Pagination and filtering are also quite easy. Perhaps we should go down the path of implementing the recursion step above ¯_(ツ)_/¯


pick one for Value syntaxes: "|" or " or "

note that other literal characters (outside of {curly brackets}) will be taken literally. That includes

whitespace
commas
semicolons

Those must not be used to indicate an either-or syntax

Value syntax
Example
Requirement
Preferred unit
Occurrence
MIXS ID

[active surveillance in response to an outbreak|active surveillance not initiated by an outbreak|clinical trial|cluster investigation|environmental assessment|farm sample|field trial|for cause|industry internal investigation|market sample|passive surveillance|population based studies|research|research and development] or {text}
field trial
M

1
MIXS:0001151

{termLabel} [{termID}] or [husk|other artificial liquid medium|other artificial solid medium|peat moss|perlite|pumice|sand|soil|vermiculite|water]
hydroponic plant culture media [EO:0007067]
X

1
MIXS:0001057

Swapping "|" or " or "


Allow for events to be blacklisted

Bug: T198386

Coverage decreased (-0.06%) to 89.099% when pulling 1b7f4e10af5c7bb13e435801c3f6610f42152db5 on d00rman:blacklist into 06178c20779c5ff213dcfdaca92fef0072e0d469 on wikimedia:master.

LGTM, one nit inline, although adding a test would be neat.

LGTM. Waiting for travis, merging and deploying.

New tests are failing!


Add IO Config Widget

Description
Adds a widget to let you configure IO sides for machine blocks
Todo

[x] Change icon
[x] Add widget to every block
[x] Display Selected Side state
[x] Hide Neighbor button

Checklist:

[x] My code follows the style guidelines of this project (.editorconfig, most IDEs will use this for you)
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

I think the Soul binder also needs the config screen. (It might not work a 100% right now since it meanly uses fluids and isn't really something you automate, but it should have it).

@ferriarnus the soulbinder uses fixed IOConfig in Pull mode. I have added the widget but it does nothing right now. Should I revert or do we keep it as is until we figure out fluid support ?

The soul binder doesn't need to be fixed anymore. I needed for testing, since a fluid is needed for the recipe. But now with the io config widget, you can easily set a side to pull and it will work. We will indeed rewrite some stuff for fluid support, but the current io config is good enough to handel it I think?

Ok I will change soul binder config and keep the widget


Scrum 2792

Oh yeah, that's great, @sweng66 !  I've implemented the improvements, thanks !

Oh yeah, right now there's no updating, but when it gets run in the future, the data might have change, and it might do updates.  I think the curators won't want to run this until WB is ready to switch over Biblio SoT, so it will be a while.

@sweng66 Ah, thanks, good point !  I tried to remove it now, but then flake8 complains about indented if block that doesn't do anything, and if I try to comment out the if statement, it complains about batch_size not being used, so I'll just leave it as-is for now.  Thank you !

I see! Not a big deal. A good place holder!


Review prototype kit content

Review new prototype kit website: https://prototype-kit.service-manual.nhs.uk/

Waiting for work to be finished updating prototype kit tutorials and update of NHS (from NHS.UK) across the site.


Update GitHubProvider to send token via header

Pull Request Checklist

[x] Have you read How to write the perfect pull request?
[x] Have you read through the contributor guidelines?
[x] Have you added copyright headers to new files?
[x] Have you suggest documentation edits?
[x] Have you added tests for any changed functionality?

Purpose
Updates GitHubProvider to send the OAuth2 token via an authorization header instead of a query param. This is needed as GitHub have deprecated the query param mechanism and are notifying API users periodically about this.
Note: this might be a breaking change for any users that have overridden the GitHub URL.
Background Context
Based the changes on the Dropbox provider which also sends via a header.
References

GitHub Developer blog post discussing the deprecation.

I'll also raise a PR against minutemen/silhouette with the same changes.

Coverage decreased (-0.07%) to 95.763% when pulling 8f27411e28d90162575676e86b0e0f1104449536 on stringbean:github-oauth-header into 1d6defb5b22995b089b44e25d5dff662e87af2d9 on mohiva:master.

Coverage decreased (-0.07%) to 95.763% when pulling 8f27411e28d90162575676e86b0e0f1104449536 on stringbean:github-oauth-header into 1d6defb5b22995b089b44e25d5dff662e87af2d9 on mohiva:master.

Coverage decreased (-0.07%) to 95.763% when pulling 8f27411e28d90162575676e86b0e0f1104449536 on stringbean:github-oauth-header into 1d6defb5b22995b089b44e25d5dff662e87af2d9 on mohiva:master.

@stringbean Many thanks 👍 . Will be released with the next Silhouette version targeting Play 2.8


Fixed bug in resource.version (#5934)

Pull request opened by the merge tool on behalf of #5934

Merged into branches iso6 in 96d96ed80de2088265b9f56b5349bafd33381b5d


Change to async_forward_entry_setups

Describe the bug
A clear and concise description of what the bug is.
2023-02-01 21:06:44.621 WARNING (MainThread) [homeassistant.helpers.frame] Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for resmed_myair using this method at custom_components/resmed_myair/__init__.py, line 23: hass.config_entries.async_setup_platforms(config_entry, PLATFORMS)

Linked PR to fix

https://developers.home-assistant.io/blog/2022/07/08/config_entry_forwards/

Home Assistant now reports this may fail in current versions:
2023-03-21 14:02:22.920 WARNING (MainThread) [homeassistant.helpers.frame] Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for resmed_myair using this method at custom_components/resmed_myair/init.py, line 23: hass.config_entries.async_setup_platforms(config_entry, PLATFORMS)

@prestomation I know you don't have the device any longer and you no longer maintain the code.  Any chance this and the other PR could be merged into a beta so we could try this out?  Thanks.

fix with #29


Fix a few papercuts with the Pulumi AI UI

Addresses a handful of minor input-related issues, including:

Extending the input maxlength to 100K
Capping the number of textarea rows to 6
Only submitting multi-line prompts input on command/control+enter
Resetting the row-count to 1 on completion (since we also clear out the input field)

Fixes https://github.com/pulumi/pulumi.ai/issues/42.

@cnunciato Looks great!! Thanks for the help!


tough-cookie-version-upgrade

PR Checklist:

[x] I have run npm test locally and all tests are passing.
[x] I have added/updated tests for any new behavior.

[x] If this is a significant change, an issue has already been created where the problem / solution was discussed: [N/A, or add link to issue here]

PR Description

Also looking to upgrade tough-cookie version to a stable version.  Should we log an issue in github here?  Or is it possible to get this PR passing tests?


Token factory not working with Android

Works on Desktop and iOS.
Can test here: x.awallet.io

#435


rpm: 4.17.1 -> 4.18.0

Description of changes
https://rpm.org/wiki/Releases/4.18.0
Fixes CVE-2021-35937, CVE-2021-35938 and CVE-2021-35939.

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

[x] 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
[x] 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.

Got a bunch of failures, some packages have broken source URLs or are already broken on master.

It looks like Darwin both x86_64 and aarch64 are unhappy, not sure why.

They are:
checking for mkfifoat... no
configure: error: function required by rpm

That's clearly new requirement by the package, sounds very much like an upstream issue.

Anyway, let me poke upstream: https://github.com/rpm-software-management/rpm/issues/2222


Add OPENAI_API_URL support

Suggestion by @vpavlin, could be used to make requests towards OpenAI compatible API endpoints

Makes sense, any examples in mind?

I use this in my go code: https://github.com/sashabaranov/go-openai/blob/master/config.go#L37


Indium crashes the game before it even loads

When I try to load the game, instead of the "loading world" it automatically gets to "Saving world" like one would see upon exiting the game, then it gets stuck there. the crash log: crash-2023-10-09_20.14.56-client.txt password: 1234

Crash report attached as a text file (please try that first instead of the link in the OP's comment):
crash-2023-10-09_20.14.56-client.txt

thanks ig

Downgrade Fabric API to 0.88.1

indium, apperently

@the-biggest-birfd well obviously the version of Indium is dependent on the version of sodium 🙄
For example, some people that use Valkyrien Skies or the Create mod will use Sodium 0.4.10. I was wondering if this was a similar situation.

a screenie

@the-biggest-birfd well the version of Indium is dependent on the version of sodium, as per it's Modrinth and CurseForge versions pages.
For example, some people that use Valkyrien Skies or the Create mod will use Sodium 0.4.10. I was wondering if this was a similar situation.

ah, no the only thing similar is litmatica fortunately.

Did Litematica say that it was incompatible with Sodium 0.5.3 (and Indium 1.0.27 and FAPI 0?89+)?

no it didnt, my issue is solved, thank you. by the way, do you know portal practice? my inventory doesn't load in, and if you could help, it would be much appreciated! thanks

Please close your issue as this is not a bug in Indium.
I haven't heard of Portal Practice personally so I can't help you there. But have you read the readme of Portal Practice? https://github.com/Semperzz/Portal-Practice/tree/v2.8


Alias success message url not clickable

When aliasing, it would be nice if the final output line:
> Success! test.now.sh now points to test-vvajzszkni.now.sh [4s]
included https:// for the alias domain, to make it clickable in terminals like Terminal.app, iTerm and Hyper:
> Success! https://test.now.sh now points to test-vvajzszkni.now.sh [4s]
I can create a PR if you want this, otherwise feel free to close. Just a minor thing 😃
Edit: Looks like it's actually clickable in iTerm (3.2.0), but not in Terminal.app or Hyper.app.

Closing because the aliased URL is now clickable with the https:// prefix in the latest Now CLI.


Method in Java never  start with capital letter

Check all classes and interfaces in your source code
e.g. I found issue in LoginControl

Myschoolboard what is that?
Give suitable name to method!!
That is lazy!!

that time was just given names of method like that
i was still learning the code


not getting NOTE_STACKED or NOTE_STORED_IN_PAYOUT events

logs for reading note.
logs.txt
as mentioned in #13 issue

We are also having some issues with receiving “stacked” and “note_stored_in_payout” events. We occasionally see them, but most of the time, nothing comes in after the “credit_note” event.
Do you receive “stack” and “note_stored_in_payout” events?
We’ve been unable to correlate this behavior with anything.

@skokov3812 I've inspected POLL command code. From what I understand currently only one event is read there. But according to protocol POLL canreturn list of events since last POLL call.
I think this could be an issue.
Am I correct about current POLL implementation?

So the issue was that we were doing poll manually ( command('POLL') ) before GET_ALL_LEVELS command. If we didn't use poll, we were getting buffer overflow. We have been having this issue with GET_ALL_LEVELS command forever. now that we moved GET_ALL_LEVELS to execute separately, the issue is gone. will open issue on GET_ALL_LEVELS command a bit later.


Writing to the same file from multiple processes does not function when concurrentWrites="true" and keepFileOpen="true"

NLog version 4.2
Behavior seen: I have an application that spawns child process. Each child process writes to the same NLog log file. We have noticed that some child processes fail to write to the log, particularly when there is a roll-over of the log file, but also sometimes at startup.
Behavior expected: It must be expensive to have to open and close the file, so I would expect the keepFileOpen to work for a concurrent process scenario.
Work Around: It seems if keepFileOpen is set to false instead of true, then things work as expected.
I will paste in a test application that demonstrates this. If you would like a ready to run application, let me know and I will email it to you out of band.
To run the code:

tart the application. This will start up 5 processes
Verify the log file contains entries for all 5
Advance the date on your computer by 1 day
Verify the log file contains entries for all 5. In most cases it will not.

using System;
using System.Diagnostics;
using System.Reflection;
using System.Threading;
using NLog;

namespace ConcurrentFileTargetTest
{
  class Program
  {
    private static readonly ILogger Logger = LogManager.GetCurrentClassLogger();
    static void Main(string[] args)
    {
      string processName;
      if (args.Length == 0)
      {
        processName = "0";
        for (int i = 1; i < 5; ++ i)
        {
          Process.Start(Assembly.GetEntryAssembly().Location, i.ToString());
        }
      }
      else
      {
        processName = args[0];
      }

      bool running = true;
      Console.CancelKeyPress += (sender, eventArgs) => running = false; // shutdown on Control-C
      while (running)
      {
        Logger.Debug("{0} - Happily Running Still", processName);
        Thread.Sleep(1000);
      }
    }
  }
}

Thanks for this nice report. Also this will be checked, probably before Monday.

If you like,  it would be helpful if you change above code into an unit test and send a PR.

Ow unit test will be difficult because of

Yes, I looked at doing a unit test, but didn't know how to trick NLog into thinking the current datetime had changed. Also, I would have to spin up multiple processes which would mean I would have to check in my .exe from the test application I wrote.

I was thinking about this. Could this even work? If someone keeps it open, how could others write to it?
Why not keepFileOpen=false?

I was thinking about this. Could this even work? If someone keeps it open, how could others write to it?

That is why Windows and other OS's have Share.ReadWrite | Share.Delete. Also, a process mutex is taking out for writing to the file. I'm not sure why FileLocks are not used, but I'm sure there is a reason.

Why not keepFileOpen=false?

Have you seen how this is implemented? It would be very poor performance. Each Logger loops until the file is available for writing. I would switch to another logging implementation before I would use this option.
The documentation sounds like it is meant to force keepFileOpen=true if concurrentWrites=true. So I'm sure it is supposed to work.
"concurrentWrites - Indicates whether concurrent writes to the log file by multiple processes on the same host. Boolean Default: True
This makes multi-process logging possible. NLog uses a special technique that lets it keep the files open for writing.
NOTE: are ignored unless keepFileOpen are set to true."

Have you seen how this is implemented?

Not in details, yet. I first try to get all the input from an issue, and then check the code.

It would be very poor performance. Each Logger loops until the file is available for writing. I would switch to another logging implementation before I would use this option.

Well I don't have that experience (and we use it form an application which spans a lot of threads and async tasks). If way more faster then just writing to file with standard .Net stuff  (e.g. WriteLine to filestream)

Well I don't have that experience (and we use it form an application which spans a lot of threads and async tasks). If way more faster then just writing to file with standard .Net stuff (e.g. WriteLine to filestream)

It is certainly great with multiple threads and async tasks. The issue here is the performance when you have multiple processes writing to the same log file. Here is the loop that is run for every message that is logged when you have concurrentWrites = "False". If multiple processes are writing to the same file, it has to open the file exclusively (because Share.None is used). If it fails to do so because another process is currently writing, it loops (as below) with a sleep until the file is available, or until the ConcurrentWriteAttempts has been reached. So there is no guarantee the message will actually be logged.
       protected FileStream CreateFileStream(bool allowFileSharedWriting)
        {
            int currentDelay = this.CreateFileParameters.ConcurrentWriteAttemptDelay;

			InternalLogger.Trace("Opening {0} with allowFileSharedWriting={1}", this.FileName, allowFileSharedWriting);
            for (int i = 0; i < this.CreateFileParameters.ConcurrentWriteAttempts; ++i)
            {
                try
                {
                    try
                    {
                        return this.TryCreateFileStream(allowFileSharedWriting);

Yes, I looked at doing a unit test, but didn't know how to trick NLog into thinking the current datetime had changed. Also, I would have to spin up multiple processes which would mean I would have to check in my .exe from the test application I wrote.

If we just span a lot of threads, isn't that enough? Then I will fix setting the datetime on the filetarget (https://github.com/NLog/NLog/issues/1022)

Hi Julian, it is not a threading issue. It is a multi-process issue. Spinning up threads will not test this functionality. You need to spin up processes.

I think the lock is blocking too much:

before:

after:

sure, we need the lock, but maybe a smaller scope?

I can reproduce it:
archived log file:

new log file after archive:

I did some research into the filetarget recently.  Will look at this soon.

when  keepFileOpen="true" => MutexMultiProcessFileAppender.TheFactory
when  keepFileOpen="false" => RetryingMultiProcessFileAppender.TheFactory

File "unknown" in process which isn't writing anymore:

not sure where the problem lies. No exceptions, and just this.file.write/flush  (filestream) is called (so no lock issues), but it won't write! Anyone an idea?

Not Sure if this will be useful or you have seen this already.
http://stackoverflow.com/questions/18690537/multi-processes-readwrite-one-file
http://stackoverflow.com/questions/640122/is-there-a-global-named-reader-writer-lock?answertab=active#tab-top

Thanks for the info!
I will those in detail. Anyway good to know:

We use the Mutex approach
and this seems to work really good, but not after archive (File.Move).

This issue seems to be fixed with the latest build.

That would be great news! I will validate this (as I reproduced the issue before)

Confirmed :)
Tested it with branch https://github.com/NLog/NLog/tree/1029-Writing-to-the-same-file-from-multiple-processes
before merge the issue was again reproducible, after the merge it all works.
Thanks @bhaeussermann !

I have done a deeper investigation of this issue.
The issue happens because of a rather strange anomaly involving file handles. The MutexMultiProcessFileAppender works using a FileStream that is constructed from a file handle with shared-writing access. When the log file is archived, it is moved to its new file path. This does not physically move the file, but merely makes an update in the file system's allocation table. This means that the file handle of the MutexMultiProcessFileAppender is still pointing to the same file which is now archived.
So with the current release of NLog, the following happens:

The first process to log after changing the date, archives the current log file, and its appender is invalidated. A new appender is created for the new log file.
This causes the last-write-time of the archived file to be updated.
The second process still has a handle to the now-archived file. It reads the updated last-write-time and concludes that the file must not be archived. It continues logging to that archived file.

The reason this issue no longer seems to be occuring in the new build is because we have changed the archiving-criteria to be based on the created-date of the file instead of the last-write-time. When the log file is moved to its archive file path, the created-date stays the same, so the second process will try to archive the file again. This does not succeed as the archive file already exists, but the file appender is nevertheless invalidated. Therefore a new file appender is created and the file handle is updated to point to the new log file.
When the archiving fails in the second process, it fails with an exception causing the log message to get lost. I have made a pull request that fixes this. This pull request also adds a test that tests against the situation described above so that we won't regress in the future (we emulate separate processes by configuring two different file targets that log the same file).
The new test still fails under Mono and I shall look into that.

Great work!

Great job bhaeussermann!