-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken temp-v0.10.0 branch merge #1522
Conversation
* Remove constants test * Fix flaky test One of the unsafe evaluate test is flaky because the setInterval used internally might be potentially be called 4 times until the evaluation is suspended by the node VM. This fix is to change the tick period to make this even less probable. * Use API_CALL_TIMEOUT constant in tests * Remove API_CALL_TOTAL_TIMEOUT * Add worker timeout test * Refactor airnode-utilities timeouts * Rename default timeout to default blockchain call timeout * Add changeset * Fix lint * Remove unused delay configuration for deployer handlers
Remove heartbeatId
* Add heartbeat signing * Add changeset * Use timestamp in heartbeat signature
* Add heartbeat signing * Add changeset * Use timestamp in heartbeat signature * Add airnode_address, cloud_provider, stage, region to heartbeat payload * Add changeset * Remove airnode_address from heartbeat payload * Fix martin github account
…1418) * Remove gateway keys from validator and configs * Remove gateway keys from local handlers, examples, request headers, gcp verification * Add gateway path_key uuid to deployer, terraform and openapi templates * Add pathKey to local gateway server * Remove unused path_key variable from terraform, add uuid to local gateway docs, fix example secrets file, fix openApi template paths * Increase npm registry ping delay * Fix GCP gateway output url * Generate gateway uuid with terraform random_uuid * Uuse constant pathKey in local gateways * Merge branch temp-v0.10.0 into remove-gateway-api-keys * Update local gateway pathKey constant
ac3fe05
to
f924cf9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest testing all the "newly" added features again (after the merge), just to be on the safe side.
Yeah, we should do that. The heartbeat will be tested by @andreogle, but we should re-test the gateways. |
Closes #1521
What happened
See #1521 (comment). Apart from the force push (which removed heartbeat signature, heartbeat data and shift from gateway API keys) two other features got lost (avoiding constants with side effects, heartbeat ID removal).
The fix
I listed all PRs which were merged into
temp-v0.10.0
branch and sorted them. This can be seen here. The sorting is approximate, since GH doesn't have a sort function based on merged date.I checked what was actually merged when we merged the
temp-v0.10.0
branch back tomaster
. This can be seen here. As mentioned everything merged after #1434 was added to master.To include all of the merged PRs before #1434, I determined the order in which they were merged and cherry-picked them one by one. There were minimal merge conflicts since Airnode hasn't changed much.
Sorry, for the trouble I caused.