Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix broken Helm README and NGC links in Docker Compose quickstart (bug 5966370)
Summary
Removes corrupted characters from two markdown links in the Deploy with Docker Compose quickstart so links resolve correctly instead of returning 404 or odd behavior.
Problem
The raw.githubusercontent link under Specify MIG slices for NIM models included the literal sequence %E2%80%8B (the UTF-8 encoding of U+200B) at the end of the URL, so GitHub treated it as a different path and returned 404.
A zero-width space (U+200B) also appeared after the Helm README link and after the catalog.ngc.nvidia link, which is unnecessary and easy to reintroduce via copy-paste.
##Changes