Executive Delay - 2021-08-21

Hello everyone,

Just wanted to throw up a quick post detailing why this week’s executive didn’t go up until this morning.
The extra time was to ensure everything was functioning properly with the proposal and not the result of any intentional delay.

The delay was caused by two main factors:

  • The team needed to wait for some Oracle updates before pushing the vote live, specifically dealing with the MATIC collateral that is being onboarded by this Exec
  • After the all-clear, we hit a wall in our checklist with the “Onchain Effects” tab of the voting portal no longer having a functional API. This part of the process is a sanity check on the proposal, but more to allow voters to see what is changing via the code directly on the voting portal. The issue returning onchain effects can be observed here.

The compounding of delays pushed the executive process well into the night. In absence of having the onchain effects as a final check on the code, we decided to run tests against the code one more time. At that point, I decided the 10-hour delay (already well past typical working hours both in UTC and out here in the US) would have minimal impact on voting and give more time to surface any issues in the absence of an item on our checklist.

The new executive can be found here or as usual at the top of the list in the “Executive” tab.

Note: this means that two executives are currently active, which hasn’t happened for quite a while. Please make sure you are supporting the proposal you intend when voting.

As usual, I’m open to field questions, comments, and concerns :slight_smile:

16 Likes

Thanks for the write up @prose11, sorry about the executive delay. The DUX team has also added a post mortem here.

5 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.