I'm personally frustrated that it's taken almost 3 weeks to address this problem. For a developer-focused product, it's concerning that no temporary fix or workaround was implemented sooner.