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

Is GitHub raw storage reliable?

未关闭
  • 哪里不对？
#213 16 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
github, node.js
领域
cloud

调研方向

Start with the linked Node app and its test that writes misc/now.txt, then compare the non-raw and raw GitHub URLs described in the report. Determine whether the observed delay is reproducible and whether this repository has a specific change or documentation update that could address it; completion is not defined by the issue.

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

描述

I've been building apps on the assumption that if you store something on GitHub, when you get the raw version of that thing, it'll be current. I was getting inconsistent results, so I decided to test that assumption, and it seems that it is not reliable storage.

If you read an object immediately after writing it, you will not always get back what you wrote. It's not just a matter of waiting a second or two, sometimes it's wrong for up to 10 seconds (the delay I programmed into the test).

Here's the Node app I'm running to test this. It wakes up every minute and saves a file to GitHub with the current local time string. If I reload the non-raw version of the page, it usually seems to have the current value. But if I reload the raw version of the page, it often does not have the correct value.

If you see a problem in this app, please let me know. I had big plans for using GitHub for user storage. It'll make a huge difference in interop, common ground in the fast growing Tools for Thought space.

Here are the results of the app for the first 30 minutes.

everyMinute: 1:58:13 PM, status == 200, bad
everyMinute: 1:59:00 PM, status == 200, bad
everyMinute: 2:00:00 PM, status == 200, bad
everyMinute: 2:01:00 PM, status == 200, good
everyMinute: 2:02:00 PM, status == 200, bad
everyMinute: 2:03:00 PM, status == 200, bad
everyMinute: 2:04:00 PM, status == 200, bad
everyMinute: 2:05:00 PM, status == 200, bad
everyMinute: 2:06:00 PM, status == 200, bad
everyMinute: 2:07:00 PM, status == 200, good
everyMinute: 2:08:00 PM, status == 200, bad
everyMinute: 2:09:00 PM, status == 200, bad
everyMinute: 2:10:00 PM, status == 200, bad
everyMinute: 2:11:00 PM, status == 200, bad
everyMinute: 2:12:00 PM, status == 200, bad
everyMinute: 2:13:00 PM, status == 200, good
everyMinute: 2:14:00 PM, status == 200, bad
everyMinute: 2:15:00 PM, status == 200, bad
everyMinute: 2:16:00 PM, status == 200, bad
everyMinute: 2:17:00 PM, status == 200, bad
everyMinute: 2:18:00 PM, status == 200, bad
everyMinute: 2:19:00 PM, status == 200, good
everyMinute: 2:20:00 PM, status == 200, bad
everyMinute: 2:21:00 PM, status == 200, bad
everyMinute: 2:22:00 PM, status == 200, bad
everyMinute: 2:23:00 PM, status == 200, bad
everyMinute: 2:24:00 PM, status == 200, bad
everyMinute: 2:25:00 PM, status == 200, good
everyMinute: 2:26:00 PM, status == 200, bad
everyMinute: 2:27:00 PM, status == 200, bad
everyMinute: 2:28:00 PM, status == 200, bad

You can see that more often than not the raw value is incorrect after ten seconds.

I'm leaving the app running for a while, so if you want to verify this, you can.

I'll post a note in the GitHub thread when I turn the app off.

主要语言
HTML
星标
134
派生
10
30 天内没有已合并 PR

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

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

scripting/Scripting-News 的其他 Issue

查看 scripting/Scripting-News 的全部 Issue

相似的 Issue

更多 Cloud Issue

把新 issue 发到你的邮箱

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