Create test.md

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] File:../.vscode/settings.json not existed.
[Error] Some error ocurred while parsing changelist file: W:\51ii-log-421685a6\change-list-with-redirection.tsv.

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

BingMaps/spatial-data-services/TOC.yml
:warning:Warning

Details

BingMaps/v8-web-control/spatial-data-services-module-examples.md
:warning:Warning

Details

BingMaps/v8-web-control/spatial-data-service-module.md
:warning:Warning

Details

BingMaps/spatial-data-services/query-api/query-response-description.md
:warning:Warning

Details

BingMaps/spatial-data-services/public-data-sources/2010-us-census-data-sources.md
:warning:Warning

Details

BingMaps/spatial-data-services/geocode-dataflow-api/index.md
:warning:Warning

Details

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-sample-code.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/download-data-source-dataflow/index.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/download-data-source-dataflow/get-downloaded-data.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/delete-data-source.md
:warning:Warning

Details

BingMaps/spatial-data-services/whats-new-in-bing-spatial-data-services.md
:warning:Warning

Details

BingMaps/spatial-data-services/bing-spatial-data-services-api-reference.md
:warning:Warning

Details

BingMaps/spatial-data-services/query-api/query-options.md
:warning:Warning

Details

BingMaps/spatial-data-services/query-api/query-near-route.md
:warning:Warning

Details

BingMaps/spatial-data-services/query-api/query-by-property.md
:warning:Warning

Details

BingMaps/spatial-data-services/query-api/query-by-id.md
:warning:Warning

Details

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-data-schema-version-2-0.md
:warning:Warning

Details

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-data-schema-version-1-0.md
:warning:Warning

Details

BingMaps/spatial-data-services/geocode-dataflow-api/download-geocode-job-results.md
:warning:Warning

Details

BingMaps/spatial-data-services/geocode-dataflow-api/create-a-geocode-job-and-upload-data.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/download-data-source-dataflow/get-download-data-source-job-status.md
:warning:Warning

Details

BingMaps/spatial-data-services/release-history.md
:warning:Warning

Details

BingMaps/spatial-data-services/make-a-data-source-public.md
:warning:Warning

Details

BingMaps/getting-started/understanding-bing-maps-transactions.md
:warning:Warning

Details

BingMaps/articles/accessing-the-bing-spatial-data-services-using-php.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/create-a-load-data-source-job-and-input-entity-data.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/get-data-source-information.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/get-all-public-data-sources.md
:warning:Warning

Details

BingMaps/v8-web-control/choropleth-map-example.md
:warning:Warning

Details

BingMaps/spatial-data-services/index.md
:warning:Warning

Details

BingMaps/spatial-data-services/getting-started-with-the-spatial-data-services.md
:warning:Warning

Details

BingMaps/v8-web-control/what-s-new.md
:warning:Warning

Details

BingMaps/spatial-data-services/query-api/query-by-area.md
:warning:Warning

Details

BingMaps/spatial-data-services/query-api/query-api-sample-code-vb.md
:warning:Warning

Details

BingMaps/spatial-data-services/geocode-dataflow-api/get-status-of-a-geocode-job.md
:warning:Warning

Details

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-walkthrough.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/publish-staged-data-source.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/geography-types.md
:warning:Warning

Details

BingMaps/rest-services/routes/calculate-a-distance-matrix.md
:warning:Warning

Details

BingMaps/getting-started/getting-data-source-information.md
:warning:Warning

Details

BingMaps/v8-web-control/find-nearby-example.md
:warning:Warning

Details

BingMaps/v8-web-control/find-by-property-example.md
:warning:Warning

Details

BingMaps/spatial-data-services/query-api/query-api-sample-code-csharp.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/load-data-source-data-schema-and-sample-input.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/download-data-source-dataflow/create-a-download-job.md
:warning:Warning

Details

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-sample-input-and-output-data-version-2-0.md
:warning:Warning

Details

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-sample-input-and-output-data-version-1-0.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/helpful-tips-for-entity-data.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/get-load-data-source-status.md
:warning:Warning

Details

BingMaps/spatial-data-services/data-source-management-api/rollback-data-source-dataflow.md
:warning:Warning

Details

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

BingMaps/spatial-data-services/TOC.yml

Line 0: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/load-data-source-dataflow/publish-a-staged-data-source.md).
Line 0: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/make-a-data-source-public.md).

BingMaps/v8-web-control/spatial-data-services-module-examples.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/query-api.md).
Line 19: [Warning] Invalid file link:(~/spatial-data-services/query-api.md).

BingMaps/v8-web-control/spatial-data-service-module.md

Line 21: [Warning] Invalid file link:(~/spatial-data-services/query-api.md).
Line 23: [Warning] Invalid file link:(~/spatial-data-services/query-api.md).

BingMaps/spatial-data-services/query-api/query-response-description.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-id.md).

BingMaps/spatial-data-services/public-data-sources/2010-us-census-data-sources.md

Line 95: [Warning] Invalid file link:(~/spatial-data-services/v8-web-control/choropleth-map-example.md).

BingMaps/spatial-data-services/geocode-dataflow-api/index.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-and-data-source-limits.md).
Line 23: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-data-schema-version-2-0.md).
Line 23: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-data-schema-version-1-0.md).
Line 25: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/create-a-geocode-job-and-upload-data.md).
Line 27: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/get-status-of-a-geocode-job.md).
Line 29: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/download-geocode-job-results.md).
Line 31: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-walkthrough.md).
Line 33: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/get-job-list.md).
Line 39: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/create-a-geocode-job-and-upload-data.md).
Line 40: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/get-status-of-a-geocode-job.md).
Line 41: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/download-geocode-job-results.md).
Line 42: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-response-description.md).
Line 43: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-walkthrough.md).
Line 44: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-code.md).
Line 45: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-data-schema-version-1-0.md).
Line 46: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-data-schema-version-2-0.md).
Line 47: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-1-0.md).
Line 48: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-2-0.md).

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-sample-code.md

Line 23: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/create-a-geocode-job-and-upload-data.md).

BingMaps/spatial-data-services/data-source-management-api/download-data-source-dataflow/index.md

Line 23: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/create-a-download-job.md).
Line 25: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-download-data-source-job-status.md).
Line 27: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-downloaded-data.md).
Line 33: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/create-a-download-job.md).
Line 34: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-download-data-source-job-status.md).
Line 35: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-downloaded-data.md).
Line 36: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/download-data-source-walkthrough.md).
Line 37: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/download-data-source-dataflow-response-description.md).

BingMaps/spatial-data-services/data-source-management-api/download-data-source-dataflow/get-downloaded-data.md

Line 103: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/download-data-source-dataflow-response-description.md).
Line 105: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/download-data-source-walkthrough.md).

BingMaps/spatial-data-services/data-source-management-api/delete-data-source.md

Line 21: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-and-data-source-limits.md).
Line 23: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/get-job-list.md).
Line 33: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/get-data-source-information.md).
Line 50: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/get-data-source-information.md).
Line 51: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/get-data-source-information.md).
Line 70: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/status-codes-and-error-handling.md).

BingMaps/spatial-data-services/whats-new-in-bing-spatial-data-services.md

Line 37: [Warning] Invalid file link:(~/spatial-data-services/load-data-source-data-schema-and-sample-input.md).
Line 37: [Warning] Invalid file link:(~/spatial-data-services/geography-types.md).
Line 43: [Warning] Invalid file link:(~/spatial-data-services/geography-types.md).
Line 43: [Warning] Invalid file link:(~/spatial-data-services/query-by-area.md).
Line 45: [Warning] Invalid file link:(~/spatial-data-services/public-data-sources.md).
Line 47: [Warning] Invalid file link:(~/spatial-data-services/query-by-area.md).
Line 47: [Warning] Invalid file link:(~/spatial-data-services/query-by-property.md).
Line 55: [Warning] Invalid file link:(~/spatial-data-services/geocode-dataflow-api.md).
Line 55: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api.md).

BingMaps/spatial-data-services/bing-spatial-data-services-api-reference.md

Line 24: [Warning] Invalid file link:(~/spatial-data-services/geocode-dataflow-api.md).
Line 25: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api.md).
Line 26: [Warning] Invalid file link:(~/spatial-data-services/query-api.md).

BingMaps/spatial-data-services/query-api/query-options.md

Line 26: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-area.md).
Line 27: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geography-types.md).
Line 88: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geography-types.md).

BingMaps/spatial-data-services/query-api/query-near-route.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-options.md).
Line 17: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/traffic-incident-data-source.md).
Line 52: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-options.md).
Line 52: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-options.md).
Line 56: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).
Line 92: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/fourthcoffeesample.md).
Line 226: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/status-codes-and-error-handling.md).
Line 243: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-area.md).
Line 244: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-id.md).
Line 245: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-property.md).

BingMaps/spatial-data-services/query-api/query-by-property.md

Line 43: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geography-types.md).
Line 59: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geography-types.md).
Line 61: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-options.md).
Line 65: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).
Line 351: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/status-codes-and-error-handling.md).
Line 368: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-area.md).
Line 369: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-id.md).

BingMaps/spatial-data-services/query-api/query-by-id.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/load-data-source-data-schema-and-sample-input.md).
Line 56: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-options.md).
Line 60: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).
Line 262: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/status-codes-and-error-handling.md).
Line 279: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-area.md).
Line 280: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-property.md).

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-data-schema-version-2-0.md

Line 23: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-2-0.md).
Line 28: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-2-0.md).
Line 76: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-2-0.md).
Line 222: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-2-0.md).
Line 341: [Warning] Invalid file link:(~/spatial-data-services/rest-services/common-parameters-and-types/location-and-area-types.md).
Line 356: [Warning] Invalid file link:(~/spatial-data-services/rest-services/common-parameters-and-types/location-and-area-types.md).
Line 372: [Warning] Invalid file link:(~/spatial-data-services/rest-services/common-parameters-and-types/location-and-area-types.md).

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-data-schema-version-1-0.md

Line 18: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-2-0.md).
Line 26: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-1-0.md).
Line 217: [Warning] Invalid file link:(~/spatial-data-services/rest-services/common-parameters-and-types/location-and-area-types.md).
Line 218: [Warning] Invalid file link:(~/spatial-data-services/rest-services/common-parameters-and-types/location-and-area-types.md).

BingMaps/spatial-data-services/geocode-dataflow-api/download-geocode-job-results.md

Line 51: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-data-schema-version-2-0.md).
Line 54: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-code.md).
Line 54: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-walkthrough.md).

BingMaps/spatial-data-services/geocode-dataflow-api/create-a-geocode-job-and-upload-data.md

Line 27: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-and-data-source-limits.md).
Line 45: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-data-schema-version-2-0.md).
Line 50: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-2-0.md).
Line 86: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-response-description.md).
Line 89: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-code.md).
Line 89: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-walkthrough.md).
Line 182: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/status-codes-and-error-handling.md).

BingMaps/spatial-data-services/data-source-management-api/download-data-source-dataflow/get-download-data-source-job-status.md

Line 29: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/create-a-download-job.md).
Line 35: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-downloaded-data.md).
Line 37: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/download-data-source-walkthrough.md).
Line 57: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/download-data-source-dataflow-response-description.md).
Line 60: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-downloaded-data.md).
Line 147: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/status-codes-and-error-handling.md).

BingMaps/spatial-data-services/release-history.md

Line 21: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api.md).
Line 22: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api.md).
Line 23: [Warning] Invalid file link:(~/spatial-data-services/geocode-dataflow-api.md).
Line 23: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api.md).
Line 24: [Warning] Invalid file link:(~/spatial-data-services/load-data-source-data-schema-and-sample-input.md).
Line 24: [Warning] Invalid file link:(~/spatial-data-services/geography-types.md).
Line 24: [Warning] Invalid file link:(~/spatial-data-services/geography-types.md).
Line 24: [Warning] Invalid file link:(~/spatial-data-services/query-by-area.md).
Line 24: [Warning] Invalid file link:(~/spatial-data-services/query-by-area.md).
Line 24: [Warning] Invalid file link:(~/spatial-data-services/query-by-property.md).
Line 24: [Warning] Invalid file link:(~/spatial-data-services/query-api.md).
Line 24: [Warning] Invalid file link:(~/spatial-data-services/query-api.md).
Line 24: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api.md).
Line 25: [Warning] Invalid file link:(~/spatial-data-services/rollback-a-data-source-dataflow.md).
Line 25: [Warning] Invalid file link:(~/spatial-data-services/query-by-area.md).
Line 25: [Warning] Invalid file link:(~/spatial-data-services/delete-a-data-source.md).
Line 25: [Warning] Invalid file link:(~/spatial-data-services/get-data-source-information.md).
Line 25: [Warning] Invalid file link:(~/spatial-data-services/get-data-source-information.md).
Line 25: [Warning] Invalid file link:(~/spatial-data-services/create-a-download-job.md).
Line 25: [Warning] Invalid file link:(~/spatial-data-services/publish-a-staged-data-source.md).
Line 25: [Warning] Invalid file link:(~/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).
Line 26: [Warning] Invalid file link:(~/spatial-data-services/geocode-dataflow-api.md).
Line 26: [Warning] Invalid file link:(~/spatial-data-services/query-by-area.md).
Line 26: [Warning] Invalid file link:(~/spatial-data-services/query-by-area.md).
Line 26: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api.md).

BingMaps/spatial-data-services/make-a-data-source-public.md

Line 55: [Warning] Invalid file link:(~/spatial-data-services/download-data-source-dataflow-response-description.md).
Line 66: [Warning] Invalid file link:(~/spatial-data-services/get-data-source-information.md).

BingMaps/getting-started/understanding-bing-maps-transactions.md

Line 109: [Warning] Invalid file link:(~/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).
Line 110: [Warning] Invalid file link:(~/spatial-data-services/get-load-data-source-status.md).
Line 110: [Warning] Invalid file link:(~/spatial-data-services/get-load-data-source-status.md).
Line 110: [Warning] Invalid file link:(~/spatial-data-services/get-status-of-a-geocode-job.md).
Line 111: [Warning] Invalid file link:(~/spatial-data-services/download-geocode-job-results.md).
Line 112: [Warning] Invalid file link:(~/spatial-data-services/get-data-source-information.md).
Line 113: [Warning] Invalid file link:(~/spatial-data-services/get-data-source-information.md).
Line 114: [Warning] Invalid file link:(~/spatial-data-services/get-data-source-information.md).
Line 115: [Warning] Invalid file link:(~/spatial-data-services/get-data-source-information.md).
Line 116: [Warning] Invalid file link:(~/spatial-data-services/get-downloaded-data.md).
Line 116: [Warning] Invalid file link:(~/spatial-data-services/create-a-download-job.md).
Line 117: [Warning] Invalid file link:(~/spatial-data-services/delete-a-data-source.md).
Line 119: [Warning] Invalid file link:(~/spatial-data-services/query-by-area.md).
Line 119: [Warning] Invalid file link:(~/spatial-data-services/query-api.md).

BingMaps/articles/accessing-the-bing-spatial-data-services-using-php.md

Line 152: [Warning] Invalid file link:(~/spatial-data-services/geocode-dataflow-data-schema-version-1-0.md).

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/create-a-load-data-source-job-and-input-entity-data.md

Line 21: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/geocode-and-data-source-limits.md).
Line 37: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/geocode-and-data-source-limits.md).
Line 55: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/load-data-source-data-schema-and-sample-input.md).
Line 56: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/make-a-data-source-public.md).
Line 57: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/publish-a-staged-data-source.md).
Line 57: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/publish-a-staged-data-source.md).
Line 65: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/load-data-source-data-schema-and-sample-input.md).
Line 94: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/load-data-source-dataflow-response-description.md).
Line 99: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/load-data-source-data-schema-and-sample-input.md).
Line 196: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/load-data-source-dataflow-response-description.md).
Line 199: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/status-codes-and-error-handling.md).

BingMaps/spatial-data-services/data-source-management-api/get-data-source-information.md

Line 86: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-options.md).
Line 288: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/status-codes-and-error-handling.md).

BingMaps/spatial-data-services/data-source-management-api/get-all-public-data-sources.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/make-a-data-source-public.md).

BingMaps/v8-web-control/choropleth-map-example.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/2010-us-census-data-sources.md).

BingMaps/spatial-data-services/index.md

Line 21: [Warning] Invalid file link:(~/spatial-data-services/geocode-dataflow-api.md).
Line 23: [Warning] Invalid file link:(~/spatial-data-services/query-api.md).
Line 23: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api.md).
Line 37: [Warning] Invalid file link:(~/spatial-data-services/public-data-sources.md).
Line 41: [Warning] Invalid file link:(~/spatial-data-services/geocode-dataflow-api.md).
Line 42: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api.md).
Line 43: [Warning] Invalid file link:(~/spatial-data-services/query-api.md).

BingMaps/spatial-data-services/getting-started-with-the-spatial-data-services.md

Line 30: [Warning] Invalid file link:(~/spatial-data-services/geocode-dataflow-api.md).
Line 30: [Warning] Invalid file link:(~/spatial-data-services/geocode-dataflow-api.md).
Line 30: [Warning] Invalid file link:(~/spatial-data-services/geocode-dataflow-walkthrough.md).
Line 33: [Warning] Invalid file link:(~/spatial-data-services/load-data-source-dataflow.md).
Line 36: [Warning] Invalid file link:(~/spatial-data-services/query-api.md).
Line 39: [Warning] Invalid file link:(~/spatial-data-services/load-data-source-dataflow.md).
Line 42: [Warning] Invalid file link:(~/spatial-data-services/download-a-data-source-dataflow.md).
Line 45: [Warning] Invalid file link:(~/spatial-data-services/delete-a-data-source.md).
Line 48: [Warning] Invalid file link:(~/spatial-data-services/load-data-source-dataflow.md).
Line 48: [Warning] Invalid file link:(~/spatial-data-services/publish-a-staged-data-source.md).
Line 51: [Warning] Invalid file link:(~/spatial-data-services/rollback-a-data-source-dataflow.md).
Line 54: [Warning] Invalid file link:(~/spatial-data-services/get-data-source-information.md).
Line 64: [Warning] Invalid file link:(~/spatial-data-services/navteqna.md).
Line 65: [Warning] Invalid file link:(~/spatial-data-services/navteqeu.md).
Line 66: [Warning] Invalid file link:(~/spatial-data-services/traffic-incident-data-source.md).
Line 67: [Warning] Invalid file link:(~/spatial-data-services/fourthcoffeesample.md).

BingMaps/v8-web-control/what-s-new.md

Line 140: [Warning] Invalid file link:(~/spatial-data-services/2010-us-census-data-sources.md).

BingMaps/spatial-data-services/query-api/query-by-area.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-options.md).
Line 37: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-near-a-route.md).
Line 39: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-property.md).
Line 63: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geography-types.md).
Line 79: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geography-types.md).
Line 80: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-options.md).
Line 80: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-options.md).
Line 84: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).
Line 480: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/status-codes-and-error-handling.md).
Line 497: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-id.md).
Line 498: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-by-property.md).

BingMaps/spatial-data-services/query-api/query-api-sample-code-vb.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-api.md).

BingMaps/spatial-data-services/geocode-dataflow-api/get-status-of-a-geocode-job.md

Line 29: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-response-description.md).
Line 29: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/create-a-geocode-job-and-upload-data.md).
Line 42: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-response-description.md).
Line 60: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-response-description.md).
Line 63: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-code.md).
Line 63: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-walkthrough.md).
Line 153: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/status-codes-and-error-handling.md).

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-walkthrough.md

Line 22: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-data-schema-version-2-0.md).
Line 24: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-2-0.md).
Line 69: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/create-a-geocode-job-and-upload-data.md).
Line 78: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-response-description.md).
Line 112: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/get-status-of-a-geocode-job.md).

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/publish-staged-data-source.md

Line 19: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/geocode-and-data-source-limits.md).
Line 29: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/geocode-and-data-source-limits.md).
Line 33: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).
Line 54: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-data-source-information.md).
Line 54: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-load-data-source-status.md).
Line 55: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-data-source-information.md).
Line 55: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-load-data-source-status.md).
Line 56: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/geography-types.md

Line 19: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/load-data-source-data-schema-and-sample-input.md).
Line 21: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/query-options.md).
Line 23: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/query-options.md).

BingMaps/rest-services/routes/calculate-a-distance-matrix.md

Line 60: [Warning] Invalid file link:(~/media/distancematrixcellcalculation2.PNG).
Line 66: [Warning] Invalid file link:(~/media/distancematrixasynccellcalculation2.PNG).
Line 77: [Warning] Invalid file link:(~/media/distancematrixtransactioncalculation2.PNG).
Line 83: [Warning] Invalid file link:(~/media/distancematrixasynctransactioncalculation2.PNG).

BingMaps/getting-started/getting-data-source-information.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api.md).

BingMaps/v8-web-control/find-nearby-example.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/navteqna.md).

BingMaps/v8-web-control/find-by-property-example.md

Line 68: [Warning] Invalid file link:(~/spatial-data-services/navteqna.md).

BingMaps/spatial-data-services/query-api/query-api-sample-code-csharp.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/query-api.md).

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/load-data-source-data-schema-and-sample-input.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).
Line 17: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/geocode-and-data-source-limits.md).
Line 30: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/helpful-tips-for-entity-data.md).
Line 74: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/geography-types.md).
Line 104: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/geography-types.md).
Line 136: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).

BingMaps/spatial-data-services/data-source-management-api/download-data-source-dataflow/create-a-download-job.md

Line 37: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-download-data-source-job-status.md).
Line 39: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/download-data-source-walkthrough.md).
Line 48: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-data-source-information.md).
Line 49: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-data-source-information.md).
Line 50: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-data-source-information.md).
Line 61: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/download-data-source-dataflow-response-description.md).
Line 68: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/get-download-data-source-job-status.md).
Line 148: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/status-codes-and-error-handling.md).

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-sample-input-and-output-data-version-2-0.md

Line 17: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-data-schema-version-2-0.md).

BingMaps/spatial-data-services/geocode-dataflow-api/geocode-dataflow-sample-input-and-output-data-version-1-0.md

Line 18: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-2-0.md).
Line 18: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-sample-input-and-output-data-version-2-0.md).
Line 20: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-dataflow-data-schema-version-1-0.md).

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/helpful-tips-for-entity-data.md

Line 21: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/load-data-source-data-schema-and-sample-input.md).

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/get-load-data-source-status.md

Line 29: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).
Line 31: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/load-data-source-dataflow-response-description.md).
Line 45: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).
Line 55: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/load-data-source-dataflow-response-description.md).
Line 60: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).
Line 234: [Warning] Invalid file link:(~/spatial-data-services/data-source-management-api/spatial-data-services/status-codes-and-error-handling.md).

BingMaps/spatial-data-services/data-source-management-api/rollback-data-source-dataflow.md

Line 19: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/geocode-and-data-source-limits.md).
Line 21: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/get-job-list.md).
Line 33: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/get-data-source-information.md).
Line 54: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/get-data-source-information.md).
Line 56: [Warning] Invalid file link:(~/spatial-data-services/spatial-data-services/create-a-load-data-source-job-and-input-entity-data.md).

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


[1.2.x] Backport JDK 11 testing

To validate this pull request against other sbt modules, please visit this link.


feat: create cosmwasmclient & its cdn

To do
Publish cosmwasmclient & cdn

Changes

Supported CosmWasm/wasmd v0.28.0
Update cosmos-client-ts v0.46
Add REST API for CosmWasm
Test code for MsgInstantiateContract Tx
Change some environment setting files


Image layout options

I'm using the PowerShell Module PSWriteOffice for Word document creation and I'm trying to insert an image using the following code:
elseif ($Paragraph.Text -like "<TODO: Insert  Image>") {
            $Paragraph.Text = ''
            $Paragraph.AddImage("C:\temp\image.png")
            $Paragraph.ParagraphAlignment = 'Center'
            $Paragraph.IndentationBefore = 1
            $Paragraph.IndentationAfter = 1
        }

But I need to apply the following layout configuration.

How can this be done programmatically?
Regards,
Stefan Stranger

Hi,
I need to update PSWriteOffice to newest library version, because we already support those layouts in newest one
var pargraphWithImage = paragraph.AddImage(file, 100, 100, WrapTextImage.InLineWithText, "Przemek and Kulek on an image");

In PowerShell it will be like
$pargraphWithImage = $paragraph.AddImage(file, 100, 100, [WrapTextImage]::InLineWithText, "Przemek and Kulek on an image");

Probably the WrapTextImage will need a full type or using to work. New version also allows switching between TextWrappings

So as soon as the image is added you can also change it on the fly. I'm neglegtic powershell version a bit, but OfficeIMO alone is hard to manage ;)

Hi Przemysław,
Thanks for your fast response. Do I understand I need to wait for you to update the PowerShell module to use the latest library?
When I try to do it using the existing library I get the following error:
$Paragraph.Image.WrapText = 'BehindText'
SetValueInvocationException: Exception setting "WrapText": "This needs to be implemented properly!"

Regards,
Stefan Stranger

Ye, I'll try to release it tonight. I've not updated the library for a bit. Also keep in mind that when you switch between different Wraps (Inline vs Anchor) it looses certain prroperties. Inline has minimal set properties because it's kind of bound to paragraph, and the rest is basically anchored, so you would need to play with positioning after doing changes like that.

I've released new version - you can try it out.

@PrzemyslawKlys
I tried to update the PSWriteOffice module via the PowerShell gallery but got this error message:
Install-Package: Authenticode issuer 'CN=Przemysław Kłys EVOTEC, O=Przemysław Kłys EVOTEC, L=Mikołów, C=PL' of
the new module 'PSWriteOffice' with version '0.2.0' from root certificate authority
'CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US' is not matching with
the authenticode issuer 'CN=Przemysław Kłys EVOTEC, O=Przemysław Kłys EVOTEC, L=Katowice,
S=Śląskie, C=PL' of the previously-installed module 'PSWriteOffice' with version '0.1.0' from
root certificate authority 'CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert
Inc, C=US'. If you still want to install or update, use -SkipPublisherCheck parameter.

Install-Module PSWriteOffice -Force -Verbose -SkipPublisherCheck
I changed certificate some time ago, as my last one expired and there's no other way around it.

Ok I did the use the -skippublishercheck option to resolve this.
Should I ask internally on how above error can be fixed?
Stefan Stranger
[MSFT]

The error above is not really an error. Once you install module with certain certificate it's there to protect you a bit from changes or dropping non-signed versions. However when my 3 year certificate expired and it changes - that is the cert warning you get. I wish it was easier, but you can either delete the old versions and do install-module without skippublishercheck, or use skippublishercheck. Otherwise that's the warning you get.


Never uninstall APK without permission

Use case

Currently, "flutter run" on Android will attempt to install the APK and if it fails, it will uninstall the old version and try to install the app again. This is very bad, because it has the effect of wiping all of the app's storage without permission, potentially deleting important data.
Proposal

Add a command-line option to force removal of the old version, and suggest this option to the user if a normal invocation of "flutter run" fails, but don't let "flutter run" uninstall an app without permission.

Installing can fail for any number of reasons. Requiring users to always pass a flag to uninstall is going to be extremely disruptive.
Do you have any alternative suggestions for behavior changes here?

Installing can fail for any number of reasons.

Still, this is not the normal case, and it makes me very concerned that flutter could delete an app's storage without permission as a fallback option when an exceptional error occurs.

Requiring users to always pass a flag to uninstall is going to be extremely disruptive.

Ahem... Losing all of my data last night was extremely disruptive. Which do you think is more disruptive?

Do you have any alternative suggestions for behavior changes here?

Telling the user that the install failed and asking them permission before deleting the app's storage. If you don't like the idea of passing a force option, you could make it a prompt, but the prompt should default to "No" and should require a 3 letter "Yes" answer because I do not want any chance of accidentally deleting data by hitting the wrong key at the prompt.

Prompting to uninstall seems like a reasonable change we could make, provided a terminal is attached.

That's OK for me as a terminal user, although in the spirit of not causing a "critical data loss" for anyone else, I think something equally safe should also be done for non-terminal users.
I don't know much about how the non-terminal interface(s) works, though. Maybe a dialog: "Installation failed." with two options "Try again" or "Remove and re-install app - Note: this will delete the app's storage!"

For anyone else who, like me, is TERRIFIED to type flutter run because flutter might delete all of their app's data, I found a way to protect your app's data from the flutter tool.
In my case, it was triggered by a flaky USB connection. This is no excuse to delete your data without warning, but if this is also the trigger in your case, you can just try running adb over WIFI:
adb tcpip 5555
adb connect ip-address-of-android-device

I hope nobody lost as much data as I did, but try the above and save your data.

adb over wifi can still lead to data loss if adb reports INSTALL_FAILED_INSUFFICIENT_STORAGE.


Is there a way to support multiline blockquotes?

Currently on a blockquote line if you hit enter, quill starts a new blockquote (rather than what I  expected -- just adding a new line into the current blockquote). This feels like a bug imo -- the blockquote should end on 2 enters (i.e. a blank line between them).
Although if you consider this expected behavior is there a way to create a new blockquote blot that would behave this way? Or any other way?
Expected behavior:
Support for multiline blockquote
Actual behavior:
Multiple blockquote blocks
Platforms: Any
Version: 1.0.6

This is behaving as designed. You can create your own blockquote format that behaves as you'd like and there's a large body of documentation on the topic of custom formats. A starting point is http://quilljs.com/guides/cloning-medium-with-parchment/ and a good reference is https://github.com/quilljs/parchment/. You may also find the code block's behavior / code informative as it does something similar.

Did someone achieve multiline blockquote?

Hello everyone, I find a simple way to do this. with pure CSS.
This is the code

I figured it out!

Open Medium Editor
Select "Markdown"
Paste your multiline blockquote into the embedded Markdown editor
Select the pasted multiline quote
Click the quote mark icon
Profit!

I'm also super interested in this and after reading the documentation and linked guides I am not comfortable with implementing my own,

Seems it's really easy achievable by just customizing the CSS style for <blockquote>. There's a blockquote style:
.ql-snow .ql-editor blockquote {
  border-left: 4px solid #ccc;
  margin-bottom: 5px;
  margin-top: 5px;
  padding-left: 16px;
}

So we should simply replace margin-bottom and margin-top with padding-bottom and padding-top, and we've got what we want:
.ql-snow .ql-editor blockquote {
  border-left: 4px solid #ccc;
  padding-bottom: 5px;
  padding-top: 5px;
  padding-left: 16px;
}

The con here is that you need to host the .css file on your side; alternatively -- overwrite it after the main css is loaded.

Seems it's really easy achievable by just customizing the CSS style

This still produces multiple <blockquote> Tags.
I actually kind of managed to write something custom... its basically a slightly modified code block. It definitely wasn't easy and I don't really understand what I did here. You also can't escape the blockquote anymore, maybe someone with more knowledge than me on quill can help. Here's what I got:
import { Quill } from 'react-quill';

const BlockQuote = Quill.import('formats/blockquote');
const Parchment = Quill.import('parchment');
const Delta = Quill.import('delta');
const TextBlot = Quill.import('blots/text');

class CustomBlockQuote extends BlockQuote {
  static formats() {
    return true;
  }

  delta() {
    let text = this.domNode.textContent;
    // Should always be true
    if (text.endsWith('\n')) {
      text = text.slice(0, -1);
    }
    return text.split('\n').reduce((delta, frag) => {
      return delta.insert(frag).insert('\n', this.formats());
    }, new Delta());
  }

  format(name, value) {
    if (name === this.statics.blotName && value) return;
    let [text, ] = this.descendant(TextBlot, this.length() - 1);
    if (text != null) {
      text.deleteAt(text.length() - 1, 1);
    }
    super.format(name, value);
  }

  formatAt(index, length, name, value) {
    if (length === 0) return;
    if (Parchment.query(name, Parchment.Scope.BLOCK) == null ||
      (name === this.statics.blotName && value === this.statics.formats(this.domNode))) {
      return;
    }
    let nextNewline = this.newlineIndex(index);
    if (nextNewline < 0 || nextNewline >= index + length) return;
    let prevNewline = this.newlineIndex(index, true) + 1;
    let isolateLength = nextNewline - prevNewline + 1;
    let blot = this.isolate(prevNewline, isolateLength);
    let next = blot.next;
    blot.format(name, value);
    if (next instanceof BlockQuote) {
      next.formatAt(0, index - prevNewline + length - isolateLength, name, value);
    }
  }

  insertAt(index, value, def) {
    if (def != null) return;
    let [text, offset] = this.descendant(TextBlot, index);
    text.insertAt(offset, value);
  }

  length() {
    let length = this.domNode.textContent.length;
    if (!this.domNode.textContent.endsWith('\n')) {
      return length + 1;
    }
    return length;
  }

  newlineIndex(searchIndex, reverse = false) {
    if (!reverse) {
      let offset = this.domNode.textContent.slice(searchIndex).indexOf('\n');
      return offset > -1 ? searchIndex + offset : -1;
    } else {
      return this.domNode.textContent.slice(0, searchIndex).lastIndexOf('\n');
    }
  }

  optimize(context) {
    if (!this.domNode.textContent.endsWith('\n')) {
      this.appendChild(Parchment.create('text', '\n'));
    }
    super.optimize(context);
    let next = this.next;
    if (next != null && next.prev === this &&
      next.statics.blotName === this.statics.blotName &&
      this.statics.formats(this.domNode) === next.statics.formats(next.domNode)) {
      next.optimize(context);
      next.moveChildren(this);
      next.remove();
    }
  }

  replace(target) {
    super.replace(target);
    [].slice.call(this.domNode.querySelectorAll('*')).forEach(function(node) {
      let blot = Parchment.find(node);
      if (blot == null) {
        node.parentNode.removeChild(node);
      } else if (blot instanceof Parchment.Embed) {
        blot.remove();
      } else {
        blot.unwrap();
      }
    });
  }
}

CustomBlockQuote.blotName = 'blockquote';
CustomBlockQuote.tagName = 'blockquote';

export default CustomBlockQuote;

Can't quite understand why there is no option for this - it could have been done like css and inline-styles can be opt-in.

Hello everyone, I find a simple way to do this. with pure CSS.
This is the code

I really like 嘉然's CSS solution above because it's super simple. But my quote block needs to start and end with quotation marks, so I need the quote lines to be wrapped in a container.

I tried digging around with custom blots, but it was way too complicated. It didn't seem right to build a quote block from scratch. Then I realized the built-in code-block tool fits my needs perfectly. So, I grabbed some source code and made a custom quote block.  Check it out in the codesandbox.
Demo video:
https://github.com/slab/quill/assets/23119906/46599142-70b7-4a89-b781-7df64b7a1b96

Just stumbled on this thread and I'll just leave another solution for posterity.
In my case adding this to my CSS worked:
.ql-snow .ql-editor blockquote+blockquote{ margin-top:-5px; }

The idea is to cancel the margin-top in the second blockquote of a sequence of two more. That makes multiple blockquotes look like they belong to single one. Fully supports indents and works on Chrome and Firefox. But, it may have other problems I'm not aware of.
One issue is that it is dependent on the snow theme: other themes might define a different margin-top and require some trimming. Unfortunately the selector must use the theme class otherwise it would be not specific enough to get any changes done to the style.


Fix condition for checking if we should use our own variant

There's no longer a feature check for std::variant. We assume it is always available.

retest cscs

LGTM thanks a lot I probably messed up when rebasing :/

I doubt it. There were enough changes to try to keep track of.
Note that this does not compile with CUDA for some mysterious reason. Changing to draft so noone accidentally merges.

This now compiles again with CUDA on Piz Daint (there's another CUDA problem with the CUDA version on Rostam, but I'm going to look at that separately). The original problem appeared when enabling namespace hpx { using std::variant; }. The three character change to not trigger the problem was to change hpx::tuple to std::tuple here: https://github.com/STEllAR-GROUP/hpx/blob/0db6fc565cc24a1356d0d87ae3728b1f0b69d399/libs/parallelism/execution/include/hpx/execution/algorithms/bulk.hpp#L101-L103. I'm assuming this is a result of some sort of name lookup bug in nvcc. In any case, since https://github.com/STEllAR-GROUP/hpx/blob/0db6fc565cc24a1356d0d87ae3728b1f0b69d399/libs/parallelism/execution/include/hpx/execution/algorithms/bulk.hpp#L101-L103 was nonsense anyway (I've copy-pasted it from another sender algorithm) I changed the code anyway and the problem no longer appears. I'm hoping it won't come back to bite us. I've also changed all uses of std::variant to hpx::variant (and the same for tuple and optional) in the sender algorithms. I'm somewhat worried about what this will do https://github.com/STEllAR-GROUP/hpx/blob/0724a93172c114093feaeb73ca4a64d5e4ce04d6/libs/core/datastructures/include/hpx/datastructures/variant.hpp#L16, but at least CI seems to be happy with it.


doc: fix doxygen error in ethernet.h

Doxygen comments for net_eth_promisc_mode parameters were incorrect
Signed-off-by: David B. Kinder<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #9100   +/-   ##
=======================================
  Coverage   52.42%   52.42%
=======================================
  Files         199      199
  Lines       25034    25034
  Branches     5236     5236
=======================================
  Hits        13125    13125
  Misses       9789     9789
  Partials     2120     2120

Impacted Files
Coverage Δ

include/net/ethernet.h
38.46% <ø> (ø)
:arrow_up:

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 a698e84...f9d5ecf. Read the comment docs.


Tweetbot support

this is a pull request that relates to issue #14

Wow, I am really surprised Tweetbot would support such a comprehensive list of deeplinking actions, even though they don't have a web interface ... Great work!
I think Xcode is making changes to the project on its own, and that caused a merge conflict with #15 .. I think you can revert the Xcode scheme changes or try to merge the latest master, and it should work.

fixed :+1:

Thanks for taking care of that, time to ship this! (also, thanks for taking care of the facebook docs!)


Rework the Engine using Actions and add Disaster/Prevention Cards

I rewrote the engine using an action framework where each action has a class that carries out the work.
I also added Disaster Me/All and Prevention cards to the deck.
The idea of having to put a disaster on another player isn't here because I didn't implement that logic on the client side or for the bots. The server logic exists.
I left all the unit tests in place for the old engine but didn't create new ones.
I did some game rebalancing for card frequency so that game stayed fun and winnable in a decent timeframe.
Fully addresses: #23
Partially addresses: #16

@mmwoodfo, those are great ideas. I had considered them, but got bogged down in the UI stuff and just wanted to get it committed. Thanks.


statistics: remove assumption of store time

What problem does this PR solve?
PR #1881 assumes time of stores are synchronized, but it's not true.
What is changed and how it works?
Remove that assumption.
Check List
Tests

Unit test

Codecov Report

Merging #1941 into master will increase coverage by 0.07%.
The diff coverage is 93.33%.

@@            Coverage Diff             @@
##           master    #1941      +/-   ##
==========================================
+ Coverage   78.09%   78.17%   +0.07%
==========================================
  Files         170      170
  Lines       16847    16845       -2
==========================================
+ Hits        13157    13168      +11
+ Misses       2683     2678       -5
+ Partials     1007      999       -8

Impacted Files
Coverage Δ

server/statistics/hot_peer_cache.go
89.63% <100%> (+0.39%)
:arrow_up:

server/statistics/hot_cache.go
95.83% <66.66%> (-2.39%)
:arrow_down:

pkg/etcdutil/etcdutil.go
82.6% <0%> (-5.8%)
:arrow_down:

server/schedulers/random_merge.go
65.45% <0%> (-3.64%)
:arrow_down:

server/tso/tso.go
77.37% <0%> (-2.92%)
:arrow_down:

server/heartbeat_streams.go
69% <0%> (-1%)
:arrow_down:

client/client.go
69.18% <0%> (-0.84%)
:arrow_down:

server/schedule/operator_controller.go
90.84% <0%> (-0.23%)
:arrow_down:

server/grpc_service.go
57.97% <0%> (+0.21%)
:arrow_up:

server/cluster.go
83.41% <0%> (+0.48%)
:arrow_up:

... and 5 more

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 5b831f6...caad674. Read the comment docs.


duplicate routes with Laravel 10 using breeze and sub domain not posting register to correct db

Bug description
I am getting duplicate route names when using Auth breeze package.  all the routes from the sub domain seems to be posting to the landlord database and not the new tenant db which was created when creating a new tenant.
Steps to reproduce

install new laravel version 10 on local
install breeze and run migrations etc...
install this package and follow install instructions for multi tenancy using separate databases etc...
setup tenancy as per docs for new tenancy and domain

Expected behavior
I would expect when navigating to /register or /login url from any of the sub domains, any of the post/get should default to the new tenant database and not the landlord database
Laravel version
10.14.1
stancl/tenancy version
3.7

i would also expect not to see duplicate routes with duplicate route names.  for example, password.update is referenced twice for tenant.test/password and /password - same for all the auth routes. /register and tenant.test/register

Hey!
Thanks for opening the issue. This doesn't seem to be a bug in the package, it seems to be related to your setup.
If you need quick support, you can visit our Discord community here: https://archte.ch/discord
Thanks


[Enhancement] Compatible with msql use truncate to delete partitions

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #9528
Problem Summary(Required) ：

Our users want SR to be compatible with msql using 'truncate' to delete partitions.
This issue will fix this issue

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

drop and truncate do not represent the same semantics.
Drop means to delete the partition, the partition does not exist anymore.
Truncate means to clear the data of this partition, and the partition still exists.


No longer works for SuperCollider?

Hello
All of a sudden, playground stopped working for supercollider files. Did you disable supercollider somehow? In other languages like python it works fine. But running :TSPlaygroundToggle in a supercollider buffer (.scd) no longer does anything

That's the least useful issue we've had in a while, could you at least try to fill in the forms and add valuable information into the issues ?
We can't do anything without context.

That's the least useful issue we've had in a while, could you at least try to fill in the forms and add valuable information into the issues ?
We can't do anything without context.

There are no forms for this repo and so nothing to fill out.
That said, I understand that a lack of context isn't helpful.
What would you like to know ?
I'm using tree-sitter version 0.20.0
On Manjaro Linux
Nvim v.0.5.0
tree-sitter-nvim is at commit '460a26ef3218057a544b3fd6697e979e6bad648d'
playground is at commit 'deb887b3f49d66654d9faa9778e8949fe0d80bc3'
To replicate:
Open a supercollider file, eg someting.scd and run :PlaygroundToggle. Nothing happens.
Then run :tabnew otherfile.py to open a python file and then :PlaygroundToggle and then it opens for that buffer correctly.

Are you sure the supercollider filetype is on for the file you are trying to open ?

Are you sure the supercollider filetype is on for the file you are trying to open ?

yes. The strange thing is it used to work fine but all of a sudden it stopped, which is why I was curious if anything changed that would disable it by default or something for supercollider?

I tried going back to an earlier version (commit 1bf0f79cb461b11196cc9f419763be3373db2848) but that didn't help, so maybe it isn't something in this plugin that changed after all. Any ideas what it could be?

I have absolutely no idea, what does checkhealth report ?

Seems alright:

health#nvim_treesitter#check
========================================================================
## Installation
  - OK: `tree-sitter` found  0.20.0 (parser generator, only needed for :TSInstallFromGrammar)
  - OK: `node` found v16.6.1 (only needed for :TSInstallFromGrammar)
  - OK: `git` executable found.
  - OK: `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl" }
  - OK: Neovim was compiled with tree-sitter runtime ABI version 13 (required >=13). Parsers must be compatible with runtime ABI.

Can reproduce.
Arch Linux
neovim 0.5.0
nvim-treesitter @ f2076b267ef2d53c35a964a8752eef38d7040fd5
playground @ deb887b3f49d66654d9faa9778e8949fe0d80bc3
:checkhealth:
health#nvim_treesitter#check
========================================================================
## Installation
  - OK: `tree-sitter` found  0.20.0 (parser generator, only needed for :TSInstallFromGrammar)
  - OK: `node` found v16.6.2 (only needed for :TSInstallFromGrammar)
  - OK: `git` executable found.
  - OK: `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl" }
  - OK: Neovim was compiled with tree-sitter runtime ABI version 13 (required >=13). Parsers must be compatible with runtime ABI.

The supercollider parser and nvim treesitter work fine otherwise. Code highlighting is correct, the parsing looks correct too behind the scenes, but there's just nothing happening when running playgrund

Debugging this a bit now. Seems like it is the split function that is failing and that it might be connected to the window? WTF?
if you uncomment this line:
https://github.com/nvim-treesitter/playground/blob/787a7a8d4444e58467d6b3d4b88a497e7d494643/lua/nvim-treesitter-playground/internal.lua#L641
The split opens with the parsed node tree. But then, when you jump back to the main window (where the buffer of the file to be parsed is) it closes the Playground split automatically?
Here I am with the set window line uncommented, navigating the node tree and then jumping to the main buffer using C-w and then it disappears.

Ah and then if you also comment out this line:
https://github.com/nvim-treesitter/playground/blob/master/lua/nvim-treesitter-playground/internal.lua#L765
It is fixed.
Can some of the devs with more knowledge of what's going on here clarify what the issue might be?

When I run the toggle playground command, this is the value of
bufnr: 1
current_window: 1000
M._entries[bufnr].display_bufnr: 2
in the .open() method

Something odd: the .detach() method is called before opening the split when using .scd files, but not for for example .cpp files.

And then because of that,  clear_entry is trying to use a value that does not exist here:
https://github.com/nvim-treesitter/playground/blob/master/lua/nvim-treesitter-playground/internal.lua#L111

When opening TSPlaygroundToggle in a SuperCollider buffer M.attach is called, followed by M.detach followed by M.attach. This does not happen in .cpp.

I can also reproduce.
Arch Linux
neovim 0.6.1 and 0.7.0
nvim-treesitter @ 783a54e305e06d1f5e239efb0baa4a3d91e9fbe7
playground @ 7dbcd4d647010a80d135804b3fc1da3fb77083d6
nvim-treesitter: require("nvim-treesitter.health").check()
========================================================================
## Installation
  - OK: `tree-sitter` found 0.20.6 (parser generator, only needed for :TSInstallFromGrammar)
  - OK: `node` found v17.8.0 (only needed for :TSInstallFromGrammar)
  - OK: `git` executable found.
  - OK: `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }
    Version: cc (GCC) 11.2.0
  - OK: Neovim was compiled with tree-sitter runtime ABI version 14 (required >=13). Parsers must be compatible with runtime ABI.

## Parser/Features H L F I J
..
...
... ...
  - supercollider  ✓ ✓ ✓ ✓ ✓
... ...
...

and when commenting out nvim-treesitter-playground/internal.lua#L765 as suggested by @madskjeldgaard and to sum it up doing this: https://github.com/madskjeldgaard/playground/commit/854afcf3d90b3f0b6bd6920392d29d2e378f638d
then :TSPlaygroundToggle works as expected with the supercollider filetype

So I bisected a bit and rolled back several times in the commit history of playground to see when I could get it to work. No luck. But I found something else which seems to be the real issue.
As long as a buffer is called *.scd or *.sc (no matter if the file exist or not) then :TSPlaygroundToggle does absolutely nothing. BUT opening an empty buffer and setting the filetype to supercollider (very important that buffer is not named .scd/.sc) then playground works just fine.

Ah maybe this is about scnvim's filetype setting ?Get Outlook for Android

Aha! So a quick test with both nvim-tressiter and playground in "buddy/friends rollback"-mode. Now I'm at the latest commit on both repos as of 22 March 2021. It was def not enough to just rollback on Playground. Because now :TSPlaygroundToggle works with .scd / .sc files again. And I also just tested with the latest playground commit and a nvim-treesitter commit from 22 March. And there :TSPlaygroundToggle also works. So it seems that this is not really a Playground issue it is a Nvim-TreeSitter issue.

Ah maybe this is about scnvim's filetype setting ?Get Outlook for Android
Maybe a combination, i remember we did som scnvim filetype detect stuff recently.

I will never get Outlook :)~

Okay the jsonc filetype detect fix: 9be9ebda0ad5d5ffb880829ad3315ab7c55a2acc is breaking supercollider usage with :TSPlaygroundToggle. So it definitely seems to be a filetype detect issue here.

And it seems the issue is how the scnvim plugin is making filetype detection on .scd files.
I just tried disabling (removing) scnvim from my setup. And now I can use :TSPlaygroundToggle with .scd  and .sc files, though the first is now detected as a scdoc file and the latter as a scala file. But setting the filetype to supercollider yields success.
So this is not a nvim-treesitter or playground issue but a scnvim issue. It seems [fingers crossed]. Next up is to try and figure out what we need to do in scnvim to detect the filetypes properly (using the newer nvim filetype.lua) and still not reintroduce the issue of jumpy scala-supercollider behavior due to the standard "last one wins"-way of filetype detection, which just switches filetypes in order.
-- notes on using playground while having scnvim installed
-- 9be9ebd seems to break playground usage with sc filerype or at least trigger something which is broken in scnvims detect sys
    commit = "74d1d58572a0e017aacb3fb66b43add9d208b86e", -- Jul 18, 2021 working
    commit = "9be9ebda0ad5d5ffb880829ad3315ab7c55a2acc",  -- Jul 18, 2021 not working

Looking into the new API with filetype.lua (in version 0.7.0). Then all of this may not even be a problem. Potential RIP hours :)
Will report back at some point.


Test: Source maps for built-in extensions

Test for #10994

This isn't user-facing. @ramya-rao-a will pick up these changes for the error telemetry service.

agreed. I have verified that the sourcemaps are indeed published for built in extensions from 1.6 onwards


Support "Zulu OpenJDK Discovery API" for auto provisioning toolchains

Gradle currently supports Adoptium API for auto provisioning.
This feature request is to also support "Zulu OpenJDK Discovery API" for auto provisioning:
https://app.swaggerhub.com/apis-docs/azul/zulu-download-community/1.0
when JVM vendor spec is AZUL("azul systems", "Zulu") it should autoprovision from the Zulu API.
Expected Behavior
It generally should operate in the same way as Adoptium auto provisioning.
you should be able to override the base URI of the API with this Gradle property:
org.gradle.jvm.toolchain.install.zulu.baseUri

Context
Zulu supports Apple Silicon (M1 mac) for JDK 8 and JDK 11, Adoptium/Temurin doesn't currently offer builds of JDK 8 and JDK 11 for Apple Silicon (M1 mac), so it would be nice if Gradle supported their API for auto provisioning.

The plan is to offer an SPI for plugin authors to provide that feature. The migration from AdoptOpenJDK to Adoptium has shown that having this baked into Gradle is a bad idea as these things are outside of our control for their lifecycle.

might be worth looking at https://github.com/foojayio/discoapi as this is the Friends of OpenJDK discovery API as well.

This seems like a complicated situation.  The linked API in https://docs.gradle.org/current/userguide/toolchains.html is apparently deprecated.  There are Zulu and Adoptium APIs as well out there, not clear if they conform to the same V1? API.
Is there a matrix of ones that work, Providers/Versions? Or docs for which API baseUris are supported?
The docs make it all sound really hopeful, but I think I've come to the same conclusion of as @aalmiray https://github.com/jreleaser/jreleaser/commit/4362c41e9a3bae09d0af4ad43759b557ff6653e9 that it only actually supports ADOPTOPENJDK.
If I sound frustrated, it's because this seems so close to being really effective solution, and I keep coming back every 3 months and failing.  Any advice that could unblock me is really appreciated!

Never has Gradle announced that it supported more than AdoptOpenJDK. We made the base URL configurable so that you could decided to support your own server, but that had other side effects.
The team wants to go down the SPI path and will share more information when that topic can be picked up and worked on.

@ljacomet ok thanks, that makes sense.
I read too much optimism into the following, which is presumably written because eventually someone may implement this.  At the moment it seems that these JDK providers are choosing alternative API mechanisms incompatible with Gradle's choice.

By default, the public AdoptOpenJDK APIs are used to determine and download a matching JDK. In case you want to use another server that is compatible with v3 of the AdoptOpenJDK API, you can point Gradle to use a different host. For that you use the Gradle property as in the example below:

@ljacomet Just wondered if there was any more information on using an SPI to configure JDK provisioning? We're extremely heavy users of Gradle at my compnay and I'm looking at how we can host our jvm discovery server, as calling out to the adoptopenjdk/adoptium api over the internet is not really possible. Our preferred jvm vendor is Azul (we even pay them already) so I'm looking at how to "trick" gradle into downloading a zulu jdk - if there's some work that prevents me from having to doing this (especially if it can be shipped as a gradle plugin) I'd be very interested!

We are still looking into doing that, no ETA though.
For the moment your only option is to replicate the AdoptOpenJDK URL structure on a web server and serve Azul JDKs from it, without using the vendor in the toolchain spec.

Also, existing AdoptOpenJdk auto-provisioning is not working for JDK 18:
https://github.com/gradle/gradle/issues/20344

For people's SA, we've ended up building our own plugin for JDK auto-provisioning and started using it on all our projects.
Features over the existing auto-provisioning include:

You can choose your favoured JDK vendor.
Use the same JDK version for representative, reproducible builds on dev machines and in CI.
Automatically add JDK CA certificates.
Point to an internal mirror for JDKs.

@CRogers your plugin is awesome -- thank you for sharing it!
Out of curiosity, did you consider submitting this functionality as a Gradle PR (to implement https://github.com/gradle/build-tool-roadmap/issues/29), instead of as a standalone plugin?  We are considering creating something similar, and were considering submitting a PR for https://github.com/gradle/build-tool-roadmap/issues/29, when we found your plugin.  We're thinking it would be ideal to have this functionality as a first class part of Gradle Toolchains, because eventually, IDEs could integrate with Gradle Toolchains and use whatever JDK your Toolchain is configured to use (so you get the correct code completion and syntax highlighting, for example).

@tomakita Well, somebody tried to implement something of that nature over at https://github.com/gradle/gradle/pull/18028, but it's not clear where the review ended up. Getting a PR actually merged isn't totally trivial...

for paying customers of Zulu we need to provide credentials would this API accept credentials for auto provisioning with Zulu?

Conceptually, what we are planning is to have an SPI so that plugin authors can design their own logic for matching a toolchain spec to a URI.
Plugin configuration will allow to pass in credentials if the endpoint requires them.
Will try to share an example soon!

Any links to documentation on how to use this feature now that it has been marked as completed?

Any links to documentation on how to use this feature now that it has been marked as completed?

There's some docs at https://github.com/gradle/gradle/pull/22123/files#diff-23ed1cf4b4d7e28f4236ae239e1a4546983788d249ac320fec08642240ff3b43R272.

Release notes for nightlies can be used as the entry point.
We will also release a plugin close to the effective 7.6 release.

https://docs.gradle.org/release-nightly/userguide/toolchains.html#sub:download_repositories

We will also release a plugin close to the effective 7.6 release.

@ljacomet is this plugin released? is the in-progress source code for that plugin available anywhere?
the docs/release notes don't make it clear that AzulResolver is from a theoretical future plugin, and not included in Gradle 7.6. Might be worth updating the release notes, to avoid people copy/pasting the AzulResolver stuff and then filing issues saying it doesn't work. :)
https://docs.gradle.org/current/release-notes.html#toolchain-provision

As mentioned above, would be great to have support for the foojay Disco API
 as well (but maybe that is a separate ticket).

the docs/release notes don't make it clear that AzulResolver is from a theoretical future plugin, and not included in Gradle 7.6

@yogurtearl, I'd say that

For example, the following uses custom plugins that provide AzulResolver and AdoptiumResolver to add custom toolchains for Adoptium and Azul:

as written here (emphasis mine) is pretty clear about that.

would be great to have support for the foojay Disco API

You mean like in https://github.com/gradle/foojay-toolchains? :wink:


Cyhuang01 schema 1

:warning: Validation status: warnings

File
Status
Preview URL
Details

academic-services/graph/reference-data-schema.md
:warning:Warning

Details

academic-services/graph/media/create-hdinsight-account-details.png
:white_check_mark:Succeeded

academic-services/graph/media/create-hdinsight-storage-account-details.png
:white_check_mark:Succeeded

academic-services/graph/media/entity-relationship-diagram-thumbnail.png
:white_check_mark:Succeeded

academic-services/graph/media/entity-relationship-diagram.pdf
:white_check_mark:Succeeded

academic-services/graph/reference-data-schema.md

Line 20: [Warning] Invalid file link:(~/graph/media/entity-relationship-diagram.pdf).
Line 130: [Warning] Invalid file link:(~/graph/resources-faq).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

academic-services/graph/reference-data-schema.md
:warning:Warning

Details

academic-services/graph/media/create-hdinsight-account-details.png
:white_check_mark:Succeeded

academic-services/graph/media/create-hdinsight-storage-account-details.png
:white_check_mark:Succeeded

academic-services/graph/media/entity-relationship-diagram-thumbnail.png
:white_check_mark:Succeeded

academic-services/graph/media/entity-relationship-diagram.pdf
:white_check_mark:Succeeded

academic-services/graph/media/entity-relationship-diagram.png
:white_check_mark:Succeeded

academic-services/graph/reference-data-schema.md

Line 20: [Warning] Invalid file link:(~/graph/media/entity-relationship-diagram.pdf).
Line 130: [Warning] Invalid file link:(~/graph/resources-faq).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

academic-services/graph/reference-data-schema.md
:warning:Warning

Details

academic-services/graph/media/create-hdinsight-account-details.png
:white_check_mark:Succeeded

academic-services/graph/media/create-hdinsight-storage-account-details.png
:white_check_mark:Succeeded

academic-services/graph/media/entity-relationship-diagram-thumbnail.png
:white_check_mark:Succeeded

academic-services/graph/media/entity-relationship-diagram.pdf
:white_check_mark:Succeeded

academic-services/graph/media/entity-relationship-diagram.png
:white_check_mark:Succeeded

academic-services/graph/reference-data-schema.md

Line 130: [Warning] Invalid file link:(~/graph/resources-faq).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

academic-services/graph/reference-data-schema.md
:warning:Warning

Details

academic-services/graph/media/create-hdinsight-account-details.png
:white_check_mark:Succeeded

academic-services/graph/media/create-hdinsight-storage-account-details.png
:white_check_mark:Succeeded

academic-services/graph/media/entity-relationship-diagram-thumbnail.png
:white_check_mark:Succeeded

academic-services/graph/media/entity-relationship-diagram.png
:white_check_mark:Succeeded

academic-services/graph/reference-data-schema.md

Line 130: [Warning] Invalid file link:(~/graph/resources-faq).

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

Add entity relationship diagram.


IMN-436 Add getPurposes in purpose-process

[To be merged after #419]
This pull request is for implementing the getPurposes endpoint in purpose-process.

Replaced by #438, with a different target branch.


Feature : system filters for Mineral

Being able to restrict to quickly select populated systems only (or systems with colonies even if empty?) would be nice.
Also be able to deselect hostile alien/military-restricted systems.

https://github.com/rubybrowncoat/Aurora-Electrons/releases/tag/v0.8.10

Released in https://github.com/rubybrowncoat/Aurora-Electrons/releases/tag/v0.8.10


Swagger http response return type being "file" triggers KeyError "IO" when deserializing data

Problem:

I have been playing with schema registry swagger file, and changed the return type of "GetById" method to be file to see what response I would get. However it seems like I accidentally triggered a bug in autorest.
The exception traceback I got when I ran get_by_id method is as following:

Traceback (most recent call last):
  File ..\"azure-sdk-for-python/sdk/schemaregistry/azure-schemaregistry/samples/sync_samples/schema_registry.py", line 84, in <module>
    schema_str = get_schema_by_id(schema_registry_client, schema_id=schema_id)
  File "..\azure-sdk-for-python/sdk/schemaregistry/azure-schemaregistry/samples/sync_samples/schema_registry.py", line 62, in get_schema_by_id
    schema = client.get_schema(schema_id)
  File "..\azure-sdk-for-python\sdk\schemaregistry\azure-schemaregistry\azure\schemaregistry\_schema_registry_client.py", line 142, in get_schema
    **kwargs
  File "..\azure-sdk-for-python\sdk\schemaregistry\azure-schemaregistry\azure\schemaregistry\_generated\operations\_schema_operations.py", line 103, in get_by_id
    deserialized = self._deserialize('IO', pipeline_response)
  File "..envs\srenv37\lib\site-packages\msrest\serialization.py", line 1356, in __call__
    return self._deserialize(target_obj, data)
  File "..envs\srenv37\lib\site-packages\msrest\serialization.py", line 1395, in _deserialize
    return self.deserialize_data(data, response)
  File "..\envs\srenv37\lib\site-packages\msrest\serialization.py", line 1588, in deserialize_data
    obj_type = self.dependencies[data_type]
KeyError: 'IO'

How to reproduce:

The change I made to the swagger is simple -- for line 98, I change "type": "string" to "type": "file":
https://github.com/yunhaoling/azure-rest-api-specs/blob/00da70e4191d304de1d1488d2640a288499905fa/specification/schemaregistry/data-plane/Microsoft.EventHub/preview/2020-09-01-preview/schemaregistry.json#L98
The generated code for get_by_id now looks like this:

    def get_by_id(
        self,
        schema_id,  # type: str
        **kwargs  # type: Any
    ):
        # type: (...) -> IO
        """Get a registered schema by its unique ID reference.

        Gets a registered schema by its unique ID.  Azure Schema Registry guarantees that ID is unique
        within a namespace.

        :param schema_id: References specific schema in registry namespace.
        :type schema_id: str
        :keyword callable cls: A custom type or function that will be passed the direct response
        :return: IO, or the result of cls(response)
        :rtype: IO
        :raises: ~azure.core.exceptions.HttpResponseError
        """
        cls = kwargs.pop('cls', None)  # type: ClsType[IO]
        error_map = {
            401: ClientAuthenticationError, 404: ResourceNotFoundError, 409: ResourceExistsError
        }
        error_map.update(kwargs.pop('error_map', {}))
        api_version = "2020-09-01-preview"
        accept = "text/plain; charset=utf-8"

        # Construct URL
        url = self.get_by_id.metadata['url']  # type: ignore
        path_format_arguments = {
            'endpoint': self._serialize.url("self._config.endpoint", self._config.endpoint, 'str', skip_quote=True),
            'schema-id': self._serialize.url("schema_id", schema_id, 'str'),
        }
        url = self._client.format_url(url, **path_format_arguments)

        # Construct parameters
        query_parameters = {}  # type: Dict[str, Any]
        query_parameters['api-version'] = self._serialize.query("api_version", api_version, 'str')

        # Construct headers
        header_parameters = {}  # type: Dict[str, Any]
        header_parameters['Accept'] = self._serialize.header("accept", accept, 'str')

        request = self._client.get(url, query_parameters, header_parameters)
        pipeline_response = self._client._pipeline.run(request, stream=False, **kwargs)
        response = pipeline_response.http_response

        if response.status_code not in [200]:
            map_error(status_code=response.status_code, response=response, error_map=error_map)
            error = self._deserialize('object', response)
            raise HttpResponseError(response=response, model=error)

        response_headers = {}
        response_headers['Location']=self._deserialize('str', response.headers.get('Location'))
        response_headers['Serialization-Type']=self._deserialize('str', response.headers.get('Serialization-Type'))
        response_headers['Schema-Id']=self._deserialize('str', response.headers.get('Schema-Id'))
        response_headers['Schema-Id-Location']=self._deserialize('str', response.headers.get('Schema-Id-Location'))
        response_headers['Schema-Version']=self._deserialize('int', response.headers.get('Schema-Version'))
        deserialized = self._deserialize('IO', pipeline_response)

        if cls:
            return cls(pipeline_response, deserialized, response_headers)

        return deserialized
    get_by_id.metadata = {'url': '/$schemagroups/getSchemaById/{schema-id}'}  # type: ignore

cc: @lmazuel

hey @yunhaoling this looks like it might be a bug in msrest, since that's where the error is being triggered.
The one reason where this would be an autorest bug is if deserialized = self._deserialize('IO', pipeline_response) is generated incorrectly, @lmazuel is IO the incorrect serialization type for a file as far as msrest is concerned?

This is an issue with swagger. To get file response, the response content type should be application/octet-stream, not text/plain. Thanks to @daviwil for finding and @yunhaoling for looking out for the autorest python crew, closing this issue now


CLIENT_EVENTS.RTM.DISCONNECT not supported

We are currently listening to the disconnect event so we get the code&reason for a disconnect. More specifically we want to know when an invalid_auth error happened.
Though this is impossible to test as rtm.send method does not allow for a callback containing two parameters. Disconnect event returns code and reason.

What does the disconnect payload look like? Is it JSON?


Added Password Strength Checker: #347

Closes: #347

Title : Password Strength Checker
Name: : Anshika
Idenitfy yourself: : GSSOC

Describe the add-ons or changes you've made 📃
Added a password strength checker which helps us to check strength of our password.
How Has This Been Tested? ⚙
I have tested it on my own.
Screenshots 📷

Type of change ☑
What sort of change have you made:

[x] New feature (non-breaking change which adds functionality)

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Note to reviewers 📄

@Avdhesh-Varshney sir, please review it
and if it is good ,can you please increase its level and please merge it.


StorageCluster: add uninstall mode

Rook and Noobaa are now both defaulting to wait for removal of existing
PVCs and OBCs before deleting their operands. In cases where the admin
wants to enforce a forced cleanup, this label on the StorageCluster
should be set.
uninstall-mode.ocs.openshift.io="yes-really-uninstall-even-if-in-use"
Co-authored-by: Nitin Goyal<EMAIL_ADDRESS>Signed-off-by: Raghavendra Talur<EMAIL_ADDRESS>

I only see one commit, is there supposed to be more? Also, why not just extend the cleanup policy?

We were confused about the Noobaa field and its use. As you can see with the updated commits, the cleanup policy in Noobaa spec actually refers to the uninstall behavior, specifically, whether it is graceful or forced.
This PR introduces a new label in the StorageCluster which determines the uninstall mode for both Rook and Noobaa. As of now, we are using it only to set the uninstall mode for Noobaa. The commit for Rook will come in a later PR after making relevant changes in Rook.
Added comments to make it clean in the code too, let us know if it not clear.
cc: @iamniting

@jarrpa Now, with the new PR #730 and with the updates in this PR, we have addressed all the review suggestions.
Changes:

Moved from labels to annotations
Clubbed the annotations under uninstall.ocs.openshift.io

cc: @iamniting


Refactor to Auro-Interruption w/ Component Base

Alaska Airlines Pull Request
Summary:
Refactors dialog into a component-base file for the purpose of adding drawer later.
Type of change:
Please delete options that are not relevant.

[x] Revision of an existing capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

@blackfalcon this is ready for your touch. Pending items:

[ ] have common styles.scss file (I left these separate because I don't know how much you'll touch the drawer styles)

[ ] Fix the margin issue:

I'm aiming to have a similar UI as the CH drawer:
https://components.alaskaair.com/catelog/demo/fs-drawer
Thanks again Dale!

I was able to solve the margin error, but I'm still having trouble fundamentally understanding the left-alignment and centered default nature of this element. Would appreciate pairing on this to learn the cause.

@blackfalcon have you had a chance to look at this positioning issue? would love to pair to learn more.

@gusnaughton this PR needs to be moved to auro-interruption


Add redux for book detail

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


AMQ-6706 Allow for hooks before broker stop occurs

When Camel is run embedded within ActiveMQ it's shutdown is called at the point the broker is already stopped, this can lead to data loss as there could be exchanges that have not ended.
This adds the ability to specify preStopHook(s) that can be invoked during ActiveMQ shutdown but before the broker is shutdown.
With this Camel can gracefully shutdown while the broker is still started.

Don't see any tests here that confirm this works or ensure it remains working into the future.

@tabish121 I've added tests


Durations and AggregateRoot tests

I had the following compilation warning:
Note: /Users/sanders/Projects/Spine/Sources/core-java/core-java/src/test/java/org/spine3/server/aggregate/AggregateRootShould.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
I've fixed them. See changes to this class in method-map branch.


Demo mode

Implement possibility to disable demo mode if it's necessary. Right now it's default behaviour.

https://github.com/alexander-kulikovskii/toster/pull/31


Issues accessing data

Hi!
I was trying to reproduce your paper using the shared data. I think I was able to download the data using the sra toolkit provided by NCBI, but the data comes in the .fastq format rather than the .fast5 you use in the paper. I was not able to find a converter but I feel something is wrong because you don't mention any .fastq format in the paper. These are the two datasets I downloaded: https://www.ncbi.nlm.nih.gov/sra/?term=SRP296988
Would you be able to help me understand whether I'm looking to the wrong places and how to access the .fast5 files you used?
Thanks!

Hello! Thanks for your interests in our work. The fast5 datasets are available on demand due to the size of the files. Please send your request to<EMAIL_ADDRESS>We are happy to work with you on transferring the large datasets.


Remove TLS Client certificate from BackendPolicy

What happened:
BackendPolicy contains has spec.tls.clientCertificateRef .
In my understanding, for a backend, like a k8s service,

there would be a single BackendPolicy resource that would be associated with it (in case of conflict, there will be a winner).
The Service owner would maintain the backend policy

For every service/gateway that talks to a service, it would have its dedicated client certificate and that is not something the service owner would care for or even decide. But even then, the client certificate definition is part of the BackendPolicy resource.
What you expected to happen:
Client certificate definition should not be part of BackendPolicy.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:

/assign

This is now fixed.
/close


Check the language in the mail: there are some mails that have the title in english and the body in italian

Estimated required time: ~1 day


Disable Kallisto / graph DB to NOT start by default

Enable the database to start only if specified on the command line like:
./lucy start kallisto

The default behavior will be to only start Lucyfer:
./lucy start # only starts the Lucyfer dev stuff

@phillipross @kinabalu @sbalmos - Thoughts?  Recommendations?  I think there's little to gain from starting Blazegraph as part of the distribution by default.  Going forward, given data volumes, connecting to Neptune might be a better idea.  Thanks!

I agree, better to leave it turned off by default


Minimize semantic differences between library.proto and library_gapic.yaml

This is so we can later test using only the library.proto (annotated) to generate a client, and it should have a similar surface to the client generated using the library_gapic.yaml.

Codecov Report

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

@@            Coverage Diff            @@
##             master    #2363   +/-   ##
=========================================
  Coverage     86.66%   86.66%
  Complexity     5220     5220
=========================================
  Files           455      455
  Lines         20810    20810
  Branches       2255     2255
=========================================
  Hits          18035    18035
  Misses         1980     1980
  Partials        795      795

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 156a4c6...49906e2. Read the comment docs.

PTAL

PTAL
fixed tests


Update package-info.java

There is no blank line in the middle, the code comments are not standardized

This is automated and standardized.  The first slash start comment is the header which complies with checkstyle.  The second is the javadoc.  This is correct per our checkstyle rules.