Since last Friday evening in Korea, the problem that the final state of Github Source is not downloaded with curl continues.
From the past, there has been a 10-minute sync issue from evening time in Korea (approximately after 9pm). In curl , the past source that was just committed is downloaded.
Since last Friday, the problem has become more serious.
I waited for more than 2 hours, but there was no sign of recovery, and after sleeping one night and more than 10 hours the next day (I have not been able to measure accurately),
I can receive the last synced source.
It seems that this problem still persists.
What is MS doing?
I've heard rumors that it's related to CharGPT.
Do you have this problem in other countries besides Korea?
Question
Peter Suh
Since last Friday evening in Korea, the problem that the final state of Github Source is not downloaded with curl continues.
From the past, there has been a 10-minute sync issue from evening time in Korea (approximately after 9pm). In curl , the past source that was just committed is downloaded.
Since last Friday, the problem has become more serious.
I waited for more than 2 hours, but there was no sign of recovery, and after sleeping one night and more than 10 hours the next day (I have not been able to measure accurately),
I can receive the last synced source.
It seems that this problem still persists.
What is MS doing?
I've heard rumors that it's related to CharGPT.
Do you have this problem in other countries besides Korea?
Edited by Peter Suh1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.