Breadcrumb updates

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

File
Status
Preview URL
Details

docs/reference/nuspec.md
:warning:Warning
View
Details

docs/create-packages/Creating-a-Package.md
:warning:Warning
View
Details

docs/resources/check-project-format.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/faqs/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/reference/migrate-packages-config-to-package-reference.md
:white_check_mark:Succeeded
View

docs/reference/nuspec.md

Line 34: [Warning] Illegal link: `<a href="reference/migrate-packages-config-to-package-reference.md#create-a-package-after-migration">msbuild -t:pack</a>` -- missing bookmark. The file reference/migrate-packages-config-to-package-reference.md doesn't contain a bookmark named create-a-package-after-migration.

docs/create-packages/Creating-a-Package.md

Line 18: [Warning] Illegal link: `<a href="reference/migrate-packages-config-to-package-reference.md#create-a-package-after-migration">msbuild -t:pack</a>` -- missing bookmark. The file reference/migrate-packages-config-to-package-reference.md doesn't contain a bookmark named create-a-package-after-migration.

docs/resources/check-project-format.md

Line 21: [Warning] Illegal link: `<a href="reference/migrate-packages-config-to-package-reference.md#create-a-package-after-migration">msbuild -t:pack</a>` -- missing bookmark. The file reference/migrate-packages-config-to-package-reference.md doesn't contain a bookmark named create-a-package-after-migration.

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.

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

File
Status
Preview URL
Details

docs/consume-packages/migrate-packages-config-to-package-reference.md
:warning:Warning
View
Details

docs/reference/nuspec.md
:warning:Warning
View
Details

docs/create-packages/Creating-a-Package.md
:warning:Warning
View
Details

docs/resources/check-project-format.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/consume-packages/migrate-packages-config-to-package-reference.md

Line 12: [Warning] Invalid file link:(~/consume-packages/packages-config.md).

docs/reference/nuspec.md

Line 34: [Warning] Illegal link: `<a href="reference/migrate-packages-config-to-package-reference.md#create-a-package-after-migration">msbuild -t:pack</a>` -- missing bookmark. The file reference/migrate-packages-config-to-package-reference.md doesn't contain a bookmark named create-a-package-after-migration.

docs/create-packages/Creating-a-Package.md

Line 18: [Warning] Illegal link: `<a href="reference/migrate-packages-config-to-package-reference.md#create-a-package-after-migration">msbuild -t:pack</a>` -- missing bookmark. The file reference/migrate-packages-config-to-package-reference.md doesn't contain a bookmark named create-a-package-after-migration.

docs/resources/check-project-format.md

Line 21: [Warning] Illegal link: `<a href="reference/migrate-packages-config-to-package-reference.md#create-a-package-after-migration">msbuild -t:pack</a>` -- missing bookmark. The file reference/migrate-packages-config-to-package-reference.md doesn't contain a bookmark named create-a-package-after-migration.

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.

Docs Build status updates of commit 61e50b7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/consume-packages/migrate-packages-config-to-package-reference.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/consume-packages/Package-References-in-Project-Files.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5120.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5121.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5122.md
:white_check_mark:Succeeded
View

docs/reference/nuspec.md
:white_check_mark:Succeeded
View

docs/release-notes/NuGet-4.7-RTM.md
:white_check_mark:Succeeded
View

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/resources/check-project-format.md
:white_check_mark:Succeeded
View

docs/consume-packages/migrate-packages-config-to-package-reference.md

Line 12: [Warning] Invalid file link:(~/consume-packages/packages-config.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.

Docs Build status updates of commit dd148c0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/consume-packages/Package-References-in-Project-Files.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/migrate-packages-config-to-package-reference.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/guides/Native-Packages.md
:white_check_mark:Succeeded
View

docs/guides/analyzers-conventions.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5120.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5121.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5122.md
:white_check_mark:Succeeded
View

docs/reference/nuspec.md
:white_check_mark:Succeeded
View

docs/release-notes/NuGet-4.7-RTM.md
:white_check_mark:Succeeded
View

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/resources/check-project-format.md
:white_check_mark:Succeeded
View

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.

Docs Build status updates of commit 6a083ac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/consume-packages/Package-References-in-Project-Files.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/migrate-packages-config-to-package-reference.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/guides/Native-Packages.md
:white_check_mark:Succeeded
View

docs/guides/analyzers-conventions.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5120.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5121.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5122.md
:white_check_mark:Succeeded
View

docs/reference/nuspec.md
:white_check_mark:Succeeded
View

docs/release-notes/NuGet-4.7-RTM.md
:white_check_mark:Succeeded
View

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/resources/check-project-format.md
:white_check_mark:Succeeded
View

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.

Docs Build status updates of commit ba4c842:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/consume-packages/Package-References-in-Project-Files.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/migrate-packages-config-to-package-reference.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/create-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/guides/Native-Packages.md
:white_check_mark:Succeeded
View

docs/guides/analyzers-conventions.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5120.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5121.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5122.md
:white_check_mark:Succeeded
View

docs/reference/nuspec.md
:white_check_mark:Succeeded
View

docs/release-notes/NuGet-4.7-RTM.md
:white_check_mark:Succeeded
View

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/resources/check-project-format.md
:white_check_mark:Succeeded
View

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.

Docs Build status updates of commit 34790ac:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/concepts/Dependency-Resolution.md
:warning:Warning
View
Details

docs/consume-packages/Package-References-in-Project-Files.md
:warning:Warning
View
Details

docs/reference/nuspec.md
:warning:Warning
View
Details

docs/create-packages/Prerelease-Packages.md
:warning:Warning
View
Details

docs/release-notes/NuGet-1.4.md
:warning:Warning
View
Details

docs/api/package-base-address-resource.md
:warning:Warning
View
Details

docs/api/registration-base-url-resource.md
:warning:Warning
View
Details

docs/archive/project-json-impact.md
:warning:Warning
View
Details

docs/consume-packages/Overview-and-Workflow.md
:warning:Warning
View
Details

docs/reference/packages-config.md
:warning:Warning
View
Details

docs/reference/errors-and-warnings/NU1101.md
:warning:Warning
View
Details

docs/create-packages/includes/choose-package-id.md
:warning:Warning

Details

docs/what-is-nuget.md
:warning:Warning
View
Details

docs/archive/project-json-archive.md
:warning:Warning
View
Details

docs/consume-packages/Reinstalling-and-Updating-Packages.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/concepts/Package-Versioning.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/migrate-packages-config-to-package-reference.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/create-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/guides/Native-Packages.md
:white_check_mark:Succeeded
View

docs/guides/analyzers-conventions.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5120.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5121.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5122.md
:white_check_mark:Succeeded
View

docs/release-notes/NuGet-4.7-RTM.md
:white_check_mark:Succeeded
View

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/resources/check-project-format.md
:white_check_mark:Succeeded
View

docs/concepts/Dependency-Resolution.md

Line 26: [Warning] Invalid file link:(~/concepts/packages-and-source-control.md).
Line 40: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-1.png).
Line 44: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-2.png).
Line 48: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-3.png).
Line 58: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-4.png).
Line 61: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.
Line 72: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-5.png).
Line 79: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-6.png).
Line 87: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-7.png).
Line 91: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-8.png).
Line 107: [Warning] Invalid file link:(~/concepts/package-references-in-project-files.md#controlling-dependency-assets).

docs/consume-packages/Package-References-in-Project-Files.md

Line 46: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.
Line 61: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#floating-versions">Floating versions</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named floating-versions.

docs/reference/nuspec.md

Line 72: [Warning] Illegal link: `<a href="reference/package-versioning.md#pre-release-versions">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named pre-release-versions.
Line 280: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/create-packages/Prerelease-Packages.md

Line 18: [Warning] Illegal link: `<a href="reference/package-versioning.md#pre-release-versions">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named pre-release-versions.
Line 36: [Warning] Illegal link: `<a href="reference/package-versioning.md#pre-release-versions">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named pre-release-versions.

docs/release-notes/NuGet-1.4.md

Line 70: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">version range format</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/api/package-base-address-resource.md

Line 69: [Warning] Illegal link: `<a href="reference/package-versioning.md#normalized-version-numbers">normalized NuGet version strings</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named normalized-version-numbers.
Line 102: [Warning] Illegal link: `<a href="reference/package-versioning.md#normalized-version-numbers">normalization rules</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named normalized-version-numbers.
Line 138: [Warning] Illegal link: `<a href="reference/package-versioning.md#normalized-version-numbers">normalization rules</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named normalized-version-numbers.

docs/api/registration-base-url-resource.md

Line 214: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">version range</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/archive/project-json-impact.md

Line 23: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.

docs/consume-packages/Overview-and-Workflow.md

Line 27: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#resolving-incompatible-package-errors">Resolving incompatible package errors</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named resolving-incompatible-package-errors.

docs/reference/packages-config.md

Line 27: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/reference/errors-and-warnings/NU1101.md

Line 21: [Warning] Illegal link: `<a href="reference/package-versioning.md#semantic-versioning-200">Semantic Versioning 2.0.0</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named semantic-versioning-200.

docs/create-packages/includes/choose-package-id.md

Line 12: [Warning] Illegal link: `<a href="reference/package-versioning.md#semantic-versioning-200">semver 2 compliant</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named semantic-versioning-200.
Line 12: [Warning] Illegal link: `<a href="reference/package-versioning.md#semantic-versioning-200">semver 2 compliant</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named semantic-versioning-200.
Line 14: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution with PackageReference</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.
Line 14: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution with PackageReference</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.

docs/what-is-nuget.md

Line 103: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">version ranges</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/archive/project-json-archive.md

Line 52: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.
Line 58: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#managing-dependency-assets">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named managing-dependency-assets.
Line 64: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#excluding-references">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named excluding-references.
Line 81: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#resolving-incompatible-package-errors">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named resolving-incompatible-package-errors.

docs/consume-packages/Reinstalling-and-Updating-Packages.md

Line 57: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

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.

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

File
Status
Preview URL
Details

docs/concepts/Dependency-Resolution.md
:warning:Warning
View
Details

docs/consume-packages/Package-References-in-Project-Files.md
:warning:Warning
View
Details

docs/reference/nuspec.md
:warning:Warning
View
Details

docs/archive/project-json-impact.md
:warning:Warning
View
Details

docs/reference/packages-config.md
:warning:Warning
View
Details

docs/consume-packages/Reinstalling-and-Updating-Packages.md
:warning:Warning
View
Details

docs/release-notes/NuGet-1.4.md
:warning:Warning
View
Details

docs/api/package-base-address-resource.md
:warning:Warning
View
Details

docs/create-packages/includes/choose-package-id.md
:warning:Warning

Details

docs/api/registration-base-url-resource.md
:warning:Warning
View
Details

docs/consume-packages/Overview-and-Workflow.md
:warning:Warning
View
Details

docs/create-packages/Prerelease-Packages.md
:warning:Warning
View
Details

docs/archive/project-json-archive.md
:warning:Warning
View
Details

docs/reference/errors-and-warnings/NU1101.md
:warning:Warning
View
Details

docs/what-is-nuget.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/concepts/Package-Versioning.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/migrate-packages-config-to-package-reference.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/create-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/guides/Native-Packages.md
:white_check_mark:Succeeded
View

docs/guides/analyzers-conventions.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5120.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5121.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5122.md
:white_check_mark:Succeeded
View

docs/release-notes/NuGet-4.7-RTM.md
:white_check_mark:Succeeded
View

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/resources/check-project-format.md
:white_check_mark:Succeeded
View

docs/concepts/Dependency-Resolution.md

Line 26: [Warning] Invalid file link:(~/concepts/packages-and-source-control.md).
Line 40: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-1.png).
Line 44: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-2.png).
Line 48: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-3.png).
Line 58: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-4.png).
Line 61: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.
Line 72: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-5.png).
Line 79: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-6.png).
Line 87: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-7.png).
Line 91: [Warning] Invalid file link:(~/concepts/media/projectJson-dependency-8.png).
Line 107: [Warning] Invalid file link:(~/concepts/package-references-in-project-files.md#controlling-dependency-assets).

docs/consume-packages/Package-References-in-Project-Files.md

Line 46: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.
Line 61: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#floating-versions">Floating versions</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named floating-versions.

docs/reference/nuspec.md

Line 72: [Warning] Illegal link: `<a href="reference/package-versioning.md#pre-release-versions">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named pre-release-versions.
Line 280: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/archive/project-json-impact.md

Line 23: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.

docs/reference/packages-config.md

Line 27: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/consume-packages/Reinstalling-and-Updating-Packages.md

Line 57: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/release-notes/NuGet-1.4.md

Line 70: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">version range format</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/api/package-base-address-resource.md

Line 69: [Warning] Illegal link: `<a href="reference/package-versioning.md#normalized-version-numbers">normalized NuGet version strings</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named normalized-version-numbers.
Line 102: [Warning] Illegal link: `<a href="reference/package-versioning.md#normalized-version-numbers">normalization rules</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named normalized-version-numbers.
Line 138: [Warning] Illegal link: `<a href="reference/package-versioning.md#normalized-version-numbers">normalization rules</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named normalized-version-numbers.

docs/create-packages/includes/choose-package-id.md

Line 12: [Warning] Illegal link: `<a href="reference/package-versioning.md#semantic-versioning-200">semver 2 compliant</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named semantic-versioning-200.
Line 12: [Warning] Illegal link: `<a href="reference/package-versioning.md#semantic-versioning-200">semver 2 compliant</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named semantic-versioning-200.
Line 14: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution with PackageReference</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.
Line 14: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution with PackageReference</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.

docs/api/registration-base-url-resource.md

Line 214: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">version range</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/consume-packages/Overview-and-Workflow.md

Line 27: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#resolving-incompatible-package-errors">Resolving incompatible package errors</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named resolving-incompatible-package-errors.

docs/create-packages/Prerelease-Packages.md

Line 18: [Warning] Illegal link: `<a href="reference/package-versioning.md#pre-release-versions">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named pre-release-versions.
Line 36: [Warning] Illegal link: `<a href="reference/package-versioning.md#pre-release-versions">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named pre-release-versions.

docs/archive/project-json-archive.md

Line 52: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.
Line 58: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#managing-dependency-assets">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named managing-dependency-assets.
Line 64: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#excluding-references">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named excluding-references.
Line 81: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#resolving-incompatible-package-errors">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named resolving-incompatible-package-errors.

docs/reference/errors-and-warnings/NU1101.md

Line 21: [Warning] Illegal link: `<a href="reference/package-versioning.md#semantic-versioning-200">Semantic Versioning 2.0.0</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named semantic-versioning-200.

docs/what-is-nuget.md

Line 103: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">version ranges</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

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.

Docs Build status updates of commit 1439ae8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/concepts/Dependency-Resolution.md
:warning:Warning
View
Details

docs/consume-packages/Package-References-in-Project-Files.md
:warning:Warning
View
Details

docs/reference/nuspec.md
:warning:Warning
View
Details

docs/archive/project-json-impact.md
:warning:Warning
View
Details

docs/consume-packages/Reinstalling-and-Updating-Packages.md
:warning:Warning
View
Details

docs/create-packages/includes/choose-package-id.md
:warning:Warning

Details

docs/api/package-base-address-resource.md
:warning:Warning
View
Details

docs/what-is-nuget.md
:warning:Warning
View
Details

docs/release-notes/NuGet-1.4.md
:warning:Warning
View
Details

docs/api/registration-base-url-resource.md
:warning:Warning
View
Details

docs/archive/project-json-archive.md
:warning:Warning
View
Details

docs/create-packages/Prerelease-Packages.md
:warning:Warning
View
Details

docs/reference/packages-config.md
:warning:Warning
View
Details

docs/consume-packages/Overview-and-Workflow.md
:warning:Warning
View
Details

docs/reference/errors-and-warnings/NU1101.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/concepts/Package-Versioning.md
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-1.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-2.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-3.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-4.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-5.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-6.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-7.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-8.png
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/migrate-packages-config-to-package-reference.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/create-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/guides/Native-Packages.md
:white_check_mark:Succeeded
View

docs/guides/analyzers-conventions.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5120.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5121.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5122.md
:white_check_mark:Succeeded
View

docs/release-notes/NuGet-4.7-RTM.md
:white_check_mark:Succeeded
View

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/resources/check-project-format.md
:white_check_mark:Succeeded
View

docs/concepts/Dependency-Resolution.md

Line 26: [Warning] Invalid file link:(~/concepts/packages-and-source-control.md).
Line 61: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.
Line 107: [Warning] Invalid file link:(~/concepts/package-references-in-project-files.md#controlling-dependency-assets).

docs/consume-packages/Package-References-in-Project-Files.md

Line 46: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.
Line 61: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#floating-versions">Floating versions</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named floating-versions.

docs/reference/nuspec.md

Line 72: [Warning] Illegal link: `<a href="reference/package-versioning.md#pre-release-versions">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named pre-release-versions.
Line 280: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/archive/project-json-impact.md

Line 23: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.

docs/consume-packages/Reinstalling-and-Updating-Packages.md

Line 57: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/create-packages/includes/choose-package-id.md

Line 12: [Warning] Illegal link: `<a href="reference/package-versioning.md#semantic-versioning-200">semver 2 compliant</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named semantic-versioning-200.
Line 12: [Warning] Illegal link: `<a href="reference/package-versioning.md#semantic-versioning-200">semver 2 compliant</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named semantic-versioning-200.
Line 14: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution with PackageReference</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.
Line 14: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution with PackageReference</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.

docs/api/package-base-address-resource.md

Line 69: [Warning] Illegal link: `<a href="reference/package-versioning.md#normalized-version-numbers">normalized NuGet version strings</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named normalized-version-numbers.
Line 102: [Warning] Illegal link: `<a href="reference/package-versioning.md#normalized-version-numbers">normalization rules</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named normalized-version-numbers.
Line 138: [Warning] Illegal link: `<a href="reference/package-versioning.md#normalized-version-numbers">normalization rules</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named normalized-version-numbers.

docs/what-is-nuget.md

Line 103: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">version ranges</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/release-notes/NuGet-1.4.md

Line 70: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">version range format</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/api/registration-base-url-resource.md

Line 214: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">version range</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/archive/project-json-archive.md

Line 52: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named dependency-resolution-with-packagereference.
Line 58: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#managing-dependency-assets">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named managing-dependency-assets.
Line 64: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#excluding-references">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named excluding-references.
Line 81: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#resolving-incompatible-package-errors">Dependency resolution</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named resolving-incompatible-package-errors.

docs/create-packages/Prerelease-Packages.md

Line 18: [Warning] Illegal link: `<a href="reference/package-versioning.md#pre-release-versions">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named pre-release-versions.
Line 36: [Warning] Illegal link: `<a href="reference/package-versioning.md#pre-release-versions">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named pre-release-versions.

docs/reference/packages-config.md

Line 27: [Warning] Illegal link: `<a href="reference/package-versioning.md#version-ranges-and-wildcards">Package versioning</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named version-ranges-and-wildcards.

docs/consume-packages/Overview-and-Workflow.md

Line 27: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#resolving-incompatible-package-errors">Resolving incompatible package errors</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named resolving-incompatible-package-errors.

docs/reference/errors-and-warnings/NU1101.md

Line 21: [Warning] Illegal link: `<a href="reference/package-versioning.md#semantic-versioning-200">Semantic Versioning 2.0.0</a>` -- missing bookmark. The file reference/package-versioning.md doesn't contain a bookmark named semantic-versioning-200.

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.

Docs Build status updates of commit 03a5f2c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/consume-packages/Overview-and-Workflow.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/api/package-base-address-resource.md
:white_check_mark:Succeeded
View

docs/api/package-details-template-resource.md
:white_check_mark:Succeeded
View

docs/api/registration-base-url-resource.md
:white_check_mark:Succeeded
View

docs/api/search-autocomplete-service-resource.md
:white_check_mark:Succeeded
View

docs/api/search-query-service-resource.md
:white_check_mark:Succeeded
View

docs/archive/project-json-archive.md
:white_check_mark:Succeeded
View

docs/archive/project-json-impact.md
:white_check_mark:Succeeded
View

docs/archive/project-json.md
:white_check_mark:Succeeded
View

docs/concepts/Dependency-Resolution.md
:white_check_mark:Succeeded
View

docs/concepts/Package-Versioning.md
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-1.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-2.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-3.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-4.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-5.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-6.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-7.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-8.png
:white_check_mark:Succeeded
View

docs/concepts/package-installation-process.md
:white_check_mark:Succeeded
View

docs/consume-packages/Package-References-in-Project-Files.md
:white_check_mark:Succeeded
View

docs/consume-packages/Package-Restore.md
:white_check_mark:Succeeded
View

docs/consume-packages/Reinstalling-and-Updating-Packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/migrate-packages-config-to-package-reference.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-Localized-Packages.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/create-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/create-packages/Prerelease-Packages.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/create-packages/includes/choose-package-id.md
:white_check_mark:Succeeded
View

docs/guides/Create-NET-Standard-Packages-VS2015.md
:white_check_mark:Succeeded
View

docs/guides/Create-UWP-Packages.md
:white_check_mark:Succeeded
View

docs/guides/Native-Packages.md
:white_check_mark:Succeeded
View

docs/guides/analyzers-conventions.md
:white_check_mark:Succeeded
View

docs/guides/create-packages-for-xamarin.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-the-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio-net-framework.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU1101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU1103.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5120.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5121.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5122.md
:white_check_mark:Succeeded
View

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

docs/consume-packages/Overview-and-Workflow.md

Line 27: [Warning] Illegal link: `<a href="consume-packages/dependency-resolution.md#resolving-incompatible-package-errors">Resolving incompatible package errors</a>` -- missing bookmark. The file consume-packages/dependency-resolution.md doesn't contain a bookmark named resolving-incompatible-package-errors.

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.

Docs Build status updates of commit 9eedae4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/api/package-base-address-resource.md
:white_check_mark:Succeeded
View

docs/api/package-details-template-resource.md
:white_check_mark:Succeeded
View

docs/api/registration-base-url-resource.md
:white_check_mark:Succeeded
View

docs/api/search-autocomplete-service-resource.md
:white_check_mark:Succeeded
View

docs/api/search-query-service-resource.md
:white_check_mark:Succeeded
View

docs/archive/project-json-archive.md
:white_check_mark:Succeeded
View

docs/archive/project-json-impact.md
:white_check_mark:Succeeded
View

docs/archive/project-json.md
:white_check_mark:Succeeded
View

docs/concepts/Dependency-Resolution.md
:white_check_mark:Succeeded
View

docs/concepts/Package-Versioning.md
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-1.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-2.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-3.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-4.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-5.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-6.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-7.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-8.png
:white_check_mark:Succeeded
View

docs/concepts/package-installation-process.md
:white_check_mark:Succeeded
View

docs/consume-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/consume-packages/Package-References-in-Project-Files.md
:white_check_mark:Succeeded
View

docs/consume-packages/Package-Restore.md
:white_check_mark:Succeeded
View

docs/consume-packages/Reinstalling-and-Updating-Packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/migrate-packages-config-to-package-reference.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-Localized-Packages.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/create-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/create-packages/Prerelease-Packages.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/create-packages/includes/choose-package-id.md
:white_check_mark:Succeeded
View

docs/guides/Create-NET-Standard-Packages-VS2015.md
:white_check_mark:Succeeded
View

docs/guides/Create-UWP-Packages.md
:white_check_mark:Succeeded
View

docs/guides/Native-Packages.md
:white_check_mark:Succeeded
View

docs/guides/analyzers-conventions.md
:white_check_mark:Succeeded
View

docs/guides/create-packages-for-xamarin.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-the-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio-net-framework.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU1101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU1103.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5120.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5121.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5122.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
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.

Docs Build status updates of commit 45a2481:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/_breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/api/package-base-address-resource.md
:white_check_mark:Succeeded
View

docs/api/package-details-template-resource.md
:white_check_mark:Succeeded
View

docs/api/registration-base-url-resource.md
:white_check_mark:Succeeded
View

docs/api/search-autocomplete-service-resource.md
:white_check_mark:Succeeded
View

docs/api/search-query-service-resource.md
:white_check_mark:Succeeded
View

docs/archive/project-json-archive.md
:white_check_mark:Succeeded
View

docs/archive/project-json-impact.md
:white_check_mark:Succeeded
View

docs/archive/project-json.md
:white_check_mark:Succeeded
View

docs/concepts/Dependency-Resolution.md
:white_check_mark:Succeeded
View

docs/concepts/Package-Versioning.md
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-1.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-2.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-3.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-4.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-5.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-6.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-7.png
:white_check_mark:Succeeded
View

docs/concepts/media/projectJson-dependency-8.png
:white_check_mark:Succeeded
View

docs/concepts/package-installation-process.md
:white_check_mark:Succeeded
View

docs/consume-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/consume-packages/Package-References-in-Project-Files.md
:white_check_mark:Succeeded
View

docs/consume-packages/Package-Restore.md
:white_check_mark:Succeeded
View

docs/consume-packages/Reinstalling-and-Updating-Packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/migrate-packages-config-to-package-reference.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-Localized-Packages.md
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/create-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/create-packages/Prerelease-Packages.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/create-packages/includes/choose-package-id.md
:white_check_mark:Succeeded
View

docs/guides/Create-NET-Standard-Packages-VS2015.md
:white_check_mark:Succeeded
View

docs/guides/Create-UWP-Packages.md
:white_check_mark:Succeeded
View

docs/guides/Native-Packages.md
:white_check_mark:Succeeded
View

docs/guides/analyzers-conventions.md
:white_check_mark:Succeeded
View

docs/guides/create-packages-for-xamarin.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-the-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio-net-framework.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU1101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU1103.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5101.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5120.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5121.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5122.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
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.


Many devices not reachable since today

Issue
Many devices will not be Initialized since today, only a few.
Home App shows "No Response".

What do you mean?  Initialised by whom?

Home App shows "No Response".

That’s an issue between Homebridge and HomeKit, typically nothing to do with any plugin.

Many devices not reachable since today

What do you mean?  Do they show as not reachable in the Hue app?  That’s an issue between the Hue bridge and the devices.

Log Messages

I don’t see any errors here.  Please run Homebridge in DEBUG mode and capture and attach the full log file.

What do you mean? Initialised by whom?
-> Homebridge
What do you mean?
Setup Payload:
X-HM://0023SYYT0P8I8
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 202-21-108 │
└────────────┘

[4/2/2024, 8:33:51 AM] [Hue] npm registry: request 1: GET /homebridge-hue/latest
[4/2/2024, 8:33:51 AM] Homebridge v1.7.0 (HAP v0.11.1) (Homebridge) is running on port 51826.
[4/2/2024, 8:33:51 AM] [Hue] Hue Bridge: event stream connected to https://<IP_ADDRESS>/eventstream/clip/v2
[4/2/2024, 8:33:51 AM] [Hue] npm registry: request 1: 200 OK
[4/2/2024, 8:33:51 AM] [Hue] latest version: homebridge-hue v0.13.70
[4/2/2024, 8:33:52 AM] [Hue] Hue Bridge: request 3: GET /lights
[4/2/2024, 8:33:52 AM] [Hue] Hue Bridge: request 3: 200 OK
[4/2/2024, 8:33:57 AM] [Hue] Hue Bridge: request 4: GET /lights
[4/2/2024, 8:33:57 AM] [Hue] Hue Bridge: request 4: 200 OK
[4/2/2024, 8:34:02 AM] [Hue] Hue Bridge: request 5: GET /lights
[4/2/2024, 8:34:02 AM] [Hue] Hue Bridge: request 5: 200 OK
[4/2/2024, 8:34:07 AM] [Hue] Hue Bridge: request 6: GET /lights
[4/2/2024, 8:34:07 AM] [Hue] Hue Bridge: request 6: 200 OK
[4/2/2024, 8:34:12 AM] [Hue] Hue Bridge: request 7: GET /lights
[4/2/2024, 8:34:12 AM] [Hue] Hue Bridge: request 7: 200 OK
[4/2/2024, 8:34:17 AM] [Hue] Hue Bridge: request 8: GET /lights
[4/2/2024, 8:34:17 AM] [Hue] Hue Bridge: request 8: 200 OK
`

another short question.
Is it good to use your huebridgev2 plugin yet?
If yes, how can I migrate the old to the new one?

I dont understand the part:
ID of the Homebridge Hue2 migration resource link.

I think these are lights exposed by the Hue bridge, not by Homebridge Hue?
As I said before, “No Response” typically means network issues between HomeKit and the accessories.  HomeKit uses DNS-SD over mDNS (a.k.a. Bonjour) for service discovery.  This protocol is not routable, and I’ve seen plenty of routers that fail to forward it to your iDevice after it has changed WiFi access points.  Best workaround is to disable and re-enable WiFi on your iDevices.  Structurally: make sure your router(s) and/or switch(es) don’t do IP snooping (trying to optimise traffic by only forwarding multicast packets to ports where there are devices registered to the multicast address).
Homebridge Hue2 currently is still only a placeholder.

Thanks!


neofetch: 3.2.0 -> 3.3.0

Motivation for this change
Also included: Maintainer email change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Rebased to master in 25944370e1d0dd0ba231e3a6fd78413a0b4403d5. Thanks for the update!


Add regression test for gdscript valid function signature

Previously, there was an issue where the gdscript analyzer incorrectly raised a validation error for code that had a default Dictionary, Array, or custom type.
Context: This is the test case that I used to confirm that https://github.com/godotengine/godot/issues/58856 no longer exists in master.

Thanks! And congrats for your first merged Godot contribution :tada:


Update step-2.mdx

The imports for core-js have changed as of version 3.0.1
To use the grid you have to import the grid

Closes #
Edit the react tutorial step 2
Changelog
New

import carbon grid in index.scss

Changed

Edit the polyfills imports in index.js

Removed

{{removed thing}}

Getting
./src/index.js
Module not found: Can't resolve 'core-js/modules/es.array.fill' in '/Users/tjegan/Dev/IBM/carbon-tutorial/src'

Seems like the tutorial is only using<EMAIL_ADDRESS>so the new paths are causing errors.

Getting
./src/index.js
Module not found: Can't resolve 'core-js/modules/es.array.fill' in '/Users/tjegan/Dev/IBM/carbon-tutorial/src'

Seems like the tutorial is only using<EMAIL_ADDRESS>so the new paths are causing errors.

@tw15egan I'm using npm instead of yarn, and i started the tutorial with npx create-react-app and not the template. Maybe consider updating the core-js package for the tutorial.

Gonna close this out since this seems to be related to using npm versus yarn (which should pick up the correct corejs version using the lockfile). Definitely will make sure someone takes a look at updating the corejs package, though! Thanks again for taking the time to PR this 🙏


solarposition.py: args mismatch for pyephem call from get_solarposition function

pyephem function is defined with next args:
def pyephem(time, latitude, longitude, altitude=0, pressure=101325,
            temperature=12):

then we call it from get_solarposition.
    elif method == 'pyephem':
        ephem_df = pyephem(time, latitude, longitude, pressure, temperature,
                           **kwargs)

as far as altitude is missing and we are passing positional args -  pressure goes to altitude,  temperature goes to pressure and temperature receives its default value
during the tests pyephem is called with keyword args and the is no test for calling get_solarposition with method='pyephem'  arg.
def test_pyephem_physical(expected_solpos):
...
    ephem_data = solarposition.pyephem(times, golden_mst.latitude,
                                       golden_mst.longitude, pressure=82000,
                                       temperature=11)
...

I have fixed pyephem function call from get_solarposition but before creating a pull request I'd like to check what test will be sufficient for covering such a mistake? Will get_solarposition call with a method='pyephem' be enough?

Good catch. I think the proposed test would be sufficient.

closed by #381


Example build error

Tried to build with: zig build run -Dpath="ui/examples/counter.zig" -Dgraphics -Drelease-safe
And got:
./GitRepoStep.zig:183:10: error: type '@typeInfo(@typeInfo(@TypeOf(std.child_process.ChildProcess.init)).Fn.return_type.?).ErrorUnion.error_set!*std.child_process.ChildProcess' does not support field access
child.stdin_behavior = .Ignore;
^

Make sure you have a recent version (dev/master) of the zig compiler. https://ziglang.org/documentation/master/std/#std;ChildProcess.init shows that it doesn't return an error union.

You can get the latest here: https://ziglang.org/download/

Yeah, sorry, used the old version of 0.10.0-dev (.804)


Handle serialisation of response date types

Currently, we just assign each attribute to whatever Python determines the response type to be when it renders JSON. We should provide the ability to explicitly set the types of attributes that are returned.
For example: returning date time objects or more complex types should be handled.

+1 for this, I am using a version of the Becket data structure here where I have added a datetime_attribute tuple. Bit of a hack so would be nice to have something more dynamic.

+1


v1/api: Export empty subscription on existing subscription

In case the Subscription field is nil, we leave it nil. Otherwise, we overwrite it with an empty subscription.
This should help us on import to detect if there was a subscription, and therefore prefill the fields according to that.
I hope this makes sense.

/retest

/retest

/retest

If the goal here is to have an empty {} subscription in the exported blueprint
{
"customizations":
  "subscription": {}
}

then, the Subscription struct should have omitempty for each field.

So the initial plan was to handle the nil values of the struct on frontend, and set default values instead. But Amir is right, that this smells.
I looked into the possibilities. Currently, we have almost all the fields in Subscription set as required, therefore there is no omitempty in the json structure definition for Subscription. In order to be able to marshal the Subscription structure as Subscription{}, we would have to:
a) make all of the values inside Subscription as "not required", which we do not want for sure
b) create a separate SubscriptionExport structure that would be part of CustomizationExport
BlueprintExportResponse {
    CustomizationExport {
        SubscriptionExport {
            everythingTheSameAsSubscriptionButPointers,
        },
        everythingElseSameAsCustomizations,
    }
}

^ sounds like tons of duplication, and a huge overkill for this purpose; smells as well
c) let's do the following in internal/v1/handler_blueprints.go
		Metadata: BlueprintMetadata{
			ExportedAt: time.Now().UTC().String(),
			ParentId:   &id,
			Subscribed: blueprint.Customizations.Subscription != nil,
		},

What do you think? / Any suggestions? Did I miss something?

In RHEL context, "don’t register" is only useful for quick testing, perhaps for us as engineers and designers. But in real production use, every RHEL must be registered, thus it makes sense to have "Register to:" with default customer activation key as the default option during import.
Activation keys cannot be exported as they are "secret" information, thus, any sort of auto-population is not possible there. And I see very little value in pre-selecting "Do not register" when that was the option used in the source blueprint. However, if you really need it, I suggest to put this information into blueprint metadata, a special structure that is stored with every blueprint and leave Subscription off the blueprint structure for every single export.

Okay, I am closing this pull request, as it seems like we came to the conclusion that this has very low value for customers. :) Thank you for your inputs. I believe this is a smart decision.


1.7 images taking up a lot more space than with 1.6.2 on Ubuntu 14.04

Description of problem: docker build and docker pull commands take up a lot more space, to the point that containers that fit comfortably on my machine cannot be built anymore because they fill the hard drive. It's also much slower, though I guess that can be attributed to all the additional writing.
I think this is because of a change of storage driver: 1.6.2 used devicemapper, while 1.7.0 seems to try to use overlay and falls back on vfs.
docker version
Client version: 1.7.0
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 0baf609
OS/Arch (client): linux/amd64
Server version: 1.7.0
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 0baf609
OS/Arch (server): linux/amd64

docker info
Containers: 0
Images: 0
Storage Driver: vfs
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-55-generic
Operating System: Ubuntu 14.04.2 LTS
CPUs: 1
Total Memory: 994 MiB
Name: vagrant-ubuntu-trusty-64
ID: LMK6:AMD2:2SSS:UBJV:TRUY:RIM4:6BWP:WHS7:SNUR:DCSN:FDRH:ADY2
WARNING: No swap limit support

uname -a
Linux vagrant-ubuntu-trusty-64 3.13.0-55-generic #92-Ubuntu SMP Sun Jun 14 18:32:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Environment details
Docker is running within VirtualBox, provisioned by a Vagrantfile using the ubuntu/trusty64 official Vagrant image:
Vagrant.configure(2) do |config|
  config.vm.box = "ubuntu/trusty64"
  config.vm.provider "virtualbox" do |vb|
    vb.gui = false
    vb.memory = "1024"
  end

  config.vm.provision "shell", inline: <<-SHELL
    apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 \
                --recv-keys 36A1D7869245C8950F966E92D8576A8BA88D21E9
    echo deb https://get.docker.io/ubuntu docker main >> /etc/apt/sources.list
    apt-get update
    #apt-get install -y lxc-docker-1.6.2
    apt-get install -y lxc-docker-1.7.0
    gpasswd -a vagrant docker
    service docker restart
  SHELL
end

Physical host is a MacBook Air (OS X 10.10.3).
How reproducible
Any docker build or docker pull command is much slower and takes up much more space than with Docker 1.6.2. (This may be expected behavior for vfs; I knew absolutely nothing about docker Storage Drivers before encountering this issue, and know no more than they exist at this point.)
 This will lead to unexpected behavior, data loss and errors. For more information, see https://docs.docker.com/reference/commandline/cli/#daemon-storage-driver-option
ERRO[0000] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded.
WARN[0000] Running modprobe bridge nf_nat failed with message: , error: exit status 1
WARN[0000] Your kernel does not support swap memory limit.
INFO[0000] Loading containers: start.

INFO[0000] Loading containers: done.
 This will lead to unexpected behavior, data loss and errors
INFO[0000] +job init_networkdriver()
INFO[0000] -job init_networkdriver() = OK (0)
WARN[0000] Your kernel does not support cgroup swap limit.
INFO[0000] Loading containers: start.

INFO[0000] Loading containers: done.
INFO[0000] docker daemon: 1.6.2 7c8fca2; execdriver: native-0.2; graphdriver: devicemapper
INFO[0000] +job acceptconnections()
INFO[0000] -job acceptconnections() = OK (0)
INFO[0000] Daemon has completed initialization
^CINFO[0001] Received signal 'interrupt', starting shutdown of docker...
INFO[0001] -job serveapi(unix:///var/run/docker.sock) = OK (0)
vagrant@vagrant-ubuntu-trusty-64:~$

I had this problem today with a fresh ec2 ubuntu machine, docker was installed with curl -s https://get.docker.io/ubuntu/ | sh, the storage driver was Storage Driver: vfs and pulling a 420mb image took around 21gb of disk space!
When I installed docker with (the current instructions) wget -qO- https://get.docker.com/ | sh on another fresh equivalent machine the storage driver was Storage Driver: aufs and the problem went away.

I was working with @gaverhae on this and a couple other IRC fellows who were having the same issues. It seems like the new Volumes plugin is what is causing the issues although I haven't been able to pinpoint exactly what about it is the issues.
The common factor seems to be that its been an upgrade from an older version of docker to 1.7 although I haven't yet confirmed that a fresh docker install doesn't have the same issues.
Users seem to experience slightly different symptoms as far as error messages are concerned with the common factor being 1.7 and exhausted or huge disk space usage around a vfs.
Some of the IRC users reported that using the newer installation script as found in the docker documentation (the wget one) resolved their issues. So I recommend anyone having the same issues to try that first.

I should also mention that @gaverhae was using the Ubuntu PPA for docker at first.

I can confirm the 1.7 new install has the same issue.  A build that took up 22% of 20GB EC2 system under 1.6.2 filled the disk and failed to complete under 1.7.  This was using a fresh EC2 instance using automated build systems that installed the "latest" docker so did not upgrade.

@ra120271 can you paste the output you get from docker info on an affected system?

In Docker 1.7, docker will refuse to use devicemapper if you don't have the proper environment setup... so basically, you need a dynamically built docker binary and dynamically built devicemapper so that devicemapper can stay synced with udev... otherwise you are guaranteed to run into problems, data loss, etc.
The ordering of usage of drivers has not changed.

aufs
btrfs
zfs
devicemapper
overlay
vfs

VFS of course use tons and tons of space becaue there is no CoW functionality.
How to resolve?

Install the linux-image-extra package for your kernel, which includes AUFS support
Use a dynamically built docker binary so you can use devicemapper
Use a newer kernel so you can use overlay or btrfs
Setup ZFS

Closing since this isn't really an issue with docker itself.

@cpuguy83 if the order hasn't changed, why is it that some upgrades break anyway? For instance, one person on IRC was using AUFS and after the upgrade docker defaulted to vfs. When changing back to aufs there were numerous errors.
I guess what I'm trying to understand is why its suddenly using vfs for people that weren't using vfs previously...

@jaitaiwan because they probably also did a kernel upgrade and didn't install the aufs modules for that kernel.


fix: #2262 sending comment while saving uploading

What

Sending comment by calling OpenFoodAPIClient.saveProduct and OpenFoodAPIClient.addProductImage
Screenshot

Fixes bug(s)

Fixes: #2262

Could you add the platform (ios or android ?)

Could you add the platform (ios or android ?)

yes, you want to send it in User's comment or in UserAgent's comment,  the second one might be better, but we have to modify the OFF API, or the server side...

I've just created https://github.com/openfoodfacts/openfoodfacts-dart/issues/482

comment

Thanks @monsieurtanuki, I will put the platform info in this attribute, but if we don't send a combined string in comment, the work should be done on server side

Codecov Report

Merging #2274 (6094da9) into develop (2ea0da3) will decrease coverage by 1.31%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           develop   #2274      +/-   ##
==========================================
- Coverage     8.86%   7.54%   -1.32%
==========================================
  Files          161     185      +24
  Lines         6623    9345    +2722
==========================================
+ Hits           587     705     +118
- Misses        6036    8640    +2604

Impacted Files
Coverage Δ

...kages/smooth_app/lib/widgets/attribute_button.dart
0.00% <0.00%> (-92.00%)
:arrow_down:

...s/smooth_app/lib/data_models/user_preferences.dart
8.73% <0.00%> (-23.57%)
:arrow_down:

packages/smooth_app/lib/themes/smooth_theme.dart
60.00% <0.00%> (-22.98%)
:arrow_down:

...p/lib/generic_lib/dialogs/smooth_alert_dialog.dart
15.47% <0.00%> (-18.74%)
:arrow_down:

...mooth_app/lib/data_models/product_preferences.dart
26.47% <0.00%> (-4.96%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/welcome_page.dart
0.00% <0.00%> (-3.13%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/scan_example.dart
0.00% <0.00%> (-2.28%)
:arrow_down:

packages/smooth_app/lib/main.dart
15.74% <0.00%> (-2.16%)
:arrow_down:

...p/lib/pages/onboarding/consent_analytics_page.dart
0.00% <0.00%> (-1.57%)
:arrow_down:

...smooth_app/lib/pages/product/new_product_page.dart
0.00% <0.00%> (-0.88%)
:arrow_down:

... and 174 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 8c9f372...6094da9. Read the comment docs.

Thanks monsieurtanuki, I added platform info into userAgent.system and put a combined string into userAgent.comment. For the issue openfoodfacts/openfoodfacts-dart#482, I created a pr to add app_platform and comment as parameter.

@cli1005 I've just merged https://github.com/openfoodfacts/openfoodfacts-dart/issues/482 in off-dart v1.18.2
You can now adapt your code here in smoothie if relevant.

Thanks monsieurtanuki, I added platform info into userAgent.system and put a combined string into userAgent.comment. For the issue openfoodfacts/openfoodfacts-dart#482, I created a pr to add app_platform and comment as parameter.

@cli1005 I've just merged openfoodfacts/openfoodfacts-dart#482 in off-dart v1.18.2 You can now adapt your code here in smoothie if relevant.

Thanks, adaptation been done.


chore(ops): add dockerfile

What this PR does / why we need it:
Which issue(s) does this PR fixes?:

Fixes #
Sample Links & Screenshots:

Link:

Desktop Screenshot

Mobile Screenshot

Additional comments?:
Developer Checklist:

[ ] Read your code changes at least once
[ ] Tested on multiple web browsers
[ ] Tested responsiveness (e.g, iPhone, iPad, Desktop)
[ ] No console errors
[ ] Unit tests*
[ ] Added e2e tests*

New containers are being generated each time docker run -p 3000:3000 defiscan-image is ran, else its working as per normal


[core] Automatically log the URDF and options

Currently, the log file only contains data. As a result, it is impossible to replay the simulation or to compute some dynamical quantities using only a log file.
It would be great to log the URDF and options as string constants directly in the header of the log file (it may requires to not assume that the header is not split in multiple chunks while reading it).

Fixed by https://github.com/Wandercraft/jiminy/pull/251


[FEAT] Allow specifying the playbook state directory

Is your feature request related to a problem? Please describe.
We have multiple users who might run ansible configuration playbooks against a given system. Since the state for the playbook is stored in a user-specific state directory based on either env.XDG_STATE_HOME or env.HOME, that means that the current state isn't always found depending on who runs the ansible commands.
Describe the solution you'd like
I think the best solution would be allowing a variable like tailscale_state_directory that could override the following set_fact declaration in the playbook. It would have to be a shared folder that allows multiple users to read/write it too.
- name: Install | Determine state folder
  ansible.builtin.set_fact:
    # Following https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
    tailscale_state_folder: "{{ ansible_env.XDG_STATE_HOME | default(ansible_env.HOME + '/.local/state') }}"

Thanks for raising this @neilschelly
I have had this issue in my backlog for quite some time, and I was just about to post the same thing. I believe another way to make the state user-independent is to place the state into the /var/lib/<role_name> folder, which is specifically designed for storing the state.

Is this not resolved by setting XDG_STATE_HOME to your desired location? The state folder will install as $XDG_STATE_HOME/artis3n-tailscale/state or $HOME/.local/state/artis3n-tailscale/state. It sounds like you would like to customize the location of the artis3n-tailscale directory, in which case you can set the XDG_STATE_HOME env var when invoking this playbook. Could you help me better understand your use case if this isn't sufficient?

@artis3n , yes, I believe you could do something like that. I guess I felt like that was  a mis-use of the XDG_STATE_HOME variable, since it implies that value should be some user-specific location.  Then, we'd have to ensure that every user who uses this in our organization uses it with the same XDG_STATE_HOME set, which I think we could handle.
I do think there would be more to it though, because of permissions.
If I chose a more global place, like /var/lib/artis3n-tailscale/, the code looks like it would fail unless my user can create folders under /var/lib without become: true privileges. Even if I used /tmp/artis3n-tailscale, my user could create it without become: true, but it would be created with 0700 permissions, so other users wouldn't be able to get the state.

This makes sense - the state folder could be globally readably, it just includes a sha256 hash of the Tailscale authkey so I wanted to restrict access unless necessary. Does overriding a tailscale_state_directory variable satisfy this, it feels like permissions would need to be more open regardless, right?
And I agree now with the conceptual difference of allowing configuring tailscale_state_directory as a role variable vs. setting XDG_STATE_HOME, to your point that it's a misuse of that env var since this state is specific to the server, not to a user on the server.

How about something like this?
tailscale_state_directory: {{ ansible_env.XDG_STATE_HOME | default(ansible_env.HOME + '/.local/state') }}
tailscale_state_directory_owner: "{{ansible_user_id}}"
tailscale_state_directory_group: "{{ansible_user_gid}}"
tailscale_state_directory_mode: 0700

The other change would be that you'd need to use become: true in the - name: Install | Set state idempotency folder task.
This would basically recreate the existing configuration, but allow someone to put the folder in a better shared location with other users able to access it for deployments too.


feat: sidebar set active using query string

The current sidebar setActiveLink strips off any query string before checking if it matches the link href. I currently use query strings in some of my hrefs for basic CRUD operations on a database in the side navbar. I have added the ability to keep the query string as part of the link in setActiveLink by adding 'nav-link-queried' to the class list on a 'nav-link' item.
Not sure if there is a better way, but this is how I did it. Might be useful to someone else.

^^ This is a great PR, any chance of it getting in? Project dead?


Add Linux and Android makefile

In general we only resort to Makefiles for architectures and platforms that are either unsupported by bazel, or for which bazel support is buggy/experimental. Android/Linux are both fairly well-supported by bazel, so I'm curious what the motivation is for this change? There's no description provided.

@jdduke We want to use lite without java api, and use subset of the lite ops for small size of lib.  Also we are not familiar with bazel.

You don't have to use the full set of ops. If you build a static library (via bazel), you can provide a custom OpResolver with a smaller set of ops to trim the binary size. See also https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/g3doc/apis.md.
We have a shared library target for the C API in https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/experimental/c/BUILD#L20. We'll be introducing one for the C++ API, but for now you can tweak the version_script.lds to preserve the C++ symbols.

@jdduke Does have a guide for compile Android tflite .so or .a lib without Java API? or C api under Android?

Sure, for Android, make sure your bazel Android environment is configured properly (see this guide). You can build the C library with:
bazel build -c opt --cxxopt=--std=c++11 \
  --config=android_arm \
  //tensorflow/lite/experimental/c:libtensorflowlite_c.so

If you want to use the C++ API you'll need to tweak the linker script to avoid stripping the C++ symbols.

@jdduke Is there an integration example with Linux c++? We have only model inference in a mobile app. What it is suggested for a standalone app on a linux host? XLA AOT? Tensorflow standard with c++ api?

Sure, you can look at our minimal and label_image samples for guidance, they should both run on a Linux host using the usual bazel build commands.

I'm going to tentatively close this for now. We're going to add proper C/C++ shared library targets over the next month or so as we move the C API out of experimental.


Prepare metadata for OpenMetadata ingestion

These changes provide a first draft of metadata for the OS-Climate OpenMetadata catalog.
Next steps (as part of this PR or part of a subsequent PR) would be to align that metadata with other metadata for the benefit of the Data Exchange.
Happy Easter!
@toki8 @erikerlandson @ericbroda @NickKellett @HeatherAck @caldeirav @reilly335
Signed-off-by: Michael Tiemann<EMAIL_ADDRESS>

Thanks!


[Bot test] Squashes

Test squashes

cms-bot internal usage

+code-checks

A new Pull Request was created by  iarspider  for master.
It involves the following packages:

L1Trigger/TrackFindingTracklet (l1)

epalencia, aloeliger, iarspider can you please review it and eventually sign? Thanks.
skinnari, missirol, erikbutz, Martin-Grunewald this is something you requested to watch as well.
rappoccio, antoniovilela, sextonkennedy you are the release manager for this.
cms-bot commands are listed here

+code-checks

Pull request #10 was updated. aloeliger, subirsarkar, srimanob, epalencia, iarspider can you please check and sign again.

+l1

+code-checks

Pull request #10 was updated. subirsarkar, epalencia, srimanob, aloeliger, iarspider can you please check and sign again.

+l1

test parameters:

pull_request = cms-sw/cmssw#123, cms-sw/cmsdist#456


python3Packages.meshtastic: 1.2.88 -> 1.2.90

Description of changes
https://github.com/meshtastic/Meshtastic-python/releases/tag/1.2.90

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 163375 run on x86_64-linux 1

2 packages built:

python310Packages.meshtastic
python39Packages.meshtastic


Improve the Profile page.

This issue belongs to @nicysneiros.
Improvements:

Form layout
Twitter

Can you help me where the files are located?
Which improvements do you need? :)

This issue is assigned to @nicysneiros @girol

@nicysneiros @luanfonceca ,
yesterday I sent #310 that is related to this issue.
remember to hide the Change Photo button if user is not in its own profile.

@meiralins i will merge both, okay?

@luanfonceca okay!
but if it is easier to @nicysneiros and you, feel free to reject it =)

either way, i will do a quick rebase now.

This was done on the PR #327


[Feature] StateMinerFaults RPC.

Summary of changes

Changes introduced in this pull request:

Introduces StateMinerFaults server and client support, Lotus-compatible.

Reference issue to close (if applicable)

Work on https://github.com/ChainSafe/forest/issues/3639
Other information and links

Tested with forest-tool api compare --filter MinerFaults --lotus /dns/api.calibration.node.glif.io/tcp/443/https snapshot-latest, for some reason Lotus mostly returns internal server error, but the forest json is valid.
Needs to be retested with an up-to-date Lotus node.
Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

I don't understand.

Introduces StateMinerFaults server and client support, Lotus-compatible.

Tested with forest-tool api compare --filter MinerFaults --lotus /dns/api.calibration.node.glif.io/tcp/443/https snapshot-latest, for some reason Lotus mostly returns internal server error, but the forest json is valid.
Needs to be retested with an up-to-date Lotus node.

How do we know it's Lotus-compatible?

I don't understand.

Introduces StateMinerFaults server and client support, Lotus-compatible.

Tested with forest-tool api compare --filter MinerFaults --lotus /dns/api.calibration.node.glif.io/tcp/443/https snapshot-latest, for some reason Lotus mostly returns internal server error, but the forest json is valid.
Needs to be retested with an up-to-date Lotus node.

How do we know it's Lotus-compatible?

tested locally, it's compatible.

Fixed


Rewrite mobile frontend components structure

Use a attern like here https://medium.com/@alexmngn/how-to-better-organize-your-react-applications-2fd3ea1920f1

done


"Cut and paste" not working if cell is deleted between "cut" and "paste"

Cutting and pasting from a cell which is deleted before pasting doesn't seem to work.
Environment data

VS Code version: 1.64.2
Jupyter Extension version: v2022.1.1201831736
Python Extension version: v2022.0.1814523869
OS: Windows 10
Python version: 3.8
Type of virtual environment used: N/A
Jupyter server running: Local

Expected behaviour
Cut text from a cell which is deleted should be pasted.
Actual behaviour
Nothing is pasted.
Steps to reproduce:

Create an empty notebook
Create two code cells
Write something in the first cell
Cut (ctrl+x) the text written in the same cell
Delete the first cell (select cell + x)
Try to paste the cut text on the second (now unique) cell

This is another data loss issue. As mentioned is at least related to #144102

Shouldn't this use system clipboard functionality?

@rebornix Mind if I poach this bug from you? It's in the same area related to my previous change. Felt I could at a minimum investigate at the same time.

@IanMatthewHuff that would be really nice if you can look into this, thanks in advance!

Yeah it's interesting, unlike the other issue I'm not sure if there is a quick / easy fix here. If there is a per cell undo / redo stack then we don't want to keep it around if the cell is deleted, each cell is essentially a document and I wouldn't expect a deleted document to somehow save off an undo redo stack just in case it was restored. But I'm pretty new to the code here, so that might be an over simplification on my part. I'll know more soon.

Root cause is https://github.com/microsoft/vscode/issues/122462


[FEATURE] Redesign of provider introspection for metadata & security

Affected project(s)

[ ] documentation
[ ] examples
[X] wasmCloud host
[ ] wasmCloud CLI (wash)
[ ] wasmCloud dashboard UI (washboard)
[X] capability providers
[ ] provider bindgen
[ ] control interface client
[ ] other / not sure

Is your feature request related to a problem? Please describe.
After the removal of capability signing, we lost a very easy way to identify which contracts binary providers would listen on.
For building things in the future and from a metadata standpoint (and possibly future security standpoint) it would be ideal to be able to know ahead of time (and limit) what namespaces, packages, interfaces and possibly even functions a provider intends to import or export, and control access accordingly.
At present, binary providers have quite free access to the NATS cluster, but this should change in the future, and at the very least we'll need this functionality to implement more advanced features that correlate providers and other things (components, traffic, etc).
Describe the solution you'd like
A design (and possibly first implementation/PoC) should be produced that improves the interaction with providers (and the host that can interact with them before/at runtime) which helps us achieve the following goals:

improving metadata access (namespaces, packages, interfaces, functions imported/exported by a provider)
security (should providers only receive new, restricted NATS keys?)

Generally, this should start with adding the relevant metadata-producing functions to provider traits that are expected to be implemented, in the binary provider case.
If providers are WIT-ified by the time this is pursued, the intended solutions do change a bit, and may require further discussion (as we can rely on the isolation and other properties of WebAssembly more)
Describe alternatives you've considered
N/A
Additional context
See previous discussion:
https://github.com/wasmCloud/wasmCloud/pull/1748

At present, binary providers have quite free access to the NATS cluster, but this should change in the future

I don't think I agree with this statement, could you expand on the reasoning here and provide some pros/cons of this approach. I think this prompts more thorough discussion.
My main arguments against requiring any sort of invocation signing, origin verification by default or otherwise restricting NATS cluster access here for wasmCloud entities are:

NATS cluster is within the trust domain of wasmCloud applications, meaning that all NATS traffic is implicitly trusted - NATS operators are free, however, to define their own ACL rules on top of NATS - this is out-of-scope for wasmCloud, as wasmCloud operates at a higher level of abstraction and builds on top of the security primitives provided by NATS (e.g. encryption, ACL etc.)
wasmCloud's main goal is making building distributed applications simpler - restricting access to the NATS cluster in any way here is directly against that goal, since that would add friction to extending wasmCloud applications.
interoperability with other tools/components/services/plugins - in a perfect world aligned with promises of WebAssembly and Component Model in particular - components and plugins available in the ecosystems should be compatible with one another. For example, any plugin for any Wasm runtime (let's say, Wasmtime), should be compatible with wasmCloud applications out-of-the-box. Requiring any sort of additional steps to make off-the-shelf plugins of this sort work in wasmCloud is directly against this goal

@rvolosatovs I think the security aspect of this was meant more as a discussion item and I think we are mostly on the same page around not needing invocation signing (though restricted NATS keys is a more interesting idea I haven't thought through). For me, the most critical part of this issue is metadata. Without having some sort of metadata (preferably the embedded wit world or list of exports), it makes it harder to introspect the provider and know what it is doing (this is used right now in the wasmcloud-operator to identify what Kubernetes services need to be created).
I've been thinking about this should work and I think that we should embed either all the wit, or at least the world in the created parcheezy (par.gz). So wash par create (and wash build by extension) would look for a world in the available wit or take an optional path and then embed that in the parcheezy

Please correct me if I am wrong ... but I just realized that wasmCloud does not do any validation whatsoever of the packages/interfaces (and the versions of those interfaces) specified in a link against the target (capability). I can do something like this, where I specify a hostname-provider target capability and want to use the keyvalue package. The missing version field is a related problem.
       - type: link
          properties:
            target: provider-sqldb-postgres
            namespace: wasi
            package: keyvalue
            interfaces: [atomics, store]

This means that it is up to the manifest to ensure all links are between compatible components and providers. I was initially attracted towards wasmCloud because I thought it would be able to provide this sort of runtime functionality. That is, the system would say you tried to create a link from $componentX to $capabilityY, but $capabilityY doesn't satisfy the following interfaces/versions....
This is going to be even more useful as entire teams onboard wasmCloud, and when provider instances are shared between components.

Hey @atifsyedali this is a great point, and one we've thought about as well.
If I were to try and rephrase what you're saying to make sure I understand -- The two primary issues:

Interfaces exported by a lattice participant (whether component or provider) are not verified at the host level when a link is created
Version is not specified in links

As far as (1) goes, it turns out it's not always possible to check the provider or component on the other end of a link -- they're not always there! Links can be created without the other end being present.
That said, bundling WIT information in a provider to enable provider introspection is the first step to making (1) possible, on the provider side at least.
As for (2), this is a lower level issue and we do need to rethink how the lower layers, we have an issue for it, created way back in July :)


APEXCORE-466 #resolve improved logging from the *Agent.java files

@PramodSSImmaneni please merge

LGTM