Expected behavior
I can create a proposal that has a global voting delay set via the API by also calculating and setting the delay.
Actual behavior
The API creates a timestamp that is either 1 second later than when the delay was calculated. This results in a failure since the service calculate the delay off of the timestamp and realizes it is 1 second off from the global setting.
Steps to reproduce the behavior
- Set a global setting in a space
- Use the SnapshotJS API to create a proposal, setting the delay from
Date.now()
- Notice how the timestamp in the signing is 1 second off from the projected delay.