-
Notifications
You must be signed in to change notification settings - Fork 6
Add ETH estimates #34
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
Conversation
src/api/ProjectsApi.js
Outdated
this.retrieveProjectsWithHttpInfo = this.retrieveProjectsWithHttpInfo.bind( | ||
this | ||
); | ||
this.retrieveProjectsWithHttpInfo = | ||
this.retrieveProjectsWithHttpInfo.bind(this); |
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.
It looks like there was a problem with my prettier settings yesterday and the code formatting hadn't run properly. Sorry about the noise here!
expect(estimate.type).to.be.eq('ethereum'); | ||
expect(estimate.mass_g).to.be.above(0); | ||
expect(estimate.production).to.be.eq(false); | ||
}); |
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.
Should there be tests for project_id
,timestamp
, and create_order
params as well?
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.
No blockers but...
The test failures on this branch seem to be intermittently failing. I reran the GH actions and saw different errors on different node versions. I pulled this branch locally (toggling builds with nvm
) and saw the same behavior where tests would fail randomly. Unfortunately, I couldn't reproduce stably nor do I see an obvious issue with the most common failure; createEthereumEstimate
is undefined
. I'm unsure if this is a common issue so didn't keep digging but let me know if you'd like to take a look together
Yeah, I think one of the issue is a race condition between the tests on each version of node. It looks like the preference test can have conflicts if several tests are run in a matrix. Let me add that to Asana. |
What
Why
SDK Release Checklist