Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[main / 2.0] Upgrade notice: SQLite defaults and in-place migration / SQLite 默认存储与原地升级提醒

Aperta
  • Qualcosa non va?
#6,810 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
20/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
python, sqlite
Ambito
documentation

Direzione di ricerca

This issue is an upgrade notice, not a request to implement migration work. Read docs/guides/agent-upgrade.md for the maintained procedure, then consult loopx/capabilities/machine_configuration/goal_storage.py for the referenced new-Goal defaults; done is understanding the guidance, not changing users’ installations.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

For developers tracking main

main is now on the LoopX 2.0 development line. At the verified revision below, the package version is 2.0.0a1; this is not an announcement of a stable 2.0 release.

For new Goals on devices without an explicit storage setting, the default is canonical SQLite with hard_lease. Existing Goals and valid explicit provider/policy settings are preserved. Pulling main, updating the CLI, or changing new-Goal defaults does not migrate existing Goal data.

Upgrade an existing 1.x workspace
  1. Select the intended 2.0 version or source revision.
  2. Open the Agent-assisted upgrade guide and give its complete English or Chinese prompt to your Agent, replacing the target-version placeholder.
  3. Let the Agent inspect the installation owner and actual Goal state, stop affected old writers through their owners, reconcile pending operations, and make and verify a private backup before applying the necessary upgrade steps.
  4. Verify the original Goals, Agents, complete active/archived Tasks, configuration and receipts; activate the intended runtime and continue one useful step of the original work.

The upgrade is in place: retain the same machine, project, registry/runtime routes and Goal identities. An already current canonical Goal needs no import. Keep valid explicit providers and policies; SQLite becoming the new-Goal default is not a requirement to force every existing File Goal to SQLite.

Use the existing upgrade/import/policy owners described in the guide. Do not hand-edit registry/SQL, replace the project with empty Goals, or overwrite newer writes with an old backup. A successful package update alone does not prove that data migration and runtime activation succeeded.

If an upgrade step fails, preserve the source and report the specific failing stage, selected/installed versions, OS, and a redacted error. Do not upload private databases, raw Goal state, credentials or private work content.

给使用 main 的开发者

main 已进入 LoopX 2.0 开发线；本公告核对版本为 2.0.0a1，不代表稳定版 2.0 已发布。

未显式配置存储的新 Goal 默认使用 canonical SQLite 和 hard_lease。已有 Goal 不会因拉取 main、更新 CLI 或修改新 Goal 默认值而自动完成迁移；有效的显式 provider/policy 保持不变。

需要从 1.x 升级的开发者，请打开：

Agent 原地升级指南：复制其中完整的中文或英文提示给 Agent

先填明要升级到的 2.0 版本或源码 revision。Agent 应通过原安装及数据 owner，处理旧写方和未完成操作，先私有备份并校验，再按实际状态执行必要的格式升级、Markdown 导入或历史所有权策略迁移。

保持同一机器、项目、registry/runtime 路由和 Goal/Agent 身份，保留完整活动与归档任务、关系、材料、配置及原操作回执。已经是当前 canonical 格式的 Goal 无需再次导入；已有有效 File 配置也不因默认值变化而被强制切换。

升级后应读回原数据、激活目标 runtime，并继续原任务的一步、检查真实结果。仅安装新版包不等于迁移完成。不要手改 registry/SQL、新建空 Goal 冒充升级，或用旧备份覆盖后续写入。

遇到失败时保留原数据，反馈具体阶段、目标/实际版本、操作系统和脱敏错误；不要公开上传私人数据库、原始 Goal 状态、凭据或工作内容。

Verified baseline: main at f37d0d9, 2026-10-18. Guide at that revision · New-Goal defaults implementation.

The linked main-branch guide is the maintained procedure; this issue is the developer notice, not a second migration implementation or a request to migrate anyone's installation automatically.

Lingua principale
Python
Stelle
6.2k
Fork
596
Merge medio
7h 35m
PR unite (30g)
928

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di loopx-project/loopx

Tutte le issue di loopx-project/loopx

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.