Skip to content
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

CRC audit: child chain renders using its own transfersize. Fixes #2597 #2610

Merged
merged 3 commits into from
Jun 28, 2017

Conversation

ebidel
Copy link
Contributor

@ebidel ebidel commented Jun 28, 2017

Children chains were using the overall longestChain.transferSize instead of their own size.

Also updated the renderer test to actually be useful.

Fixes #2597

Copy link
Member

@brendankenny brendankenny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice fix 👍

LGTM

assert.equal(chains[1].querySelector('.crc-node__tree-hostname').textContent, '(example.com)');
const durationNodes = chains[1].querySelectorAll('.crc-node__chain-duration');
assert.equal(durationNodes[0].textContent, ' - 5,000ms, ');
assert.equal(durationNodes[1].textContent, '1.95KB');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe put a comment/assertion message that this is the transferSize and 2000 bytes is being formatted to KB? Took me a little while to see where it came from/if the new transfer sizes were being tested.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@patrickhulce
Copy link
Collaborator

sorry this'll need a rebase for the formateBytesToKB typo :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants