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/6.0-staging] dotnet.exe prints error messages to console when launched with empty DOTNET_MULTILEVEL_LOOKUP #88664

Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jul 11, 2023

Backport of #84322 to release/6.0-staging

/cc @elinor-fung @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 confusing for users - particularly since VS does this.

See #82260, #87687

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 and backported to 7.0 two weeks ago.

Risk

Isolated change, simple if statement.

@ghost
Copy link

ghost commented Jul 11, 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/6.0-staging

/cc @elinor-fung @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: -

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 6.0.x

@rbhanda rbhanda modified the milestones: 6.0.x, 6.0.21 Jul 20, 2023
@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Jul 20, 2023
@carlossanlop
Copy link
Member

Friendly reminder: if you want this servicing fix to be included in the September 2023 Release, you'll have to merge this PR before August 14th.

@vitek-karas
Copy link
Member

@elinor-fung can you take a look what's needed to merge this?

@elinor-fung
Copy link
Member

Timeout is unrelated.

@elinor-fung elinor-fung merged commit bed1eb9 into release/6.0-staging Aug 2, 2023
170 of 172 checks passed
@elinor-fung elinor-fung deleted the backport/pr-84322-to-release/6.0-staging branch August 2, 2023 20:48
@ghost ghost locked as resolved and limited conversation to collaborators Sep 2, 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
None yet
Development

Successfully merging this pull request may close these issues.

6 participants