11/9/2021 Publish

Docs Build status updates of commit 6e4784a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

2017-03-09-profile/docs-ref-autogen/TOC.yml
:warning:Warning
View (azure-cli-2017-03-09-profile)
Details

2018-03-01-hybrid/docs-ref-autogen/TOC.yml
:warning:Warning
View (azure-cli-2018-03-01-hybrid)
Details

latest/docs-ref-autogen/TOC.yml
:warning:Warning
View (azure-cli-latest)
Details

2017-03-09-profile/docs-ref-autogen/aks.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/arcdata/dc/config.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/batch-deployment.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/batch-endpoint.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/component.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/compute.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/data.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/dataset.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/environment.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/job.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/model.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/online-deployment.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/online-endpoint.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/ml/workspace.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/network/manager.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/network/manager/connect-config.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/network/manager/group.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/network/manager/security-admin-config.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/network/manager/security-admin-config/rule-collection.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/network/manager/security-admin-config/rule-collection/rule.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/network/manager/security-user-config.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/network/manager/security-user-config/rule-collection.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/network/manager/security-user-config/rule-collection/rule.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/sig/image-version.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/spring-cloud/app.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/spring-cloud/app/deployment.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/webpubsub.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2017-03-09-profile/docs-ref-autogen/webpubsub/hub.yml
:bulb:Suggestion
View (azure-cli-2017-03-09-profile)
Details

2018-03-01-hybrid/docs-ref-autogen/aks.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/arcdata/dc/config.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/batch-deployment.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/batch-endpoint.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/component.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/compute.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/data.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/dataset.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/environment.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/job.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/model.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/online-deployment.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/online-endpoint.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/ml/workspace.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/network/manager.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/network/manager/connect-config.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/network/manager/group.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/network/manager/security-admin-config.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

2018-03-01-hybrid/docs-ref-autogen/network/manager/security-admin-config/rule-collection.yml
:bulb:Suggestion
View (azure-cli-2018-03-01-hybrid)
Details

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

2017-03-09-profile/docs-ref-autogen/TOC.yml

Line 1215, Column 12: [Warning: xref-not-found] Cross reference not found: 'sp-Azure_Devops'.

2018-03-01-hybrid/docs-ref-autogen/TOC.yml

Line 1215, Column 12: [Warning: xref-not-found] Cross reference not found: 'sp-Azure_Devops'.

latest/docs-ref-autogen/TOC.yml

Line 2423, Column 12: [Warning: xref-not-found] Cross reference not found: 'sp-Azure_Devops'.

2017-03-09-profile/docs-ref-autogen/aks.yml

Line 930, Column 39: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'target' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 951, Column 290: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'target' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/arcdata/dc/config.yml

Line 54, Column 88: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'cwd' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 60, Column 88: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'cwd' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/batch-deployment.yml

Line 51, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 223, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 226, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/batch-endpoint.yml

Line 47, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 126, Column 58: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'data-name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 126, Column 70: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'data-version' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 147, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 271, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 274, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/component.yml

Line 41, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 177, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 180, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/compute.yml

Line 150, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 171, Column 112: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'ResourceID1' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 171, Column 126: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'ResourceID2' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 477, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 480, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 483, Column 112: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'ResourceID1' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 483, Column 126: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'ResourceID2' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/data.yml

Line 56, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 181, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 184, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/dataset.yml

Line 65, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 193, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 196, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/environment.yml

Line 77, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 207, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 210, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/job.yml

Line 75, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 232, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 235, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/model.yml

Line 56, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 189, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 192, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/online-deployment.yml

Line 60, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 271, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 274, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/online-endpoint.yml

Line 58, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 308, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 311, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/ml/workspace.yml

Line 52, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 213, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 216, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/network/manager.yml

Line 417, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 423, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/network/manager/connect-config.yml

Line 257, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 260, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/network/manager/group.yml

Line 243, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 246, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/network/manager/security-admin-config.yml

Line 182, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 189, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/network/manager/security-admin-config/rule-collection.yml

Line 203, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 206, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/network/manager/security-admin-config/rule-collection/rule.yml

Line 328, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 331, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/network/manager/security-user-config.yml

Line 182, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 189, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/network/manager/security-user-config/rule-collection.yml

Line 203, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 206, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/network/manager/security-user-config/rule-collection/rule.yml

Line 310, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 313, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/sig/image-version.yml

Line 69, Column 221: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'MajorVersion' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 69, Column 236: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'MinorVersion' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 69, Column 251: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'Patch' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/spring-cloud/app.yml

Line 44, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 82, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 136, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 202, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 242, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 301, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 329, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 376, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 414, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 460, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 485, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 507, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 534, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 564, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 596, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 636, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/spring-cloud/app/deployment.yml

Line 8, Column 219: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'staging' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 55, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 131, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 167, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 203, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 228, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 254, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 287, Column 124: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/webpubsub.yml

Line 167, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 170, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2017-03-09-profile/docs-ref-autogen/webpubsub/hub.yml

Line 152, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 155, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/aks.yml

Line 930, Column 39: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'target' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 951, Column 290: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'target' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/arcdata/dc/config.yml

Line 54, Column 88: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'cwd' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 60, Column 88: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'cwd' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/batch-deployment.yml

Line 51, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 223, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 226, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/batch-endpoint.yml

Line 47, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 126, Column 58: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'data-name' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 126, Column 70: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'data-version' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 147, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 271, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 274, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/component.yml

Line 41, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 177, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 180, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/compute.yml

Line 150, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 171, Column 112: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'ResourceID1' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 171, Column 126: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'ResourceID2' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 477, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 480, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 483, Column 112: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'ResourceID1' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 483, Column 126: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'ResourceID2' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/data.yml

Line 56, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 181, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 184, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/dataset.yml

Line 65, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 193, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 196, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/environment.yml

Line 77, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 207, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 210, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/job.yml

Line 75, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 232, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 235, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/model.yml

Line 56, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 189, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 192, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/online-deployment.yml

Line 60, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 271, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 274, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/online-endpoint.yml

Line 58, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 308, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 311, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/ml/workspace.yml

Line 52, Column 115: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 213, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 216, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/network/manager.yml

Line 417, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 423, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/network/manager/connect-config.yml

Line 257, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 260, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/network/manager/group.yml

Line 243, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 246, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/network/manager/security-admin-config.yml

Line 182, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 189, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

2018-03-01-hybrid/docs-ref-autogen/network/manager/security-admin-config/rule-collection.yml

Line 203, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 206, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

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


value builder ignores constraint violations if there is no UoW - fix

Is this really the case?
Association<Person> owner();

If it doesn't have @Optional, then it should be possible to return 'null'. But your change seems to suggest that that would be possible. Or?

fix is for issue that properties constraints are ignored as early return ( no UoW) does't throw exception.
( attached test fails without change )
I see that there is another question that nullability ( @Optional) check for associations could be evaluated.

Ok, so there are actually more than one issue with Constraints in 3.0.
On Sun, Sep 10, 2017 at 4:03 PM, Tibor Mlynarik<EMAIL_ADDRESS>wrote:

fix is for issue that properties constraints are ignored as early return (
no UoW) does't throw exception.
( attached test fails without change )
I see that there is another question that nullability ( @optional
https://github.com/optional) check for associations could be evaluated.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apache/polygene-java/pull/7#issuecomment-328326604,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGgxVR35wl5-vuNK3kKzpO3kCyzg01eks5sg5fLgaJpZM4PSHn0
.

--
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java

I suggest that you integrate this yourself.
On Sun, Sep 10, 2017 at 5:01 PM, Niclas Hedhman<EMAIL_ADDRESS>wrote:

Ok, so there are actually more than one issue with Constraints in 3.0.
On Sun, Sep 10, 2017 at 4:03 PM, Tibor Mlynarik<EMAIL_ADDRESS>wrote:

fix is for issue that properties constraints are ignored as early return
( no UoW) does't throw exception.
( attached test fails without change )
I see that there is another question that nullability ( @optional
https://github.com/optional) check for associations could be evaluated.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apache/polygene-java/pull/7#issuecomment-328326604,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGgxVR35wl5-vuNK3kKzpO3kCyzg01eks5sg5fLgaJpZM4PSHn0
.

--
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java

--
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java

Should I be able to merge ?

We can't merge in GitHub. One need to pull from GitHub into local
repository and then push it back. And I think one should include the PR
number in the commit and the PR will be closed (or maybe it is just the
commit will do it automatically as well, I am not sure).
On Sun, Sep 10, 2017 at 5:31 PM, Tibor Mlynarik<EMAIL_ADDRESS>wrote:

Should I be able to merge ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apache/polygene-java/pull/7#issuecomment-328330930,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGgxWNJeW-weZBdWHVsr3h668qTt-Ogks5sg6x8gaJpZM4PSHn0
.

--
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java

I have tried to follow
https://polygene.apache.org/community/codebase.html
and
https://help.github.com/articles/checking-out-pull-requests-locally/
but I am getting
ERROR: Permission to apache/polygene-java.git denied to tbml

Merged in 1d75d91e4a4b5fafdf9229a84d8950d73bb4d877


Create new resources on the server using POST

We need to support create using POST in the sync API.

**Describe the bug**
Locally created Resources are assigned ID at creation/before saving to the local db. Once this Resource is up-synced, the server assigns a new ID to the resource and disregards the assigned ID  (in case of HTTP-POST). The created object is returned  in the POST response.
Since the lD for local & remote copy are different now, need to update all the local id references with the remote id.
Component
Core library, SDC library, reference app, or SDC gallery app
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. Pixel4a emulator]
Android version: [e.g. Settings -> About phone -> Android version]
Build number: [e.g. Settings -> About phone -> Build number]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.

lowering the priority since we do not use POST any more. we are explicitly supporting PUT for creating resources (for now). it is possible that we will need to add support for POST in the future so keeping this issue open.

We have been working on a number of PRs to redesign the upload process in order to support this feature:

https://github.com/google/android-fhir/pull/2156
https://github.com/google/android-fhir/pull/2166
https://github.com/google/android-fhir/pull/2137
https://github.com/google/android-fhir/pull/2121
https://github.com/google/android-fhir/pull/2147
https://github.com/google/android-fhir/pull/2109
https://github.com/google/android-fhir/pull/2168

There will be another PR introducing upload strategies and then the PR to update the IDs after POST.
@omarismail94 @anchita-g


Implement debiased/double ML algorithm using chirho.robust

See Algorithm 1 in https://www.overleaf.com/project/654a5a7d75f4dfbebfa57f61.

Hi @juanitorduz . Thanks for your interest in this work! We are currently preparing a manuscript on our flavor of influence function-based estimators that we're planning on sharing publicly in the next several months, but as of right now we don't have any pre-prints or public links available. At Basis we're still figuring out exactly how to balance our organizational mission of "doing work in public" while not prematurely making strong scientific claims we can't yet substantiate with evidence.
We'll think more about how best to communicate this in issues and PRs, maybe with a tag describing that the issue or PR links to unreleased material?

Thanks for the input! I'm genuinely interested in the project and I saw this issue as a potential entry point :)
I'll wait for this issue to be properly described and open for contributions.

@juanitorduz thanks for checking out ChiRho! If you're interested in contributing, you could also take a look at issues marked with "help wanted" and "good first issue", which aren't blocked by ongoing work and might be easier places to start.


docs: Clean up SDL docs

Rather than duplicating the synopsys description refer to DDL for most
things and make a separate mention of the nested sub-declarations (liked
to SDL declarations).

I've made a fair bit of additional changes making sure that the DDL synopsis and descriptions were more explicit, up-to-date and exhaustive since they are the final source of truth.


Remove fragment from GraphQL subscription due to validation issues

This PR fixes an issue with app registration caused by Saleor's subscription query validation issues.
It removes fragment from the subscription.

Replaced by #423


[SUB-TASK][KPIP-4] Support proxy user for BatchesResource DELETE /batches/${batchId}

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the feature
sub task of #2240
Motivation
No response
Describe the solution
No response
Additional context
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

closed by #2379


Libri Can't Go in Bookshelves

The Animalia Libri can't be stored in bookshelves because it isn't in group:book. I was able to add it and place an unused Libri in a bookshelf. I would greatly appreciate having this fix in the next update.

Quite an oversight on my part, but it's fixed now.

Thank you so much


feat: add DepositData SSZ container

Description
This issue is to adding the DepositData SSZ container
Closes #52

looking good so far! Plz sync with main

except from last line it seems like it is good to go actually it is the same line but idk why it seems like it is changed @mpaulucci

@all-contributors please add @karasakalmt for code


Remove 2023 A/L Application form

Is your feature request related to a problem? Please describe.

In the Quick Access section on the home page, the A/L application form should be removed because the deadline has passed.
Describe the solution you'd like
Remove the A/L application form from the Quick Access section.

Shall I work on this ?

Sure, Go ahead.

Shall I work on this ?


Enable dependencies based on dep: features

Now that Rust 1.60 includes the explicit dep: syntax for dependency features, we need to look for those as well when figuring out which dependencies are enabled. This fixes the broken build of serde_with 2.0.0.

It it looks like right now you have features and deps living in the "same namespace"? I am not sure that is a good.
Can you make it separate?
Similarly, can you make the test have a dependency and feature that are completely unrelated but share the same name?

What do you mean by "same namespace"? Are you talking about dep: features being a type of feature even though they represent dependencies?
And yes, as written, if we do use dep: features and also have an unrelated feature with the same name as the dependency, enabling that feature will lead to crate2nix including that dependency. It seems like a weird edge case that there's no good reason anyone would ever do, but I guess I could perform a much larger overhaul to fix that; my main focus here was just erring on the side of including more dependencies to prevent build errors.

It is more, work, but I don't think it will be too hard.
The entire reason they added dep: upstream was to fix this ambiguity, so supporting dep: without supporting the motivation feature for why it exists doesn't seem good to me.

Heh, I need this now, so I'll merge after all, but making a issue to fix the semantics.


proposal: use file system to store draft in progress

Currently, draft editing occurs in a new unsaved editor tab. Draft submit does a select all, copy, and paste. The selected text is stored in a global python variable so that it can be pasted a second time.
This has a few downsides. One is that if the select all or copy fails, as has happened to me recently, the entered text is lost irrecoverably. Another is that the global python variable is relatively hard to get at. This makes people nervous, even knowing that a second draft submit should cause it to get pasted. And if your draft submit command gets misinterpreted by the voice engine as, say, draft edit, the python variable contents are lost forever.
I propose an alternative approach, one which is used by other systems that call out to an external editor, such as git commit. That is to create a new temporary file and read the file when the user is done editing. Using the file system makes the job of getting the draft contents easier and more reliable, as well as making error recovery simpler and more robust.
The tradeoff here is that, unlike before, the draft contents will be saved to disk. If the contents are sensitive, this could pose a security problem.
I propose the following tradeoff between usability and security.
I propose that each draft start in a new file, rather than reusing a single file. A cron will delete all draft files with an mtime older than an hour.
Drafts are thus regularly cleaned up and exist only on disk for a short time. An hour should be enough for almost all disaster recovery, particularly since most disasters will be discovered immediately.
There are a few corner cases that are worth discussing.

If the user quits talon, the cron will stop running. This potentially leaves some number of drafts lying around indefinitely.
If the user has a draft open for more than an hour, the cron may delete the underlying file. This will generally not be a problem. Most editors will happily save the file anyway, and on some file systems, the delete itself may fail. Enter
Some file systems and editors may not do an fsync promptly. This might reduce the reliability of retrieving the contents. This would be a transient and self-correcting error.

One open question is where to put the drafts. There are two obvious options: the temp dir, and TALON_HOME/drafts. The advantage to the temp dir is that it will eventually get cleaned up by the operating system, and they are clearly temporary files. The advantage to putting them in TALON_HOME is that they are easier to find, easier to clean up, and likely to get deleted if talon itself gets deleted.

Note we only update the global last_draft variable on draft submit. Meaning that in accidental "draft this" does not prohibit you from going back to your previous application and doing a draft submit to paste the last submitted draft.
I'm not against using the file system, but I think that if the existing system is not reliable we should fix that instead. Using the file system just sounds like a work around for a poor implementation. For example we could actually verify that the copy succeeded before we closed the editor?


feat: cree_example tag to properly render "like: itwêwin" in the current orthography

Renders this part properly:

Codecov Report

Merging #466 into master will increase coverage by 0.03%.
The diff coverage is 93.75%.

@@            Coverage Diff             @@
##           master     #466      +/-   ##
==========================================
+ Coverage   86.45%   86.48%   +0.03%
==========================================
  Files          67       67
  Lines        2650     2664      +14
==========================================
+ Hits         2291     2304      +13
- Misses        359      360       +1

Impacted Files
Coverage Δ

...eeDictionary/templatetags/creedictionary_extras.py
97.36% <83.33%> (-2.64%)
:arrow_down:

...CreeDictionary_tests/test_creedictionary_extras.py
100.00% <100.00%> (ø)

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 77029bb...5919e23. Read the comment docs.

LGTM


local vs internet ws server

I am trying to open connection to the server and now I have an issue with it. If it local started crossbar.io server - I am able to connect to it, but I am can't connect to any internet server ( for example wss://demo.crossbar.io/ws ). In this case only cycled disconnect-connection states. What I am doing incorrect ?
try {
// Create a builder and configure the client
WampClientBuilder builder = new WampClientBuilder();
//            builder.withUri("ws://<IP_ADDRESS>:8282/ws")
builder.withUri("wss://demo.crossbar.io/ws")
.withRealm("realm1")
.withInfiniteReconnects()
.withReconnectInterval(5, TimeUnit.SECONDS);
// Create a client through the builder. This will not immediatly start
// a connection attempt
client = builder.build();
        client.statusChanged().subscribe(new Action1<WampClient.Status>() {
            private Subscription procSubscription;

            public void call(WampClient.Status t1) {
                Log.d("info", "Session status changed to " + t1);

                if (t1 == WampClient.Status.Connected) {
                    Log.d("info", "Connected");
                }
            }
        });

        client.open();

    } catch (WampError e) {
        // Catch exceptions that will be thrown in case of invalid configuration
        e.printStackTrace();
        return;
    }

I am sorry - I forget to add... I try to connect from the android (device and emulator), if it important

Your code is correct. Does your android app have the internet permission?

Yes, internet permission is set ( as I said my localhost is available form my app ). May be I do not set some dependencies in gradle ? ( maven repository have set in another gradle file ) Or may be I need make some steps to connect to wss server ? I tried withSslContext(SslContext.newClientContext(InsecureTrustManagerFactory.INSTANCE)) - but nothing changed.
apply plugin: 'com.android.application'

android {
    compileSdkVersion 22
    buildToolsVersion '21.1.2'

    defaultConfig {
        applicationId "...."
        minSdkVersion 10
        targetSdkVersion 22
        versionCode 1
        versionName "1.0"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }

    android {
        packagingOptions {
            exclude 'META-INF/io.netty.versions.properties'
            exclude 'META-INF/INDEX.LIST'
            exclude 'META-INF/LICENSE'
            exclude 'META-INF/NOTICE'
        }
    }
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    compile 'com.android.support:appcompat-v7:22.1.0'
    compile 'com.android.support:support-v4:22.1.0'
    compile 'ws.wamp.jawampa:jawampa:0.2.0'
}

Sorry, can't help you regarding Android configuration as I have no experience with that. In #21 there was a discussion about the correct settings for Proguard, maybe you have a problem with that. @jrogers also build an example for android, maybe this helps: https://github.com/jrogers/AndroidWampExample
If you want to debug why the connection fails you could put breakpoints in the associated Netty Channel Handlers for the connection  (e.g. in WampClientWebsocketHandler, WebSocketClientProtocolHandler, WebSocketClientProtocolHandshakeHandler, WebSocketClientHandshaker08). Sorry - currently don't have time to investigate that deeper myself.

Thank you. I found nexus 7 (5.0) and tried to start my app on  it - all working! I do not understand why samsung galaxy s not allow me to connect. I hope it is just certificates issue or something and my server will be working without problems.


ETA Field

A read-only DateTime ETA field needs to be added to Shipments to be used for BI purposes. This field should not be editable via the frontend, as the BI service will be manipulating it directly. The value should be visible on all existing Shipment views.

Added the header. This field will be updated by an external service.

Should there be a test to ensure that the external service is able to update field?


Allow For Creation of pinning Files without root_info

Is there an existing issue for this?

[X] I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?
Pinning files should be allowed to be generated even without a root_info dict as you can use Ayon without setting a project root for your site id.
How would you imagine the implementation of the feature?
remove the check for root_info and allow the creation without it.
Are there any labels you wish to add?

[X] I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:
No response
Additional context:
No response

a moment ago @BigRoy mentioned that there is an option to have a siteId without project roots set, this issue debates if this is a intended use case and if it is will remove the root_info check from the pinning file creation to allow for the creation of pinning files that act more like caching files and loos the root replace function.

Let me start of by saying that I have no idea how to configure things so that I do have something valid returned for root_info. :) It's just that on my debug server and production scenarios this returns an empty dict:
root_info = ayon_api.get_project_roots_for_site(os.environ.get("AYON_PROJECT_NAME"))
print(root_info)
# {}

source

@martastain @dee-ynput i assumed that site roots are needed for more than just the resolver? can you comment on that.
if the comment is that its not needed we can just remove the check.

Site roots are needed elsewhere indeed. And btw, ideally it should be:
import ayon_api
from ayon_core.pipeline import get_current_project_name
ayon_api.get_project_roots_for_site(get_current_project_name())

(just because I am scared of enviornment variables)

First - get_project_roots_for_site() is now deprecated - replaced by get_project_root_overrides_by_site_id.
But I think that there is a bug in ayon_api itself. Because to get the roots, you need either site_id or platform. If you don't set one, it will get back 400 error. If you look at the get_project_root_overrides_by_site_id it isn't passing the site_id or the platform to the server at all, it is probably expecting that server will return all sites and ayon_api will just filter the correct one.

But I think that there is a bug in ayon_api itself. Because to get the roots, you need either site_id or platform. If you don't set one, it will get back 400 error. If you look at the get_project_root_overrides_by_site_id it isn't passing the site_id or the platform to the server at all, it is probably expecting that server will return all sites and ayon_api will just filter the correct one.

That seems to match the REST api docs though:

Anyway, no matter what I do.. it's all an empty dict for me:
import ayon_api
from ayon_core.pipeline import get_current_project_name

project_name = get_current_project_name()
site_id = ayon_api.get_site_id()
root_info = ayon_api.get_project_roots_for_site(project_name, site_id)

print(f"{site_id=}")
print(f"{root_info=}")
print(ayon_api.get(f"projects/{project_name}/roots").text)
print(ayon_api.get(f"projects/{project_name}/roots/{site_id}").text)

Basically results in:
site_id='spiritual-garnet-impala'
root_info={}
{}
{"code":404,"detail":"API endpoint /api/projects/ayontest/roots/spiritual-garnet-impala not found","path":"/api/projects/ayontest/roots/spiritual-garnet-impala"}

print(ayon_api.get(
    f"projects/{project_name}/siteRoots",
    platform="windows",
).text)
# {"work":"C:/projects"}

This does return something. Is that what we'd expect?
And again, why did it work for Lyon? 🥹

This does return something. Is that what we'd expect? And again, why did it work for Lyon?

yes this works for me no problem.

okay for the relative path issue:
basic testing returned that the relative paths get combined with the layer path to an absolute path.
sooo we need to support rootless paths on both sides key:value and then we are good.
i need to check if the resolver already dose this if not i will just run the root replacement functions for both sides and fix the root_generate function on the pinning file branch.
just to keep you updated and for reference.

So - I'm trying to make @iLLiCiTiT understand what's going on here. ;)
And he's basically saying we're doing it wrong.

We shouldn't be using the the root override api logic - because it doesn't include all the roots (but only the the overrides for the sites and that is why it's empty for me)
Anatomy.find_root_template_from_path in ayon_core has functionality to do exactly what we're trying to do.

But better:

@iLLiCiTiT says: even better implement it on server backend and add argument to the resolve endpoint that basically returns the rootless path to begin with. Especially because that can then even return it without knowing your site, and do "less" work on the server.

Edge case?

What if you have an entity URI that is of a different project than the current one?
We may need the roots for all the projects inside the pinning file, and also store the project_name so we know which site roots to use for that project. Etc.

So e.g. we need to store the rootless paths like {root[project][work]} instead of {root[work]} OR just store some metadata with each mapping in the pinning file:
{
    "{some long uri}": {
        "rootless_path": "{root[work]}/bla/bla",
        "project_name": "ayontest",
    }
}

And preferably then store top level all the projects used in this JSON file so we don't need to iterate all the JSON entries to make a set of the present project_name.

We shouldn't be using the the root override api logic - because it doesn't include all the roots (but only the the overrides for the sites and that is why it's empty for me)

well we want only the overwrites for the Site your on and not for all sites this is how the resolver works, and yes we currently do not support cross project usage the GH issue is open for a long long while but it was never pushed forward.
also why would we want site roots for other machines? that makes no sens at all. if your resolving to a path that is not a root on your system your resolving something outside of Ayon fouler and that should not be tracked.
https://github.com/ynput/ayon-cpp-api/issues/5
https://github.com/ynput/ayon-cpp-api/blob/2045db0cf3aa6b69ffd85e50891213c44869c3c6/src/AyonCppApi/AyonCppApi.cpp#L92

We SHOULD use ayon_api.get_project or ayon_api.get_projects to the roots for YOUR site. According to @iLLiCiTiT at least. :)

sure why not should not really change anything.

Anatomy.find_root_template_from_path in ayon_core has functionality to do exactly what we're trying to do.

okay i guess maybe it dose that? bit hard to guess from the function name.
PS: it would be so great if there would be hosted code documentation some where so that we can link against it for reference and for communication.

@iLLiCiTiT says: even better implement it on server backend and add argument to the resolve endpoint that basically returns the rootless path to begin with. Especially because that can then even return it without knowing your site, and do "less" work on the server.

that is the case and it has always been the case.
the resolver only gets a rootless path from the server and then puts the path together. this is also why we use this root replace system.
there are multiple things we could do here to do what he is saying.
A (nope): we could give the resolver a flag that then returns the rootless path instead of the resolved path. <- i wont do this because its just not the task of the resolver it adds complexity because it probably needs to be a runtime switch it also dosnt really work in all situations eg if you want to construct a stage then you will get the problem that the stage is broken, i guess we could do it so that you can call a function on the resolver and then the resolver will write the rootless paths into a separate map with the keys.
B: we could write a function that acts like the resolver and hits the resolve endpoint and then gives us back the rootless path.

Edge case?

What if you have an entity URI that is of a different project than the current one?
We may need the roots for all the projects inside the pinning file, and also store the project_name so we know which site roots to use for that project. Etc.

welp so point 1: currently you dont because the c++ api dose not support it.
point 2: yes cross project usage is something to be fixed but its a bigger game than just fixing pinning generation.

So e.g. we need to store the rootless paths like {root[project][work]} instead of {root[work]} OR just store some metadata with each mapping in the pinning file:

jup having a root identifier thats universally ture would be best. i would also like it if that would be the same on the endpoint and on the pinning file.

And preferably then store top level all the projects used in this JSON file so we don't need to iterate all the JSON entries to make a set of the present project_name.

Question: Where does the resolver get the Site ID from?
This was a question from @iLLiCiTiT - he was curious where it's taken from when the resolver starts using the pinning file. It could be defined in multiple places.

here you go. its searching all the places i was able to get at the time (the code is very old btw, last changed 7 months ago)
https://github.com/ynput/ayon-cpp-api/blob/2045db0cf3aa6b69ffd85e50891213c44869c3c6/src/AyonCppApi/AyonCppApi.cpp#L92

(and good point made by him) it may also need to generate a site id, if the local machine does not have it yet.

why dose it need to generate a site id? just because?
the only thing we need it for is to get the site root. and generating the site id dose not automatically set the root. soooo yeah any reason for that?

We SHOULD use ayon_api.get_project or ayon_api.get_projects to the roots for YOUR site. According to @iLLiCiTiT at least. :)

If you pass header x-ayon-site-id={site id} then the roots in project have already site specific roots.

If you pass header x-ayon-site-id={site id} then the roots in project have already site specific roots.

im gonna go and guess: your talking about the /resolve endpoint on the server?
if so yes doing this will return a full path for your machine but martin mentioned a good while back that this is slow (the cpp api used to use x-ayon-site-id with the /resolve endpoint) and so we decided it would be best to emulate the behavior in the cpp api by getting the site roots at instance construction and the rootless path from the server and combined them back to a full path.

So TD can potentially change the roots from AYON web ui without having direct access to the machine. Maybe a feature/enhancement, not must have.

im not following is this connected to pinning file creation? why would a TD want to change a site root remotely for a machine that generating a pinning file?
or do you mean it in a generally seance? aka: every machine should have a site id? that i could understand but i dont think that should be handled by pinning creation?

NOTE: We've discussed the changes related to how we understood what is this issue about. Maybe we didn't get what is the goal? I still don't fully understand what should happen, and where (and why).

who is WE if i might ask just for context?
sooo: ähhh: the beginning of the issue was that @BigRoy  wanted to create a pinning file on a machine where no Project roots where available. i belive this has changed by now to: how do we get the site roots because apparently some things work for some and not for others (but im a bit lost tbh too).
reason why we need the site roots:
the resolver gets the site roots so we dont need the server resolve endpoint to generate machine specific paths, this proved to be faster.
now we want to generate a pinning file. this will be a key:value pair the key is the assetIdent that the resolver gets(not important) and the value needs to be the resolver path without the site root so that we can generate a machine path on the machine that is rendering the scene, for this we set the site roots as an env variable on the rendering machine and put the paths back together with the same system we use to do this task when hitting the resolve endpoint.
we cant do cross project resolution with the resolver because the c++ api is getting its site roots at construction (this should be changed in the future but is not started) there is also the question on how we know to what project a given uri belongs because the return from the /resolve endpoint dose not give us this info if we use the path only flag (we do this to reduce the size of the return as its probable that we need to communicate 100k+ times so every byte we can shave of reduces the network latency)
i have no idea if that really answered your question but i hope it gave an idea ?

Use /project/{project name} with having x-ayon-site-id and the received project entity will have roots with site overrides. You don't have to do anything else.

Use /projects/{project name} with having x-ayon-site-id in headers. With that the received project entity will have roots with already applied site overrides. You don't have to do anything else.

I mentioned that we actively decided against doing that for performance reasons in the resolver. i also mentioned that this is not what we want for a pinning file because the pinning file needs to be portable.
(this portion i forgot to mention in the message atop, i assumed roy informed you if your missing context let me know)
when a pinning file is used the resolver dose not communicate with the server
this is done to freeze the Usd stage in time and to avoid overloading the server.
so no for multiple reasons we cant just get the machine local path from the server.

I think he didn't understand either? I'll let you chat, because I'm more and more confused about "what is this issue about".

that is the case and it has always been the case. the resolver only gets a rootless path from the server and then puts the path together. this is also why we use this root replace system. there are multiple things we could do here to do what he is saying.
A (nope): we could give the resolver a flag that then returns the rootless path instead of the resolved path. <- i wont do this because its just not the task of the resolver it adds complexity because it probably needs to be a runtime switch it also dosnt really work in all situations eg if you want to construct a stage then you will get the problem that the stage is broken, i guess we could do it so that you can call a function on the resolver and then the resolver will write the rootless paths into a separate map with the keys.

Sorry - what. No.
The resolver gets the resolved path - it doesn't need to do anything with sites or whatever, the backend does that already for you.
However, the way I understood with the file pinning is that you wanted to write the pinning file with rootless paths. Hence, my point was - can't we make that then resolve to the rootless path from the backend directly?
This is about the generation of the pinning file - it's not about the resolver itself at all.

sooo: ähhh: the beginning of the issue was that @BigRoy wanted to create a pinning file on a machine where no Project roots where available. i belive this has changed by now to: how do we get the site roots because apparently some things work for some and not for others (but im a bit lost tbh too).

Also, no no - the beginning of this issue is not about me wanting to do that. It's about the examples code provided that I should use returns no roots for me because I have no root overrides on my site. I just have the configured default roots in studio settings, hence "root overrides' are {} as I understood after the call with @iLLiCiTiT
In simple terms:

AYON has studio roots
A project can override these roots
A site can override these roots

I only have 1. and hence have no overrides.

Sorry - what? No.
The resolver gets the resolved path - it doesn't need to do anything with sites or whatever, the backend does that already for you.

okay im gonna say it again. yes the backed can do that. but like i already mentioned we dont use that system (for performance reasons). the reason why we dont use that system is as follows.
the resolver is a lot faster in generating a machine local path than the server is because the server has to ask his database the resolver only needs to get the site roots once at the beginning.
i know that its doing this because i wrote the code, i can put a std::cout into the code and show you that the resolver(or more the c++ api) dose infarct request the rootless path from the server and then puts the correct path together in the c++ code.
further more its actually using an extra argument with his request to ensure that we only get back the path to save on network bandwidth.
pathOnly sadly the documentation dosnt mention what happens if you dont give the server the side id and why this can be helpful.

However, the way I understood with the file pinning is that you wanted to write the pinning file with rootless paths. Hence, my point was - can't we make that then resolve to the rootless path from the backend directly?

yes we can do that we just simply didn't because it was not an easier way.
here is the thing, we do need to actually resolve all the paths because we need to open the other Usd Layers, aka all the sub-layers and references and so on because we need all paths needed for Stage construction not just the few in the first layer.
with that in mind i decided that its simpler to first get all the abs paths and then replace the root of them.
it was a simple question of whats simpler to implement.
yes it would be possible to A: do dubble resolution aka; first resolve the actual usd path so that  we can open the depended usd file and then ask the resolve endpoint for the rootless path. B: implement a function in the resolver that returns the rootlets path, i did not do that because its overkill and simply not needed.

This is about the generation of the pinning file - it's not about the resolver itself at all.
So, to generate the pinning file -> use the API resolve entry point to resolve to a rootless path. Easy as that.

resolve a rootless path? you mean resolve an uri to an rootless path right? because resoling the rootless path dosnt help us.
also your ideas arent covering that you can reference a usd file that is managed by ayon without an uri. first gathering all the paths and then making them rootless dose cover this case.

Also, no, the beginning of this issue is not about me wanting to do that. It's about the examples code provided that I should use returns no roots for me because I have no root overrides on my site. I just have the configured default roots in studio settings, hence "root overrides' are {} as I understood after the call with @iLLiCiTiT
In simple terms:

AYON has studio roots
A project can override these roots
A site can override these roots

I only have 1. and hence have no overrides.

ahh good to know i didnt know it was about the example code i assumed because of the name of the issue(named after what i understood in the catch-up meeting) you want to create pinning file without root_info because you dont have root info.

okay the REST API endpoint /api/projects/{prj_name}/siteRoots dose return the default site root if no overwrite is set.
sooo the c++ site is working and its time to figure out what to put into the example.
@iLLiCiTiT am i right assuming that ayon_api.get_project_roots_for_site is not hitting the endpoint atop of the message ?
i would have assumed that thees to would be the same. (tested via interactive ayon terminal)
>>>print(requests.get("https://ayon_dev.open-planck.de/api/projects/AY01_VFX_demo/siteRoots", headers={"x-ayon-site-id": "groovy-amiable-reindeer", "Authorization": "Bearer ffa5d1bad0cb32bae4d983ba267d678ac8c1e2c0a407e57274152ca9be0df9b5"}).text)
>>>{"work":"/mnt/share/projects"}

>>> print(ayon_api.get_project_roots_for_site("AY01_VFX_demo"))
>>>{}

@iLLiCiTiT am i right assuming that ayon_api.get_project_roots_for_site is not hitting the endpoint atop of the message ?

No, as mentioned above, that method is deprecated. It was replaced with get_project_root_overrides_by_site_id. There are 2 methods using that endpoint get_project_roots_by_site_id and get_project_roots_by_platform, but we don't use them because we use /projects/{project name} to get root (as in most of the time we also need other data from project at the same time).

No, as mentioned above, that method is deprecated. It was replaced with get_project_root_overrides_by_site_id.

ahhhhh many thanks now i understand what is replaced by what.

There are 2 methods using that endpoint get_project_roots_by_site_id and get_project_roots_by_platform, but we don't use them because we use get_project (/projects/{project name}) to get roots, as most of the time we also need other data from project.

okay now i get the idea with using project template (what roy mentioned)

Do you need python implementation or C++ implementation? Because if you need python implementation in pipeline part, then there are better ways how to get the roots.

c++ site works no problem.
we need a better python example for this document i assumed that the other function would work but was not aware that its deprecated (do we have an option to log a warning when a deprecated function is used from inside the function, like a cpp compiler warning? just out of interest) .

we need a better python example for this document i assumed that the other function would work but was not aware that its deprecated (do we have an option to log a warning when a deprecated function is used from inside the function, like a cpp compiler warning? just out of interest) .

In develop it is warned. Not sure if last release already did.

I'm asking because if you're in pipeline (e.g. during publishing) you already have multiple ways how to access roots without need to call anything in ayon_api. So where it's used does matter. When you're in pipeline part, you should be using Anatomy.

yeah good point maybe we should do multiple examples then.
one for ayon_api "raw dog it" one for your in publishing ?

Yes, sort of. It'd even be nice if potentially the generate pinning file function allows root_info=None (like it's optional) where it defaults to your site's root info to begin with.

hmmm i dont want ayon imports in standalone tools as they should be able to run standalone so having it optional and having a system that auto gets them is not the way.
i even target testing standalone tools without ayon at all, makes testing a lot easyer and the addition is just to small to argument the extra complexity that we will have on the CI side.

And of course the example, can be in the docstring ;)

when we have a good example and the automatic documentation like the cpp tools we could even link to the examples page.

Anyway, I'm still not entirely sure now how to proceed with testing the generate pinning file PR itself hehe.

well for testing i think this is good enough. its what the cpp api dose so its the same in the end.
from what i get of this discussion, the data is right just the way we access it isn't so its a question of building a better example.
print(ayon_api.get(f"projects/{project_name}/siteRoots").text)
# {"work":"C:/projects"}

This can be closed - the issue here was mostly due to the roots used during the test run as returned from the AYON API was just the wrong result because using the wrong API function for this.
The correct API call seems to be:
import ayon_api
from ayon_core.pipeline import get_current_project_name

root_info = ayon_api.get_project_roots_by_site_id(get_current_project_name())


Query returned no candles (do you have local data for the specified range?)

I am running the newest version of gekko now and tried multiple markets (Kraken XBT/EUR and Bitstamp BTC/EUR) but if I run gekko for a half a day and then try to backtest it that half a day almost always says its missing some time periods. Something like:

Simulation based on incomplete market data (7 missing between 2016-07-03 19:10:00 and 2016-07-03 19:52:00).

and then ofcourse:

Error:
Query returned no candles (do you have local data for the specified range?)

What is the cause of this? Backtesting weeks or months seems impossible now since each 12 hours there is a hickup in the data flow somewhere.
My database of the Kraken run is attached.
kraken_0.1.db.zip
Thanks.

Will do some research into this asap!

That is very strange, for me it is working fine:
➜  gekko git:(stable) ✗ node gekko --config kraken.js --backtest
2016-07-03 23:39:17 (INFO): Gekko v0.2.5 started
2016-07-03 23:39:17 (INFO): I'm gonna make you rich, Bud Fox.

2016-07-03 23:39:17 (INFO): Setting up Gekko in backtest mode
2016-07-03 23:39:17 (INFO):
2016-07-03 23:39:17 (WARN): The plugin Candle writer does not support the mode backtest. It has been disabled.
2016-07-03 23:39:17 (INFO): Setting up:
2016-07-03 23:39:17 (INFO):    Trading Advisor
2016-07-03 23:39:17 (INFO):    Calculate trading advice
2016-07-03 23:39:17 (INFO):    Using the trading method: StochRSI
2016-07-03 23:39:17 (WARN): Warning, trading method has no name
2016-07-03 23:39:17 (INFO):

2016-07-03 23:39:17 (WARN): The plugin Advice logger does not support the mode backtest. It has been disabled.
2016-07-03 23:39:17 (INFO): Setting up:
2016-07-03 23:39:17 (INFO):    Profit Simulator
2016-07-03 23:39:17 (INFO):    Paper trader that logs fake profits.
2016-07-03 23:39:17 (INFO):

2016-07-03 23:39:17 (WARN): unable to find Web Server in the config. Is your config up to date?

2016-07-03 23:39:17 (INFO):   WARNING: BACKTESTING FEATURE NEEDS PROPER TESTING
2016-07-03 23:39:17 (INFO):   WARNING: ACT ON THESE NUMBERS AT YOUR OWN RISK!

2016-07-03 23:39:17 (INFO): Profit simulator got advice to long @ 2016-07-03 09:46:00, buying 1.16349917 XBT  (1.16349917)
2016-07-03 23:39:17 (INFO): Profit simulator got advice to short  @ 2016-07-03 17:34:00, selling 0 XBT<PHONE_NUMBER>8)
2016-07-03 23:39:17 (INFO): Profit simulator got advice to short  @ 2016-07-03 19:34:00, selling 0 XBT<PHONE_NUMBER>8)

2016-07-03 23:39:17 (INFO): (PROFIT REPORT) start time:      2016-07-03 08:25:00
2016-07-03 23:39:17 (INFO): (PROFIT REPORT) end time:      2016-07-03 20:00:00
2016-07-03 23:39:17 (INFO): (PROFIT REPORT) timespan:      12 hours days

2016-07-03 23:39:17 (INFO): (PROFIT REPORT) start price:       605
2016-07-03 23:39:17 (INFO): (PROFIT REPORT) end price:       599.99
2016-07-03 23:39:17 (INFO): (PROFIT REPORT) Buy and Hold profit:     -0.8281000000000063%

2016-07-03 23:39:17 (INFO): (PROFIT REPORT) amount of trades:    3
2016-07-03 23:39:17 (INFO): (PROFIT REPORT) original simulated balance:  708.46800 EUR
2016-07-03 23:39:17 (INFO): (PROFIT REPORT) current simulated balance:   687.88514 EUR
2016-07-03 23:39:17 (INFO): (PROFIT REPORT) simulated profit:    -20.58286 EUR (-2.90526%)
2016-07-03 23:39:17 (INFO): (PROFIT REPORT) simulated yearly profit:   -15565.97087 EUR (-2197.13112%)

Could you post the backtest settings (in the config)?

Hmm that is weird. Yesterday I tested with the same times and it failed. Now this morning I run the backtest with the same config and it works. However now if I use 7:19 (which is now) and run the backtest I get a other error again:

2016-07-04 07:20:43 (WARN):	Simulation based on incomplete market data (10 missing between 2016-07-04 04:40:00 and 2016-07-04 05:19:00).

but then for the following backtest range:
config.backtest = {   adapter: 'sqlite',   daterange: {     from: moment.utc("2016-07-03 10:20:00"),     to: moment.utc("2016-07-04 07:19:00")   },   batchSize: 50 }
and with this newer database:
kraken_0.1.db.zip
I guess you cannot use now or a the last couple of hours in your backtest range.

Keep in mind that strings passed into moment.utc will assume the utc
timezone! At the time you wrote that comment it was only 5:24 UTC.
If you want to use your system's local timezones, just adjust the
configuration to:
moment("your time")

(remove .utc)
Hmm that is weird. Yesterday I tested with the same times and it failed.
Now this morning I run the backtest with the same config and it works.
However now if I use 7:19 (which is now) and run the backtest I get a other
error again:
2016-07-04 07:20:43 (WARN): Simulation based on incomplete market data (10
missing between 2016-07-04 04:40:00 and 2016-07-04 05:19:00).
but then for the following backtest range:
config.backtest = {
adapter: 'sqlite',
daterange: {
from: moment.utc("2016-07-03 10:20:00"),
to: moment.utc("2016-07-04 07:19:00")
},
batchSize: 50
}
and with this newer database:
kraken_0.1.db.zip
https://github.com/askmike/gekko/files/345648/kraken_0.1.db.zip
I guess you cannot use now or a the last couple of hours in your backtest
range.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/askmike/gekko/issues/366#issuecomment-230207391, or mute
the thread
https://github.com/notifications/unsubscribe/AA7MD6O1W_d55jBjPkhnSRuvv54cA8EPks5qSJkkgaJpZM4JD8L2
.

I am pretty sure that should fix the issue, if you have more problems just comment here and I'll re open.

@rvzanten I just pushed a new feature to the develop branch which might be of interest. If you change your config.backtest.daterange to scan, Gekko will dynamically figure out what dateranges are available to you:
2016-07-07 00:33:33 (INFO): Scanning local history for backtestable dateranges.
2016-07-07 00:33:33 (INFO): The database has 3 candles missing, Figuring out which ones...
2016-07-07 00:33:33 (INFO): Gekko detected multiple dateranges in the locally stored history. Please pick the daterange you are interested in testing:
2016-07-07 00:33:33 (INFO):      OPTION 1:
2016-07-07 00:33:33 (INFO):    from: 2016-07-03 08:50:00
2016-07-07 00:33:33 (INFO):    to: 2016-07-03 12:50:00
2016-07-07 00:33:33 (INFO):      OPTION 2:
2016-07-07 00:33:33 (INFO):    from: 2016-07-03 13:50:00
2016-07-07 00:33:33 (INFO):    to: 2016-07-03 21:50:00
prompt: option:

And then you type either 1 or 2 (and hit enter), depending on what data you want to Gekko to backtest against.

@askmike Awesome!


Add nationality, remark, and priority fields to Person class

Tasks

[ ] Add nationality field (PR #)
[x] Add remark field (PR #40)
[ ] Add priority field (PR #)

Nationality field to be implemented in Milestone 1.3 (i.e. week 9)


API Security - Prevent NoSQL Injection & Sanitize Data

API Security - Implement functionality to  Prevent NoSQL Injection & Sanitize Data.

installed express-mongo-sanitize package to sanitize data, therefore, preventing NoSQL injection.

$npm i express-monog-sanitize


CI is not reporting the results of the test

Environment
The node.js.yaml workflow is not being reported even though it passes
Steps to reproduce

Create a PR that passes all tests

Expected result

Tests to be reported

Actual Result

Waiting for reports

@btlghrants fixed this by editing a branch protection rule


Hotfix/fixtests

This PR fixes the current testsuite by adapting the calls to phpunits deprecated getMock-methods to either createMock or to getMockObject
During this process I stumbled over two tests created by @choult that are either obsolete by now or that were working already but have been marked to skip. Can you shed some light there please?

@heiglandreas Oo, that's a bit old... I suspect that was a bit naughty - found a problem via testing and then didn't fix it... There might be a corresponding ticket in JIRA somewhere

As to the VersionedRouter test, yes we still need it (we're using VersionedRouter in the front controller) but you can probably convert the mocked VersionedRouter to a concrete one and remove the reference to getLegacyRoute - it looks like that was a piece of scaffolding that is no longer required.

I didn't want to remove all of the VersionedRouterTests :wink: I'll have a look at the getRouteas that one seemed to expect that legacy method...
Thanks for the insight @choult!

The changes to replace getMockBuilder etc are all good, but I'm a little nervous about removing the Timezone class - I can't see why it would have been written in the first place if it wasn't needed...
That said, perhaps it is just something that has been 'written out' of the system over time and is no-longer required, so perhaps it just needs a close going over to ensure it doesn't have any knock-on elsewhere?

I checked for occurrences of calls to the Timezone-class and couldn't find some apart from the removed ones. But you are right, it'S out of the scope of the test-fixes so I should move that to a separate PR with separate tests.

OK cool, I'll leave that with you then :-)

Moved the Timezone-stuff into https://github.com/joindin/joindin-api/pull/344

Perfect- looks good, but I'm on my mobile, will merge when I get a chance.


Jest config is recognized in config-overrides.js but not package.json

I had to set transformIgnorePatterns in my rewired app to fix build issues with Jest, but for some reason I could not get it to honor my config when putting it in package.json in the jest field (which seems to be supported according to the readme). This caused me a bit of confusion until I realized the same config worked in config-overrides.js with the jest config function.
Oddly enough, I do get validation errors when the Jest config in package.json is in the wrong format, even though Jest still ignores transforming this module as if I never configured it and errors with SyntaxError: Cannot use import statement outside a module.
Working with config-overrides.js: https://github.com/nickmccurdy/type-explorer/tree/c710a2bd65d1c565662781cb81c8c2b00d878ca1
Broken with package.json: https://github.com/nickmccurdy/type-explorer/tree/1dc167e4139c5ded037b7e5dfc60ed15e67bdeca

Closing this as no one has picked it up.
If you believe this is a bug please like to a sample repo ... better chance of someone looking at it.

@nickmccurdy
写在 package.json 里面：新加的规则与 cra 默认规则 or 操作 new RegExp(config.transformIgnorePatterns.join('|')), cra 默认匹配node_modules 所有，因此你写的 ?!monaco-editor/ 无效
写在 config-overrides.js 里面：覆盖 cra 默认规则

If you want to customize your build tool, use Vite