Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Extension persistence logic breaks when extension versions are removed from SMD image

未关闭
#248 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@pilgd-aws 已经在做这个了。

开始于 2026年6月16日。

评估

这个 Issue 还没有评估数据。

描述

Issue

There is no impact to new spaces. This is related to extension persistence impacting existing spaces that are updated to use new SMD image.
Example scenario to show how existing spaces can be impacted:
Let's say a CodeEditor app - appA - is created with SMD 1.0 which has toolkit v1.0
And SMD 2.0 updates the toolkit extension to v2.0

If the appA is stopped and restarted with SMD 2.0 - it will not show the toolkit extension as installed anymore.
They will see a popup that says that the image has extension with a version different than in space's storage.

Root cause

When the CodeEditor app is starting up, we "persist" the extensions from image
This is done by creating extensions folder in space EBS storage and creating symlinks for each extension from EBS storage to image. Code link
This means that the complete extension folder for toolkit v1.0 is not copied over and only a symlink is created
Now, when we launch the app with SMD 2.0, that folder for toolkit v1.0 does not exist anymore and we do not see that extension as installed

主要语言
Shell
星标
26
派生
24
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

aws/code-editor 的其他 Issue

查看 aws/code-editor 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。