fix(data): preserve more field in media metrics to fix image loading …

[Talljack]

…issue

• Modified __filter_list to accept keep_none_list parameter
• Ensure more field is always present in log data even when all values are None
• This fixes the frontend TypeError when accessing more[0]

Fixes #1354

Description

Please include a concise summary, in clear English, of the changes in this pull request. If it closes an issue, please
mention it here.

Closes: #(issue)

🎯 PRs Should Target Issues

Before your create a PR, please check to see if there is an existing issue
for this change. If not, please create an issue before you create this PR, unless the fix is very small.

Not adhering to this guideline will result in the PR being closed.

[gemini-code-assist]

Summary of Changes

Hello @Talljack, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a frontend TypeError related to image loading by modifying how media metrics data, specifically the more field, is processed. The core change involves enhancing a list filtering utility to ensure that certain lists, like the more field, always maintain their list structure, even when empty or containing only None values. This prevents the frontend from encountering errors when expecting a list and receiving None instead.

Highlights

• Modified __filter_list method: The __filter_list static method in swanlab/data/modules/wrapper.py has been updated to accept a new boolean parameter, keep_none_list.
• Preservation of more field structure: The more field, which contains media metrics, will now always retain its list structure, even if all its internal values are None. This is achieved by passing keep_none_list=True to the modified __filter_list method when processing the more data.
• Frontend TypeError fix: This change directly addresses a TypeError that occurred on the frontend when attempting to access more[0], which previously failed if more was filtered out entirely when all its elements were None.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request effectively resolves a frontend TypeError by modifying __filter_list to conditionally preserve lists containing only None values. The logic is sound. My review includes suggestions to improve the clarity of a docstring and to make the implementation of __filter_list more concise.

[SAKURA-CAT]

虽然这会导致前端出现一堆空对象：

不过总的来讲问题不大～