Skip to content

[ty] Improve memory report formatting#23216

Merged
ibraheemdev merged 1 commit into
mainfrom
ibraheem/memory-report-improvements
Feb 10, 2026
Merged

[ty] Improve memory report formatting#23216
ibraheemdev merged 1 commit into
mainfrom
ibraheem/memory-report-improvements

Conversation

@ibraheemdev

Copy link
Copy Markdown
Member

A couple small improvements to the memory report:

  • Consistent sorting between the summary and expanded view.
  • Human readable memory size.
  • Strip the inner whitespace from type names.

@ibraheemdev ibraheemdev added ci Related to internal CI tooling ty Multi-file analysis & type inference labels Feb 10, 2026
@astral-sh-bot

astral-sh-bot Bot commented Feb 10, 2026

Copy link
Copy Markdown

Memory usage report

Memory usage unchanged ✅

@astral-sh-bot

astral-sh-bot Bot commented Feb 10, 2026

Copy link
Copy Markdown

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

✅ ecosystem check detected no format changes.

@AlexWaygood AlexWaygood left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm still slightly sceptical it's all that useful to have a table displayed if all top-line changes are <0.01MB large? But I don't feel too strongly

@ibraheemdev ibraheemdev merged commit 1cf481a into main Feb 10, 2026
43 checks passed
@ibraheemdev ibraheemdev deleted the ibraheem/memory-report-improvements branch February 10, 2026 22:53
@ibraheemdev

Copy link
Copy Markdown
Member Author

That's fair, I think it's fine to land your PR rebased on top of this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Related to internal CI tooling ty Multi-file analysis & type inference

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants