-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Output "Failed to load host data for template" to Error and not Verbose level logging #3627
Labels
good first issue
easy issue, good for first-time contribution to the repo
help-wanted
good opportunity for contribution to the repo
triaged
The issue was evaluated by the triage team, placed on correct area, next action defined.
Comments
DavidKarlas
added
good first issue
easy issue, good for first-time contribution to the repo
help-wanted
good opportunity for contribution to the repo
triaged
The issue was evaluated by the triage team, placed on correct area, next action defined.
labels
Aug 11, 2021
We'll add the warning for .NET 6, however it needs to be moved to --validate functionality (#2623) later. |
2 tasks
vlada-shubina
added a commit
to vlada-shubina/templating
that referenced
this issue
Aug 16, 2021
vlada-shubina
added a commit
to vlada-shubina/templating
that referenced
this issue
Aug 16, 2021
vlada-shubina
added a commit
that referenced
this issue
Aug 17, 2021
GangWang01
pushed a commit
to GangWang01/sdk
that referenced
this issue
Jun 7, 2022
… to warning level
GangWang01
pushed a commit
to GangWang01/sdk
that referenced
this issue
Jun 21, 2022
… to warning level
GangWang01
pushed a commit
to GangWang01/sdk
that referenced
this issue
Jul 11, 2022
… to warning level
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
easy issue, good for first-time contribution to the repo
help-wanted
good opportunity for contribution to the repo
triaged
The issue was evaluated by the triage team, placed on correct area, next action defined.
If template author accidentally corrupts "dotnetcli.host.json" we log that issue only in verbose logging, hence it goes unnoticed and causes problems since that file is ignored.
The text was updated successfully, but these errors were encountered: