Outage Updates 26/7 #143
Comments
|
Yeah this is getting ridiculous. There's still nothing from MyGet or their parent company regarding this outage. We're trying to reach out through our support line to get anything. |
|
We're assuming they're gone gone and are moving what we can to Github Packages |
|
Their docs page...
|
|
|
|
Hi there! Any news about this??!?!?!! |
|
That is their standard answer. There is no SLA guarantee. According to our support contact. |
|
We are migrating off |
|
Still no update @redsquare ? Thanks :) |
|
Also received the same response. We've started our migration away. It's been something we've put off for a while but this has forced our hand. |
|
Are they go out of business? |
nope, no update....we have migrated away |
nope, just no love for myget it seems - my advice is to migrate away asap |
|
@maartenba @xavierdecoster any updates? It has been down for almost 24 hours... |
|
They have nothing to do with myget these days
…On Wed, 26 Jul 2023, 18:40 Felipe K. De Boni, ***@***.***> wrote:
@maartenba <https://github.com/maartenba> @xavierdecoster
<https://github.com/xavierdecoster> any updates? It has been down for
almost 24 hours...
—
Reply to this email directly, view it on GitHub
<#143 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAOSDXXDFEEAZAJPC263JTXSFI7DANCNFSM6AAAAAA2X5ZM3Y>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
iVendi Ltd is registered in England and Wales under company number
07003191. Registered address Llys Eirias, Abergele Road, Colwyn Bay LL29
8BW. VAT registered number 987472949. Authorised and regulated by the
Financial Conduct Authority number 679767.
This email, including any
attachments, is private and confidential and may contain privileged
information. It is intended for use by the addressee(s) only. If you have
received this message in error, please contact us immediately and delete it
from your system; do not read, copy or disclose its contents to anyone or
use it for any purpose. It is the recipient's responsibility to check this
email and any attachments for the presence of viruses. iVendi Ltd accepts
no liability for any damage caused by any virus transmitted by this email.
No responsibility is accepted for emails unconnected with our business.
|
Any suggestions for migration options, preferably one that works well with BitBucket pipelines? |
|
how about the bitbucket package registry? Not sure why this didn't quote what I replied to. Was replying to @jakecolman-dpi most git repo hosting now include package registries, including github, azure develops, bitbucket, gitlab, etc. |
We are going with Azure Artifacts :) |
|
Unfortunately, Azure Artifacts don't support upstream sources for public feeds, even if they in fact belong to a paid account. Our alternative now is Feedz.io, but we need to expand that to avoid being in the same situation in the future. |
|
I think we'll go with AWS CodeArtifact, since we are an AWS shop and it like BitBucket pipelines has a connector for it. |
|
I've been looking at using Sleet to publish to an a S3/Asure bucket for public feeds. not sure if that woud be any use to you? |
|
We got this from them a few hours ago - |
|
Too little, much too late. Appalling way to conduct business
…On Wed, 26 Jul 2023, 21:23 christopherjburgess, ***@***.***> wrote:
We got this from them a few hours ago -
[image: IMG_4337]
<https://user-images.githubusercontent.com/74456771/256355147-bfaff09b-2219-439e-88cb-11e692d8351e.jpeg>
—
Reply to this email directly, view it on GitHub
<#143 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAOSDTZTWTDNZXXSWTGU63XSF4EHANCNFSM6AAAAAA2X5ZM3Y>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
iVendi Ltd is registered in England and Wales under company number
07003191. Registered address Llys Eirias, Abergele Road, Colwyn Bay LL29
8BW. VAT registered number 987472949. Authorised and regulated by the
Financial Conduct Authority number 679767.
This email, including any
attachments, is private and confidential and may contain privileged
information. It is intended for use by the addressee(s) only. If you have
received this message in error, please contact us immediately and delete it
from your system; do not read, copy or disclose its contents to anyone or
use it for any purpose. It is the recipient's responsibility to check this
email and any attachments for the presence of viruses. iVendi Ltd accepts
no liability for any damage caused by any virus transmitted by this email.
No responsibility is accepted for emails unconnected with our business.
|
You don't need pass through feeds though. You can provide multiple sources to nuget and it will search them all to find the packages. |
Yup, that works with NuGet, but we have some limitations in our distribution system that requires a single feed to be provided. That will change in the future, but we need a drop-in replacement now. |
|
@fabricioferreira Jfrog hosted artifactory. I don't see that disappearing anytime soon. You can setup remote virtual feeds on that so that you can have a single nuget feed to hit. Which is in fact what we had configured and were using MyGet hence the reason I am here. MyGet was setup as a virtual repository in our jfrog instance for some legacy code that stopped building because the downstream MyGet call was timing out. We've now removed it and everything is working again. |
|
For those needing to migrate old packages from MyGet over to Azure Artifacts, the article below may help: |
|
If anyone needs help with the migration, I am available to help. Just drop me a message at [email protected] |
|
Thanks if somebody have some updating information? |
|
Hello Guys, we are migrating to AWS codeartifact. I am available to address questions |
|
If anyone need help with GH packages I'm also available for a chat. |
|
https://myget.org/ is back up again, let the mass exodus begin! |
|
The sites are back the damn packages arent 404 - Not Found |
|
The small volume of complaints makes me wonder how big their client base is and how much it'll decrease because of this. |
|
You can't access the packages programmatically, but you -CAN- click the button "DOWNLOAD" and then choose "All versions" via browser and proceed to upload all the packages to the next nuget feed of your choice. |
I was using the UI after the feed gave no joy. |
Any luck? I can't download specific packages and versions but I -can- download the whole feed in a zip bundle without an issue. |
Do not fool yourself, I don't think most of the clients complained, since nothing could be obtained from that. The current outage was handled "perfectly" if you wanted to lose your clients. And losing will be the result of the past 2 days. I assume we will see the aftermath later. If they have a small number of clients, than losing them would not matter, they lost nothing in the grand scheme of things. If on the other hand, they had a large number of clients and handled this crisis the way they did, it sent a bigger message to the clients than actually keeping them informed on twitter / blogs / news sites whatever: "Thank you for your money, we actually do not care about you, not even a little, not even a tiny bit. Thank you again for your money". |
|
If anyone wants I created a simple program to migrate from myget to azure artifacts in C# https://github.com/erik-hooper/NugetMigrator |
|
We'd already considered moving once before this, but didn't really want to go through the hassle. Having a total outage (which continues still given the DNS subdomain for our packages no longer exists, and logging in doesn't show the feed even) has meant that its been worth to migrate everything to something else and abandon MyGet. That does mean we've gone through and migrated to a nuget feed hosted in aws using sleet to maintain the feed... and 2 days of rebuilding everything from scratch to get updates. |
|
@erik-hooper Microsoft already had such a script available |
|
We are in the middle of migrating to azure artifacts but they are having problems too now (Europe): |
|
Hello everyone, I have a question for those who are migrating to Azure Artifacts. How are you managing authentication to connect with the feed using "_authtoken" without the need to use a personal access token? I have found ways to do it with a personal access token, but I haven't come across clear documentation on how to do it with OAuth. Has anyone been able to connect to their Azure Artifacts feed without a personal access token? Thank you. |
|
@jquintanaln We are in the same place. All I can say for now is to check: https://github.com/dotnet/dotnet-docker/blob/main/documentation/scenarios/nuget-credentials.md |
|
I realize this is unhelpful commentary, but MyGet is owned by a private equity firm. If they do have an ops team, they're likely far too busy to treat MyGet well since they likely have to monitor several different products. Everyone should get off ASAP. |
|
@jquintanaln For non-interactive uses or scenarios like docker containers, as far as I know, you can't do it without a PAT. What we did was generate an access token using |
and others
MyGet has been down for 7+ hours and no updates I can find apart from the status page - https://status.myget.org/
Any updates?
The text was updated successfully, but these errors were encountered: