Closed yayitserica closed 1 month ago
I saw this message from other customers too. it seems moving to new sdk will help solving this issue.
because old sdk is jquery and jqueryui based and new sdk is not, it'll help to trim more KBs
While moving to the new SDK will have a positive effect on the extensions load time I doubt it is the cause for load times >10min that some have reported.
I would think that the backend possibly has very long response times sometimes.
hmm, I think we should have ~5 seconds timeout to backend requests. if it's not responding in around 5 seconds, we should skip it. very good suggestion @mpth thanks!...
Just guessing though. I think you should see proof in AppInsights if dependency tracking is enabled on the client (it is by default)
We found that Google Chrome is blocking mixed content delivered by http and https with our on-prem installation.
We re-enabled mixed content delivery through the browser options. We would happily turn off http on the Azure DevOps server, but we are concerned about how this would affect the ~200 developers that we support, and their link to Visual Studio.
As Retrospectives are essential to Agile teams I would suggest in taking up the code of it and put it in the core of ADO.
maybe one day core team will add our code into AzDO (hopefully! 😊)
I get this every two weeks. I attempt to load Retrospectives, and it says it's taking too long to load. I see this in by browser's console when it happens
If I go away for a day and try again, then something loads. But, if I don't prime the pump, so to speak, a day before our team's retro, the tool just doesn't load.
Comments about browsers blocking requests I think is a red herring, as the page will load a day later.
I think I fixed this issue long time ago, please feel free to reopen it if you think it still takes long time to load
This issue occurs for me in more than one ADO organization, sometimes taking ~10 minutes to load.