Skip to content

[Bug]: 压缩上下文后的日志位置不正确 #74

Closed as not planned
Closed as not planned

Description

@owenzhao

Version / 版本号

3.0.42-inside.10.10

Platform / 平台

macOS

OS version / 系统版本

macOS 26.5.1

Issue area / 问题类型

Model output quality

Upload ID / 日志上传 ID

409056127828394

What happened? / 问题描述

正常对话的输出,最下方是文件改动的位置,也就是那些文件发生了改动。此时,如果我选择手动压缩上下文,使用命令“总结”。就会进行上下文压缩。但是压缩之后,本来应该在日志的最下方拉一条横线,显示上下文压缩。但是这个横线却拉在了文件改动的上方。变成了。

-----压缩上下文----
文件改动

这会看起来是压缩上下文后又进行了文件改动,实际上文件改动是压缩上下文之前的。

Steps to reproduce / 复现步骤

  1. 修改文件
  2. 压缩上下文

Expected behavior / 预期行为

压缩上下文显示在最下方

Actual behavior / 实际行为

压缩上下文显示在文件改动上方。

Logs or crash report / 日志或崩溃信息

Screenshots / 截图

No response

Before submitting / 提交前确认

  • I have searched existing issues.
  • I am using the latest version available to me.
  • I have removed sensitive information from logs/screenshots.

Activity

  1. added
    desktopMiniMax Code desktop app
    needs-triageAwaiting maintainer assessment
    and removed
    desktopMiniMax Code desktop app
    on Sep 19, 2026
  2. hetaoBackend commented on Sep 21, 2026

    @hetaoBackend
    Collaborator

    This was generated by AI during triage.

    确认理解:压缩分隔线应插入在当前日志末尾,实际却插到了文件改动块上方,造成时序误读。属于 UI 渲染顺序 bug,已记录待复现修复。感谢清晰的复现步骤。

  3. hetaoBackend commented on Oct 19, 2026

    @hetaoBackend
    Collaborator

    Closing as part of a backlog cleanup: this issue was filed more than a month ago against an older release, and the codebase has changed substantially since then. If it still reproduces on the latest version, please open a new issue with the current version and reproduction steps. Thank you for the report!

    批量清理积压:该 issue 创建已超过一个月,针对的是较旧版本,代码已有较大变化。如果在最新版本上仍能复现,欢迎附上当前版本号和复现步骤重新提交 issue。感谢反馈!

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdesktopMiniMax Code desktop appneeds-triageAwaiting maintainer assessment

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions