[GH-ISSUE #2867] 设置同步-gitee-下载设置报错 #1882

New issue

Closed

opened 2026-02-27 00:05:12 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 00:05:12 +03:00

Owner

Originally created by @Kabulaka on GitHub (Jun 28, 2023).
Original GitHub issue: https://github.com/electerm/electerm/issues/2867

Electerm Version and download file extension(Electerm版本和下载文件后缀)

1.26.2 所有版本

Platform detail (平台详情)

windows 11，mac os(ARM)

What steps will reproduce the bug?(重新问题的详细步骤)

点击“设置同步”
点击“gitee”
配置“token”、“gist”、“加密密码”
点击“下载配置”

此时出现错误：

Error: Seems you have a empty gist, you can try use existing gist ID or upload first
    at Proxy.e.downloadSetting (http://127.0.0.1:30974/js/electerm.js?1.26.2:2:1889388)

但是实际书签是同步成功的，但是重启后书签丢失

What should have happened?(期望的结果)

下载配置，可以正常完成

Would this happen in other terminal app(是否能够在其他同类软件重现这个问题)

No response

Additional information(其他任何相关信息)

No response

Originally created by @Kabulaka on GitHub (Jun 28, 2023). Original GitHub issue: https://github.com/electerm/electerm/issues/2867 ### Electerm Version and download file extension(Electerm版本和下载文件后缀) 1.26.2 所有版本 ### Platform detail (平台详情) windows 11，mac os(ARM) ### What steps will reproduce the bug?(重新问题的详细步骤) 1. 点击“设置同步” 2. 点击“gitee” 3. 配置“token”、“gist”、“加密密码” 4. 点击“下载配置” 此时出现错误： ``` Error: Seems you have a empty gist, you can try use existing gist ID or upload first at Proxy.e.downloadSetting (http://127.0.0.1:30974/js/electerm.js?1.26.2:2:1889388) ``` 但是实际书签是**同步成功**的，但是重启后**书签丢失** ### What should have happened?(期望的结果) 下载配置，可以正常完成 ### Would this happen in other terminal app(是否能够在其他同类软件重现这个问题) _No response_ ### Additional information(其他任何相关信息) _No response_

kerem

2026-02-27 00:05:12 +03:00

closed this issue
added the
need investigate
label

kerem commented

2026-02-27 00:05:12 +03:00

Author

Owner

@zxdong262 commented on GitHub (Jun 29, 2023):

复现不了这个情况。数据是什么样的，方便提供一个脱敏的副本让我试试不

@zxdong262 commented on GitHub (Jun 29, 2023): 复现不了这个情况。数据是什么样的，方便提供一个脱敏的副本让我试试不

kerem commented

2026-02-27 00:05:12 +03:00

Author

Owner

@Kabulaka commented on GitHub (Jun 29, 2023):

复现不了这个情况。数据是什么样的，方便提供一个脱敏的副本让我试试不

应该是老版本升级上来数据不兼容，报错后不重启，直接再上传一次，下载一次就正常了

@Kabulaka commented on GitHub (Jun 29, 2023): > 复现不了这个情况。数据是什么样的，方便提供一个脱敏的副本让我试试不应该是老版本升级上来数据不兼容，报错后不重启，直接再上传一次，下载一次就正常了

kerem referenced this issue

2026-02-27 01:53:19 +03:00

[PR #1884] [MERGED] fix #1882 fix: Fix tests #3657