• 0 Posts
  • 16 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle


  • Go had the same behavior until recently. Closures captures the variable from the for loop and it was a reference to the value.
    They changed it because it’s “common” in Go to loop over something and run a goroutine that uses the variable defined in the loop. Workaround was to either shadow the variable with itself before the loop, or to pass the value as an argument.
    It’s been a long time since I wrote c# so idk if the same is expected from the avg dev, but in Go it’s really not explicit that the variable will be a reference instead of a plain value


  • From the incident report it seems the impact was limited to VMs in one DC in one region to be stopped, as the power was lost. And some service degradation in the region.
    So not that much impact. Of course resources in this DC would stop working, but the rest of the region was still working properly. If you built your infra in this region in a resilient manner, your services should not have been impacted that much