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

test: close remaining oracle contract and native execution gaps

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

メンテナーはふだん 1 日以内に返信

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
20/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
nodejs, sqlite, tauri, typescript
領域
databases, desktop-dev, mobile-dev, testing

調査の方向性

#1808 と #1816 の限定オラクル作業から始め、続いて監査 ID A05、R8、R10 と 113-law の永続化マニフェストを確認します。契約またはホストエビデンスの項目は、その法的履歴、受信経路、制御、リプレイ、クリーンアップ、環境、コストを特定してから選択してください。完了には、明示的なレシートまたは文書化された非対応機能が必要です。

索引モデルが issue の本文から書いたものです。

説明

Scope

Follow-up to the bounded oracle repair in #1808 / #1816. Preserve current contracts and useful tests. This is not a mandate to convert all ordinary tests or to add a universal model. Offline persistence/execution policy is owned by #1659.

Contract decisions
  • Effect self-disposal. External disposal waits for in-flight handlers. Synchronous disposal inside a handler is allowed. A handler returning independent pending work and a handler awaiting its own disposal are different histories: waiting for the former can deadlock the latter. Choose the public rule before applying the candidate wait. Preserve abort, source release, shared disposal outcome and no post-disposal publications. Existing disposal behavior remains unchanged in #1816.
  • Proxy native mutation and symbol writes. Decide Date/typed-array mutator and end-to-end symbol-key support versus a clear rejection. Existing standard live Map/Set iteration and supported detachment must remain. Compare actual stored rows, not just a helper result, and do not erase native edits through cloning. Audit IDs A05 R8/R10.
Real provider and host evidence
  • Eight progressive cells: initial explicit snapshot/atomic transition, snapshot loading/swap, multiple snapshot predicates, incremental after swap, predicates during/after snapshot, snapshot dedupe, txid before/after swap, and cleanup/restart during snapshot. Electric's ready hook is after application and cannot prove the pre-publication phase. Use a conforming installed-SDK source gate before application and the original write's actual transaction identity. TrailBase supplies no progressive capability; an early-return pass is not evidence. Preserve existing partial witnesses and make unsupported capabilities explicit.
  • 24 Electric move registrations: reconcile exact case execution and content/cleanup results from the service CI artifacts. The current PR's successful E2E job is evidence for the job, not proof of every callback-phase claim. Existing finite helper probes are not service framing evidence.
  • Native host matrix: distinguish Node SQLite/PowerSync SDK, browser shims, Capacitor/Tauri app builds and actual device/host runs. The 113-law persisted manifest intentionally excludes progressive/move suites. Expo's native-mode skipped branch and unresolved app-specific type/build/runtime cells need explicit owners and receipts; do not infer them from shared registration tests.
Optional mechanics, after correctness boundaries
  • Separate costly guarded-replay subprocess checks into a named campaign while keeping a real default execution smoke and false-target controls. Do not reintroduce progress starvation; yield only between completed histories/tests.
  • Evaluate shared Capacitor/Tauri test-runner code only with both host builds and semantic/result-transport controls preserved. Identical text alone is not enough evidence.
  • Optional cancellation/readiness corruption calibration, proxy construction-work budgets, and conditional full-payload top-K checks where a new promise requires them. Existing intentionally ID-only laws remain valid.
  • An earlier review suggested consolidating three cleanup helpers without naming them. Recover exact targets before deciding; do not merge ownership semantics blindly.

Acceptance

For each selected item: contract source, legal distinguishing history, independently computed observation, real receiving path, positive reach and fault control, exact replay, cleanup evidence, explicit environment and run cost. Keep design decisions separate from reproduced defects. No deletion without a replacement law/path map.

主要言語
TypeScript
スター
3.9k
フォーク
268
平均マージ
1日 1時間
マージ済み PR（30日）
212

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

TanStack/db のほかの issue

TanStack/db の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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