Need a way to determine what release of checkout_externals was used in a specific CESM tag
还没有人认领这个 Issue。
评估
调研方向
首先，将 CESM 标签的 plans 页面与通过克隆 CESM 并挖掘其 log 找到的 checkout_externals 引用进行比较。确定当它被纳入一个标签时，plans 页面可以在哪里公开 checkout_externals 版本；完成的标准是每个标签页面都能在无需手动挖掘 log 的情况下识别该版本。
由索引模型根据 Issue 内容生成。
描述
Summary of Issue:
External components which maintain standalone capability need to maintain the checkout_externals version. Typically for CAM's case we take a previously tested CESM tag and duplicate the externals used in it. This is now being extended to needing to also maintain the version of checkout_externals. We want to identify and use the version of checkout_externals that was used in a specific CESM tag. Being able to check this easily, becomes more important as time goes on and checkout_externals is only updated sporadically - we need an easy way to determine that it has been updated.
Expected behavior and actual behavior:
An ideal solution would be for the plans page to have a location somewhere on each tag's page which indicates the checkout_externals which was used. Perhaps this could be populated (automatically?) when checkout_externals is brought into the CESM tag. Currently, there is no good way to determine the checkout_externals tag other than cloning cesm and mining the log.
Steps to reproduce the problem. Include externals description file(s) and link to public repository):
N/A
What is the changeset ID of the code, and the machine you are using:
N/A
have you modified the code? If so, it must be committed and available for testing:
N/A
Screen output or log file showing the error message and context:
N/A
@bjandre suggested that I bring @mvertens , @fischer-ncar , @bertinia and possibly @jedwards4b into this discussion.
- 主要语言
- Python
- 星标
- 495
- 派生
- 253
- 平均合并
- 34 分钟
- 30 天内合并 PR
- 4
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ESCOMP/CESM 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 72/100
-
fleximod-test GitHub workflow isn't working right可能已有人在做 @samsrabin 于 6 天前认领。 未关闭bug
-
There are no default PE layouts using the tx2_3v3 grid可能重新可做 @mnlevy1981 于 63 天前认领，目前没有进行中的 PR。 未关闭
-
No default PE layout on derecho for CESM3 development runs with MARBL可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 3/5 1-2 天 新手友好度 68/100
-
难度 5/5 一周以上 新手友好度 25/100
相似的 Issue
-
question
难度 1/5 1 小时以内 新手友好度 68/100
vllm-project/vime#524 ·
维护者通常 7 天内回复
-
WOPI editor page is scrollable by a few pixels, which breaks scrolling in the document (Firefox)未关闭
难度 2/5 1-3 小时 新手友好度 84/100
suitenumerique/drive#969 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
theupdateframework/python-tuf#3044 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
FAIRmat-NFDI/pynxtools#861 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
NVIDIA/nsight-python#88 ·
维护者通常 1 天内回复