Update PayrollUS.md

update

Docs Build status updates of commit 76b3d3e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/payroll/PayrollUS.md
:warning:Warning
View
Details

dynamics-gp/payroll/PayrollUS.md

Line 576, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot' is duplicated. Within an article, alt text must be unique.
Line 617, Column 3: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 711, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 733, Column 3: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 766, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1077, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1168, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1179, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1193, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1512, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1632, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1811, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot again' is duplicated. Within an article, alt text must be unique.
Line 1871, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot again' is duplicated. Within an article, alt text must be unique.
Line 1875, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'one screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1879, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Another screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1883, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Also a screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1936, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/CREDITOR.JPG'.
Line 1936, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot again' is duplicated. Within an article, alt text must be unique.
Line 1940, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/CREDITOR1.JPG'.
Line 1940, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'one screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1944, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/CREDITOR2.JPG'.
Line 1944, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Another screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1948, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/CREDITOR3.JPG'.
Line 1948, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Also a screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1958, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/CREDITOR4.JPG'.
Line 1958, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Also a screenshot ' is duplicated. Within an article, alt text must be unique.
Line 2107, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 2444, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 2727, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 2913, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 3018, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 3138, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'screenshot' is duplicated. Within an article, alt text must be unique.
Line 3271, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 3420, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 3488, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 3556, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 3621, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 3863, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 3962, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4094, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot' is duplicated. Within an article, alt text must be unique.
Line 4181, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot' is duplicated. Within an article, alt text must be unique.
Line 4370, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4386, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4507, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4758, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4792, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4839, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4871, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4901, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4932, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4964, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4995, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5028, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5058, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5083, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5107, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5138, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a computer Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5218, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5337, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5410, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5435, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5597, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5603, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a computer Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5609, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a computer Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5927, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6615, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6661, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6953, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6990, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 7286, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 7405, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 7451, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'screenshot' is duplicated. Within an article, alt text must be unique.
Line 7864, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 8021, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 8267, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 8514, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 8542, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2c439f1:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/payroll/PayrollUS.md
:warning:Warning
View
Details

dynamics-gp/payroll/media/CREDITOR.JPG
:white_check_mark:Succeeded
View

dynamics-gp/payroll/media/CREDITOR1.JPG
:white_check_mark:Succeeded
View

dynamics-gp/payroll/media/CREDITOR2.JPG
:white_check_mark:Succeeded
View

dynamics-gp/payroll/media/CREDITOR3.JPG
:white_check_mark:Succeeded
View

dynamics-gp/payroll/media/CREDITOR4.JPG
:white_check_mark:Succeeded
View

dynamics-gp/payroll/PayrollUS.md

Line 576, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot' is duplicated. Within an article, alt text must be unique.
Line 617, Column 3: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 711, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 733, Column 3: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 766, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1077, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1168, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1179, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1193, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1512, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1632, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1811, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot again' is duplicated. Within an article, alt text must be unique.
Line 1871, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot again' is duplicated. Within an article, alt text must be unique.
Line 1875, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'one screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1879, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Another screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1883, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Also a screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1936, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot again' is duplicated. Within an article, alt text must be unique.
Line 1940, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'one screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1944, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Another screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1948, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Also a screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1958, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Also a screenshot ' is duplicated. Within an article, alt text must be unique.
Line 2107, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 2444, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 2727, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 2913, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 3018, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 3138, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'screenshot' is duplicated. Within an article, alt text must be unique.
Line 3271, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 3420, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 3488, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 3556, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 3621, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 3863, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 3962, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4094, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot' is duplicated. Within an article, alt text must be unique.
Line 4181, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot' is duplicated. Within an article, alt text must be unique.
Line 4370, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4386, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4507, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4758, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4792, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4839, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4871, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4901, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4932, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4964, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4995, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5028, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5058, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5083, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5107, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5138, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a computer Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5218, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5337, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5410, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5435, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5597, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5603, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a computer Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5609, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a computer Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5927, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6615, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6661, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6953, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6990, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 7286, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 7405, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 7451, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'screenshot' is duplicated. Within an article, alt text must be unique.
Line 7864, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 8021, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 8267, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 8514, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 8542, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f456fe6:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/payroll/PayrollUS.md
:warning:Warning
View
Details

dynamics-gp/payroll/media/CREDITOR.JPG
:white_check_mark:Succeeded
View

dynamics-gp/payroll/media/CREDITOR1.JPG
:white_check_mark:Succeeded
View

dynamics-gp/payroll/media/CREDITOR2.JPG
:white_check_mark:Succeeded
View

dynamics-gp/payroll/media/CREDITOR3.JPG
:white_check_mark:Succeeded
View

dynamics-gp/payroll/media/CREDITOR4.JPG
:white_check_mark:Succeeded
View

dynamics-gp/payroll/PayrollUS.md

Line 576, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot' is duplicated. Within an article, alt text must be unique.
Line 617, Column 3: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 711, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 733, Column 3: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 766, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1077, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1168, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1179, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1193, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 1512, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1632, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1811, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot again' is duplicated. Within an article, alt text must be unique.
Line 1871, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot again' is duplicated. Within an article, alt text must be unique.
Line 1875, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'one screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1879, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Another screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1883, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Also a screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1937, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot again' is duplicated. Within an article, alt text must be unique.
Line 1941, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'one screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1945, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Another screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1949, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Also a screenshot ' is duplicated. Within an article, alt text must be unique.
Line 1959, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Also a screenshot ' is duplicated. Within an article, alt text must be unique.
Line 2108, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 2445, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 2728, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 2914, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 3019, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 3139, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'screenshot' is duplicated. Within an article, alt text must be unique.
Line 3272, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 3421, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 3489, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 3557, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 3622, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 3864, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 3963, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4095, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot' is duplicated. Within an article, alt text must be unique.
Line 4182, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot' is duplicated. Within an article, alt text must be unique.
Line 4371, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4387, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4508, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4759, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4793, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4840, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4872, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4902, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4933, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4965, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 4996, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5029, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5059, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5084, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5108, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5139, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a computer Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5219, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5338, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5411, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5436, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5598, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5604, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a computer Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5610, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a computer Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 5928, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6616, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6662, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6954, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 6991, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 7287, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot of a cell phone Description automatically generated' is duplicated. Within an article, alt text must be unique.
Line 7406, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 7452, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'screenshot' is duplicated. Within an article, alt text must be unique.
Line 7865, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 8022, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot' is duplicated. Within an article, alt text must be unique.
Line 8268, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 8515, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.
Line 8543, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'A screenshot ' is duplicated. Within an article, alt text must be unique.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Fixes embed changeset corruption when parent insert fails.

This fixes the bug reported in #1584. The issue was caused by the fact that embedded changes are already replaced in the changeset with their target struct before the parent records in the changeset are processed. So if a parent insert causes an error, we end up returning a changeset with the replaced struct, not the original changeset for the embedded object. I've fixed this by checking if the changeset is still valid after attempting to process the parents, and only after that check are the embed changesets converted to structs.
I've gone for a minimal set of changes to get this test to pass (and not break anything else). But if there is anything I should refactor, let me know.

@seangeo great job! Can you please make sure we also don't have the same bug on updates? :D

Will do. Thanks 👍

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


Fix item positioning, text alignment & unwanted clipping of ItemList items

Implements part of the fixes mentioned in #88217
The following points are fixed:

Clipping of selection indicator at the top or bottom of the list
Gap at the bottom of the list in rows mode when the end of the scrollbar is reached
In grid display, labels were not properly centered, a little offset to the side was happening
Separators overlapping some items by a pixel or two beyond the border
Inconsistent scale of vertical separation, which is double in comparison to horizontal separation (if you put 10px vertically, it displays like 20px, while if you put 10px horizontally, it remains 10px). Default & editor themes adjusted to compensate.

For the sake of consistency, the horizontal separation which did nothing on list rows (non-grid) mode is now acting like an internal padding, the same way it does for grid items.
This is a rewrite of the positioning algorithm so that internal calculation of item positions now corresponds to the actual screen rendering.
In the base situation before this fix, items positions are calculated with a gap in mind then grown on the four sides to cover that gap. This is responsible of the clipped selection indicators.
With this fix applied, the position calculation takes into account an appropriate padding to give the same effect as in the initial situation, and positions them correctly to align with the container borders without unwanted clippings and paddings.
No more clipping at the top and left

No more extra gap at the bottom

Text is correctly centered within grid items

Row items can have horizontal padding, leveraging the h_separation parameter that was not taken into account in this mode

Indeed, I forgot to adjust the default theme after the vertical spacing fix. Will have a look.
I don't think some smaller item height makes the thing harder to click, on the opposite it becomes less small-screen-friendly and requires more work when using the default theme in a low-res, scaled-up game. But I agree with your point that we should avoid breaking existing projects appearance as much as possible and limit those to more important version upgrades.
I have additional fixes and improvements that I plan to build on top of this work, btw.

I limited the blast radius of this refactoring so that we can merge it in 4.2. Perhaps I can revert the v_separation to use the old 2x behavior to avoid breaking current themes. What do you think?
Saying this because I have other points to refactor that can break existing themes, and I want to deliver those in a different PR that would wait for the correct timing for such changes. This PR would have not point then as it is considered breaking in the current state.

Thanks!


SendGetGroups giving bad request error

Even w:g2 giving feature-not implemented error

i have same problem...
have you solutions?


Wrong cardinality for output parameter 'payload' in operation GetAllSubmodelDescriptors

What?
AAS Part 2 v3.0 (IDTA Number 01002-3-0), Section 6.3.2 (page 52) defines operation GetAllSubmodelDescriptors with output parameter payload with cardinality 1..* but should ne 0..* as it could happen that there is no matching SubmodelDescriptor in the registry.

The payload is optional, this means if there are not Submodel Descriptors a corresponding error message is returned but no empty list, probably "SuccessNoContent"

I understand your train of thought, however there are some issues.
SuccessNoContent is not an error code but, as the name suggests, an return code indicating that an operation has successfully been executed but does not have a result. Mapping things to the REST API, it would technically be ok to return 204 No Content with an empty body when there is no result.
Although technically possible, the best practice for REST APIs does not do this but returns just an empty array. Personally, I have never seen any REST API return 204 instead of an empty array, so at least it will be unexpected behavior for anyone using the AAS API.
The specification also never specifies that SuccessNoContent should/must be returned. In fact, the Swagger definition does not allow to return 204 No Content.
I also did some deeper digging/analysis to cross-check how this done for other GetAll calls and I did notice that there is some level of inconsistency. Basically, there are two "types" how the return value of those operations is defined

with cardinality 0..* and mandatory=true
with cardinality 1..* and mandatory=false

To me, this seems inconsistent and should be harmonized. I also noticed the following things during the analysis

Operation AAS Repository#GetAllAssetAdministrationShells has output cardinality of exactly 1 while it should allow a list to be returned
Operation AAS Repository#GetAllAssetAdministrationShellsByIdShort has output cardinality of exactly 1 while it should allow a list to be returned
Operation Submodel Repository#GetAllSubmodelsBySupplementalSemanticId is defined in the overview table of the interface but detailed description defining its in-/output parameter is missing completely
Operation AAS Basic Discovery#GetAllAssetAdministrationShellIdsByAssetLink has cardinality 1..* and mandatory=true - a unique combination that does not make sense
Descriptions of the output parameter is quite inconsistent, sometime saying list of ... and sometime request ....s

To better understand the issues I am adding a table of all GetAll... methods in the specification

Interface
Operation
Cardinality
Mandatory
Output argument description text

AAS
GetAllSubmodelReferences
0..*
yes
Requested Submodel References

Submodel
GetAllSubmodelElements
0..*
yes
Requested submodel elements

AASX File Server
GetAllAASXPackageIds
0..*
yes
Matching package list; the PackageDescription includes all Asset Administration Shell identifiers, also those which may have not been requested through the aasId input parameter

AAS Registry
GetAllAssetAdministrationShellDescriptors
1..*
no
List of Asset Administration Shell Descriptors

Submodel Registry
GetAllSubmodelDescriptors
1..*
no
List of requested submodel descriptors

AAS Repository
GetAllAssetAdministrationShells
1
no
List of Asset Administration Shells

AAS Repository
GetAllAssetAdministrationShellsByAssetId
1..*
no
Requested Asset Administration Shells

AAS Repository
GetAllAssetAdministrationShellsByIdShort
1
no
Requested Asset Administration Shells

Submodel Repository
GetAllSubmodels
1..*
no
List of submodels

Submodel Repository
GetAllSubmodelsBySemanticId
1..*
no
Request Submodels

Submodel Repository
GetAllSubmodelsBySupplementalSemanticId

Missing!

Submodel Repository
GetAllSubmodelsByIdShort
1..*
no
Requested Submodels

CD Repository
GetAllConceptDescriptions
1..*
no
List of Concept Descriptions

CD Repository
GetAllConceptDescriptionsByIdShort
1..*
no
Requested Concept Descriptions

CD Repository
GetAllConceptDescriptionsByIsCaseOf
1..*
no
Requested Concept Descriptions

CD Repository
GetAllConceptDescriptionsByDataSpecificationReference
1..*
no
Requested Concept Descriptions

AAS Basic Discovery
GetAllAssetAdministrationShellIdsByAssetLink
1..*
yes
Identifiers of all Asset Administration Shells which contain all asset identifier key-value-pairs in their asset information, i.e. AND-match of key-value-pairs per Asset Administration Shell

AAS Basic Discovery
GetAllAssetLinksById
1..*
no
Requested asset identifier, which could be the globalAssetId or specificAssetIds.

In my opinion, there should only be one way to interact with such collections and in the REST API world this is typically returning 0..* (mandatory: yes) which is simply left empty when there are no (matching) results.


Include datasets with underscores when listing BigQuery datasets

This is #954, with regression tests against the v0.10.1 state.
To get the tests to fail you actually have to remove the try/except here: https://github.com/fishtown-analytics/dbt/blob/554ecb0/dbt/adapters/bigquery/impl.py#L471-L475, it was suppressed incidentally as part of #856. This fix still skips a few get/create calls, so we should keep it! Thank you @k4y3ff!

can we also change the base of this PR to dev/guion-bluford?


startOfFailure

Just a simple Feature Request.
If you know the endOfFailure and the duration, it is possible to calculate the startOfFailure :-)
        "longPowerFailureLog": {
            "count": 2,
            "log": [
                {
                    "endOfFailure": "2010-12-08T14:24:15.000Z",
                    "duration": 240,
                    "unit": "s"
                },
                {
                    "endOfFailure": "2010-12-08T14:10:04.000Z",
                    "duration": 301,
                    "unit": "s"
                }
            ]
        },

Sounds like a good addition! I can add by the end of the week. Or you can submit a PR ;)

Thanx,
I will, but first i have to rebuild my scripts with your great p1 module :-)

The feature has been added in version 1.4.0, which is now released.

great thx


[SPARK-34079][SQL][FOLLOW-UP] Remove debug logging

What changes were proposed in this pull request?
To remove debug logging accidentally left in code after https://github.com/apache/spark/pull/32298.
Why are the changes needed?
No need for that logging.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.

cc @cloud-fan

Merged to master and branch-3.3.

Thanks @HyukjinKwon.


Improve configurability

Done for me because I use  as a leader and that would break in markdown files and because I don't use spell checking.

Thanks! All the last reported issues are about the spell checking that is perceived as "wrong syntax highlight" :smile:


pull request for e2e test at 01/29/2017 21:56:12

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


highlight DU cases and Active Patterns as "Enum" Roslyn classification

WIP
It looks like this:

Issues:

it does not highlight enums
it does not highlight Active Patterns on declaration site

If this change is OK in principle, I can add highlighting for modules and, maybe, some other symbol kinds.

Ignore the AppVeyor failure, it's a timeout

@vasily-kirichenko How does this compare to default VFPT colorization?  thanks

@dsyme by default VFPT highlights types, modules and quotations. So,I think it'd be ok to have types and modules highlighted in RTM, as a first step. The problem is than existing code has access to full ranges, which results with https://github.com/Microsoft/visualfsharp/issues/1697 and fully.qualified.ctor.names are entirely colored in this PR. Also it's impossible to distinguish namespaces, which should not be colored, from modules.

I'm closing it. See https://github.com/Microsoft/visualfsharp/pull/1841 instead.

super, thanks


[XamarinWorkbooks-Windows]: Accessibility: MAS 4.3.1: High Contrast: "Reset all preferences" button border appearing in green color in High contrast black mode and brown color in High contrast white mode.

Steps to Reproduce
Pre-Requisite: Change the system high contrast mode before launching the application.

Launch Xamarin Workbooks application. Which invokes "Create New Workbook" window.
Navigate to Tools -> Preferences. Invoke preferences tab. It will open the general tab of preferences.
Observe the border color of "Reset all preferences" button.

Expected Behavior
Border color should follow high contrast standards
Actual Behavior
"Reset all Preferences" button border is appearing in green color in High contrast balck and brown color in high contrast white, but it is not a disabled button. User may perceive it as disabled button because of green color border.
User Impact
As the border color appears in green color in HC Black and brown in HC White, user may perceive it as disabled element which is actually not. It deviates the user from the purpose.
Screenshots

Environment
Windows :Windows 10 Pro Version 1803 (OS Build : 17672.1000)
Xamarin Version : 1.4 (master/b3f92f9)

Log File

Please add the following labels to the bug:
A11yMAS
Accessibility
Xamarin-Workbooks-Windows
Wipro
MAS4.3.1

Exemption Approved - 1813


Thanks for the great work

I am very excited about your work and its potential applications.  I have been following the multi-modal LLM space for a while and am glad to see things moving beyond images and text. I was really impressed by LLaVA and the recent Med-LLaVA work, but without modification  they are/we limited to images and single images at that. There have been a few publications related to generalized inputs and LLMs, but I have not seen much actionable code or models, so I was very happy to see your work.
Our primary interest is in the application of multi-modal models to medicine for research and academic purposes.  The inputs might be signal, tabular, image, multi-image, text, or other data.  The majority of our applications require several independent inputs, like a set of images, and potentially in-context learning where the output of the first request programmatically impacts the second and so on.  The Otter project (https://github.com/Luodian/Otter), which I am not associated with, has some interesting in-context features:.  A related project OtterHD (https://github.com/Luodian/Otter/blob/main/docs/OtterHD.md) allow for much larger image sizes than you would typically get with extracted image features.  The downside of these projects are that they seem to rely on specific models for both embeddings and the underlying LLM.
Being in an academic setting we have access to computational resources for training and testing.  I would be happy to contribute to your effort through model training and potentially code contributions.  I would especially be interested in training something for the new Mixtral dataset, which in our limited experience seem to work very well, with less computational requirements that a 70B model.
On a related note, the use of Lora adapters I think will be extremely important as modular inference engines are developed.  There are efforts underway on several projects to allow the run-time loading of adapters using the same based model, allowing potentially hundreds or thousands of models to be run from a single server.
I would be interested to hear your thoughts.

Hey, that sounds great and there's a ton of overlap here.
Assuming the independent inputs have some encoder (image = CLIP, text = some document embedding model or just dump in context, tabular (?), signal (?)) it should be very do-able to train a multi-domain, multi-input Mixtral.
The main limitations I mentioned in the post are datasets and compute. Do you have a specific dataset + set of modalities + model you are interested in?

On a related note, the use of Lora adapters I think will be extremely important as modular inference engines are developed.

Currently only set up to do LoRA-based LLM training so that works! Will also note that the library doesn't support multi-GPU training but this is potentially not a bottleneck unless the datasets are much larger (1M+) since LoRA and LMM projectors train fairly fast.

Sounds good. After the holidays I could create a quick script to format LLAVA-Med into the right format and send over the suggested training cli commands for you to try when you get a chance.
High level implementation is very similar to LLAVA which does support multi-gpu so definitely think it's do-able but would require some trial and error in multi-gpu/node environment.

It turns out that post-holiday commitments are more than expected. I won't be able to provide the preprocessing script but I am happy to provide any guidance or library debugging if you are still interested in using this for your work!


GD-246: Add error handler to catch push_error and script errors at test execution.

Currently GdUnit is not able to handle push_error or script errors at runtime (not debug mode), such tests end with success but should fail.
This is a major problem with the Godot API, which simply ignores such errors and continues execution.
Example Test-suite
# GdUnit generated TestSuite
#warning-ignore-all:unused_argument
#warning-ignore-all:return_value_discarded
class_name TestTest
extends GdUnitTestSuite

# TestSuite generated from
const __source = 'res://test.gd'

func test_with_script_errors() -> void:
	# this test should fail here because the Resource has no function `foo`
	Reference.new().foo()
	assert_str("abc").is_empty()

func test_with_push_errors() -> void:
	# this test should fail here because a `push_error` is used
	push_error("Test error push notification")
	assert_str("abc").is_empty()

When run this suite with "run" one test is passed but should be failed

The Godot.log shows
SCRIPT ERROR: TestTest.test_with_script_errors: Invalid call. Nonexistent function 'foo' in base 'Reference'.
          At: res://test_test/test_test.gd:13
ERROR: call: Test error push notification
   At: modules/gdscript/gdscript_functions.cpp:803

Describe the solution you'd like
GdUnit should report script errors and let test fail.

And optional/configuable failing for push_error.
Describe alternatives you've considered
There is no API on Godot at the moment to catch such errors.

Thanks for creating this. The optional flag is really important for me; I have lots of validation in my game code that my tests break (e.g. look for a player and find zero, or two) that call push_error. I would need this off for all my tests.

Thanks for creating this. The optional flag is really important for me; I have lots of validation in my game code that my tests break (e.g. look for a player and find zero, or two) that call push_error. I would need this off for all my tests.

Yes, that's the reason why I wanted to make it optional ;)

BTW you can join the GdUnit3 Discord server for direct comunication ;)

I'll keep that in mind for next time, thanks!


Implement BitIcon and UUIDIcon

BitIcon represents a 128bit as 8x8 grid 4 color icon
UUIDIcon represents a UUID as 8x8 grid 4 color icon

Codecov Report
Attention: Patch coverage is 0% with 44 lines in your changes missing coverage. Please review.

Project coverage is 66.75%. Comparing base (66ab840) to head (1852485).
Report is 1 commits behind head on main.

Files
Patch %
Lines

packages/biticon/src/base.tsx
0.00%
42 Missing :warning:

packages/biticon/src/bitShuffle.ts
0.00%
1 Missing :warning:

packages/biticon/src/colors.ts
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #438      +/-   ##
==========================================
- Coverage   70.43%   66.75%   -3.69%
==========================================
  Files          44       47       +3
  Lines        1502     1585      +83
  Branches      277      282       +5
==========================================
  Hits         1058     1058
- Misses        444      527      +83

Flag
Coverage Δ

unittests
66.75% <0.00%> (-3.69%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[6.0][Runtime] Don't attempt to look up prespecialized metadata involving pointers outside the shared cache.

Cherry-pick https://github.com/apple/swift/pull/72870 to release/6.0.
The descriptor and arguments for prespecialized metadata will always be in the shared cache. Skip creating the mangling for any lookup involving pointers outside the shared cache, as an optimization.
rdar://125974577

Explanation: Computing the mangled name for a prespecialized generic metadata request is somewhat expensive. This optimization avoids it altogether when the addresses of the descriptor or generic arguments mean we know for sure we won't find one anyway.
Original PR: https://github.com/apple/swift/pull/72870
Reviewed by: @al45tair
Risk: Low. The range checks are straightforward.
Resolves: rdar://125974577
Tests: Manual testing.

@swift-ci please test

@swift-ci Please test macOS platform

@swift-ci please test macos platform


Report excess property errors on object literal names

it's a spiritual follow-up to https://github.com/microsoft/TypeScript/pull/52943
the problem was noticed by @jakebailey here
Note that this is how it was already behaving in JSX so it unifies both paths, see the playground here

Love it! Are we missing any more cases? 😄

I plan to grep the test cases against all multi-line errors. I think that this should find all candidates for potential improvements - gonna categorize them and rethink if error spans can be improved for any of them.


feat: add parameter aggregation support for SSP

Types of changes

[ ] Hot fix (emergency fix and release)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Documentation (change which affects the documentation site)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Release (develop -> main)

Quality assurance (all should be covered).

[x] My code follows the code style of this project.
[x] Documentation for my change is up to date?
[x] My PR meets testing requirements.
[x] All new and existing tests passed.
[x] All commits are signed-off.

Summary
Closes #1596
I'm making this as a feature addition as we didn't initially considered this to be supported in SSP, just in profile.
Key links:

Sonar coverage

Before you merge

Ensure it is a 'squash commit' if not a release.
Ensure CI is currently passing
Check sonar. If you are working for a fork a maintainer will reach out, if required.

@vikas-agarwal76 could you confirm this as feature? I'm making this as a feature addition as we didn't initially considered this to be supported in SSP, just in profile.


Slow face detector

Hi!
I'm tried one of the python_examples: face_detector.py.
But i try to increase the number_of_times_to_upsample to 3:
detector(img, 3)
With this code change every photo take more than 8 seconds. The photo size is 1280X720 and i don't want to resize the photos.
i installed dlib with : pip install dlib
and also tried with: python setup.py install and all the instructions that defined in the main page:  https://github.com/davisking/dlib
I'm running the code on:
Intel Core i7-8750H 2.2GHz
Any suggestions how i can decrease running time? I don't want to rezise the photo because the camera is locate in big space and need to cover big space.
Thanks!

 It's going to be slow.


Test Ticket for Converting to Isse

Prevent Users from Committing directly to Main branch (including Administrators)

This is such a common issue that Github have made functionality to support this. See link below for instructions.
https://stackoverflow.com/questions/46146491/prevent-pushing-to-master-on-github

Instructions above followed.
Manual test confirm that a push with changes on main branch is prevented.
Pull request not tested yet.

https://github.com/cmtr/cmtr-static-public/pull/2

Successfully implemented rule


Russian language support for voice model Vosk-model-small-ru-0.22

Had to revert this change because it undid some of my OpenAI/Together changes in the webroot - you likely made your changes before I added my changes


angular 2.0 tutorial impossible on windows 10

I just started a new project and wanted to give angular2 a swing with meteor. Unfortunately my enthusiasm was swiftly met with disappointment when I learned that even the first angular 2 step in the tutorial stopped me in my tracks.
https://www.angular-meteor.com/tutorials/socially/angular2/bootstrapping
The command :
meteor npm install --save angular2-meteor @angular/platform-browser-dynamic
gives back this result:

npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Users\Daan\AppData\Local\.meteor\packages\meteor-tool\1.3.3\mt-os.windows.x86_32\dev_bundle\bin\\node.exe" "C:\Users\Daan\AppData\Local\.meteor\packages\meteor-tool\1.3.3\mt-os.windows.x86_32\dev_bundle\lib\node_modules\n
pm\bin\npm-cli.js" "install" "--save" "angular2-meteor" "@angular/platform-browser-dynamic"
npm ERR! node v0.10.45
npm ERR! npm  v2.15.1
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>
This is a fresh project.
I am using windows 10 with meteor <IP_ADDRESS>. I would use 1.3.3, but that version does not seem to work with windows 7 and 10 in its current state.
Thanks! :)

Hey Daan. You'd better post this in the angular2-meteor repo, mate :)

@pbastowski hey paul! fancy seeing you here ;-)
Thanks for the swift answer, Ill post it there then :+1:

@alberthoekstra https://github.com/Urigo/angular2-meteor/issues/301#issuecomment-226615592
Here you go m8 :)

the new fixes were released and tutorial was updated and deployed.
Please open another issue if it doesn't work for you


Technologies to use planning

Coming up with technologies to use as basic core for the application.
Using the Intervals API for the timer.
Passport for Authentication.

material-ui for now, may add animations library if needed

my bad, what we will be using is not the material-ui library, but the materialize library


[SPARK-36108][SQL] Refactor first set of 20 query parsing errors to use error classes

What changes were proposed in this pull request?
This PR refactor some exceptions in QueryParsingErrors to use error classes.
There are currently ~100 exceptions in this file; so this PR only focuses on the first set of 20.
Why are the changes needed?
To improve auditing, reduce duplication, and improve quality of error messages thrown from Spark, we should group them in a single JSON file (as discussed in the mailing list and introduced in SPARK-34920).
Does this PR introduce any user-facing change?
'No'.
Just use new error classes.
How was this patch tested?
Jenkins test.

Test build #141693 has started for PR 33535 at commit 32b28e0.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46207/

cc @karenfeng FYI

Test build #141695 has started for PR 33535 at commit 9aea3eb.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46207/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46209/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46207/

Test build #141693 has finished for PR 33535 at commit 32b28e0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141693/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46209/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46209/

Test build #141695 has finished for PR 33535 at commit 9aea3eb.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141695/

Test build #141771 has started for PR 33535 at commit 91d05b9.

Thanks for working on this! I left some suggestions to simplify the error classes. We should also make sure the SQLSTATEs match the ISO standard; if you're not sure what SQLSTATE fits, you can also leave it empty for now.

Can you tell me how to know the SQLSTATEs?

Test build #141772 has started for PR 33535 at commit 907e96d.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46284/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46285/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46285/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46284/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46284/

Test build #141771 has finished for PR 33535 at commit 91d05b9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141771/

Hi @beliefer! The SQLSTATEs are in the ISO standard, but it's behind a paywall. You can look at free resources like the Wikipedia article, or the Oracle or DB2 manuals (although they often define their own classes and subclasses). I'll push a PR soon with a summarized version of the ISO standards.

Test build #141772 has finished for PR 33535 at commit 907e96d.

This patch fails from timeout after a configured wait of 500m.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141772/

Test build #141803 has started for PR 33535 at commit b1f97b0.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46316/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46316/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46316/

Test build #141803 has finished for PR 33535 at commit b1f97b0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141803/

Test build #141812 has started for PR 33535 at commit f3380a5.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46325/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46325/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46325/

Test build #141812 has finished for PR 33535 at commit f3380a5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141812/

ping @karenfeng @HyukjinKwon Any other suggestion?

ping @HyukjinKwon too.

Test build #142018 has started for PR 33535 at commit 3971047.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46529/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46529/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46529/

Test build #142018 has finished for PR 33535 at commit 3971047.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142018/

Test build #142078 has started for PR 33535 at commit 86ea00d.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46591/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46591/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46591/

Test build #142078 has finished for PR 33535 at commit 86ea00d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142078/

@cloud-fan Could you help me to remove Stale label?


usb: usb_dc_nrfx: Remove dead code

Fix deadcode warning.
Signed-off-by: Andrei Emeltchenko<EMAIL_ADDRESS>

Codecov Report

Merging #11081 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11081   +/-   ##
=======================================
  Coverage    53.1%    53.1%
=======================================
  Files         218      218
  Lines       26853    26853
  Branches     5950     5950
=======================================
  Hits        14259    14259
  Misses      10162    10162
  Partials     2432     2432

Continue to review full report at Codecov.

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


Time-Sensitive TCP server

Hi,
I've got an explanation for this bug:
https://github.com/usedbytes/serial-flash/blob/51e30aae59cde7daa17cb43accabf6d1315964b8/main.go#L80
What happens:

Client connects
tcp_comm_client_init is called

the gpio led turns on https://github.com/usedbytes/picowota/blob/main/tcp_comm.c#L461
While communicating with the cyw43 to enable the led, network packages are discovered that need to be processed, incl. the initial opcode.
the recv-callback is not set yet, so the callback invocation is skipped

tcp_comm_client_init continues to set up callbacks, the initial data is lost.

A fix seems to be, that the gpio pin is not turned on directly inside an lwip callback, but dispatched to the main loop as an event.
In general the TCP implementation seems to be very sensitive to timing/packeting. Sending multiple commands at once or sending commands before having received the previous reply confuses the handling code, resulting in skipped data, or plain hangups. This is generally not expected from TCP peers.
Is it desired to make the tcp client more robust against this?

Sorry I missed this - thanks so much for your investigation! If you open a pull request I'd be happy to merge that in


chore: fetch invoices with non-zero amount only

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
9460

Relevant Lines:
96785

💛  - Coveralls


Add mqtt2prometheus push gateway to third party tools

Is this working off an existing standard way that someone would already would have things setup, or would they have to set all of the pushing to MQTT with such and such a topic name with specifically formatted data just to use this? What happens when a sensor stops publishing or no longer exists?
I'm concerned that this might be inventing a new way of doing things rather than building on what a user is likely to already have, in which case as per above using the Prometheus format would be better.

Also how does it compare to alternatives? I know there are multiple of the.

Hello,
thank you for your feedback. It was a design goal of mine to build the MQTT side of the gateway very generic. I had in mind a use case where the user of the MQTT gateway can not change exiting IoT devices. The feedback I got via PRs and issues reflect just that. For example: https://github.com/hikhvar/mqtt2prometheus/pull/9.  I assume they send (at the moment JSON) payload to certain topics. I did not implement any specific sensoring protocoll based on MQTT. For that use case, there should be a dedicated exporter. @roidelapluie that distinct my gateways from alternatives like

https://github.com/tg44/mqtt-prometheus-message-exporter
https://github.com/inuits/mqttgateway

What happens when a sensor stops publishing or no longer exists?

At the moment the exporter caches the ingested metrics for a configurable time. If there is no update during the cache time, the exporter discard the value and do not present it anymore. I work on a solution using timestamps.

Thanks for the explanation, this sounds like this is trying to work with what exists rather than inventing a whole new thing. The inuits one seems to require devices to be coded for it. The tg44 is more generic, however also appears to include an entire bespoke client library which is a bit odd, and has a smaller community. Accordingly I'd be tending towards this one.
The readme indicates that this is an analog of the pushgateway. This is in fact explicitly not the sort of use case that pushgateway is for. Can you correct this please? The text in this PR should also only be the exporter name.
This should probably go up in messaging systems.
In terms of general comments to help you improve your exporter it'd be good if your temperature examples included _celsius as a suffix on the metric name. Your default port number is outside of https://github.com/prometheus/prometheus/wiki/Default-port-allocations, so presuming there's not some technical consideration I'm missing I'd suggest changing it. const_labels is a bit odd, for the given example I'd expect that to be part of the metric name. I'd also suggest looking at the other two exporters, as they do have ideas that'd be good to incorporate into one really good exporter (inuit's metric for last push timestamp, tg44's topic name label extraction).

hikhvar/mqtt2prometheus#9

As an aside, if that ends up not being sophisticated enough you should take a look at how the JMX and SNMP exporters approach this. Given it's JSON hopefully you can avoid that level of complexity though.

Thanks!


Can't match any files

What's going on here? The files obviously exist.

Oh, I didn't realize those were folders, not files. Never mind


apk builds on cloud for android fails

Problem description
My builds for android in cloudservice doesnt work. The last one three days ago was working. I tried it also with another version that was definitly working.
ios, by the way, is working.
I tried it with two different apps. Both went into the same error.
It seems like something went wrong with gradle.
Expected behavior
Build the apk ;)
Environment

Tabris.js version: 3.8.0

Snippet from detail log where it fails
Welcome to Gradle 6.5!
Here are the highlights of this release:
 - Experimental file-system watching
 - Improved version ordering
 - New samples
For more details see https://docs.gradle.org/6.5/release-notes.html
To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/6.5/userguide/gradle_daemon.html.
Daemon will be stopped at the end of the build stopping after processing
> Configure project :app
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.
FAILURE: Build failed with an exception.
* What went wrong:
Could not determine the dependencies of task ':CordovaLib:compileDebugAidl'.
> Could not resolve all task dependencies for configuration ':CordovaLib:debugCompileClasspath'.
   > Could not resolve org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.4.32.
     Required by:
         project :CordovaLib
      > Skipped due to earlier error
      > Skipped due to earlier error
   > Could not resolve com.eclipsesource.j2v8:j2v8:6.2.1.
     Required by:
         project :CordovaLib > com.eclipsesource.tabris.android:tabris:3.8.0
      > Skipped due to earlier error
      > Skipped due to earlier error
   > Could not resolve org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.5.21.
     Required by:
         project :CordovaLib > com.eclipsesource.tabris.android:tabris:3.8.0
      > Skipped due to earlier error
      > Skipped due to earlier error
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 3m 43s
Command failed with exit code 1: /home/travis/build/eclipsesource/tabris-js-build-template/build/build/cordova/platforms/android/gradlew cdvBuildDebug -b /home/travis/build/eclipsesource/tabris-js-build-template/build/build/cordova/platforms/android/build.gradle
Error: Command failed with exit code 1: /home/travis/build/eclipsesource/tabris-js-build-template/build/build/cordova/platforms/android/gradlew cdvBuildDebug -b /home/travis/build/eclipsesource/tabris-js-build-template/build/build/cordova/platforms/android/build.gradle
    at makeError (/home/travis/build/eclipsesource/tabris-js-build-template/build/build/cordova/platforms/android/cordova/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/home/travis/build/eclipsesource/tabris-js-build-template/build/build/cordova/platforms/android/cordova/node_modules/execa/index.js:114:26)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
The command /home/travis/.tabris-cli/cordova/9.0.0/node_modules/.bin/cordova exited with 1

This looks like it could be related to a maven central outage. Could you try again?

Works now, thank you 👍


install and build instructions

Hi again,
Should be great if you add some hints related to install and build.
ty !

Closed as duplicate, see https://github.com/PetrosiliusPatter/ingooutgo/issues/1#issuecomment-1813234053


Fix macOS and Windows build with statically linked ANGLE/EGL.

Fixes macOS and Windows build after https://github.com/godotengine/godot/pull/83930, static ANGLE always include EGL 1.5 and does not use GLAD to load it therefore GLAD_EGL_VERSION_1_5 is undefined.

Thanks!


Restore logging of rules updates

This got put down to Debug in #719, and I missed it on review.

Oh, shoot, sorry about that. Got overzealous with my replacements!


Added the code for firebasae login

This is i regard to #301.
I request @AmeyaJain-25 sir to please review my work and give your valuable feedback.

@ritik-vashist why have you commented the code?

@ChitvanRamani22  ma'am because as per the present code we are passing the token from backend to frontend but the code has not been designed to handle bearer token so as per talks between @AmeyaJain-25 sir and @Tejas1510 sir they suggested me to do this in this issue and work on the rest part latter.

Bearer token means the token which is generated by firebase-admin for the user.

@ritik-vashist why have you commented the code?

Yes @ChitvanRamani22 ,
I and @Tejas1510 sir had a talk about this.
If we use firebase, then we need to shift completely over there. And for right now, we shouldn't, because other participants may get confused and not understand.
So, the functionality is written properly by Ritik, only the thing is that it's commented so that when we shift to firebase, we can uncomment and re work on it

@AmeyaJain-25 okay fine...
Great work @ritik-vashist !

Thank you @ChitvanRamani22 ma'am.


Fix for issue 622 and prevent to remove placeholder if out of bound.

Fix for issue #622.
I have removed checking for 'outOfBound' condition, because it was causing a problem when dragging an element outside of ui-tree.

@namerci can you rebase this branch please to fix merge conflicts?


Can't delete messages when bot has admin privileges

Description
Trying to use chat.delete on another users post does not work through a bot with admin privileges. If I create a legacy api token with my account (an admin account) and use it to create the slackclient instance, I can use chat.delete on the same timestamp successfully. No matter the scope permissions I give to the app, the token does not let me delete the timestamp and gives me a "cant_delete_message" error.
What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
slackclient version: 1.0.6
python version: 2.7.3
OS version(s): MATE 1.12.1
Steps to reproduce:

Add an app integration, give it chat:write permissions and admin permissions
Get a timestamp of another user post
Attempt to delete the post with the slackclient made from the app integration token.

Expected result:
Deletion should work successfully since it is an admin integration.
Actual result:
"cant_delete_message" response given

hi @brubakbd!
it turns out that you can't do this with a bot token, its not meant to have any admin privileges! but you can do this with a user token (xoxp-...). don't worry about the admin scope, that's not what its for. just obtain a user token for a user who is an admin on the team. feel free to ask further questions, but i'm closing the issue because its not specific to the python SDK.


bug: Failed to generate outputs

Get assertion error with https://github.com/kharvd/gpt-cli
Traceback (most recent call last):
  File "/home/gaocegege/applications/miniconda3/envs/dev/bin/gpt", line 8, in <module>
    sys.exit(main())
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/gpt.py", line 189, in main
    run_interactive(args, assistant)
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/gpt.py", line 237, in run_interactive
    session.loop(input_provider)
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/session.py", line 183, in loop
    while self.process_input(*input_provider.get_user_input()):
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/session.py", line 175, in process_input
    response_saved = self._respond(args)
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/session.py", line 109, in _respond
    for response in completion_iter:
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/openai.py", line 20, in complete
    openai.ChatCompletion.create(
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/openai/api_resources/chat_completion.py", line 25, in create
    return super().create(*args, **kwargs)
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/openai/api_resources/abstract/engine_api_resource.py", line 165, in create
    assert not isinstance(response, OpenAIResponse)
AssertionError
An uncaught exception occurred. Please report this issue on GitHub.
Traceback (most recent call last):
  File "/home/gaocegege/applications/miniconda3/envs/dev/bin/gpt", line 8, in <module>
    sys.exit(main())
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/gpt.py", line 189, in main
    run_interactive(args, assistant)
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/gpt.py", line 237, in run_interactive
    session.loop(input_provider)
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/session.py", line 183, in loop
    while self.process_input(*input_provider.get_user_input()):
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/session.py", line 175, in process_input
    response_saved = self._respond(args)
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/session.py", line 109, in _respond
    for response in completion_iter:
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/gptcli/openai.py", line 20, in complete
    openai.ChatCompletion.create(
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/openai/api_resources/chat_completion.py", line 25, in create
    return super().create(*args, **kwargs)
  File "/home/gaocegege/applications/miniconda3/envs/dev/lib/python3.9/site-packages/openai/api_resources/abstract/engine_api_resource.py", line 165, in create
    assert not isinstance(response, OpenAIResponse)
AssertionError

The server actually generated the output:
2023-08-02T16:31:53.058244518+08:00 stderr F 2023-08-02 08:31:53,058 - 1 - INFO - falcon_service.py:46 - ChatResponse(id='2bfbb49d-3d5b-4333-adfe-93531fd70b5f', object='chat', created=datetime.datetime(2023, 8, 2, 8, 31, 52, 982729), model='bigscience/bloomz-560m', usage=TokenUsage(prompt_tokens=11, completion_tokens=8, total_tokens=19), choices=[ChatChoice(message=ChatMessage(content='ive been working for you for a while', role=<Role.ASSISTANT: 'assistant'>, name=''), index=0, finish_reason='stop')])

/assign @kemingy


must-gather: collect journal and kernel logs for all nodes

This commit collects the journal and kernel logs
seperately according to the nodes.
Signed-off-by: yati1998<EMAIL_ADDRESS>

@idryomov can you please review again.

with the pids in same same array, the journal logs collection is not reached.

What do you mean by "not reached"?

That I think can be due to reached limit and hence can't accumulate more pids and resulting in not executing the journal collection part. With this change in new array for journal log, this is resolved.

What limit do you have in mind?  The number of PIDs is definitely not the issue here because the new code spawns the same number of processes.  The only difference is that one of the returned PIDs is put into a separate array.

A ton of improvements could be made here but, considered purely as a fix for journal.gz and kernel.gz getting overwritten when there is more than one node, LGTM!

yeah sure, will check that and send subsequent PRs.

/lgtm

/cherry-pick release-4.12


Granular versioning for Guides

Record each draft save/publication as a separate edition.
Whenever changes are made, create a new guide edition. We used to do that for
currently published guides, but not for guides in draft state. Recording each
edition save aligns us with the Performance Platform team (responsible for
publishing-api) future plans for versioning. It also gives us better
accountability tracking as author of each change is now recorder.
Note that I opted to "clone" the previous edition before applying attributes
sent from the form. This is to ensure that we will not loose any data if it is
not passed from the form due to any potential changes in future.
This PR does not deal with versioning and optimistic-locking as the publishing-api changes to deal with that are still in development. We'll need to update this process a bit once the mentioned changes go live.
This PR also adds a minimalistic view for Guide history with aim to make it easier to demo, develop and design upcoming features.

Thanks for looking at it :)


Error handling when trying to load template that doesn't exist

Currently, trying to load a template that doesn't exist using load_template causes an unhandled KeyError exception.

This causes test_load_template_not_found to fail due to the KeyError.


Default empty Arrays

What do you think about using [] as a "default" array value and allowing the key to be missing when parsing?  (or maybe even empty or mempty for any valid types)
Not sure if this has drawbacks I'm not thinking of, but it'd sure be nice to get rid of a bunch of my Maybe (Array a) fields.  Nothing and [] are kind of the same thing 🙂

Why not simply use Array a and live with the serialised key=[]?

Nothing and [] are kind of the same thing

😱
nononooooonoo. Especially in decoding you don't want your parser to make these implicit assumptions. One common situation I can think of is an API call querying a collection.
Now (1) null might mean the collection didn't exist, whereas (2) an empty Array means it's empty. That's a very different thing though. 1) means a programmer error, and 2) means the user should populate it with some data.

I think in this case, having readJSON read from an input and then applying a series of replace functions (get a property by key, delete that property, insert a new property with the type you want) should work right? Since the key :: Maybe a -> key :: a transformations will provide the types there and your end result being some concrete type of a record should work?
e.g.
import Data.Nullable (toMaybe)

type MyThing =
  { a :: String
  , b :: Array String
  }

json = """
  { "a": "sedf", "b": null }
"""

parse :: String -> E MyThing
parse str = replace (SProxy :: SProxy "b") (fromMaybe [] <<< toMaybe) <$> readJSON str

or something like that?

Nothing and [] are kind of the same thing

Probably works if you only use NonEmpty Array everywhere, but not entirely sure if that's what you want in your codebase either

@jacereda Sorry, only referring to deserialization.
You're probably right.. unfortunately C# is really loose with nullability so I have a bunch of apis to work with which like to leave off arrays when they're empty, so I'll probably need to write custom ReadForeign implementations for those records.

Gist example for those reading this thread later: https://gist.github.com/justinwoo/9d0bb67a84c227f327da7171bb7105c2

Is the toMaybe necessary?  Or does the Maybe instance distinguish between missing and null?

the Maybe instance is just a hack and shouldn't be relied on at all. As noted in https://github.com/justinwoo/purescript-simple-json#warning-maybe

Seems clear enough.. are you suggesting it shouldn't be used?

Yeah, mostly just shouldn't be used unless you're willing to lock down versions of simple-json (which is the easy part if you use psc-package I guess) and read all the release notes to make sure the behavior wasn't changed again


Cheat will not build, I have Clang compiler but am having an issue with building

[!WARNING]
Download Vcpkg, integrate him and download MinHoook as Static Library