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

Don't verify content running for rendered content

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
cli

调研方向

The payload names no files, so start by tracing the deploy path in this Python CLI: where content is rendered during deploy, where the verify GET runs, and where activation triggers a second render. Confirm whether a recent change already blocks activation after a failed render, as the issue suggests. Done means a static-content deploy skips verify, and a rendered deploy renders only once.

由索引模型根据 Issue 内容生成。

描述

Deploying (by default) renders the content. Doing a GET on the content URL doesn't validate anything I don't think. Then activating renders again. If the rendering errored, the deploy would have errored (right?) so there is no value to trying something in the middle. (I think there was a recent change to prevent activating if render failed? We should double check.) In any case, we don't want to render twice.

Clearly for static content we should also skip the verify step if we aren't already.

主要语言
Python
星标
38
派生
28
平均合并
1 天 7 小时
30 天内合并 PR
14

环境准备

从这里开始

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

posit-dev/rsconnect-python 的其他 Issue

查看 posit-dev/rsconnect-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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