Activities of "maris.vigulis"

@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.

All our build is failing ATM, cause https://nuget.abp.io/ is down again.

ABP Framework version: v7.X.X

UI Type: Angular / MVC / Blazor WASM / Blazor Server

Database System: EF Core (SQL Server)

Tiered (for MVC) or Auth Server Separated (for Angular): yes

Exception message and full stack trace:

Steps to reproduce the issue:

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.

All our build is failing ATM, cause https://nuget.abp.io/ is down.

• ABP Framework version: v7.X.X
• UI Type: Angular / MVC / Blazor WASM / Blazor Server
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Exception message and full stack trace:
• Steps to reproduce the issue:

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.

• ABP Framework version: v7.2.2
• UI Type: Angular (Lepton)
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Exception message and full stack trace:
• Steps to reproduce the issue:

https://nuget.abp.io/ is down, all pipelines are pipelines are failing. Please react asap.

Example: https://nuget.abp.io/32503e08-0df9-4c11-a4a4-60e93d2e55af/v3/package/system.servicemodel.nettcp/index.json

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!