@Anjali_Sumade, can you please somehow enhance your infra related to nuget source to ensure that it will not happen in the future.
It's already a second occurrence during last month(and I can't event count how many times it happened during this year). Each time when it happens - whole our build and development pipelines gets blocked producing a large hustle and money waste.
Please also provide an information how you plan to mitigate a risk of occurrence of the same incident in the future, thank you.
Abp support haven't written anything afterwards but that problem was resolved after 4-5 hours. Everthing seems to be fine now.
But to be honest that happens pretty often, not sure why ABP decided to go with some handmade unstable bicycle for storing nuget packages.
It turns out that abp has made custom nuget package source(some bicycle), which works like a xmas tree. Not a first time and not a last one when it's down, I assume. If you use a azure devops I would highly recommend to enable custom artifact feed. It has built-in capabilities to Azure devops and forward restores to it.
If it's 2 seconds, I think it's normal. You can temporarily disable redis to see its performance.
But if there will be 10 times more permissions - it will load 20 seconds. oO Don't you think that in ABP there is a big architectural issue in that regards? 2 seconds response from a core of system - is too long already.
@mahmut.gundogdu is there any estimate, when а problem could be solved?
Hello Mahmut, any update on this ticket?
Thank you for an update Mahmut!
Thank you for an update Mahmut and your effort! No worries I was not expecting to get a fix today. It would be lovely to get some fix in upcoming week or two. I bet a fix will require several patches inside of ABP.
