Closed gabrieligbastos closed 4 months ago
@gabrieligbastos that is likely because microsoft's installer script is throwing a 500 at the moment.
Currently we download the latest version of this script at the moment of installation. Maybe we can improve that by caching the latest version as well.
But for now I would suggest you to wait for some hours, hopefully it will get fixed soon.
We can also improve the error handling here to show a better error message when this happens.
Oh, you were right! Now, it is back. Thanks Yeah, probably those caching and better error handling would be great :)
How would that cache be?
Oh, you were right! Now, it is back. Thanks Yeah, probably those caching and better error handling would be great :)
How would that cache be?
That's nice! Great that it is working again :)
So that "caching" could be achieved by removing this line https://github.com/hensou/asdf-dotnet/blob/6a2425fc2215a01fa202d7ab2daad82251bee4fc/lib/utils.bash#L52 . I haven't given too much thought too it, but I think it would just work.
I have to think more about it.
Closing this as it was not a bug on our side. However I created two other issues for better error handling and caching.
Describe the bug
Not installing dotnet 3.1.426
Steps to reproduce
dotnet install dotnet 3.1.426
Expected behavior
To install
Screenshots
Additional context
any clue on how to install any 3.1 dotnet ?