Problem with pip - 'latest' and parse from freeze options

Simple configuration:

python:
    dev: latest
    pip: latest
    python_pips:
      erl_terms:
        ensure: 0.1.1
        pkgname: erl_terms
      psutil:
        pkgname: psutil

CentOS 7.2/7.3
Using pip 'latest' doesn't work. Pip stays at 8.1.2.

Parse unless with pip freeze

In your 'unless' statement, exemplary phrase:
pip freeze | grep -i -e ^erl_terms==0.1.1$ || pip list | sed -e 's/[ ]\+/==/' -e 's/[()]//g' | grep -i -e ^erl_terms==0.1.1
will always return notify due to:

You are using pip version 8.1.2, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
You are using pip version 8.1.2, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

After manual upgrade pip to 9.0.1, notify changes to:
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
This still generates notify event and installs pips on every puppet run.

I have the same issue.
My workaround:
python::pip { 'pip':
  ensure => '9.0.1',
  install_args => `'--upgrade',
}

In my case pip argument requires a string not a hash, so no way to use workaround.

I'm not certain if it works for all version of pip , but using 'pip -q freeze | grep ...'  quashes the 'consider upgrading' noise so that the behaviour of Exec[ ] with unless works like intended


fix missing descriptions - batch 9

@MandiOhlinger @MightyPen and number nine... number nine...

Docs Build status updates of commit 246ce43:
:warning: Validation status: warnings

File
Status
Preview URL
Details

his/core/transaction-errors.md
:warning:Warning
View
Details

his/db2oledbv/data-consumer-issues.md
:warning:Warning
View
Details

his/db2oledbv/data-source-wizard.md
:warning:Warning
View
Details

his/esso/installing-password-synchronization.md
:warning:Warning
View
Details

his/esso/sso-security-recommendations.md
:warning:Warning
View
Details

technical-reference/alert-manager.md
:warning:Warning
View
Details

technical-reference/host-name-properties-dialog-box-wcf-extensions-tab-wcf-custom-adapter-send-handler.md
:warning:Warning
View
Details

technical-reference/host-name-properties-dialog-box-wcf-extensions-tab-wcf-custom-or-wcf-customisolated-adapter-receive-handler.md
:warning:Warning
View
Details

his/core/ti-in-a-non-dpl-environment3.md
:bulb:Suggestion
View
Details

his/core/ti-in-a-non-dpl-environment4.md
:bulb:Suggestion
View
Details

his/core/ti-tcp-ip-load-balancing2.md
:bulb:Suggestion
View
Details

his/core/tn3270-emulator1.md
:bulb:Suggestion
View
Details

his/core/tn5250-access1.md
:bulb:Suggestion
View
Details

his/core/token-ring-link-statistics2.md
:bulb:Suggestion
View
Details

his/core/tp-started2.md
:bulb:Suggestion
View
Details

his/core/trace-viewer1.md
:bulb:Suggestion
View
Details

his/core/tracing-and-debugging1.md
:bulb:Suggestion
View
Details

his/core/transaction-integrator-architecture1.md
:bulb:Suggestion
View
Details

his/core/transaction-size-vs-data-throughput2.md
:bulb:Suggestion
View
Details

his/core/transaction-size-vs-transaction-throughput2.md
:bulb:Suggestion
View
Details

his/core/transactional-data-flows-that-support-bounded-recordsets1.md
:bulb:Suggestion
View
Details

his/core/trm-format-for-the-tcp-trm-link-programming-model2.md
:bulb:Suggestion
View
Details

his/core/two-phase-commit2.md
:bulb:Suggestion
View
Details

his/core/understanding-cpi-c2.md
:bulb:Suggestion
View
Details

his/core/understanding-peer-to-peer-networking2.md
:bulb:Suggestion
View
Details

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

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

his/core/x-25-802-2-or-switched-sdlc-line-xids-exchanged-2.md
:bulb:Suggestion
View
Details

his/db2oledbv/data-access-tool1.md
:bulb:Suggestion
View
Details

his/db2oledbv/data-link-tool.md
:bulb:Suggestion
View
Details

his/db2oledbv/data-provider-error-codes.md
:bulb:Suggestion
View
Details

his/db2oledbv/data-type-mapping1.md
:bulb:Suggestion
View
Details

his/db2oledbv/installing-data-provider-version-6-0.md
:bulb:Suggestion
View
Details

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

his/db2oledbv/performance1.md
:bulb:Suggestion
View
Details

his/db2oledbv/protection1.md
:bulb:Suggestion
View
Details

his/db2oledbv/security2.md
:bulb:Suggestion
View
Details

his/esso/configuring-enterprise-single-sign-on1.md
:bulb:Suggestion
View
Details

his/esso/enterprise-single-sign-on1.md
:bulb:Suggestion
View
Details

his/esso/issoadmin-members.md
:bulb:Suggestion
View
Details

his/esso/issoadmin-methods.md
:bulb:Suggestion
View
Details

his/esso/issoconfigstore-setconfiginfo.md
:bulb:Suggestion
View
Details

his/esso/issolookup1-members.md
:bulb:Suggestion
View
Details

his/esso/issolookup1-methods.md
:bulb:Suggestion
View
Details

his/esso/issolookup2-members.md
:bulb:Suggestion
View
Details

his/esso/issolookup2-methods.md
:bulb:Suggestion
View
Details

his/esso/issomapper-members.md
:bulb:Suggestion
View
Details

his/esso/issomapper-methods.md
:bulb:Suggestion
View
Details

his/esso/issomapper2-members.md
:bulb:Suggestion
View
Details

his/esso/issomapping-members.md
:bulb:Suggestion
View
Details

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

his/core/transaction-errors.md

Line 43, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/p/?linkid=217339' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
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/db2oledbv/data-consumer-issues.md

Line 290, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=241525' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 301, 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/db2oledbv/data-source-wizard.md

Line 201, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkID=180763' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 123, 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/esso/installing-password-synchronization.md

Line 32, Column 1: [Warning-insecure-link] Link 'http://www.microsoft.com/downloads/details.aspx?FamilyID=C0964F2E-FA9F-4FC7-AC13-C43928EFEE9D&displaylang=en' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

his/esso/sso-security-recommendations.md

Line 58, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=24774' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 62, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=16731' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

technical-reference/alert-manager.md

Line 116, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?linkid=58869' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 116, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=58869' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

technical-reference/host-name-properties-dialog-box-wcf-extensions-tab-wcf-custom-adapter-send-handler.md

Line 36, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?linkid=163953' 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=163953' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

technical-reference/host-name-properties-dialog-box-wcf-extensions-tab-wcf-custom-or-wcf-customisolated-adapter-receive-handler.md

Line 36, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?linkid=163953' 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=163953' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

his/core/ti-in-a-non-dpl-environment3.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: TI in a Non-DPL Environment' is duplicated in 'core/ti-in-a-non-dpl-environment3.md(2,14)', 'core/ti-in-a-non-dpl-environment4.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'TI in a Non-DPL Environment' is duplicated with other articles: 'core/ti-in-a-non-dpl-environment3.md(17,1), core/ti-in-a-non-dpl-environment4.md(17,1)'. First level headings must be unique within a docset.

his/core/ti-in-a-non-dpl-environment4.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: TI in a Non-DPL Environment' is duplicated in 'core/ti-in-a-non-dpl-environment3.md(2,14)', 'core/ti-in-a-non-dpl-environment4.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'TI in a Non-DPL Environment' is duplicated with other articles: 'core/ti-in-a-non-dpl-environment3.md(17,1), core/ti-in-a-non-dpl-environment4.md(17,1)'. First level headings must be unique within a docset.

his/core/ti-tcp-ip-load-balancing2.md

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

his/core/tn3270-emulator1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: TN3270 Emulator' is duplicated in 'core/tn3270-emulator1.md(2,14)', 'install-and-config-guides/tn3270-emulator2.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'TN3270 Emulator' is duplicated with other articles: 'core/tn3270-emulator1.md(17,1), install-and-config-guides/tn3270-emulator2.md(17,1)'. First level headings must be unique within a docset.

his/core/tn5250-access1.md

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

his/core/token-ring-link-statistics2.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 37, 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/tp-started2.md

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

his/core/trace-viewer1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Trace Viewer' is duplicated in 'core/trace-viewer1.md(2,14)', 'install-and-config-guides/trace-viewer2.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Trace Viewer' is duplicated with other articles: 'core/trace-viewer1.md(17,1), install-and-config-guides/trace-viewer2.md(17,1)'. First level headings must be unique within a docset.

his/core/tracing-and-debugging1.md

Line 80, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

his/core/transaction-integrator-architecture1.md

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

his/core/transaction-size-vs-data-throughput2.md

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

his/core/transaction-size-vs-transaction-throughput2.md

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

his/core/transactional-data-flows-that-support-bounded-recordsets1.md

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

his/core/trm-format-for-the-tcp-trm-link-programming-model2.md

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

his/core/two-phase-commit2.md

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

his/core/understanding-cpi-c2.md

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

his/core/understanding-peer-to-peer-networking2.md

Line 22, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln05.gif'. Alt text is required for accessibility.
Line 37, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln06.gif'. Alt text is required for accessibility.
Line 44, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln07.gif'. Alt text is required for accessibility.

his/core/wipobjects.md

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

his/core/wipremoteenvs.md

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

his/core/x-25-802-2-or-switched-sdlc-line-xids-exchanged-2.md

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

his/db2oledbv/data-access-tool1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Data Access Tool' is duplicated with other articles: 'core/data-access-tool2.md(16,1), db2oledbv/data-access-tool1.md(17,1)'. First level headings must be unique within a docset.

his/db2oledbv/data-link-tool.md

Line 44, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

his/db2oledbv/data-provider-error-codes.md

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 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 100, 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/db2oledbv/data-type-mapping1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Data Type Mapping' is duplicated with other articles: 'core/data-type-mapping2.md(16,1), db2oledbv/data-type-mapping1.md(17,1)'. First level headings must be unique within a docset.

his/db2oledbv/installing-data-provider-version-6-0.md

Line 112, 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/db2oledbv/microsoft-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(16,1), db2oledbv/microsoft-ole-db-provider-for-db2.md(17,1)'. First level headings must be unique within a docset.

his/db2oledbv/performance1.md

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

his/db2oledbv/protection1.md

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

his/db2oledbv/security2.md

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

his/esso/configuring-enterprise-single-sign-on1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Configuring Enterprise Single Sign-On' is duplicated with other articles: 'core/configuring-enterprise-single-sign-on2.md(16,1), esso/configuring-enterprise-single-sign-on1.md(17,1)'. First level headings must be unique within a docset.

his/esso/enterprise-single-sign-on1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Enterprise Single Sign-On' is duplicated with other articles: 'core/enterprise-single-sign-on3.md(16,1), esso/enterprise-single-sign-on1.md(17,1)'. First level headings must be unique within a docset.

his/esso/issoadmin-members.md

Line 24, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 27, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 28, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 29, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 30, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.

his/esso/issoadmin-methods.md

Line 24, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 27, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 28, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 29, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 30, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.

his/esso/issoconfigstore-setconfiginfo.md

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

his/esso/issolookup1-members.md

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

his/esso/issolookup1-methods.md

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

his/esso/issolookup2-members.md

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

his/esso/issolookup2-methods.md

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

his/esso/issomapper-members.md

Line 24, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 27, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 28, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 29, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.

his/esso/issomapper-methods.md

Line 24, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 27, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 28, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 29, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.

his/esso/issomapper2-members.md

Line 23, 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/esso/issomapping-members.md

Line 24, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubproperty.gif'. Alt text is required for accessibility.
Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubproperty.gif'. Alt text is required for accessibility.
Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubproperty.gif'. Alt text is required for accessibility.
Line 27, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubproperty.gif'. Alt text is required for accessibility.
Line 28, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubproperty.gif'. Alt text is required for accessibility.
Line 34, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 35, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 36, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 37, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.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 246ce43:
:warning: Validation status: warnings

File
Status
Preview URL
Details

his/core/transaction-errors.md
:warning:Warning
View
Details

his/db2oledbv/data-consumer-issues.md
:warning:Warning
View
Details

his/db2oledbv/data-source-wizard.md
:warning:Warning
View
Details

his/esso/installing-password-synchronization.md
:warning:Warning
View
Details

his/esso/sso-security-recommendations.md
:warning:Warning
View
Details

technical-reference/alert-manager.md
:warning:Warning
View
Details

technical-reference/host-name-properties-dialog-box-wcf-extensions-tab-wcf-custom-adapter-send-handler.md
:warning:Warning
View
Details

technical-reference/host-name-properties-dialog-box-wcf-extensions-tab-wcf-custom-or-wcf-customisolated-adapter-receive-handler.md
:warning:Warning
View
Details

his/core/ti-in-a-non-dpl-environment3.md
:bulb:Suggestion
View
Details

his/core/ti-in-a-non-dpl-environment4.md
:bulb:Suggestion
View
Details

his/core/ti-tcp-ip-load-balancing2.md
:bulb:Suggestion
View
Details

his/core/tn3270-emulator1.md
:bulb:Suggestion
View
Details

his/core/tn5250-access1.md
:bulb:Suggestion
View
Details

his/core/token-ring-link-statistics2.md
:bulb:Suggestion
View
Details

his/core/tp-started2.md
:bulb:Suggestion
View
Details

his/core/trace-viewer1.md
:bulb:Suggestion
View
Details

his/core/tracing-and-debugging1.md
:bulb:Suggestion
View
Details

his/core/transaction-integrator-architecture1.md
:bulb:Suggestion
View
Details

his/core/transaction-size-vs-data-throughput2.md
:bulb:Suggestion
View
Details

his/core/transaction-size-vs-transaction-throughput2.md
:bulb:Suggestion
View
Details

his/core/transactional-data-flows-that-support-bounded-recordsets1.md
:bulb:Suggestion
View
Details

his/core/trm-format-for-the-tcp-trm-link-programming-model2.md
:bulb:Suggestion
View
Details

his/core/two-phase-commit2.md
:bulb:Suggestion
View
Details

his/core/understanding-cpi-c2.md
:bulb:Suggestion
View
Details

his/core/understanding-peer-to-peer-networking2.md
:bulb:Suggestion
View
Details

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

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

his/core/x-25-802-2-or-switched-sdlc-line-xids-exchanged-2.md
:bulb:Suggestion
View
Details

his/db2oledbv/data-access-tool1.md
:bulb:Suggestion
View
Details

his/db2oledbv/data-link-tool.md
:bulb:Suggestion
View
Details

his/db2oledbv/data-provider-error-codes.md
:bulb:Suggestion
View
Details

his/db2oledbv/data-type-mapping1.md
:bulb:Suggestion
View
Details

his/db2oledbv/installing-data-provider-version-6-0.md
:bulb:Suggestion
View
Details

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

his/db2oledbv/performance1.md
:bulb:Suggestion
View
Details

his/db2oledbv/protection1.md
:bulb:Suggestion
View
Details

his/db2oledbv/security2.md
:bulb:Suggestion
View
Details

his/esso/configuring-enterprise-single-sign-on1.md
:bulb:Suggestion
View
Details

his/esso/enterprise-single-sign-on1.md
:bulb:Suggestion
View
Details

his/esso/issoadmin-members.md
:bulb:Suggestion
View
Details

his/esso/issoadmin-methods.md
:bulb:Suggestion
View
Details

his/esso/issoconfigstore-setconfiginfo.md
:bulb:Suggestion
View
Details

his/esso/issolookup1-members.md
:bulb:Suggestion
View
Details

his/esso/issolookup1-methods.md
:bulb:Suggestion
View
Details

his/esso/issolookup2-members.md
:bulb:Suggestion
View
Details

his/esso/issolookup2-methods.md
:bulb:Suggestion
View
Details

his/esso/issomapper-members.md
:bulb:Suggestion
View
Details

his/esso/issomapper-methods.md
:bulb:Suggestion
View
Details

his/esso/issomapper2-members.md
:bulb:Suggestion
View
Details

his/esso/issomapping-members.md
:bulb:Suggestion
View
Details

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

his/core/transaction-errors.md

Line 43, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/p/?linkid=217339' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
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/db2oledbv/data-consumer-issues.md

Line 290, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=241525' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 301, 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/db2oledbv/data-source-wizard.md

Line 201, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkID=180763' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 123, 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/esso/installing-password-synchronization.md

Line 32, Column 1: [Warning-insecure-link] Link 'http://www.microsoft.com/downloads/details.aspx?FamilyID=C0964F2E-FA9F-4FC7-AC13-C43928EFEE9D&displaylang=en' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

his/esso/sso-security-recommendations.md

Line 58, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=24774' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 62, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=16731' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

technical-reference/alert-manager.md

Line 116, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?linkid=58869' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 116, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=58869' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

technical-reference/host-name-properties-dialog-box-wcf-extensions-tab-wcf-custom-adapter-send-handler.md

Line 36, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?linkid=163953' 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=163953' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

technical-reference/host-name-properties-dialog-box-wcf-extensions-tab-wcf-custom-or-wcf-customisolated-adapter-receive-handler.md

Line 36, Column 1: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?linkid=163953' 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=163953' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

his/core/ti-in-a-non-dpl-environment3.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: TI in a Non-DPL Environment' is duplicated in 'core/ti-in-a-non-dpl-environment3.md(2,14)', 'core/ti-in-a-non-dpl-environment4.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'TI in a Non-DPL Environment' is duplicated with other articles: 'core/ti-in-a-non-dpl-environment3.md(17,1), core/ti-in-a-non-dpl-environment4.md(17,1)'. First level headings must be unique within a docset.

his/core/ti-in-a-non-dpl-environment4.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: TI in a Non-DPL Environment' is duplicated in 'core/ti-in-a-non-dpl-environment3.md(2,14)', 'core/ti-in-a-non-dpl-environment4.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'TI in a Non-DPL Environment' is duplicated with other articles: 'core/ti-in-a-non-dpl-environment3.md(17,1), core/ti-in-a-non-dpl-environment4.md(17,1)'. First level headings must be unique within a docset.

his/core/ti-tcp-ip-load-balancing2.md

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

his/core/tn3270-emulator1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: TN3270 Emulator' is duplicated in 'core/tn3270-emulator1.md(2,14)', 'install-and-config-guides/tn3270-emulator2.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'TN3270 Emulator' is duplicated with other articles: 'core/tn3270-emulator1.md(17,1), install-and-config-guides/tn3270-emulator2.md(17,1)'. First level headings must be unique within a docset.

his/core/tn5250-access1.md

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

his/core/token-ring-link-statistics2.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 37, 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/tp-started2.md

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

his/core/trace-viewer1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Trace Viewer' is duplicated in 'core/trace-viewer1.md(2,14)', 'install-and-config-guides/trace-viewer2.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Trace Viewer' is duplicated with other articles: 'core/trace-viewer1.md(17,1), install-and-config-guides/trace-viewer2.md(17,1)'. First level headings must be unique within a docset.

his/core/tracing-and-debugging1.md

Line 80, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

his/core/transaction-integrator-architecture1.md

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

his/core/transaction-size-vs-data-throughput2.md

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

his/core/transaction-size-vs-transaction-throughput2.md

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

his/core/transactional-data-flows-that-support-bounded-recordsets1.md

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

his/core/trm-format-for-the-tcp-trm-link-programming-model2.md

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

his/core/two-phase-commit2.md

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

his/core/understanding-cpi-c2.md

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

his/core/understanding-peer-to-peer-networking2.md

Line 22, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln05.gif'. Alt text is required for accessibility.
Line 37, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln06.gif'. Alt text is required for accessibility.
Line 44, Column 3: [Suggestion-alt-text-missing] Missing alternate text for image '../core/media/pln07.gif'. Alt text is required for accessibility.

his/core/wipobjects.md

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

his/core/wipremoteenvs.md

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

his/core/x-25-802-2-or-switched-sdlc-line-xids-exchanged-2.md

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

his/db2oledbv/data-access-tool1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Data Access Tool' is duplicated with other articles: 'core/data-access-tool2.md(16,1), db2oledbv/data-access-tool1.md(17,1)'. First level headings must be unique within a docset.

his/db2oledbv/data-link-tool.md

Line 44, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

his/db2oledbv/data-provider-error-codes.md

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 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 100, 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/db2oledbv/data-type-mapping1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Data Type Mapping' is duplicated with other articles: 'core/data-type-mapping2.md(16,1), db2oledbv/data-type-mapping1.md(17,1)'. First level headings must be unique within a docset.

his/db2oledbv/installing-data-provider-version-6-0.md

Line 112, 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/db2oledbv/microsoft-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(16,1), db2oledbv/microsoft-ole-db-provider-for-db2.md(17,1)'. First level headings must be unique within a docset.

his/db2oledbv/performance1.md

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

his/db2oledbv/protection1.md

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

his/db2oledbv/security2.md

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

his/esso/configuring-enterprise-single-sign-on1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Configuring Enterprise Single Sign-On' is duplicated with other articles: 'core/configuring-enterprise-single-sign-on2.md(16,1), esso/configuring-enterprise-single-sign-on1.md(17,1)'. First level headings must be unique within a docset.

his/esso/enterprise-single-sign-on1.md

Line 17, Column 1: [Suggestion-duplicate-h1s] H1 'Enterprise Single Sign-On' is duplicated with other articles: 'core/enterprise-single-sign-on3.md(16,1), esso/enterprise-single-sign-on1.md(17,1)'. First level headings must be unique within a docset.

his/esso/issoadmin-members.md

Line 24, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 27, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 28, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 29, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 30, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.

his/esso/issoadmin-methods.md

Line 24, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 27, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 28, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 29, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 30, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.

his/esso/issoconfigstore-setconfiginfo.md

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

his/esso/issolookup1-members.md

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

his/esso/issolookup1-methods.md

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

his/esso/issolookup2-members.md

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

his/esso/issolookup2-methods.md

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

his/esso/issomapper-members.md

Line 24, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 27, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 28, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 29, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.

his/esso/issomapper-methods.md

Line 24, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 27, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 28, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 29, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.

his/esso/issomapper2-members.md

Line 23, 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/esso/issomapping-members.md

Line 24, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubproperty.gif'. Alt text is required for accessibility.
Line 25, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubproperty.gif'. Alt text is required for accessibility.
Line 26, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubproperty.gif'. Alt text is required for accessibility.
Line 27, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubproperty.gif'. Alt text is required for accessibility.
Line 28, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubproperty.gif'. Alt text is required for accessibility.
Line 34, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 35, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 36, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.gif'. Alt text is required for accessibility.
Line 37, Column 2: [Suggestion-alt-text-missing] Missing alternate text for image '../esso/media/pubmethod.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


Style Maps

Sorry, this branch is no longer mergeable - feel free to rebase against current master and re-submit.


Experiment with C++ mesh export backdoor

LuxCore code:
C++ code: https://github.com/LuxCoreRender/LuxCore/blob/master/src/luxcore/pyluxcoreforblender.cpp#L388 1
Python code: https://github.com/LuxCoreRender/BlendLuxCore/blob/master/export/blender_object.py#L190 1

#345


You provided 'undefined' where a stream was expected. You can provide an Observable, Promise, Array, or Iterable.

I am trying to use retryWhen  operator , my requirement is that i need to make a call to refresh token when i got 401 error ,   when new token generated only i need to retry again http call . i am unable to  do that can you try to help me with the below code.  What i am trying to do is , after token gets generated by newTokengenerator method then only i need to make this http calls to retry with new token. Can someone help with this please.
private refreshToken(error) {
       return error
           .flatMap((error: any) => {
               if (error.status === 401) {
                   let count = 0;
                  return this.httpPollingService.newTokenGenerator((res) => {
                      console.error(count++, 'http response ...', res, this.ins.IMP.InitData.Token);
                      return Observable.of(error.status).delay(2000);
                   });
               } else {
                   return Observable.throw(error);
               }

           }).take(3).concat(Observable.throw(error));
   }

RxJS version 5.5:
Code to reproduce:
Expected behavior:
Actual behavior:
Additional information:

Hey @ajaykumarReddy have you tried asking on Stack Overflow or the various community chats? This is actually the bug tracker 🙂

Yes  @jayphelps , I posted in stack Overflow as well but no answer i got it.

Cool, can you post the link here? I’m happy to answer it. 🙂

@jayphelps  here is the link  . https://stackoverflow.com/questions/50103048/how-to-use-angular-service-inside-rxjs-retrywhen-method.

Nothing to address or fix. Thanks for moving this to StackOverflow.


Fix Sheets not showing '0' when Formatting is Automatic

old behavior:

new behavior:

Sorry, I'm still a little new to pull requests, and I think I added more than just the one commit to this PR. I can submit another one if it isn't clear what I changed (literally just a single character in SheetFieldAttributes.cs).

@Monsoonexe, no worries at all.  PRs can be a little confusing at first.
Do you mind creating a brand new pull request and include just the single commit that enabled you to fix this issue?  It will be easier in the future to track down the request and the actual code that was updated alongside it.
Thank you for finding this issue and working to fix it for other folks to be able to use.

No problem! I'll submit a cleaner pull request soon.
On Mon, May 16, 2022 at 2:50 PM Steve Winward @.***>
wrote:

@Monsoonexe https://github.com/Monsoonexe, no worries at all. PRs can
be a little confusing at first.
Do you mind creating a brand new pull request and include just the single
commit that enabled you to fix this issue? It will be easier in the future
to track down the request and the actual code that was updated alongside it.
Thank you for finding this issue and working to fix it for other folks to
be able to use.
—
Reply to this email directly, view it on GitHub
https://github.com/SteveWinward/GoogleSheetsWrapper/pull/8#issuecomment-1128172288,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKNKVBKDBIF7IPRFRXTEDELVKK7KXANCNFSM5WCYHHSA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Feature request: Display meta information

It would be nice if nix-tree would also display meta information for each package, like for example the license.

Great idea! Just to start the brainstorming:

Should we simply have a "details" modal showing the meta information for the selected package, or is there any information we can/should show inline or in the modeline?
How do we get the information. The only thing nix-tree currently has access to is the metadata from nix path-info --json per every store path, but that doesn't contain much information:

% nix path-info --json /nix/store/zyvf9k2i8cma5pvb9mrvh7fsqjhbf5py-krb5-1.18 | jq .
[
  {
    "path": "/nix/store/zyvf9k2i8cma5pvb9mrvh7fsqjhbf5py-krb5-1.18",
    "narHash": "sha256-MKC140uRzp0Mvn5kZFKo1o/YKUtJJvt9n7eRc16gNCI=",
    "narSize": 4081944,
    "references": [
      "/nix/store/6rv3vhb87bgx7i205ngb4gz3gnzypnhl-keyutils-1.6.3-lib",
      "/nix/store/7figba9q8yrgz4gj9yhqgjri97h9snsb-openssl-1.1.1g",
      "/nix/store/bdf8iipzya03h2amgfncqpclf6bmy3a1-glibc-2.32",
      "/nix/store/k8p54jg8ipvnfz435mayf5bnqhw4qqap-bash-4.4-p23",
      "/nix/store/sbfj9lhpfi5v9vwrdf9my8l1m7cwbi37-libedit-20191231-3.1",
      "/nix/store/zyvf9k2i8cma5pvb9mrvh7fsqjhbf5py-krb5-1.18"
    ],
    "registrationTime":<PHONE_NUMBER>,
    "signatures": [
      "cache.nixos.org-1:XoTFbWjf7GsVJsATyMZDBF4DUl7k/V/9GL/PZp+hbX/nQ7uT7Pjr0W0F75FTIMSdp5AojKp88c/OpZXJQ6SqBg=="
    ]
  }
]

Do you know a way to obtain that license information or any other metadata given a store path?

I guess the bottom right corner of the screen could have enough space for it.
Getting the metadata could actually be a problem. The metadata is specified in the nixpkgs expression for every package and can be retrieved via pkgs.{package}.meta. But I don't know if there is a way to get the nix attribute for a store path.
Seems like the problem is a bit more complicated than originally thought.

Getting the metadata could actually be a problem. The metadata is specified in the nixpkgs expression for every package and can be retrieved via pkgs.{package}.meta. But I don't know if there is a way to get the nix attribute for a store path.

Yeah, I couldn't find a solution for this either. I'm going to leave this issue open since I still think it would be a useful piece of information, and will come back to it if I can figure out a nice way. Please let me know if you can think of any!
Thanks again.


Question: change background for a complete terminal line

When I console.log a text like this:
console.log(chalk.bgWhite.black('hello world'));

It creates the following output:

Is there any way that I can format the while line other than just then encapsulated words.

Kind of a hack, but try this:
const padConsoleWidth = (s, stream = process.stdout) => s + ' '.repeat(stream.columns - s.length);
console.log(chalk.bgWhite.black(padConsoleWidth('Hello, World!')));

This won't work in all cases but should work in most of them.

Thank you I will give it a try.

Unfortunately not; some terminal emulators will color the rest of the line if you insert the newline before the render mode reset but that's inconsistent behavior at best.
This is the most "correct" way (keeping in mind that all ANSI escape/TTY stuff is horribly archaic).
Hope that helps :)

@Qix-  At least it gave me a new idea. Currently used chalk for syntax highlighting with PrismJS with console.log in NodeJS.
Some themes there have some strange colouring.
Details: https://t.co/1gyFTTVEm6?amp=1


Allow to customize CSS to differentiate multiple instances

As ...
Patti - Platform Admin
I want ...
to be able to customize the CSS (maybe the background-color but not just this) of a Nautobot instance
So that ...
Users (operators, developpers, ..) are able to easily distinguish the different instances (dev, test, staging, prod, ...)
I know this is done when...

An option to input CSS is present in the admin section
This option is overridable using settings.py (to allow copying data from an instance to another while keeping this property)
The CSS is applied on every pages

Currently, the only option is to set a banner, but having a banner on each instance with the same blue color doesn't help to differentiate without reading the banner text.
Optional - Feature groups this request pertains to.

[ ] Automation
[ ] Circuits
[ ] DCIM
[ ] IPAM
[ ] Misc (including Data Sources)
[ ] Organization
[ ] Plugins (and other Extensibility)
[ ] Security (Secrets, etc)
[ ] Image Management
[X] UI/UX
[ ] Documentation
[ ] Other (not directly a platform feature)

Database Changes

Add an option?

External Dependencies
None ?

This is certainly not what you'll want to implement, but here's what I'm using to add a custom style (path to the files):

patcher.py

try:
  import nautobot, rest_framework
  nautobot_base_path = nautobot.__path__[0]
  rest_framework_base_path = rest_framework.__path__[0]
  del nautobot, rest_framework
except Exception:
  print('Unable to locate Nautobot or Django REST framework installation path')
  raise SystemExit(1)

templates = (
    (nautobot_base_path, 'core/templates/base.html'),
    (nautobot_base_path, 'core/templates/admin/base.html'),
    (nautobot_base_path, 'core/templates/graphene/graphiql.html'),
    (rest_framework_base_path, 'templates/rest_framework/base.html'),
    # Alternative: nautobot/core/templates/rest_framework/api.html
)
# Alternative: nautobot/core/templates/inc/media.html + graphql

where = '</head>'
patch = '''\
    {% if settings.MY_CUSTOM_STYLE %}
    <style>{{ settings.MY_CUSTOM_STYLE | safe }}</style>
    {% endif %}
'''  # '    {% if se..\n    <styl..\n    {% en..\n'

for pkg_path, template_path in templates:
    with open(f'{pkg_path}/{template_path}', 'r+') as fh:
        content = fh.read()
        content_len = len(content)
        content = content.replace(where, patch + where)

        if len(content) == content_len:
            print(f'Unable to patch file {fh.name!r}')
            raise SystemExit(1)

        fh.seek(0)
        fh.truncate()
        fh.write(content)

    print(f'Patched {pkg_path.split("/")[-1]}{template_path!r}')

settings.py

# .navbar-default, .footer { background: linear-gradient(to right, #f8f8f8, moccasin); }
if os.getenv('MY_CUSTOM_STYLE'):
    MY_CUSTOM_STYLE = os.getenv('MY_CUSTOM_STYLE').strip()
elif os.getenv('MY_CUSTOM_STYLE_FILE'):
    MY_CUSTOM_STYLE = open(
        os.getenv('MY_CUSTOM_STYLE_FILE'),
        mode='r',
        encoding='utf-8'
    )

Brainstorming on a feature-set and requirements here:

Given that we'll eventually want to set a content-security-policy in nautobot that disallows unsafe-inline, we probably don't want to add a feature that directly allows for injection of JS and CSS as a string. It'd be safer to instead provide a way to easily add another .js or .css file to inc/media.html and inc/javascript.html.
One way to do this would be via Apps, as any App can bundle additional static-files which we could then cleanly reference without needing to modify any content-security-policy configuration (as would be required to allow resources to load from a different domain). Different instances could install different apps (or different versions of the same app) to provide the desired differentiaion.
A less elegant approach would be to allow the specification of arbitrary URLs to load from as a part of the settings, but that will likely run afoul of content-security-policy restrictions.


Any guidance on how one might add vSphere coverage here?

I note you have charts for AWS, DO and Equinix. Can you advise if this approach can also cater for deploying an RKE2 cluster to vSphere yet? Thanks.

Creating a template for vsphere is very similar, you just need to create a vsphere machine/node config instead of a aws/do/equinix one. You can find an example here: https://github.com/rancher/cluster-template-examples/blob/main/charts/templates/nodeconfig-vsphere.yaml.
Alternatively, you can also create a cluster manually through the UI and then have a look at the VmwarevsphereConfig resources created in the local cluster. They are also linked on the cluster detail page under "Related resources".


[0.9.0] Parser::chain() becomes too generic to require additional type annotations at many places

This implementation (https://github.com/zesterer/chumsky/releases/tag/0.9)

Option<Vec<T>> and Vec<Option<T>> now implement Chain<T> ..

causes an abundance of possible type candidates, requiring us to give additional type parameter information at many places:

error[E0283]: type annotations needed
--> src/FILE.rs:N:M
|
N |    CODE
|      ^^^^^ cannot infer type of the type parameter U declared on the associated function chain
|
= note: multiple impls satisfying Vec<_>: chumsky::chain::Chain<_> found in the chumsky crate:
- impl chumsky::chain::Chain for T;
- impl chumsky::chain::Chain for Vec<Option>;
- impl chumsky::chain::Chain for Vec;
note: required by a bound in chumsky::Parser::chain
--> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/chumsky-0.9.0/src/lib.rs:704:12

Can we implement different methods (such as chain_iter/chain_many, chain_option/chain_unwrap) having different signatures, instead of giving one trait to different (but equally quantification-related) types?

This is indeed unfortunate and undesirable.
Resolving this should be relatively easy in practice: As you can see, the second type parameter is the one to collect into, so .chain::<_, Vec<Option<_>>, _>() (for example) should be sufficient for the compiler to disambiguate between the impls.
I am somewhat reluctant to put substantial work into resolving this, however, because chain has been ripped out in the zero-copy rewrite, given that map_slice covers almost all use-cases much more efficiently and elegantly and with fewer ugly corner cases (such as this very issue, for example).
I hope this answer isn't too disappointing.


Updates for MOI 0.8.2

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b03be7f). Click here to learn what that means.
The diff coverage is 80%.

@@            Coverage Diff            @@
##             master      #84   +/-   ##
=========================================
  Coverage          ?   83.91%
=========================================
  Files             ?        5
  Lines             ?      858
  Branches          ?        0
=========================================
  Hits              ?      720
  Misses            ?      138
  Partials          ?        0

Impacted Files
Coverage Δ

src/MOI_wrapper.jl
83.42% <80%> (ø)

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 b03be7f...629c1eb. Read the comment docs.


Unable to save configuration when having cellphone-number as username

Describe the bug
I have my cellphone-number as username in Volvo app. This has not been a problem earlier, where i used format "+4670XXXXXXX" as username in the addon. But since some versions back i get an error when i try to save the config.
To Reproduce:
Steps to reproduce the behavior:

Change username to a cellphone-number - i use "" as brackets. In my case i write the following in my config file
username: "+4670XXXXXX"

Version info:
I use version 1.8.4
Screenshot of error message:

Ah what ? It is possible to use a phone number as username ? Nevermind....

Ah what ? It is possible to use a phone number as username ? Nevermind....

Yes it is :). So there seems to be some kind of validation that restrict me from setting my phone number as usernmae. Is it possobile to change?

Yes, already done. Fix will be up in a few minutes

Please try v1.8.5!

It’s working now. Thanks!


Several improvements

Here are some of my last changes I haven't pushed. I think the last one (prefetching) has some limitation I haven't documented unfortunately.

Awesome, thanks for this!

Thanks to you for taking over!

@joeyjoejoejr Please feel free to ask if you have any questions regarding this pull request.

hey @witrin really liking this PR. Would you still be available for some questions?


Devel

Make ISAFW plugin set configurable

Can one of the admins verify this patch?

I have verified it on my local builds, I am merging it now.


Added a trailing cursor effect for enhanced user interaction

This pull request introduces a trailing cursor effect to improve user interaction and create a more dynamic interface. The effect follows the user's mouse movement, providing a visually engaging experience that complements the overall design.
#380
https://github.com/user-attachments/assets/362e4066-1d8c-4e04-82a9-e9bd09042d8d

Summary by CodeRabbit

New Features

Introduced animated circles that follow the mouse cursor, enhancing visual interactivity on the webpage.
Added multiple circles with varying colors and sizes that respond dynamically to user movement.

@akhulisumit pr closed as issue was not assigned


3.6.0 : warning compiled with 1 warning 4:12:23 pm warning in<EMAIL_ADDRESS>"export 'default' (imported as 'yn') was not found in 'date-fns-tz'

Describe the bug
After updating to version 3.6.0, datepicker makes my app fail to execute.
npm run serve display a warning in the terminal :
 WARNING  Compiled with 1 warning

 warning  in<EMAIL_ADDRESS>
"export 'default' (imported as 'Yn') was not found in 'date-fns-tz'

When I try to start the app in the browser, console displays this error :
vue-datepicker.js?5141:218 Uncaught TypeError: Cannot destructure property 'utcToZonedTime' of 'date_fns_tz__WEBPACK_IMPORTED_MODULE_2__.default' as it is undefined.

Proposal, search for solution
Seems the problem is located in this file date-fns-tz src/VueDatePicker/components/composables/utils.ts :
Line 22 to 24
import dateFnsTz from 'date-fns-tz';

const { utcToZonedTime, zonedTimeToUtc } = dateFnsTz;

The import statement refer to a module which has no export default.
Import should probably be something like :
import { utcToZonedTime, zonedTimeToUtc } from 'date-fns-tz';

Temporary solution
Downgrading to 3.5.3 in my package.json

same issue

same issue here

I believe I have the same issue since I updated with latest version. The error message is different though:
SyntaxError: ambiguous indirect export: default

Will publish a fix later today.

The fix is published and should be good now, let me know if the issue still persists.


Added possibility to specify sway output or X screen

Hello, I added a possibility to specify a sway output or X screen using the -o/--output option, and -k/--kill-swaybg option so the user can specify whether or not they want to kill existing swaybg processes. I also updated the README file to reflect these changes.
The motivation behind these additions was me moving from i3 to sway and not finding an alternative to the feh functionality I was using, specifically picking a picture from a directory randomly for each output.
Now it can be done with this tool if you specify each output using the -o flags when using the random mode.

Thanks again. I did some refactoring, and also changed --kill to --keep, flipping its behaviour. This makes it so that leaving -k out retains the original behaviour.

Nice! I think the --keep option is better too.


indentation error in  k8s.io/docs/tasks/administer-cluster/kms-provider/

This is a Bug Report

Problem:
There are indentation errors in the yaml files of EncryptionConfiguration. For example in the following yaml, lines after "- secrets" should indent two to the right.

Proposed Solution:
Correct the indentation errors.
Page to Update:
https://kubernetes.io/docs/tasks/administer-cluster/kms-provider/

Is it right to have
resources:
  - resources:

in the fixed page?

Is it right to have
resources:
  - resources:

in the fixed page?

I checked the preview page, and it's still wrong. I've close my PR.

It should looks like this
apiVersion: apiserver.config.k8s.io/v1
kind: EncryptionConfiguration
resources:
- resources:
  - secrets
  providers:
  - kms:
      name: myKmsPlugin
      endpoint: unix:///tmp/socketfile.sock
      cachesize: 100
      timeout: 3s
  - identity: {}

or
apiVersion: apiserver.config.k8s.io/v1
kind: EncryptionConfiguration
resources:
  - resources:
      - secrets
    providers:
      - kms:
          name: myKmsPlugin
          endpoint: unix:///tmp/socketfile.sock
          cachesize: 100
          timeout: 3s
      - identity: {}

"secrets" is the subcontent of the second "resources", and "providers" is with the same level of the second "resources".
Although I modified the markdown, the rendered webpage is still wrong.

/priority backlog
/language en
/help

/remove-lifecycle rotten
/assign


Use BuchheimWalkerConfiguration to show tree merge node has problem

I use BuchheimWalkerConfiguration like this, there are 2 branch and one merge node, it's OK
`graph.addEdge(node1, node2, paint: Paint()..color = Colors.red);
graph.addEdge(node2, node6);
graph.addEdge(node6, node5);
graph.addEdge(node2, node3);
graph.addEdge(node3, node4);
graph.addEdge(node4, node5);`

but if i change the order like this, it will show wrong connect line
`graph.addEdge(node1, node2, paint: Paint()..color = Colors.red);
graph.addEdge(node2, node3);
graph.addEdge(node3, node4);
graph.addEdge(node4, node5);
graph.addEdge(node2, node6);
graph.addEdge(node6, node5);`

Basically  BuchheimWalker is for treelayouts only, if you want merged nodes, suggest you use Sugiyama

@nabil6391 Yes, I checked code both Sugiyama and  FruchtermanReingoldAlgorithm, but i found they don't support change  orientation to horizontal. can add this feature to them?

Hm that is correct, yes I would prefer to add them but do not think it can be done soon.

@nabil6391 OK, Thank you very much! I will continue to pay attention and wait.

Added support for different orientation in 0.6.5. Try it out. Closing for now.


Improve TestServer support for Response.StartAsync

Addresses #8660
re: https://github.com/aspnet/AspNetCore/issues/8660#issuecomment-476435564

Can this be merged as is or does it require more changes?


Add dict|dict and dict|=dict

This change adds support for the x | y operation (ordered union) in dictionaries and the in-place x |= y statement, in which the resulting value of x aliases the original, which is mutated.
Spec change:  https://github.com/bazelbuild/starlark/pull/215
Java change: https://github.com/bazelbuild/bazel/pull/14540

Ping @brandjon ...


Data downloads page for new version of Platform

Currently, the classic (Angular) version of the Platform allows users to download the evidence, association, target list, disease list, safety, baseline expression, and tractability data files.
The ETL pipelines for the new (React) version of the Platform allow us to increase the number of files that we make available for download. These pipelines generate the following files:
gs://open-targets-data-releases/21.02/output/ETL/aotf/clickhouse/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/aotf/elasticsearch/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/associations/direct/byDatasource/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/associations/direct/byDatatype/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/associations/direct/byOverall/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/associations/indirect/byDatasource/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/associations/indirect/byDatatype/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/associations/indirect/byOverall/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/cancerBiomarkers/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/disease_hpo/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/diseases/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/drugs/drug/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/drugs/indication/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/drugs/mechanism_of_action/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/eco/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/evidences/failed/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/evidences/stats/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/evidences/succeeded/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/expression/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/hpo/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/interactions/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/interactions_evidence/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/knownDrugs/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/mousePhenotypes/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/openfda-faers/agg_by_chembl/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/openfda-faers/agg_by_chembl_parquet/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/openfda-faers/agg_critval_drug-parquet/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/openfda-faers/agg_critval_drug/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/openfda-faers/agg_critval_drug_csv/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/reactome/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/search/diseaseIndex/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/search/drugIndex/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/search/targetIndex/_SUCCESS
gs://open-targets-data-releases/21.02/output/ETL/targets/_SUCCESS

To optimise and streamline the maintenance of the data downloads page (https://beta.targetvalidation.org/downloads), the back-end team will produce a static JSON file with a list of datasets available for download. This list will include:

Path (which will function as the ID for each entry)
Format(s)
Version of data
Size of data (specifically size of entire directory with all related data files)

An example of the proposed JSON is below:
{
  "data": [
   {
     "version": "21.02",
     "datasets": [
       {
         "path": "/drug/indication",
         "format": "json",
         "directory_size": "500mb"
       },
       {
        "path": "/drug/indication",
        "format": "parquet",
        "directory_size": "534mb"
      },
      {
        "path": "/evidences/succeeded/sourceId=chembl",
        "format": "json",
        "directory_size": "52mb",
      }
     ]
   }
  ]
}

The front-end will access the file either through Google Cloud or the GraphQL API, retrieve the list of files available for download, and display the list on the /downloads page. As part of this process, the front-end will also be responsible for:

Creating and maintaining a mapping file that contains the relevant annotation per entry/path (table category, label, description)
Blacklisting files that should not be displayed on the page (e.g. search index)
Displaying the gsutil command to access the data (listing files and downloading)

After discussions amongst the team, a few points were were noted for further discussion:

Unable to provide single click to download multiple parquet or JSON files and so front-end can display link to Google Cloud Console and gsutil script to list files in directory and download files
Should we include number of files available in a given directory in JSON file?
For optimal testing, deployment environments (production, QA, dev, etc.) should have individual static JSON with links to relevant files (e.g. static file for production points to files in open-targets-prod releases directory whereas static file for QA points to files in open-targets-eu-dev releases directory
Initially offer JSON files only for download
Revamp documentation to help users self-identify which type of data access they need (basic - UI and table downloads; intermediate - GraphQL playground; advanced - BigQuery; high-powered - data downloads)

To do:

[x] Normalise dataset naming
[x] Agree on structure of iles (nested or flattened) and clean up root directory
[ ] Generate a sample JSON file representing the table of datasets (filtering by _SUCCESS dataset)
[ ] Check if any dataset copied but not processed by any ETL
[ ] Agree on how previous data files (pre 21.02) will be displayed
[ ] Create mapping file with list with renamed files, description, and category

explore idea about generating schema and dataset description within the step

Epic closed as initial implementation of data downloads page available. Further work (e.g. exposing new datasets, including links to BigQuery and GraphQL) will be captured in subsequent tickets.


when there is a '-' in the mail of the user, the DBNAME is unreachable on Cloudant Dashboard.(

That seems like a quirk in Cloudant. Is it available through the normal HTTP API?
One option would be to escape the "-" character in addition to the others.

Hey Colin !!!! I wish you a great year!!
Yes :) I know where you do that in your code I'll propose a correction !
Take care

Yes it is accessible through the normal http api

You may also file an issue with Cloudant, since the "-" character is legal under CouchDB specs.

Cloudant feedback :
I can reproduce your problem from our side. Actually you can create databases with "$" or "-" but both cannot be used together when creating databases. We already noticed our developers about this issue, but cannot give an ETA when it is going to be fixed. Apologies for the inconvenience that caused.

@ronyrun good work!

Cloudant feedback :
Unfortunately, we cannot provide an ETA of when this issue can be resolved. The best option will be not to use the symbols together in a database name.
Regards,
Mercy
--
Mercy Ilade - Cloudant Support

I will modify the code to escape dashes then.

Great Thank You so much Colin


Confusion in inst2vec_preprocess.py when reading code

When I reading code in inst2vec_preprocess.py, I find in line 865 that
assert check is not None, "Could not match argument list in:\n" + line + "\nFunction:\n" + func_name
may have to change to
assert check is None.
But  I'm confused and don't know whether I should change it.

def get_num_args_func(line, func_name=None):
    """
    Get the number of arguments in a line containing a function
    :param line: LLVM IR line
    :param func_name: function name
    :return num_args: number of arguments
            arg_list: list of arguments
    """
    modif_line = re.sub(r'<[^<>]+>', '', line)  # commas in vectors/arrays should not be counted as argument-separators
    arg_list_ = find_outer_most_last_parenthesis(modif_line)  # get last parenthesis
    if arg_list_ is None:
        # Make sure that this is the case because the function has no arguments
        # and not because there was in error in regex matching
        check = re.match(rgx.func_call_pattern + r'\(\)', modif_line)
        **_assert check is not None, "Could not match argument list in:\n" + line + "\nFunction:\n" + func_name_**
        num_args = 0
        arg_list = ''
    elif arg_list_ == '()':
        # Make sure that this is the case because the function has no arguments
        # and not because there was in error in regex matching
        check = re.match(rgx.func_call_pattern + r'\(\)', modif_line)
        if check is None:
            check = re.search(r' asm (?:sideeffect )?(\".*\")\(\)', modif_line)
        if check is None:
            check = re.search(rgx.local_id + r'\(\)', modif_line)
        if check is None:
            okay = line[-2:] == '()'
            if not okay:
                check = None
            else:
                check = True
        assert check is not None, "Could not match argument list in:\n" + line + "\nFunction:\n" + func_name
        num_args = 0
        arg_list = ''
    else:
        arg_list = arg_list_[1:-1]
        arg_list = re.sub(r'<[^<>]+>', '', arg_list)
        arg_list_modif = re.sub(r'\([^\(\)]+\)', '', arg_list)
        arg_list_modif = re.sub(r'\([^\(\)]+\)', '', arg_list_modif)
        arg_list_modif = re.sub(r'\([^\(\)]+\)', '', arg_list_modif)
        arg_list_modif = re.sub(r'\([^\(\)]+\)', '', arg_list_modif)
        arg_list_modif = re.sub(r'\"[^\"]*\"', '', arg_list_modif)
        arg_list_modif = re.sub(r'{.*}', '', arg_list_modif)
        num_args = len(re.findall(',', arg_list_modif)) + 1

    return num_args, arg_list

The assertion is correct. It checks for different regular expressions, and if there is no match continues to the next one. If the last check fails, then check is None and the assertion should fail. In any other case, the check is successful and execution should continue.
Why do you think it should be the opposite?

I think that if it goes to the branch   if arg_list_ is None: , that check must be None (as it found no "( )"). And  assert will meet False and assertion will fail.
But in this case, assertion in this brach will always fail. Does it mean that this brach should just not be executed?

Or it is the debug code left after testing the function find_outer_most_last_parenthesis. If it is that case, I understand it and the comments there. When I first see it, I just got confused and didn't realize the meaning of this code.

Yes, the assertion and regexp in the branch is a sanity check meant to make sure that find_outer_most_last_parenthesis didn't miss an empty argument list somewhere.

Thanks for your reply! Thanks for your outstanding work! I really learn a lot from it.

Happy to help :)


Add EIP-7251 spec: Increase MAX_EFFECTIVE_BALANCE

Consensus implementation for EIP-7251:  Increase MAX_EFFECTIVE_BALANCE
Extensive discussion and rationale can be found in this PR:

https://github.com/michaelneuder/consensus-specs/pull/3

Accompanying documentation:

Original ethresearch proposal: https://ethresear.ch/t/increase-the-max-effective-balance-a-modest-proposal/15801
Security considerations: https://notes.ethereum.org/@fradamt/meb-increase-security
FAQ: https://notes.ethereum.org/@mikeneuder/eip-7251-faq

MIN_SLASHING_PENALTY_QUOTIENT_EIP7251 = 65536 rationale
With this value for the quotient the initial slashing penalty will be roughly equal to 6 days of base_reward (with 32M ETH of total active balance), i.e. it is roughly 6 days worth of attestation rewards. In absolute values it will be 0.03125 ETH and 0.00050 ETH for 2048 and 32 ETH validators respectively. The main objective of this reduction is to alleviate additional risk that consolidated validators will have comparing to those that are not consolidated.
Whistleblower reward is also updated: WHISTLEBLOWER_REWARD_QUOTIENT_EIP7251 = 65536 which is 6 days worth of attestation rewards. This should still provide enough incentives to submit slashings and being capped at the MIN_SLASHING_PENALTY_QUOTIENT_EIP7251 will prevent new ETH minting when slashing is processed.
The script to compute a number of base rewards equal to a slashing penalty:
import math

BASE_REWARD_FACTOR = 64
EFFECTIVE_BALANCE_INCREMENT = 1_000_000_000
TOTAL_ACTIVE_BALANCE = 32_000_000_000 * 1_000_000_000  # 32M ETH

MIN_SLASHING_PENALTY_QUOTIENT_EIP7251 = 2**16

def get_base_reward_per_increment():
    return EFFECTIVE_BALANCE_INCREMENT * BASE_REWARD_FACTOR // math.floor(TOTAL_ACTIVE_BALANCE ** 0.5)

def get_base_reward(effective_balance: int):
    increments = effective_balance // EFFECTIVE_BALANCE_INCREMENT
    return increments * get_base_reward_per_increment()

def get_base_rewards_in_slashing_penalty(effective_balance: int):
		base_reward = get_base_reward(effective_balance)
		slashing_penalty = effective_balance // MIN_SLASHING_PENALTY_QUOTIENT_EIP7251
		return slashing_penalty // base_reward

@potuz I've added commit https://github.com/ethereum/consensus-specs/pull/3618/commits/ebdb513ec8789c0b3d5a4a8289e2f62814147a93 with queue_excess_active_balance on the fork transition. It queues all excess balance from early compounding credential adopters
@ethDreamer I've added https://github.com/ethereum/consensus-specs/pull/3618/commits/7ec93c565554ffcc176f6945ba7b4ce456195649 to switch the target consolidator into compounding credentials if the consolidation is sucessful

This PR intentionally does not modify EJECTION_BALANCE. I will share a write-up shortly justifying why 🙏

is_aggregator changes
I have removed the is_aggregator changes. While balance-based aggregator selection is necessary for safety, it is only applicable for high regimes of consolidation. The current spec includes consolidation churn, which guarantees a maximum (slow) rate of adoption. We should leave is_aggregator changes out now to reduce complexity later and include them in the subsequent fork if the stakers choose to consolidation into very concentrated validators. Will publish a doc soon with full rationale and numbers to back it up
No p2p topic
This PR is missing a p2p doc on purpose. I believe we don't need a p2p topic to distribute consolidation objects:
Ethereum today relies on HTTP connections for two key actions:

most (if not all) syncings from a blank DB (checkpoint sync)
proposing +90% of blocks (with MEV-boost)

I don't think it would be a big ask to accept the distribution of consolidations via an off-protocol solution. Most big players can just self-include on their own proposals. There's no incentive to consolidate before or after than other actors. As long the network eventually consolidates. If the off-protocol message distribution service fails that's okay there's no loss of funds just longer inclusion times. Specially because consolidations are a temporary feature that's only useful during a transition. New stake can just deposit consolidated. Removing an HTTP API in 2 years is much simpler than removing p2p code.

IIRC @fradamt has a branch with new EIP-7251 test cases: https://github.com/michaelneuder/consensus-specs/pull/20
Can we add them to this PR now?

How does the interplay with other withdrawal types go?
Concrete example,
I'm a genesis validator (not, but as an example) and i've accrued 6 eth of balance since genesis, because i've never switched to 0x01 withdrawal key..
After electra at some point, I finally get around to issuing a bls change, so now Im a validator with 38 odd eth and a 0x01 creds...
Does that mean that i get automatically switched to consolidated due to my more than one eth extra? Or would i have to specifically do a deposit?

Does that mean that i get automatically switched to consolidated due to my more than one eth extra? Or would i have to specifically do a deposit?

No validator is automatically changed into consolidating credentials. The current paths to switch are:

(implemented): through a consolidation operation, change target validator to 0x02 credentials
(pending): through a top-up deposit that includes 0x02 credentials

@hwwhww can we merge this as-is so contributors can PR fixes on ethereum/consensus-specs instead of my random fork?


Removes $ in front of the terminal command on README.md

This prevents copying the $ sign when the copy icon is clicked on GitHub

Thanks, though I feel this is a GitHub UI bug. ;)


Fix memory leak found in HypreAMS when SetOperator is called multiple times [hypreams-mem-leak-fix]

This occurs when using HypreAMS to precondition the linear system arising in a Newton solve. The fix is based on what has been used for HypreBoomerAMG. This source of the memory leak is that in HypreSolver::Setup the underlying solver's SetupFcn is called if setup_called was false, and since SetOperator sets setup_called to true, HYPRE_AMSSetup is called multiple times on the same underlying solver, creating a leak. I've introduced a new function HypreAMS::ResetAMSPrecond that is called if SetOperator is called with a valid HypreParMatrix, that destroys the old AMS solver and creates a new one based on the old solver's settings/fields. This approach is based on HypreBoomerAMG's existing ResetAMGPrecond function.
I've included a commented out approach that more closesly follows the AMG version of this that reads the existing solver's settings/fields, but Hypre doesn't expose the details of the AMS solver in a public header file, or include get versions of the set functions it does expose, I can't actually compile that version. I've created a Hypre issue about that (https://github.com/hypre-space/hypre/issues/667), so hopefully when that gets resolved we can use that version of ResetAMSPrecond. Without it, we can only reset to the default settings of HypreAMS.

@tuckerbabcock, I assume this is ready for review, so I'll add the ready-for-review label to start the review process.

Hi, @v-dobrev thanks for looking at this. I somewhat intentionally did not add the ready-for-review. I was hoping to get some feedback on the hypre issue before marking this as ready, since the implementation of the memory leak fix might change depending on how that issue is addressed.
The code in this PR does fix the leak, but in the case that anyone manually set preconditioner options through the hypre interface, this fix would wipe those out and reset them to the MFEM default options if the preconditioner was ever reset. I was hoping to wait until the hypre issue was addressed so that we could reset the preconditioner without wiping the options.
I should say though that the current current behavior of the preconditioner also wipes the options (and leaks), so this proposed implementation is still an improvement over the current one. If you want to start the review process now I'm fine with that.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Lets make sure https://github.com/hypre-space/hypre/pull/730 is merged before we merge this.

Should we do the same fix for ADS too?

Should we do the same fix for ADS too?

Probably

I believe this is still waiting for https://github.com/hypre-space/hypre/pull/730 to be merged. We should really also do the same for ADS. Is a separate PR better, or roll it into this one?

I believe this is still waiting for https://github.com/hypre-space/hypre/pull/730 to be merged.

Done now :)

We should really also do the same for ADS. Is a separate PR better, or roll it into this one?

We can do it here

We should really also do the same for ADS. Is a separate PR better, or roll it into this one?

We can do it here

I did a simple fix for ADS (and verified with valgrind that it fixes the issue). I didn't create the #if MFEM_HYPRE_VERSION >= 22600 branch, that will also require a companion PR to hypre.

Merged in next for testing...


[PDI-18997] - Browsing a file in CSV input step in local system, when connected to the repository, returns an incorrect path in Filename field [Ubuntu 18.04]

@ssamora
@smmribeiro
@moraesvc

:white_check_mark: Build finished in 19m 56s
Build command:
mvn clean verify -B -e -Daudit -amd -pl plugins/repositories/core,ui

:ok_hand: All tests passed!
Tests run: 1188, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


Default JWT_EXPIRE to True

I want to merge this change because...

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Closing in favor of: https://github.com/saleor/saleor/pull/9483/


Empty maps are deserialized as null

When configuring the mapper to also store empties
mapper.getOptions().setStoreEmpties(true);

then empty Maps and Lists are stored as well to DB.
They also get deserialized as empty Maps resp. List again.
This works for an empty
Map<String, String>

BUT it does not work for empty Maps like the following
Map<String, List<String>>
Map<String, MyObject>

where
class MyObject {
   private String valueA;
   private int valueB;
}

It seems when having a complex type in the value part of the map, the map is no longer deserialized as empty map but simply as null object, which subsequently breaks the code as they are no longer equal after loading.
Tested with Morphia 1.0.1

The issue seems to be that EmbeddedMapper#readMap doesn't take its MapperOptions' isStoreEmpties flag into account when deciding whether to set the map field's value. This doesn't occur for simple valued maps because a different Mapper implementation is used.
I've created a pull request with the necessary changes here https://github.com/mongodb/morphia/pull/869.


Add Yarn PnP support

This will resolve both node_modules/@synthetixio/synpress and the Yarn PnP equivalent, which is something like .yarn/cache/@synthetixio-synpress-npm-{version&hash}.zip/node_modules/@synthetixio/synpress .

Hey @einaralex. Thanks for pull request. I'm going to take a look at it until end of the week, test it out and merge.
Cheers,
Jakub.

Hey @drptbl , any updates ?

Hey @einaralex, sorry for delay. I have been affected by the war on Ukraine, but I'm back now. Thanks for contribution.

@drptbl I am so sorry to hear, first and foremost take care of you and your family 🙏
Thank you so much!

@einaralex Thanks for kind words ❤. That's exactly what I have done past 2 weeks 👍.
Yarn support has been released on<EMAIL_ADDRESS>All best,
Jakub.


Add some guide on port 80 problem.

Recommend user to substitute port over 1024 if they have trouble running their project.

I add the programming language in CHN-03 that I missed last time. I also add the relevant content in ENG-03. Sorry for too many commits only for some small changes, I'm new to pull request.

Don't worry, I used squash merging.


Add missing 'opam update' to Alpine fix

OK, I tested with --no-cache this time...

(merging now because CI doesn't test the Docker scripts anyway)


chore(main): release 2.0.0-1

:robot: I have created a release beep boop
2.0.0-1 (2024-04-05)
Miscellaneous Chores

release 2.0.0-1 (fa468b9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/davids-ensemble/tj-jira-panel/releases/tag/v2.0.0-1 :sunflower:


Add TCP protocol for daemon as a fallback if unix socket doesn't work.

In some earlier version of windows 10 and before, unix sockets are not supported hence there should be a fallback protocol to support daemon's reliability to make it work in all devices possible.

Added with https://github.com/warpdl/warpdl/commit/cfd87e857a6413ba96fdad911b7405a13728be81
Testing is required, leaving this issue opened till then.


Cant type. Shortcuts dont work.

Environment
Windows build number:  10.0.19041.329
Windows Terminal version: 1.0.1401.0 (Microsoft Store version)
Actual behavior
It's like the keyboard doesn't work. Cant use shortcuts(ex. switch shell) I can paste commands with the mouse right click.

Any chance you're using PowerToys?
If you manually click in the "terminal" part of the window, can you type again?
Could you share your settings.json?

In the past i used the PowerToys but i deleted.
If you manually click in the "terminal" part of the window, can you type again?

No.

I tried reinstall the app, and reboot, but no help.
Settings file (i deleted the comments):
{
  "$schema": "https://aka.ms/terminal-profiles-schema",

  "defaultProfile": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",

  "copyOnSelect": false,

  "copyFormatting": false,

  "profiles": {
    "defaults": {

    },
    "list": [

      {
        "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
        "name": "Command Prompt",
        "commandline": "cmd.exe",
        "hidden": false
      },

      {
        "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
        "name": "Windows PowerShell",
        "commandline": "powershell.exe",
        "hidden": false
      },

      {
        "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
        "hidden": false,
        "name": "Azure Cloud Shell",
        "source": "Windows.Terminal.Azure"
      }
    ]
  },

  "schemes": [],

  "keybindings": [

    {
      "command": {
        "action": "copy",
        "singleLine": false
      },
      "keys": "ctrl+c"
    },

    {
      "command": "paste",
      "keys": "ctrl+v"
    },

    {
      "command": "find",
      "keys": "ctrl+shift+f"
    },

    {
      "command": {
        "action": "splitPane",
        "split": "auto",
        "splitMode": "duplicate"
      },
      "keys": "alt+shift+d"
    }
  ]
}

I have the same problem. Is it due to a system update? I installed system updates(KB4557957, KB4560366) on June 12。

This seems like a /dupe of #4448