-
Notifications
You must be signed in to change notification settings - Fork 390
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
[WebToolsE2E] [Unstable] When running Aspire app, we sometimes see that the run session fails to start with error context deadline exceeded #3435
Comments
We're seeing this with Beta 5 right now. Just hitting run in VS.net causes this randomly and blocks dev. We're going to have to rollback to Beta 4. |
Is there a workaround here? |
The workaround is to use the latest daily build of Aspire https://github.com/dotnet/aspire/blob/main/docs/using-latest-daily.md Sorry, the fix is included in Aspire P6 but it did not make it to Aspire P5. |
This is a pretty big blocker that makes using aspire basically impossible except for in the most basic of cases... I'd suggest a point roll to fix this because you can't go back either because vs.net preview doesn't work with B4 properly so you have to revert all of your visual studio to a version that you can't even get at directly. |
@JohnGalt1717 not sure what makes you say this. I have been testing/developing Aspire with VS public preview laterly, no problems. What issues have you encountered? |
@karolz-ms I am seeing something similar. I was on aspire preview3 and it worked just fine. I then updated vs to 17.10.0 preview 3 yesterday, and the aspire apphost project suddenly could not run anymore. I then decided to update the aspire dependencies to the most recent preview, but then I get this issue with projects being in "Failed to start" state. |
@rmja understood, and sorry again. My recommendation to get rid of this issue would be to switch to the latest (main branch) Aspire bits, at least till P6 ships. I have been using public previews of VS (running VS 17.10.0 P3 as of today, like you do) and it works with latest Aspire, with the caveat that you need to use the .NET 8 NuGet source like https://github.com/dotnet/aspire/blob/main/docs/using-latest-daily.md says. |
@karolz-ms Yes, that seems to fix issue for now - thanks. |
This issue literally happens 9/10 times that I try and run the host. It makes it completely unsuable and others are going to try out Aspire and have the same experience. And worse I only have a Yarp proxy and 5 microservices. Others will have much more than that which will basically guarantee failure and have to come looking for this and hack their environment and wait at least a month for a fix and hope nothing else gets broken in the mean time. |
I was able to work around this issue by removing code from |
Another way to get this fix would be to run https://github.com/dotnet/aspire/blob/main/eng/installLatestFromReleaseBranch.ps1 which will install the preview 6 build. |
This is what I get when I run the script or do it by hand: Advertising manifest not updated. Manifest package for microsoft.net.workload.mono.toolchain.net7 doesn't exist. It appears that Aspire.StackExchange.Redis is required by DistributedCaching and OutputCaching but the right version of that package isn't in the dotnet8 nuget registry for preview 6 and thus can never work because it tries to use the version for .net 9 (that itself is not in the dotnet8 nuget package library) Hence there's no way to use the preview nuget package library to work around this problem. Which brings me back to: We need a down port to preview 5 that fixes this show stopper. |
Can you try running |
Workload installation failed. Rolling back installed packs... |
cc @dsplaisted @marcpopMSFT Can you folks help here? For context, we suggested folks to run our installLatest ps1 script which uses rollback files to update the version of Aspire they use. From the above, looks like perhaps when fetching for advertising manifest sometime before running the script a feed was used which found new manifests but not sure what feed was used there. Is there a way to get @JohnGalt1717 back into a working state? |
Ok, it looks like I got it working. Wow, that was a process:
Failure to have exactly this will cause the project to not build. |
That is an error we currently have with workload sets, which we are still working on. But you have to switch to workload set mode to hit that issue, and I'm surprised that anyone would be in that mode since it's not something that works yet. Do you know how that mode was enabled? Anyway, you should be able to switch out of workload set mode by running |
That fixed the pull it appears. It was in that mode because the instructions say to do this if you run it manually instead of in the script. |
I take both my work around and this back. The work around compiles and everything starts, but then service discovery doesn't work with yarp etc. And the workload update failed: (just on a different package) Workload update failed: One or more errors occurred. (Version 16.4.7142 of package microsoft.ios.sdk.msi.x64 is not found in NuGet feeds https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json".) Still back to we need a patch of P5 of Aspire that fixes this show stopper blocker bug so that it can be used and you don't have to endure this mess. |
I am having the same issue. I was able to eventually get the daily build installed but I need to add Aspire.Hosting.Azure.ApplicationInsights and now I get these errors. error NU1102: Unable to find package Azure.Provisioning with version (>= 1.0.0-alpha.20240315.2) |
@gabrewer at first glance your issue looks more to be around straight forward package restoration. Could you create a new issue for that so we don't get these two issues confused? It would be great if you could also post a small repro of the issue in a GitHub repository so we can pull it down on a clean machine with Aspire preview 5 installed and verify that things are working as they should. I tried preview 5 on a clean machine specifically with Azure Storage and it restored, built and ran fine. |
As I read through the thread more I can see the above is the case. So the brief summary of your adventures so far is that you were using Aspire P4, updated to Aspire P5 and started seeing the context deadline exceeded problems. @karolz-ms suggested using the latest P6 build which hasn't worked for you. We don't release patches for preview builds. We've been working this past week to finalize P6 and so it makes more sense to understand what the blocking issues are there and get them addressed. |
I created a repo which showcases the problem @gabrewer mentioned. I ran into the same problem when trying to use Preview 6 daily builds. |
Can this be closed now it's marked Done? |
Yes. It is fixed in Preview 6. |
INSTALL STEPS
REPRO STEPS
ACTUAL
Debug console shows errors and Dashboard shows that the services failed to start
Note: This repro is not very stable. The Repro Steps are what I did when I saw the issue reproduce.
Workaround
Give it a minute, close the windows and try again - it works fine.
EXPECTED
Dashboard launches the services successfully
The text was updated successfully, but these errors were encountered: