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

spike(vault): large artefacts with UnixFS in an IndexedDB blockstore

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
javascript
领域
database

调研方向

Start by locating the browser blockstore and its IndexedDB configuration, then check how the project uses @helia/unixfs. Measure write and read time, memory use, and eviction behavior for 10, 100, and 500 MB payloads on Chrome, Firefox, and Safari. Done means a results table and recommendation covering supported size limits, chunking settings, or server-side storage, with a follow-up issue if warranted.

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

描述

enhancement helia research-spike storage tier-3

Summary

Find out whether state vectors and datasets in the tens to hundreds of megabytes are practical in the browser blockstore.

Estimated size: S

Proposal

  • Store 10, 100 and 500 MB payloads with @helia/unixfs.
  • Record write time, read time, memory use and eviction behavior on Chrome, Firefox and Safari.

Acceptance criteria

  • A table of measurements and a recommendation (supported size limit, chunking settings, or server-side only).
  • Follow-up issue if a feature is justified.

Out of scope

  • Production implementation.

Dependencies

  • None; can be picked up independently.

Part of #43. Ground rules for the content layer: no secrets in the repo, content-layer failures must never block or discard quantum execution, and tests and docs ship with every PR.

主要语言
Python
星标
2
派生
4
平均合并
5 小时 19 分钟
30 天内合并 PR
11

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

QMeshPy/distributed-quantum 的其他 Issue

查看 QMeshPy/distributed-quantum 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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