Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Is GitHub raw storage reliable?

オープン
  • 何か問題がありますか？
#213 コメント 16 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

scripting/Scripting-News のほかの issue

scripting/Scripting-News の issue をすべて見る

似ている issue

Cloud の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。