This add some tracing code that helped to troubleshoot and identify the underlying cause of 401s authenticating to builder with generated user tokens.
From the comments:
// Prior to the chronos update 4 months ago this is the max timestamp used for user tokens
// We have succesfully parsed this value via the call to Utc.timestamp_opt above for years
// Yesterday (2024-09-12), this value became out of bounds and yields a 401 trying to auth
// Right now we have no idea why and some day perhaps we will all laugh around the fire as
// we remember this bug and how trivial it truly was. Today no one is laughing. I hope there
// will be a better fix than this in the near future but this will allow the many keys currently
// out in the wild with this value to authenticate.
This add some tracing code that helped to troubleshoot and identify the underlying cause of 401s authenticating to builder with generated user tokens.
From the comments: // Prior to the chronos update 4 months ago this is the max timestamp used for user tokens // We have succesfully parsed this value via the call to Utc.timestamp_opt above for years // Yesterday (2024-09-12), this value became out of bounds and yields a 401 trying to auth // Right now we have no idea why and some day perhaps we will all laugh around the fire as // we remember this bug and how trivial it truly was. Today no one is laughing. I hope there // will be a better fix than this in the near future but this will allow the many keys currently // out in the wild with this value to authenticate.
That sadly is close to all I know right now.