fix missing descriptions - batch 8

@MandiOhlinger @MightyPen batch 8

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

File
Status
Preview URL
Details

his/core/sql-server-replication-troubleshooting-1.md
:warning:Warning
View
Details

his/core/lu-pools-3270-1.md
:bulb:Suggestion
View
Details

his/core/lu-pools1.md
:bulb:Suggestion
View
Details

his/core/lus-and-sessions2.md
:bulb:Suggestion
View
Details

[his/core/lustats]1.md](https://github.com/v-kents/biztalk-docs/blob/fix-missing-desc-08/his/core/lustats]1.md)
:bulb:Suggestion
View
Details

his/core/mainframe-connection-summary1.md
:bulb:Suggestion
View
Details

his/core/mainframe-printing1.md
:bulb:Suggestion
View
Details

his/core/major-elements-affecting-overall-performance1.md
:bulb:Suggestion
View
Details

his/core/management-services-information2.md
:bulb:Suggestion
View
Details

his/core/mode-definition-information1.md
:bulb:Suggestion
View
Details

his/core/mssna-printsession-class2.md
:bulb:Suggestion
View
Details

his/core/named-pipes-clients2.md
:bulb:Suggestion
View
Details

his/core/negotiable-link-roles1.md
:bulb:Suggestion
View
Details

his/core/network-integration-configuration-1.md
:bulb:Suggestion
View
Details

his/core/node-identification-and-signaling-information2.md
:bulb:Suggestion
View
Details

his/core/objects.md
:bulb:Suggestion
View
Details

his/core/objects1.md
:bulb:Suggestion
View
Details

his/core/ole-db-provider-for-db2.md
:bulb:Suggestion
View
Details

his/core/opening-the-linlpi-connection2.md
:bulb:Suggestion
View
Details

his/core/opening-the-plu-connection1.md
:bulb:Suggestion
View
Details

his/core/opening-the-sscp-connection1.md
:bulb:Suggestion
View
Details

his/core/os-400-distributed-program-calls1.md
:bulb:Suggestion
View
Details

his/core/outages-snadis-2.md
:bulb:Suggestion
View
Details

his/core/outbound-chaining2.md
:bulb:Suggestion
View
Details

his/core/outbound-data1.md
:bulb:Suggestion
View
Details

his/core/outbound-pacing1.md
:bulb:Suggestion
View
Details

his/core/overview-of-message-formats-snadis-1.md
:bulb:Suggestion
View
Details

his/core/overview-of-message-formats1.md
:bulb:Suggestion
View
Details

his/core/overview-of-snalink1.md
:bulb:Suggestion
View
Details

his/core/package-xml-schema-v90.md
:bulb:Suggestion
View
Details

his/core/password-synchronization1.md
:bulb:Suggestion
View
Details

his/core/paths-and-dmods-snadis-1.md
:bulb:Suggestion
View
Details

his/core/paths-and-dmods2.md
:bulb:Suggestion
View
Details

his/core/performance2.md
:bulb:Suggestion
View
Details

his/core/planning-and-architecting-solutions-using-data-clients.md
:bulb:Suggestion
View
Details

his/core/planning-and-architecting-solutions-using-microsoft-service-for-drda.md
:bulb:Suggestion
View
Details

his/core/protection2.md
:bulb:Suggestion
View
Details

his/core/providing-hot-backup-and-load-balancing-3270-1.md
:bulb:Suggestion
View
Details

his/core/quiesce1.md
:bulb:Suggestion
View
Details

his/core/receiving-messages1.md
:bulb:Suggestion
View
Details

his/core/record-level-input-output-rlio-protocol-errors1.md
:bulb:Suggestion
View
Details

his/core/remote-environments1.md
:bulb:Suggestion
View
Details

his/core/resource-location-for-open-sscp2.md
:bulb:Suggestion
View
Details

his/core/rqr-and-clear1.md
:bulb:Suggestion
View
Details

his/core/sdlc-link-statistics1.md
:bulb:Suggestion
View
Details

his/core/sdlc-multipoint-connections1.md
:bulb:Suggestion
View
Details

his/core/secondary-appc-return-codes2.md
:bulb:Suggestion
View
Details

his/core/security1.md
:bulb:Suggestion
View
Details

his/core/session-information1.md
:bulb:Suggestion
View
Details

his/core/sessions-and-connections2.md
:bulb:Suggestion
View
Details

This comment lists only the first 50 files in the pull request.

his/core/sql-server-replication-troubleshooting-1.md

Line 25, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=193231' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 36, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkID=180765)' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 36, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkID=180765' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 149, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=193232' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 69, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 114, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 128, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 164, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/sql/relational-databases/system-stored-procedures/sp-addarticle-transact-sql?view=sql-server-2017

his/core/lu-pools-3270-1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln02.gif'. Alt text is required for accessibility.

his/core/lu-pools1.md

Line 22, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln13.gif'. Alt text is required for accessibility.

his/core/lus-and-sessions2.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/lua1a.gif'. Alt text is required for accessibility.

[his/core/lustats]1.md](https://github.com/v-kents/biztalk-docs/blob/fix-missing-desc-08/his/core/lustats]1.md)

Line 34, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703v.gif'. Alt text is required for accessibility.
Line 39, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703va.gif'. Alt text is required for accessibility.
Line 44, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703vb.gif'. Alt text is required for accessibility.

his/core/mainframe-connection-summary1.md

Line 22, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dep06.gif'. Alt text is required for accessibility.

his/core/mainframe-printing1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/prn01.gif'. Alt text is required for accessibility.

his/core/major-elements-affecting-overall-performance1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-ti25.gif'. Alt text is required for accessibility.

his/core/management-services-information2.md

Line 20, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Syntax''. Each second level heading (H2) in an article must be unique.
Line 36, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.
Line 66, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Syntax''. Each second level heading (H2) in an article must be unique.
Line 83, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.

his/core/mode-definition-information1.md

Line 22, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.
Line 28, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.

his/core/mssna-printsession-class2.md

Line 248, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/named-pipes-clients2.md

Line 18, Column 1: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/ref11.gif'. Alt text is required for accessibility.

his/core/negotiable-link-roles1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3e.gif'. Alt text is required for accessibility.
Line 24, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 52, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/network-integration-configuration-1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Configure Network Integration' is duplicated with other articles: 'core/network-integration-configuration-1.md(17,1), install-and-config-guides/configuration-of-network-integration2.md(16,1)'. First level headings must be unique within a docset.

his/core/node-identification-and-signaling-information2.md

Line 34, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3f.gif'. Alt text is required for accessibility.

his/core/objects.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Objects' is duplicated in 'core/objects.md(2,14)', 'core/objects1.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Objects' is duplicated with other articles: 'core/objects.md(17,1), core/objects1.md(17,1), core/wipobjects.md(16,1)'. First level headings must be unique within a docset.

his/core/objects1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Objects' is duplicated in 'core/objects.md(2,14)', 'core/objects1.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Objects' is duplicated with other articles: 'core/objects.md(17,1), core/objects1.md(17,1), core/wipobjects.md(16,1)'. First level headings must be unique within a docset.

his/core/ole-db-provider-for-db2.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'OLE DB Provider for DB2' is duplicated with other articles: 'core/ole-db-provider-for-db2.md(17,1), db2oledbv/microsoft-ole-db-provider-for-db2.md(16,1)'. First level headings must be unique within a docset.

his/core/opening-the-linlpi-connection2.md

Line 78, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3a.gif'. Alt text is required for accessibility.

his/core/opening-the-plu-connection1.md

Line 34, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703f.gif'. Alt text is required for accessibility.
Line 41, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703fa.gif'. Alt text is required for accessibility.

his/core/opening-the-sscp-connection1.md

Line 22, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703c.gif'. Alt text is required for accessibility.

his/core/os-400-distributed-program-calls1.md

Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-ti12.gif'. Alt text is required for accessibility.

his/core/outages-snadis-2.md

Line 30, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3p.gif'. Alt text is required for accessibility.

his/core/outbound-chaining2.md

Line 52, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703i.gif'. Alt text is required for accessibility.
Line 57, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703ia.gif'. Alt text is required for accessibility.
Line 62, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703ib.gif'. Alt text is required for accessibility.
Line 67, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703ic.gif'. Alt text is required for accessibility.

his/core/outbound-data1.md

Line 92, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703w.gif'. Alt text is required for accessibility.
Line 97, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703wa.gif'. Alt text is required for accessibility.
Line 102, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703wb.gif'. Alt text is required for accessibility.
Line 107, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703wc.gif'. Alt text is required for accessibility.
Line 112, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703wd.gif'. Alt text is required for accessibility.
Line 117, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703we.gif'. Alt text is required for accessibility.

his/core/outbound-pacing1.md

Line 48, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703o.gif'. Alt text is required for accessibility.
Line 53, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703oa.gif'. Alt text is required for accessibility.

his/core/overview-of-message-formats-snadis-1.md

Line 30, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-dev1d.gif'. Alt text is required for accessibility.

his/core/overview-of-message-formats1.md

Line 30, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-dev1d.gif'. Alt text is required for accessibility.

his/core/overview-of-snalink1.md

Line 22, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703b.gif'. Alt text is required for accessibility.

his/core/package-xml-schema-v90.md

Line 347, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 364, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 391, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 406, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 439, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 459, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 470, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 480, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 491, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 646, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 669, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/password-synchronization1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Password Synchronization' is duplicated with other articles: 'core/password-synchronization1.md(17,1), esso/password-synchronization3.md(16,1)'. First level headings must be unique within a docset.

his/core/paths-and-dmods-snadis-1.md

Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32701c.gif'. Alt text is required for accessibility.

his/core/paths-and-dmods2.md

Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32701c.gif'. Alt text is required for accessibility.

his/core/performance2.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Performance' is duplicated with other articles: 'core/performance2.md(17,1), db2oledbv/performance1.md(16,1)'. First level headings must be unique within a docset.

his/core/planning-and-architecting-solutions-using-data-clients.md

Line 29, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 64, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 126, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/planning-and-architecting-solutions-using-microsoft-service-for-drda.md

Line 159, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/protection2.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Protection' is duplicated with other articles: 'core/protection2.md(17,1), db2oledbv/protection1.md(16,1)'. First level headings must be unique within a docset.

his/core/providing-hot-backup-and-load-balancing-3270-1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln03.gif'. Alt text is required for accessibility.

his/core/quiesce1.md

Line 34, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703s.gif'. Alt text is required for accessibility.
Line 39, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703sa.gif'. Alt text is required for accessibility.
Line 44, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703sb.gif'. Alt text is required for accessibility.

his/core/receiving-messages1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32702a.gif'. Alt text is required for accessibility.

his/core/record-level-input-output-rlio-protocol-errors1.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/remote-environments1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Remote Environments' is duplicated with other articles: 'core/remote-environments1.md(17,1), core/wipremoteenvs.md(16,1)'. First level headings must be unique within a docset.

his/core/resource-location-for-open-sscp2.md

Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703d.gif'. Alt text is required for accessibility.

his/core/rqr-and-clear1.md

Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703t.gif'. Alt text is required for accessibility.

his/core/sdlc-link-statistics1.md

Line 22, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 26, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 31, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 48, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/sdlc-multipoint-connections1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3t.gif'. Alt text is required for accessibility.
Line 49, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3u.gif'. Alt text is required for accessibility.
Line 52, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3y.gif'. Alt text is required for accessibility.

his/core/secondary-appc-return-codes2.md

Line 64, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 '000000D7''. Each second level heading (H2) in an article must be unique.
Line 179, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 '000000D7''. Each second level heading (H2) in an article must be unique.
Line 249, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 '00000156''. Each second level heading (H2) in an article must be unique.
Line 253, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 '00000156''. Each second level heading (H2) in an article must be unique.

his/core/security1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Security' is duplicated with other articles: 'core/security1.md(17,1), db2oledbv/security2.md(16,1)'. First level headings must be unique within a docset.

his/core/session-information1.md

Line 20, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Syntax''. Each second level heading (H2) in an article must be unique.
Line 30, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.
Line 42, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Syntax''. Each second level heading (H2) in an article must be unique.
Line 75, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.
Line 162, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.

his/core/sessions-and-connections2.md

Line 30, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703b.gif'. Alt text is required for accessibility.
Line 43, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703ba.gif'. Alt text is required for accessibility.

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

his/core/sql-server-replication-troubleshooting-1.md
:warning:Warning
View
Details

his/core/lu-pools-3270-1.md
:bulb:Suggestion
View
Details

his/core/lu-pools1.md
:bulb:Suggestion
View
Details

his/core/lus-and-sessions2.md
:bulb:Suggestion
View
Details

[his/core/lustats]1.md](https://github.com/v-kents/biztalk-docs/blob/fix-missing-desc-08/his/core/lustats]1.md)
:bulb:Suggestion
View
Details

his/core/mainframe-connection-summary1.md
:bulb:Suggestion
View
Details

his/core/mainframe-printing1.md
:bulb:Suggestion
View
Details

his/core/major-elements-affecting-overall-performance1.md
:bulb:Suggestion
View
Details

his/core/management-services-information2.md
:bulb:Suggestion
View
Details

his/core/mode-definition-information1.md
:bulb:Suggestion
View
Details

his/core/mssna-printsession-class2.md
:bulb:Suggestion
View
Details

his/core/named-pipes-clients2.md
:bulb:Suggestion
View
Details

his/core/negotiable-link-roles1.md
:bulb:Suggestion
View
Details

his/core/network-integration-configuration-1.md
:bulb:Suggestion
View
Details

his/core/node-identification-and-signaling-information2.md
:bulb:Suggestion
View
Details

his/core/objects.md
:bulb:Suggestion
View
Details

his/core/objects1.md
:bulb:Suggestion
View
Details

his/core/ole-db-provider-for-db2.md
:bulb:Suggestion
View
Details

his/core/opening-the-linlpi-connection2.md
:bulb:Suggestion
View
Details

his/core/opening-the-plu-connection1.md
:bulb:Suggestion
View
Details

his/core/opening-the-sscp-connection1.md
:bulb:Suggestion
View
Details

his/core/os-400-distributed-program-calls1.md
:bulb:Suggestion
View
Details

his/core/outages-snadis-2.md
:bulb:Suggestion
View
Details

his/core/outbound-chaining2.md
:bulb:Suggestion
View
Details

his/core/outbound-data1.md
:bulb:Suggestion
View
Details

his/core/outbound-pacing1.md
:bulb:Suggestion
View
Details

his/core/overview-of-message-formats-snadis-1.md
:bulb:Suggestion
View
Details

his/core/overview-of-message-formats1.md
:bulb:Suggestion
View
Details

his/core/overview-of-snalink1.md
:bulb:Suggestion
View
Details

his/core/package-xml-schema-v90.md
:bulb:Suggestion
View
Details

his/core/password-synchronization1.md
:bulb:Suggestion
View
Details

his/core/paths-and-dmods-snadis-1.md
:bulb:Suggestion
View
Details

his/core/paths-and-dmods2.md
:bulb:Suggestion
View
Details

his/core/performance2.md
:bulb:Suggestion
View
Details

his/core/planning-and-architecting-solutions-using-data-clients.md
:bulb:Suggestion
View
Details

his/core/planning-and-architecting-solutions-using-microsoft-service-for-drda.md
:bulb:Suggestion
View
Details

his/core/protection2.md
:bulb:Suggestion
View
Details

his/core/providing-hot-backup-and-load-balancing-3270-1.md
:bulb:Suggestion
View
Details

his/core/quiesce1.md
:bulb:Suggestion
View
Details

his/core/receiving-messages1.md
:bulb:Suggestion
View
Details

his/core/record-level-input-output-rlio-protocol-errors1.md
:bulb:Suggestion
View
Details

his/core/remote-environments1.md
:bulb:Suggestion
View
Details

his/core/resource-location-for-open-sscp2.md
:bulb:Suggestion
View
Details

his/core/rqr-and-clear1.md
:bulb:Suggestion
View
Details

his/core/sdlc-link-statistics1.md
:bulb:Suggestion
View
Details

his/core/sdlc-multipoint-connections1.md
:bulb:Suggestion
View
Details

his/core/secondary-appc-return-codes2.md
:bulb:Suggestion
View
Details

his/core/security1.md
:bulb:Suggestion
View
Details

his/core/session-information1.md
:bulb:Suggestion
View
Details

his/core/sessions-and-connections2.md
:bulb:Suggestion
View
Details

This comment lists only the first 50 files in the pull request.

his/core/sql-server-replication-troubleshooting-1.md

Line 25, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=193231' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 36, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkID=180765)' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 36, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkID=180765' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 149, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=193232' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 69, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 114, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 128, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 164, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/sql/relational-databases/system-stored-procedures/sp-addarticle-transact-sql?view=sql-server-2017

his/core/lu-pools-3270-1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln02.gif'. Alt text is required for accessibility.

his/core/lu-pools1.md

Line 22, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln13.gif'. Alt text is required for accessibility.

his/core/lus-and-sessions2.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/lua1a.gif'. Alt text is required for accessibility.

[his/core/lustats]1.md](https://github.com/v-kents/biztalk-docs/blob/fix-missing-desc-08/his/core/lustats]1.md)

Line 34, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703v.gif'. Alt text is required for accessibility.
Line 39, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703va.gif'. Alt text is required for accessibility.
Line 44, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703vb.gif'. Alt text is required for accessibility.

his/core/mainframe-connection-summary1.md

Line 22, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dep06.gif'. Alt text is required for accessibility.

his/core/mainframe-printing1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/prn01.gif'. Alt text is required for accessibility.

his/core/major-elements-affecting-overall-performance1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-ti25.gif'. Alt text is required for accessibility.

his/core/management-services-information2.md

Line 20, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Syntax''. Each second level heading (H2) in an article must be unique.
Line 36, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.
Line 66, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Syntax''. Each second level heading (H2) in an article must be unique.
Line 83, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.

his/core/mode-definition-information1.md

Line 22, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.
Line 28, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.

his/core/mssna-printsession-class2.md

Line 248, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/named-pipes-clients2.md

Line 18, Column 1: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/ref11.gif'. Alt text is required for accessibility.

his/core/negotiable-link-roles1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3e.gif'. Alt text is required for accessibility.
Line 24, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 52, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/network-integration-configuration-1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Configure Network Integration' is duplicated with other articles: 'core/network-integration-configuration-1.md(17,1), install-and-config-guides/configuration-of-network-integration2.md(16,1)'. First level headings must be unique within a docset.

his/core/node-identification-and-signaling-information2.md

Line 34, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3f.gif'. Alt text is required for accessibility.

his/core/objects.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Objects' is duplicated in 'core/objects.md(2,14)', 'core/objects1.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Objects' is duplicated with other articles: 'core/objects.md(17,1), core/objects1.md(17,1), core/wipobjects.md(16,1)'. First level headings must be unique within a docset.

his/core/objects1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Objects' is duplicated in 'core/objects.md(2,14)', 'core/objects1.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Objects' is duplicated with other articles: 'core/objects.md(17,1), core/objects1.md(17,1), core/wipobjects.md(16,1)'. First level headings must be unique within a docset.

his/core/ole-db-provider-for-db2.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'OLE DB Provider for DB2' is duplicated with other articles: 'core/ole-db-provider-for-db2.md(17,1), db2oledbv/microsoft-ole-db-provider-for-db2.md(16,1)'. First level headings must be unique within a docset.

his/core/opening-the-linlpi-connection2.md

Line 78, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3a.gif'. Alt text is required for accessibility.

his/core/opening-the-plu-connection1.md

Line 34, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703f.gif'. Alt text is required for accessibility.
Line 41, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703fa.gif'. Alt text is required for accessibility.

his/core/opening-the-sscp-connection1.md

Line 22, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703c.gif'. Alt text is required for accessibility.

his/core/os-400-distributed-program-calls1.md

Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-ti12.gif'. Alt text is required for accessibility.

his/core/outages-snadis-2.md

Line 30, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3p.gif'. Alt text is required for accessibility.

his/core/outbound-chaining2.md

Line 52, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703i.gif'. Alt text is required for accessibility.
Line 57, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703ia.gif'. Alt text is required for accessibility.
Line 62, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703ib.gif'. Alt text is required for accessibility.
Line 67, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703ic.gif'. Alt text is required for accessibility.

his/core/outbound-data1.md

Line 92, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703w.gif'. Alt text is required for accessibility.
Line 97, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703wa.gif'. Alt text is required for accessibility.
Line 102, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703wb.gif'. Alt text is required for accessibility.
Line 107, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703wc.gif'. Alt text is required for accessibility.
Line 112, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703wd.gif'. Alt text is required for accessibility.
Line 117, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703we.gif'. Alt text is required for accessibility.

his/core/outbound-pacing1.md

Line 48, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703o.gif'. Alt text is required for accessibility.
Line 53, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703oa.gif'. Alt text is required for accessibility.

his/core/overview-of-message-formats-snadis-1.md

Line 30, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-dev1d.gif'. Alt text is required for accessibility.

his/core/overview-of-message-formats1.md

Line 30, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-dev1d.gif'. Alt text is required for accessibility.

his/core/overview-of-snalink1.md

Line 22, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703b.gif'. Alt text is required for accessibility.

his/core/package-xml-schema-v90.md

Line 347, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 364, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 391, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 406, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 439, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 459, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 470, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 480, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 491, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 646, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 669, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/password-synchronization1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Password Synchronization' is duplicated with other articles: 'core/password-synchronization1.md(17,1), esso/password-synchronization3.md(16,1)'. First level headings must be unique within a docset.

his/core/paths-and-dmods-snadis-1.md

Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32701c.gif'. Alt text is required for accessibility.

his/core/paths-and-dmods2.md

Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32701c.gif'. Alt text is required for accessibility.

his/core/performance2.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Performance' is duplicated with other articles: 'core/performance2.md(17,1), db2oledbv/performance1.md(16,1)'. First level headings must be unique within a docset.

his/core/planning-and-architecting-solutions-using-data-clients.md

Line 29, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 64, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 126, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/planning-and-architecting-solutions-using-microsoft-service-for-drda.md

Line 159, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/protection2.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Protection' is duplicated with other articles: 'core/protection2.md(17,1), db2oledbv/protection1.md(16,1)'. First level headings must be unique within a docset.

his/core/providing-hot-backup-and-load-balancing-3270-1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln03.gif'. Alt text is required for accessibility.

his/core/quiesce1.md

Line 34, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703s.gif'. Alt text is required for accessibility.
Line 39, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703sa.gif'. Alt text is required for accessibility.
Line 44, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703sb.gif'. Alt text is required for accessibility.

his/core/receiving-messages1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32702a.gif'. Alt text is required for accessibility.

his/core/record-level-input-output-rlio-protocol-errors1.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/remote-environments1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Remote Environments' is duplicated with other articles: 'core/remote-environments1.md(17,1), core/wipremoteenvs.md(16,1)'. First level headings must be unique within a docset.

his/core/resource-location-for-open-sscp2.md

Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703d.gif'. Alt text is required for accessibility.

his/core/rqr-and-clear1.md

Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/32703t.gif'. Alt text is required for accessibility.

his/core/sdlc-link-statistics1.md

Line 22, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 26, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 31, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 48, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

his/core/sdlc-multipoint-connections1.md

Line 20, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3t.gif'. Alt text is required for accessibility.
Line 49, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3u.gif'. Alt text is required for accessibility.
Line 52, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/dev3y.gif'. Alt text is required for accessibility.

his/core/secondary-appc-return-codes2.md

Line 64, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 '000000D7''. Each second level heading (H2) in an article must be unique.
Line 179, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 '000000D7''. Each second level heading (H2) in an article must be unique.
Line 249, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 '00000156''. Each second level heading (H2) in an article must be unique.
Line 253, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 '00000156''. Each second level heading (H2) in an article must be unique.

his/core/security1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Security' is duplicated with other articles: 'core/security1.md(17,1), db2oledbv/security2.md(16,1)'. First level headings must be unique within a docset.

his/core/session-information1.md

Line 20, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Syntax''. Each second level heading (H2) in an article must be unique.
Line 30, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.
Line 42, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Syntax''. Each second level heading (H2) in an article must be unique.
Line 75, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.
Line 162, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Members''. Each second level heading (H2) in an article must be unique.

his/core/sessions-and-connections2.md

Line 30, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703b.gif'. Alt text is required for accessibility.
Line 43, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/his-32703ba.gif'. Alt text is required for accessibility.

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Recurring financial contributions with Paypal

User story
As a financial contributor, I want to set up recurring contributions to a Collective with Paypal as the payment source, so that I can pay using my preferred method.
Best solution for this problem
Here's the feedback we got from a user:

I do not want to let you store my card in your system. Paypal is PCI compliant and only paypal should have my debit card info. I want to use my PayPal Credit Account for this Business expense, (not my personal debit card). I want to use Paypal. I want Open Collective to protect my financial information by using the Paypal API properly. I am an eCommerce developer.
I am not going to put my banking info into a form on your website... BUT I totally would "check out with paypal" using 1 click and hand over the money. Maybe you could examine that. Not having this set up in your system is baffling to me. I set this feature up all the time for clients. It works with IPN. Takes a few min to a few days... depending on your skill set.

Original issue: https://github.com/opencollective/opencollective/issues/1141

Sounds like a duplicate of https://github.com/opencollective/opencollective/issues/1141, @alanna can we close it?


NT data text getting stacked on Ubuntu linux

Describe the bug
I noticed this happens to me on my ubuntu laptop, but not on the team's windows DS,
on the NT data table preview on the side, all of the topic names are getting stacked on top of each other and makes it unreadable
To Reproduce
Steps to reproduce the behavior:

Open Advantage Scope through the Start Tool menu on WPILib vscode
Connect to the robot / sim / log file
View the side preview of the NT table

Expected behavior
All of the topic names are getting stacked on top of each other.
Screenshots

Version (required):
Version: 3.2.1
Distributor: WPILib
Platform: linux-x64
Build Date: 3/13/2024, 22:19:40 UTC
Electron: 26.2.1
Chromium: 116.0.5845.188
Node: 18.16.1

This looks like the same problem as #99, which was the result of Intel driver issues. We can potentially switch Electron/Chromium versions if there have been related changes, but it seems like this is essentially a Chromium/Intel bug.

This looks like the same problem as #99, which was the result of Intel driver issues. We can potentially switch Electron/Chromium versions if there have been related changes, but it seems like this is essentially a Chromium/Intel bug.

ye seems to be like that

Looks like this is a driver issue that can't be easily fixed on the AdvantageScope side. Closing the issue for now.


adding sso service account cleanup script

Is the idea that this will delete every SA the client can view? Any need for filtering?

yes, I can filtering to skip particular clients from deletion


FIX: remove erroneous configuration in ScalerCH init

This is now handled by the components and this particular code causes
exceptions on init because it is using the wrong names.

I didn't catch that on the kind PR that this was handled already. Very nice!


[BUG] Wrong usage of ! in helper

This is a good one:
https://github.com/vuestorefront/shopware-pwa/blob/master/packages/helpers/src/listing/getListingFilters.ts#L35
!["properties", "options"].includes(aggregationName)

this basically evaluates to
false.includes(aggregationName)

my bad, this actually works as expected...


Update target branch in rhtap in main.

/assign @Kyl-Bempah
Hi, Kyl, can you take a look on this PR? It seems we configured a incorrect the target branch.


Catch transaction deserialization error in doLedgerGrpc

Allow clio to extract ledgers with transactions that can no longer be deserialized. The problem transactions will be skipped.

Some old transactions cannot be deserialized by current rippled code. Clio can still extract the ledger headers and state objects, just not the transactions.

Does this error only apply to gRPC deserialization, or do these transactions also fail to deserialize to JSON in the rippled APIs directly? Do you have an example tx hash to look up? (If there's no way to deserialize these transactions from their binary form, that's very undesirable; I don't like having "black box" transactions in history; the 32570 missing ledgers are bad enough.)
Note, I am not saying this PR should fix the problem of deserializing things, but the answers to my question will inform whether or not we open a ticket to fix the issue more broadly, and the scope thereof.

Here's one:
hash: "C7CE7D48C50D6ABEBC8DA01447C8BDA21324094B58C0738AED30D1FCD399FAD6"
ledger sequence: 7266393
actual transaction:
            {
               "Account" : "rEX2Q18vQziVAJoiLwoVHN5u87CXm29LCQ",
               "Fee" : "10",
               "Flags" :<PHONE_NUMBER>,
               "Memos" : [
                  {
                     "TransactionMetaData" : {
                        "TransactionMetaData" : {
                           "TransactionMetaData" : {
                              "TransactionMetaData" : {
                                 "TransactionMetaData" : {
                                    "TransactionMetaData" : {
                                       "TransactionMetaData" : {
                                          "TransactionMetaData" : {
                                             "TransactionMetaData" : {
                                                "TransactionMetaData" : {
                                                   "TransactionMetaData" : {
                                                      "TransactionMetaData" : {
                                                         "TransactionMetaData" : {
                                                            "TransactionMetaData" : {
                                                               "TransactionMetaData" : {}
                                                            }
                                                         }
                                                      }
                                                   }
                                                }
                                             }
                                          }
                                       }
                                    }
                                 }
                              }
                           }
                        }
                     }
                  }
               ],
               "Sequence" : 51,
               "SigningPubKey" : "033D098A1F0664D894D0D542006541CDDC997E1B5A5F1A6E63BE5B83E12AAF00D2",
               "TransactionType" : "AccountSet",
               "TxnSignature" : "304402204DF684C465B2D110F9DF39100E205084C972FEF885AF2A9036DBB58866E224AE022055C4DF3345F8111552C4D01B896D3E22CBFAD450EF020737DD9F2C3907294D3E",
               "hash" : "C7CE7D48C50D6ABEBC8DA01447C8BDA21324094B58C0738AED30D1FCD399FAD6",
               "metaData" : {
                  "AffectedNodes" : [
                     {
                        "ModifiedNode" : {
                           "FinalFields" : {
                              "Account" : "rEX2Q18vQziVAJoiLwoVHN5u87CXm29LCQ",
                              "Balance" : "32005425",
                              "Flags" : 0,
                              "OwnerCount" : 2,
                              "Sequence" : 52
                           },
                           "LedgerEntryType" : "AccountRoot",
                           "LedgerIndex" : "BCCEA6B346A29656AFD37B8AB7F573DA705AB7A86D9FE197AC6CB1E9D5772EDB",
                           "PreviousFields" : {
                              "Balance" : "32005435",
                              "Sequence" : 51
                           },
                           "PreviousTxnID" : "82FC7296AE62216C6A58DFF6707CD441C57ECF835DD784449C8C0CA78A9ED143",
                           "PreviousTxnLgrSeq" : 7266389
                        }
                     }
                  ],
                  "TransactionIndex" : 6,
                  "TransactionResult" : "tesSUCCESS"
               }
            },

The error applies to both gRPC deserialization as well as JSON deserialization. The error actually just lies at transaction deserialization itself, where rippled cannot properly deserialize the transaction at all anymore.

Okay.  I now understand the previous comments.  The identified problem applies both to clio and, more generally, to any time rippled tries to deserialize these transactions.  The supplied fix only works for clio.  I'm good with that, but that understanding gives me context for what I'm reviewing.

I actually just copied the way the JSON handler does this: https://github.com/XRPLF/rippled/blob/ebbf4b64a57d2673d54a6b25def7726601d99bf9/src/ripple/app/ledger/impl/LedgerToJson.cpp#L176
I agree it would be better to continue on failure, but maybe that should be a separate PR? I just wanted to get things back up and running for clio, because right now the entire call returns an error (unlike the JSON version of the call).
I unfortunately don't have the patch that actually deserialized this transaction, it was so long ago.

@cjcobb23, I'm not sure I understand the motivation for putting the suggested change in a separate pull request.  The suggested code changes are not extensive and they are localized.  I'm not guaranteeing the suggested change is bug free; it needs testing.  But the implementation in the pull request has bugs that have been pointed out.
You haven't yet convinced me that it's a better idea to stay with the implementation in the pull request when we know that the pull request has fixable flaws.  But I'm listening.

The implementation in the pull request mirrors the JSON implementation that already exists. The exception is actually thrown as part of the loop iteration, not in the body of the loop. So there won't be any incomplete data. We will skip later transactions, as does the JSON implementation. However, I'd rather solve that issue in a later pull request.

Mentioning @manojsdoshi - please sync with @cjcobb23 to see how this should be tested.


Adding PID to teiHeader Persons

e.g. author, editor, editionStmt name

@linxOD , what follows from this? - what do we have to change (and how) in the XMLs?

as discussed there is a file called preprocess.xsl
please verify ORCID or GND especially for authors


Introduce useClickOutside hook

Related to #46

lgtm

Tough, when I test your pr with typescript, then I see that this looks suspicious
enhanceWithClickOutside.useClickOutside = useClickOutside;

module.exports = enhanceWithClickOutside;

writing a key of a function doesn't seem to work. Shouldn't it be an object? Otherwise supporting es6 export/import operators would make more sense when looking to export more than 1 function from a file.

Also this function seems to get complaints from typescript when I copy it over (can still probably be ignored since this isn't typescript)
Object is possibly 'null'.  TS2531

    16 |         () => {
    17 |             const onClick = (e: Event) => {
  > 18 |                 if ((!domNode || !domNode.contains(e.target)) && onClickOutside)
       |                                   ^
    19 |                     onClickOutside(e);
    20 |             };
    21 |

Hi folks,
What is the current status ? It would be extremely handy.


Setting active machine broken in 0.3.0-rc3

Docker-machine doesn't accept any arguments for the "active" command:
$ docker-machine create -d virtualbox --virtualbox-cpu-count 2 virtualbox
Creating CA: /Users/ilau/.docker/machine/certs/ca.pem
Creating client certificate: /Users/ilau/.docker/machine/certs/cert.pem
Image cache does not exist, creating it at /Users/ilau/.docker/machine/cache...
No default boot2docker iso found locally, downloading the latest release...
Downloading https://github.com/boot2docker/boot2docker/releases/download/v1.6.2/boot2docker.iso to /Users/ilau/.docker/machine/cache/boot2docker.iso...
Creating VirtualBox VM...
Creating SSH key...
Starting VirtualBox VM...
Starting VM...
To see how to connect Docker to this machine, run: docker-machine env virtualbox
$ docker-machine create -d virtualbox vbox2
Creating VirtualBox VM...
Creating SSH key...
Starting VirtualBox VM...
Starting VM...
To see how to connect Docker to this machine, run: docker-machine env vbox2
$ docker-machine ls
NAME         ACTIVE   DRIVER       STATE     URL                         SWARM
vbox2                 virtualbox   Running   tcp://<IP_ADDRESS>:2376
virtualbox   *        virtualbox   Running   tcp://<IP_ADDRESS>:2376
$ docker-machine active vbox2
Error: Too many arguments given.
$ docker-machine --version
docker-machine version 0.3.0-rc3 (a5fd8cf)

Oh okay, reading e.g. #616, #443 and #777 it seems like the whole active machine concept might be going away. A further clue is that commands like "ip" no longer seem to use the active machine by default.
The reason this would've been nice for me is that I had a bit of automation that got the IP of the active docker host by just running
IP=$(docker-machine ip)

and that would work no matter what the active machine happened to be, and also work with minimal fuss with boot2docker by just changing "docker-machine" to "boot2docker". I guess I can do
IP=$(docker-machine ip $(docker-machine active))

but it does seem a bit complex...

@ilkka yes this behavior has changed (see https://github.com/docker/machine/blob/master/docs/machine-overview.md#active).  I see your point.  I was wondering if we could add a active key to the ls filter but I don't think that would get you any better than your last workaround.

Hey @ilkka, sorry to hear that you ran into some trouble around this.  Perhaps we could communicate it better in the release notes.

@nathanleclaire the included help should also be updated (it's currently misleading given [arg...]), assuming that active isn't going away completely:
$ docker-machine help active
Usage: docker-machine active [arg...]

Print which machine is active

Good point @mojodna -- I think it's added automatically by codegangsta/cli but we'll see what we can do.

how does a machine get set "active"?
$ docker-machine create --driver virtualbox default
...
$ docker-machine ls
NAME      ACTIVE   DRIVER       STATE     URL                         SWARM
default            virtualbox   Running   tcp://<IP_ADDRESS>:2376
$ docker-machine active
Error getting active host: Active host not found

is this something I do by manually exporting DOCKER_HOST ?
in that case I can't really see any use for it

I'd love to be able to set a particular machine as the 'default' to avoid having to type the machine name on every command
I realise docker-machine has more powers and uses, but most of the time I'm using it locally as a replacement for boot2docker and will only have a single machine

ok, for the first part you have to do the eval "$(docker-machine env default)"

@ehazlett that link is now broken, I'm a bit confused about how to start any docker containers on my mac now?

Ah, okay, the documentation isn't very clear for me as a first-time user.  It says:

Connect your shell to the new machine.
$ eval "$(docker-machine env default)"

I had no idea that "Connect your shell to the new machine" means "mark the machine as active".
Also, docker-machine start default output this:

Started machines may have new IP addresses. You may need to re-run the docker-machine env command.

It would have saved me some confusion if it had just said "You may need to run eval "$(docker-machine env default)" to mark this machine active"

Is there any reason starting the only machine shouldn't set it active automatically?

It's not possible to "set a machine as active" without having the user set environment variables today (a child process, e.g. docker-machine, cannot modify the environment of its parent process, e.g. bash).
Configuring a local Docker client to talk to a remote Docker daemon requires setting DOCKER_HOST and other environment variables.

Okay, that makes sense.


fix for issue #1073, deregistering not working on windows.

When deregistering a socket make sure it is marked for deletion so it won't be used in poll updates.
Signed-off-by: Daniel Tacalau<EMAIL_ADDRESS>

Shouldn't this happen in the deregister implementation?

Shouldn't this happen in the deregister implementation?

@Thomasdezeeuw the key here is calling mark_delete() for a sock_state once it's deregistered. The call to mark_delete() could be done from other places, including deregister, but, I've chosen set_sock_state to keep things specific to TcpListener sock_state. Maybe we want other behavior for sock_state of other objects. What do you think?

I think you're right this is the best place. Does this need to happen for UdpSocket and TcpStream as well?

I think you're right this is the best place. Does this need to happen for UdpSocket and TcpStream as well?

Good point, will check.

@Thomasdezeeuw Both, UdpSocket and TcpStream, were affected by the same deregistering issue. I've made fixes for them too.

Thanks!


Fixes #3522.
[ ] Add unit tests
[ ] Update docs

Pull Request checklist:

[x] I've named my PR in the form of "Fixes #issue. Terse description."
[x] My code follows the style guidelines of Terminal.Gui - if you use Visual Studio, hit CTRL-K-D to automatically reformat your files before committing.
[x] My code follows the Terminal.Gui library design guidelines
[x] I ran dotnet test before commit
[x] I have made corresponding changes to the API documentation (using /// style comments)
[x] My changes generate no new warnings
[x] I have checked my code and corrected any poor grammar or misspellings
[x] I conducted basic QA to assure all features are working

Neat. I'll take a look at this one either later tonight or some time tomorrow.

Getting to this in a few minutes, once I go through the last few items at the top of my inbox.

Odd. WIth this new interface defn, intellisense no longer suggests members aren't implemented if they're not. Why is that?
Regarding other possible things to add to this interface: Not gonna do it until actually needed. First rule of API design is to not expose something publicly until there are at least 3 known use cases.

Ok, how's this?

I think your original naming was better. Enable is kinda confusing since that's now a member of the View. I wouldn't expect SomeView.Enable() to load demo data.

Regarding other possible things to add to this interface: Not gonna do it until actually needed. First rule of API design is to not expose something publicly until there are at least 3 known use cases.

Yep, agree there.
In any case, pretty much everything needed is already in the View class and derivatives anyway. Maybe we should take a refinement pass in beta or something to go through and annotate things around the library with appropriate/useful attributes like that?

I think your original naming was better. Enable is kinda confusing since that's now a member of the View. I wouldn't expect SomeView.Enable() to load demo data.

Now EnableForDesign


fix: revert internal api to v2beta1

Current situation
flux-build v3 uses only the v2 api version of Helmreleases just as the helm-controller from flux v2.
However this was a bad choice since this basically drops support for some features used in the beta apis such as postrender patches in the deprecated format.
While for a controller it makes sense to only work with a certain version (withouth conversion) for flux-build there is no reason to drop support as different apiVersions might be used at the same time and a controller only works with one.
Proposal
Partially revert the api changes and go back to the beta one. The advantage of the beta one is it supports both the deprecated and the new fields.
This change is fully backwards compatible, it only changes flux-build internals.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

46 of 131 (35.11%)  changed or added relevant lines in 5 files are covered.
23 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.05%) to 50.382%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/helm/postrenderer/post_renderer_namespace.go
0
1
0.0%

internal/helm/postrenderer/post_renderer_origin_labels.go
5
9
55.56%

internal/helm/postrenderer/post_renderer.go
0
11
0.0%

internal/helm/postrenderer/post_renderer_kustomize.go
41
56
73.21%

internal/build/helm.go
0
54
0.0%

Files with Coverage Reduction
New Missed Lines
%

internal/build/helm.go
1
0.0%

internal/cache/cache.go
2
68.0%

internal/helm/postrenderer/post_renderer_origin_labels.go
2
64.71%

internal/helm/postrenderer/post_renderer_kustomize.go
2
74.56%

main.go
16
0.0%

Totals

Change from base Build<PHONE_NUMBER>9:
-0.05%

Covered Lines:
1647

Relevant Lines:
3269

💛  - Coveralls


DomainPairsCountInCategory definition

The cmdlet's -Detailed switch mentions DomainPairsCountInCategory but does not provide any explanation about what this information means.
Could someone please review this concern and step up efforts to avoid making similar references in documentation?  I'm sure you will happily fix this issue and I realize it was an accident but it's time consuming to investigate then open a request to update; an explanation should have been included all along.
Thanks for your time,
Keith

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

ID: e284a198-a0bc-3e39-6077-c2de30d54c4f
Version Independent ID: 01eb0b27-7822-7e4d-ba89-a5b51c0996f4
Content: Get-PhishFilterPolicy (exchange)
Content Source: exchange/exchange-ps/exchange/Get-PhishFilterPolicy.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

Hello,
I saw this request was just closed so I took a look at the cmdlet's documentation.
I don't see any additional info that describes what DomainPairsCountInCategory means.  I did I check too soon?

@mrkeiths, yes; too soon. I merged the #6124 pull request that fixes the issue as you described, but I did not come here and close the issue. This must be a new thing where the Issue and the PR are somehow intelligent?
There were some other PRs that came in that I was trying to approve before I merged Master to Live (published). In this repo, everything takes way too long.


Add :on-load option for p/open

Add an option to run an arbitrary function once portal is loaded.
Usage:
(portal.api/open {:on-load (fn [] (portal.api/eval-str "(js/alert 1)"))})

What would be a common use case for this? Just curious how I could beenfit from this... :)

@holyjak, I think @BrianChevalier is using it to load custom viewers into the portal client.

@holyjak @djblue yes, it ensures that custom viewers are loaded once portal is open! Previously you had to open portal, wait and manually eval the string that registers the viewer. We wanted to keep it generic though so it will evaluate any function you pass. I don't know of other uses currently, but the option is open!

@BrianChevalier could you be so kind and share an example of how you do that? Perhaps even include it in the official documentation, since it will certainyl be interesting for others?

@holyjak yes, I think some more documentation for this kind of customization is a good idea in general. Here is a small example where my-custom-ns is a .cljs file that registers a custom viewer
;; NOTE - this is called in the jvm. For portal web, use
;; portal.web/open and load your string to evaluate
;; for a shadow environment I do (shadow.resource/inline "./path/to/file.cljs")
(portal.api/open {:on-load (fn []
                               (portal.api/eval-str "(require 'my-custom-ns :reload)"))})

The contents of the cljs file could looks something like the following:
(defn component [value]
  [:div (str value)])
(def viewer
  {:component component
   :predicate #()
   :name :my-custom-ns/custom-viewer})
(portal.ui.api/register-viewer! viewer)

This code is evaluated in the context of the portal frontend. Using the :on-load option ensures it is loaded after portal is open and can execute your custom code. In the context you have access to all of the namespaces exported, defined here: https://github.com/djblue/portal/blob/a23ab88b39d4265bdc4896080c4b0785a276dbff/src/portal/ui/sci/libs.cljs.
You have access to react, reagent, portal components that are exported from that namespace, etc. You can use react hooks or reagent atoms to manage state and make custom UIs. Take a look at existing viewers to get some idea of what you could implement.

Awesome, thank you! Extra credit for providing both jvm and web instructions :)

@holyjak  Related note: you can use the option :value to open to pass in an atom for your state, or any Clojure value. You can also pass in a map of atoms, which is what I do. Portal will register to watch these atoms and update the UI. You can have multiple sources of state and watch all of them and register a custom viewer to view that state in a way that makes sense for your app.


Add a property to get access to the nccl handle.

Since there are no official nccl bindings from nvidia, there is no method of using NCCL from python or other libraries outside of cuPy. By allowing the cuPy nccl handle to be directly accessed, cuPy can interop with other NCCL enabled libraries by passing the nccl handle direclty.

Thanks, this looks nice!

cuPy can interop with other NCCL enabled libraries by passing the nccl handle directly.

Which library are you going to pass the pointer? Just curious 😃

It's from the TensorRT team 🙂

/test mini

Let's get this backported to help them lifted sooner.

Thanks to you both!


Rewrites ocm-container in golang

This is a large PR, rewriting (or reimplementing, really) ocm-container in golang.  The intent is to make this more testable, more extensible, to fix some bash-induced bugs, and finally, to allow us to make and publish a binary to more easily, reliably and securely onboard new users.
This rewrite is an (almost) 1-1 feature parity and backward-compatible replacement for the ocm-container.sh file, as well as a number of other related tweaks.
Opinionated changes
In a (very) few places, it's a little more opinionated and will possibly require a minor change in usage, but for the most part opinionated changes are displayed as deprecation messages, and we can decide in the future how and when to handle them.  In most of these cases, it's to fix some ocm-container-isms that prevent us from utilizing some of the features of the container:
eg: ocm-container CLUSTERID is difficult to parse, and prevents us from easily using container-standard Entrypoint and CMD flags.  This PR deprecates that and adds ocm-container --cluster-id CLUSTERID [--entrypoint=ENTRYPOINT] -- [CMD] so that we can run arbitrary commands in ocm-container.  The original usage still currently works, but is marked Deprecated, and --cluster-id is compatible with other standard flags across other tools in use by our team.
In other cases, deprecation messages are included for things that will actually be deprecated, such as the use of OCM's OFFLINE_ACCESS_TOKEN.
Feature Parity
I've tried as best as I can to have full 1:1 feature parity with the old shell script.  EG: PagerDuty tokens, Personalizations, etc should work exactly the same, and be configured exactly the same.  In some few cases, there may be a deprecation warning, to allow us to transition to a cleaner way of enabling these using the enhanced capabilities in golang and https://github.com/spf13/viper configuration.
All features are enabled by default, but some may require additional configuration (the same configuration required for the feature in ocm-container.sh right now).  Any given feature may be disabled by using the --no-FEATURENAME=true CLI flag for testing, or setting the no_featurename: true config or related ENV var.
Note that env vars are prefixed with OCMC_ to prevent accidental parsing of system or other env vars (eg: USER).
Testing and Adoption
First, unset your ocm-container alias, if you have one.  The binary may be executed directly.
Get the binary: For testing this PR (not adoption or production), the make build-snapshot command will use Goreleaser to build a single OS/Arch appropriate binary for you to test with.
The image: ocm-container will by default use the upstream nightly build from quay.io/app-sre/ocm-container:latest.  No image build is required.  You may specifiy your own image.  See ocm-container --help for details.
Initial setup:
See the README.md in this PR for a thorough documentation on how configuration and migration works.
The most basic setup can be configured via:
# CONTAINER_ENGINE may be podman or docker
ocm-container configure set engine CONTAINER_ENGINE
ocm-container configure set offline_access_token OCM_OFFLINE_ACCESS_TOKEN

Optionally, existing ocm-container users can make use of a migration command to convert the env.source to a Viper ocm-container.yaml file.
Long term, I plan to expand this ocm-container configure init command to prompt the user to add the values to setup ocm-container and the desired features.

I would like to get as many folks involved in reviewing this and testing the functionality as possible, so we can cover all our bases and make this a seamless transition.
I also propose making a v0.1 tag for the existing master branch, and creating a pre-release v0.2 tag and binary for the contents of this PR when it merges into master, to mark the change in compatibility going forward.  However, there's no concern about merging this into master, as existing folks have their clone, and the repository DOES NOT need to be cloned to get and use the Go binary, so it can be tested in parallel with the old workflow.
Comments and reviews welcome.  Testing of the binary is especially!  Thanks in advance!

This is great Chris! I'm super excited to test this.
Just a few notes from my read-through of your description: I absolutely appreciate the messaging to deprecate some functionality - however I'd like to consider this a breaking major version change with semver (so instead of tagging as v0.1 -> v0.2, we make this v0.1 -> v1.0) and I'm more OK with removing the functionality of most things without deprecation warnings when we go to publish this.
As I would consider this PR a release candidate - I'm more than happy to keep the deprecation warnings though to help with the testing transition, but upon release I'd much rather have these deprecation warnings and the functionality be actually removed and call it a breaking change, rather than having to plan to actually remove later.
Aside from that - I'm excited to get this pulled down and start testing this during my shift next week :D

Just a few notes from my read-through of your description: I absolutely appreciate the messaging to deprecate some functionality - however I'd like to consider this a breaking major version change with semver (so instead of tagging as v0.1 -> v0.2, we make this v0.1 -> v1.0) and I'm more OK with removing the functionality of most things without deprecation warnings when we go to publish this.
As I would consider this PR a release candidate - I'm more than happy to keep the deprecation warnings though to help with the testing transition, but upon release I'd much rather have these deprecation warnings and the functionality be actually removed and call it a breaking change, rather than having to plan to actually remove later.

I like Kirk's logic here.
I am all for this option.

@rendhalver Please test with the latest commit (75364708cf18098746a0ea7205de0a2e38f6f16f) and lemme know if you're good with a /lgtm!
That commit changes to use a logger, per @iamkirkbater's suggestion.
I've removed the Draft status - this is ready for real review and merge to the main branch when you all are happy with it.

/label tide/merge-method-squash

Thanks @clcollins!
Fabulous work! Let's get his merged!
/lgtm
:shipit:


Please support cubrid db.

cubrid's manager tool is bad.
I hope you can support it with dbeaver.
https://www.cubrid.org

It is quite easy as CUBRID has JDBC driver. I'll add its configuration in the next DBeaver version.
I can't test/validate how it works so please do it after 4.2.5 release.
For now I'll mark it as beta and will set driver version to 10.1.0.

Thank you very much for supporting DBeaver  4.2.5.
I connected to cubrid. And it is good to test it.


proposing to update https://ocm.software/docs/guides/getting-started-with-ocm-flux/

What would you like to be added:
steps to create more than one component.
cat > components.yaml << EOF
components:

name: github.com/acme/podinfo-app
version: "v1.0.0"
provider:
name: acme.org
resources:

name: -app-deployment
type: Directory
input:
type: dir
path: "manifests"
compress: true
name: app-config
type: PlainText
input:
type: file
path: "app-config.yaml"
compress: true
name: app-image
type: ociImage
version: "v0.0.0"
access:
type: ociArtifact
imageReference: ghcr.io/app-image:0.0.0

name: github.com/acme/podinfo-database
version: "v1.0.0"
provider:
name: acme.org
resources:

name: database-deployment
type: Directory
input:
type: dir
path: "manifests"
compress: true
name: database-config
type: PlainText
input:
type: file
path: "database-config.yaml"
compress: true
name: database-image
type: ociImage
version: "v0.0.0"
access:
type: ociArtifact
imageReference: ghcr.io/database-image:0.0.0
........
........
........
EOF

create componentversion.yaml for each component(e.g app-componentversion.yaml, database-componentversion.yaml), similarly resource.yaml, localization.yaml, oci_kustomization.yaml for each component all put together inside ./component folder.
Why is this needed:
End user could have an understanding of how to build multiple OCM components and deploy using flux.

Sorry, I'm not following this one. The guide doesn't use a database at all. It's aimed to be an easy to follow getting started guide. I don't think adding a database and extra components would improve upon that view.


Add file syncing to README example

Got stuck on this and I figured most people would want this on by default

thanks for contribution @jtmarmon! If you could also mention that syncing may not be the best idea for production environment it would be good to merge :)

@aserafin - why is that so? The Rails logger sync is on by default. So is the Ruby logger https://github.com/ruby/ruby/blob/trunk/lib/logger.rb#L585

furthermore - if your process is forcefully killed, as might need to happen in a production environment, none of the logs for the process's life are recovered.

Of course you're right :) I just meant that maybe there are better choices for production logging, like syslog etc. but it might be out of scope of this project to kind of insist of using them. I will merge the PR, thanks!


Dynamic API Versioning with NSwag like with Swashbuckle

I'm trying to implement api-versioning using .NET 6.0 and it works fine, but I can't get automatic document generation to work.
How can the following be done with NSwag? -> https://github.com/dotnet/aspnet-api-versioning/wiki/API-Documentation#aspnet-core
All examples I can find manually call AddOpenApiDocument for every version, but I would like to do that automatically for every version.
For now I use an intermediate IServiceProvider, but this generates valid warnings:
var versionDescriptionProvider = builder.Services.BuildServiceProvider().GetService<IApiVersionDescriptionProvider>();
foreach (var description in versionDescriptionProvider.ApiVersionDescriptions)
{
    builder.Services.AddOpenApiDocument(document =>
        {
            document.DocumentName = description.GroupName;
            document.ApiGroupNames = new[] { description.GroupName };
        });
}

No, still using the mentioned workaround...


Element Change: Feedback from ecosystem team

Added toast message for the number of elements returned by API.
Emphasis no longer removed on no changes.
Added more explanation in sample information.

Probably not an issue for this PR but does APIM requests not cache?
The difference between the final version changeset and the first spatial changeset is over 10x larger.
Request for final version is 196 Bytes.
Request for first spatial version is 602 KB.
Maybe demonstrating a caching mechanism might be a good idea - swapping between them should be instantaneous after the first request.


Iscsi rescan should be executed only after unmapping

In GitLab by @paul.laffitte on Nov 4, 2020, 18:38
https://github.com/container-storage-interface/spec/blob/master/spec.md#volume-lifecycle

ControllerUnpublish is executed after NodeUnpublish
ControllerUnpublish unmap the volume on the MSA
NodeUnpublish rescan after ejecting devices, so they reappears just before being unmapped

In GitLab by @paul.laffitte on Nov 9, 2020, 18:24
assigned to @paul.laffitte

In GitLab by @paul.laffitte on Nov 9, 2020, 18:29
mentioned in commit 84653ac8746a59af046910e7f63ca1881b9c20df

In GitLab by @paul.laffitte on Nov 9, 2020, 18:33
mentioned in commit 6fa09fac90c7c189f354d31e8a025d7148224f91

In GitLab by @arcln on Nov 10, 2020, 00:36
mentioned in commit da8cd47a3851120d24d850f43b556a2c50782d10


Adds a Snyk badge to show you are vulnerability-free

graph.js has no vulnerabilities, which is awesome!
This PR adds a badge that shows that you're free of known vulnerabilities. Note that the badge works off the latest master branch.
Adding the badge will show others that you care about security, and that they should care too.
(It will also help to spread the word about Snyk, which would help us out!).
Check our documentation if you'd like to know more about our badges.
Stay secure :-)
Ben from the Snyk team

Coverage remained the same at 100.0% when pulling 608138ac54a145ee1d5fab04ec6211ce23997980 on benmag1:snyk-badge-98900752 into c2dd9b82101b05a0439f957c64ff94208b657630 on mhelvens:master.

Sorry, but there are too many red flags here.

This is one of 128 automatically generated pull requests from the benmag1 account, so it doesn't seem graph.js was ever considered specifically as a project that could benefit from this.
Indeed, as a pure data-structure implementation with zero run-time dependencies, it seems nigh impossible there ever could be a security vulnerability, and this badge would just be confusing.
I haven't been able to find any third party endorsements of Snyk. A quick Google search didn't give me anything useful, and their badge is not available via shield.io.
Snyk appears to be a for-profit organisation, and I don't see any particular reason to give them free publicity.

So I'm closing this one. But benmag1, feel free to respond to this. I'm open to arguments.


[BUG] Animated: useNativeDriver was not specified.

To Do First

[x] Did you try latest release?
[x] Did you look for existing matching issues?

Software Package Version: 1.2.0
Describe the bug
When using the lib animation function, in a react native project, the following error is reported: Animated: useNativeDriver was not specified. This is a required option and must be explicitly set to true or false After this error some functionality of the app is compromised.
To Reproduce

Go to react native project
Use some function that activates Animated. Example: onSwipeDownReleased, onSwipeUpReleased, etc.
Next error will be reported: Animated: useNativeDriver was not specified. This is a required option and must be explicitly set to true or false

Expected behavior
I expected some default value to come and the possibility to change it by parameter
Screenshots
Click here
Version (please complete the following information):

Simulator Device: Iphone 11
iOS: 13.6
react-native: 0.63.0

Just made a simple PR here: https://github.com/Luehang/react-native-easy-view-transformer/pull/12


Add mouse and keyboard documentation

@tinohager Hi, Thanks!
May be o and p should be closer, since they do simillar things.

@AlexeyAB Okay done :)


Revised test cases to fix bugs pertaining to Group and added comments

This branch is even with master but the cimpl6Import branch is out of sync with master.  I propose we use this branch cimpl6Import-ac for merging to master.  Can you close this PR and open a new one that goes against master instead of cimpl6Import?

Note: I updated my comment above to change my suggestion.


word chars line mobile responsive

Associated Issue: #152
Summary of Changes

Fixed the break of the chars on mobile view.
Now width of chars of one word will change according to the length of the word, without breaking.
Added small margin gap between them on mobile only.

This looks awesome when viewing it in chrome dev tools but when looking at it on my iPhone - it looks a bit weird. Have you tried it on an actual device? 🙂

Forgot I cannot trust dev tools on this matter... Thanks for letting me know, I will try to fix it

In version 2 of the pull request I didn't add again the char.js component that I changed in version 1, and I need this change for version 2. I guess I should have done that, right..?

@Yarden84 This still looks a weird on my iPhone 5s, maybe some more experimenting is needed. The changes you made to Char.js in your first commit will still be included in this PR even after you add additional commits 🙂


Mesh col-offset suggestion

It would be nice to have offset on the columns, as it have the Bootstrap grid system.
This way you can avoid having to use empty mesh-col-X-Y divs to create empty spaces, and instead use directly mesh-col-offset-X-Y in its place.

@escudero89, we have that feature in mind, so thanks for opening the issue, since it will help us track it!

this feature will probably duplicate mesh's filesize 👀
just say'in

@juanbrujo, it will in the raw file, but not in the gzip version that we are going to use.
That said, I'm thinking that "push/pull" could be a module that you include only if you need it. I'm starting to think that Mesh needs to be even more modular, something in the line of this little grid I made.

Closing due to #21. 💀


get_report error

Describe the bug
the sample code (as per --> https://empyrial.gitbook.io/empyrial/save-the-tearsheet/get-a-report) is throwing an error
To Reproduce
Steps to reproduce the behavior:

Go to 'https://empyrial.gitbook.io/empyrial/save-the-tearsheet/get-a-report...'
Run the sample code
Scroll down to '....'
See error

NameError                                 Traceback (most recent call last)
/var/folders/41/q1hx0rjd5xzck1vl121t6b2m0000gn/T/ipykernel_11664/2518190224.py in
10 empyrial(portfolio)
11
---> 12 get_report(portfolio)
NameError: name 'get_report' is not defined
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
using jypiterlab notebook

Hello,
I tried to reproduce the error but I didn't get one. I did get my report as you can see.

https://colab.research.google.com/drive/10LfcDL3efTtxTuGwLeMzvJZrUZXzybEE?usp=sharing
Maybe, you should retry it again. If it doesn't work, install the most recent version of Empyrial. If even by doing that, there is still a problem, please tell me and send your code so I can reproduce the error.
Best

get_report works in google colab not jupyter ..for some reason
On Fri, Nov 5, 2021 at 2:15 PM Santosh @.***> wrote:

Hello,
I tried to reproduce the error but I didn't get one. I did get my report
as you can see.
[image: image]
https://user-images.githubusercontent.com/61618641/140482834-99e02d15-6882-41f1-8c38-15a8cdf00f88.png
https://colab.research.google.com/drive/10LfcDL3efTtxTuGwLeMzvJZrUZXzybEE?usp=sharing
Maybe, you should retry it again. If it doesn't work, install the most
recent version of Empyrial. If even by doing that, there is still a
problem, please tell me and send your code so I can reproduce the error.
Best
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ssantoshp/Empyrial/issues/43#issuecomment-961718885,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF5JGBSZX52CTIHAJOIX2NTUKOKTZANCNFSM5GEIB7JA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Warm Regards,
Amit
M-9873001966

Make sure it is in your imports (and that you run the imports again). I had the same error :-D
from empyrial import get_report, empyrial, Engine

Will do, thanks!
On Wed, 29 Dec 2021 at 21:01, Stenio Ferreira @.***>
wrote:

Make sure it is in your imports (and that you run the imports again). I
had the same error :-D
from empyrial import get_report, empyrial, Engine
—
Reply to this email directly, view it on GitHub
https://github.com/ssantoshp/Empyrial/issues/43#issuecomment-1002650598,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF5JGBSHCMB46ZN52VZSYEDUTMSWTANCNFSM5GEIB7JA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Warm Regards,
Amit
M-9873001966


Implement generic mock client

Description

Checklist

[x] added release notes to Unreleased section in CHANGELOG.md, if user facing change

References

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Codecov Report

Merging #139 (b6312c7) into main (4ce2584) will increase coverage by 0.31%.
The diff coverage is 55.75%.

@@            Coverage Diff             @@
##             main     #139      +/-   ##
==========================================
+ Coverage   50.46%   50.77%   +0.31%
==========================================
  Files          96      103       +7
  Lines        4415     4693     +278
==========================================
+ Hits         2228     2383     +155
- Misses       1953     2053     +100
- Partials      234      257      +23

Flag
Coverage Δ

integration
50.77% <55.75%> (+0.31%)
:arrow_up:

unittests
39.10% <55.75%> (+1.13%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/api/mock/matcher_object_tags.go
0.00% <0.00%> (ø)

pkg/api/mock/matcher_object_deleted.go
41.66% <41.66%> (ø)

pkg/api/mock/matcher_object.go
54.54% <54.54%> (ø)

pkg/api/mock/contain_element_ntimes_matcher.go
57.50% <57.50%> (ø)

pkg/api/mock/utils.go
57.89% <57.89%> (ø)

pkg/api/mock/mock_api_implementation.go
58.82% <58.82%> (ø)

pkg/api/mock/mock_api_iterator.go
77.41% <77.41%> (ø)

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 4ce2584...b6312c7. Read the comment docs.


segfault in alloc_mmap

After compiling OpenBLAS 0.3.2 with gcc 7.2.0 from conda , I experienced Segmentation fault in gotoblas_init.
A little bit of research showed that there is a bug introduced by https://github.com/xianyi/OpenBLAS/commit/a399d004257b2f43e8211341f924f3a73171b98c
Namely , in https://github.com/xianyi/OpenBLAS/blob/develop/driver/others/memory.c#L687 current is set to allocation_block_size, and then in the loop starting in https://github.com/xianyi/OpenBLAS/blob/develop/driver/others/memory.c#L689 it is decremented by PAGESIZE
But allocation_block_size=BUFFER_SIZE + sizeof(struct alloc_t)  which is not a multiplactive of PAGESIZE, resulting in current eventually going below 0 , and since it is an unsigned integer, becoming huge number, causing a segfault.
Fix would be to replace "while(current > 0)" with "while(current > (PAGESIZE-1))" in https://github.com/xianyi/OpenBLAS/blob/develop/driver/others/memory.c#L689

Thanks. Just when I thought the code had stabilized again after 0.3.1 ... @oon3m0oo

I see the issue. BUFFER_SIZE and PAGESIZE are defined independently in common*.h. It doesn't look like there was ever a guarantee that BUFFER_SIZE would be a multiple of PAGESIZE, they just happened to be defaulted that way.
@vfonov I think your suggestion would actually be off by one, since that loop seems to increment start until all of the allocated block fits.  I think it should be something like:
640: BLASULONG best, start, current, original;
...
688: original = current;
689:
690:	while(current > 0 && current <= original) {
This way we'd detect the wraparound but still have enough pages to hold the entire allocation.  I don't have a good way to test this since we don't use mmap here, but @vfonov could you try this out and see if it works for you?

Yes, that seem to work too.
The last value is not used anyway, since the only place where these values are used are in run_bench to traverse the array and there is another condition which limits accessing that last few bytes of the buffer (line 702).


Add subsection about mobile devices to the graphics chapter.

Good idea about moving to the end - done. Merging.

Good idea about moving to the end - done. Merging.


Release v2.0.8 is actually v2.0.6

the release v2.0.8 has v2.0.6 in its dist folder.

I will try to do later this week =) Probably 28 is the day that I can go back and check this

It seems that there is no new release version now.

me too !

Hey all! Thanks for your patience! First of all, sorry for the delay in answer and fix.
That said, the original issue was fixed after v2.0.9 gets properly released and tagged on GitHub and published on NPM.
I'll close the issue for now, but feel free to re-open if any doubt pops up. Thanks again for your patience.