Skip to content
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

[release/7.0-staging] dotnet.exe prints error messages to console when launched with empty DOTNET_MULTILEVEL_LOOKUP #87734

Merged
merged 10 commits into from
Jun 26, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jun 17, 2023

Backport of #84322 to release/7.0-staging

/cc @agocke @pedrobsaila

Customer Impact

The host has a bug where it prints an error, Failed to read environment variable [DOTNET_MULTILEVEL_LOOKUP], HRESULT: 0x800700CB if DOTNET_MULTILEVEL_LOOKUP is an empty string. We've gotten feedback that this is pretty confusing for users.

This fix silences the message.

Note: Not a regression. We think some tool just started setting this more frequently.

Testing

Unit testing, and this change has been in main since April.

Risk

Isolated change, simple if statement.

@ghost
Copy link

ghost commented Jun 17, 2023

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of #84322 to release/7.0-staging

/cc @agocke @pedrobsaila

Customer Impact

Testing

Risk

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

  • If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

Author: github-actions[bot]
Assignees: -
Labels:

area-Host

Milestone: -

@agocke agocke added this to the 7.0.x milestone Jun 17, 2023
Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved. we will take for consideration in 7.0.x

@jeffschwMSFT jeffschwMSFT added the Servicing-consider Issue for next servicing release review label Jun 22, 2023
@rbhanda rbhanda modified the milestones: 7.0.x, 7.0.10 Jun 22, 2023
@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Jun 22, 2023
@agocke
Copy link
Member

agocke commented Jun 26, 2023

Test failure is unrelated.

@agocke agocke merged commit 083831e into release/7.0-staging Jun 26, 2023
2 of 4 checks passed
@agocke agocke deleted the backport/pr-84322-to-release/7.0-staging branch June 26, 2023 22:32
@ghost ghost locked as resolved and limited conversation to collaborators Jul 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Host Servicing-approved Approved for servicing release
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants