167 largest cycle in statistics not being computed correctly #176
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #167
What was changed?
The data in the right sidebar was updated and fixed so that the statistics are correct.
Why was it changed?
Currently, some of the stats on the right side of the page are incorrect, as they either reference the wrong data or are parsed incorrectly. This may give users the wrong impression about the functions they are looking at and they may draw incorrect assumptions. The fix changes this so now the stats are correct for the returned functions, allowing for quick analysis.
How was it changed?
The
postgres_connector.py
file was changed. Specifically, theget_statistics()
function was updated and altered so that the values that get pushed to the front end is the data that should be getting sent. There was no need to change any functionality on the frontend as all of the fields were present.