-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[dotnet-sdk-9.0.100-preview.7.24366.3] Fail to launch grandnode with error "Some services are not able to be constructed" #105134
Comments
Tagging subscribers to this area: @dotnet/area-extensions-dependencyinjection |
Hi @ericstj, could you please help check and triage this issue? Please kindly help to move to correct team if this is not correct. Thanks very much. |
Having a look at the repro to see if I can help find regressing change. These are the runtime changes that would be in that difference of builds: |
Tagging subscribers to this area: @dotnet/area-extensions-hosting |
This was regressed with #99199 @wcsanders1 @steveharter So this app only registers the However, it will always register validators, regardless of this: The I can fix this in the application by registering the This got me past the first error, but then I hit:
That's also related to conditional service registration: I couldn't see why it was trying to create a
At this point I stopped hacking. I worked around the change by setting ASPNETCORE_ENVIRONMENT=Staging. Seems to me like this app even tried to disable validation, but we ignored that: @wcsanders1 @steveharter @halter73 could you have a look here? Do you think others might face breaking changes like this with #99199 such that we should revert it, or is this a one off? |
Verified and this issue has been fixed on dotnet-sdk-9.0.100-preview.7.24379.15 |
Description
When run the 3rd party application grandnode with the latest .NET 9 build, it failed to launch that browser displays "can't reach this page". During the debugging, we found it failed with message "Some services are not able to be constructed" and stacktrace shows at
Microsoft.Extensions.DependencyInjection.ServiceProvider..ctor
.Because this app is very complex, and we don't identify a code snippet to reproduce the issue. So, we provided a repro machine for team to investigate. Please refer to the details from "Internal bug"
Reproduction Steps
Repro Steps for Debug Source on repro machine: (Please refer to the repro machine from Internal bug )
The machine has dotnet-sdk-9.0.100-preview.7.24366.3 sdk and mongodb installed.
Expected behavior
Loading page successfully.
Actual behavior
Can't reach this page .
error details:
Regression?
Yes
Verify Scenarios:
1). Windows 10 22H2 AMD64 + dotnet-sdk-3.1.426: Pass
2). Windows 10 22H2 AMD64 + dotnet-sdk-9.0.100-preview.7.24359.5: Pass
3). Windows 10 22H2 AMD64 + dotnet-sdk-9.0.100-preview.7.24366.3: Fail
Known Workarounds
No response
Configuration
Application Name: grandnode
OS: Windows 10 22H2
CPU: X64
.NET Build Number: dotnet-sdk-9.0.100-preview.7.24366.3
App & Source , Repro machine checking at https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2166741
Github Link:
https://github.com/grandnode/grandnode
Dotnet Info:
Other information
@dotnet-actwx-bot @dotnet/compat
The text was updated successfully, but these errors were encountered: