Track functional parity with pylance
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 15/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
Direzione di ricerca
Read the capability inventory in this issue and the linked implementation issues, starting with the source families dataset.py, fragment.py, query.py, file.py, namespace.py, and mem_wal.py at the pinned pylance revision. Map each public Python operation to its C declaration, C++ wrapper, Rust API, and semantic tests, then record gaps and Python convenience mappings. The inventory is complete when each capability has a disposition and concrete gaps are tracked in linked issues; unresolved scope and acceptance work remain.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
The goal is to expose capabilities already provided by public Lance Rust APIs to C and C++ consumers with equivalent observable behavior, ownership rules, errors, and supported data compatibility. pylance is a discovery reference, not a mandate to create missing native features.
Baselines
- Initial lance-c source snapshot was
a51ab47a9c814a746cb1714c99fad93dd3a188b8. - Initial Lance dependency was
68c12dfd7efe02f90ad2d7f3a239a7eb64884e57, version 13.0.0-beta.18. - The initial parity reference is pylance v14.0.2. Its source revision is
40f15ed1b71b66950961b175829fdf17a763f108. Reassess later upstream changes as separate deltas.
The accepted core migration landed in #122 and closed #105. Main at 135e68e5b6fa65a0dc019c4031aa270fb6b49000 uses Lance v14.0.2 (40f15ed1b71b66950961b175829fdf17a763f108) and Rust MSRV 1.94.0. The supported C ABI, C++17 and historical-data paths remain covered by the accepted migration evidence.
Rust authority
The functional inventory uses pylance as a reference. The selected Lance Rust core at 40f15ed1b71b66950961b175829fdf17a763f108 defines available capabilities, parameter meanings, operation semantics and boundaries. C/C++ additions provide the foreign-language representation, ownership and error conversion needed to call that core.
Before implementation, map each operation to its public Rust method/type and validation path. Use direct Rust behavior as the semantic oracle. Any missing core operation is an upstream prerequisite, outside binding implementation until independently provided by Lance. This task must not initiate native feature development or maintain native feature patches to fill a parity gap. Binding-only product capabilities, policies and new query/retention semantics are outside this task. Existing public compatibility constraints must be handled explicitly during migration.
Capability inventory
Map public Python operations to the C declaration, C++ wrapper, Rust implementation, and semantic test coverage. Cover dataset and fragment operations, scanning and filters, vector and full-text search, index lifecycle and distributed builds, writes and mutations, schema evolution, versions and maintenance, storage and sessions, blobs and file access, and namespace operations.
Record each capability as equivalent, partial, missing, blocked by the pinned core, or requiring a scope decision. Explain Python-specific conveniences individually. Earlier roadmap deferrals remain context for decisions and must be reassessed against this parity goal.
- Recheck every capability against public Rust APIs and record core prerequisites and Python convenience mappings.
First delivery
- Complete the source-backed capability inventory and turn concrete gaps into linked issues.
- Repair versioned vcpkg and Conan recipes and verify actual consumer installation.
- Complete E6 per-segment index coverage and version listing from #55.
- Advance typed compound FTS from #35, beginning with Boolean composition and explicit ownership and scoring contracts. Delivered in #126.
- Resolve author ownership, integration conflicts, and remaining acceptance work for #68.
- Establish a supported artifact matrix and disposition for #50.
- Reconcile completed row-prefilter work in #95 and the outdated dependency-pin premise in #85.
Delivery and acceptance
Use linked issues as the task record. Each implementation issue records the accepted contract, dependencies, current owner, next action, tested revision, and evidence limits. Preserve supported public signatures and existing consumers. Add meaningful regression or feature tests through the existing Rust and C/C++ entry points.
Bind review and validation to actual source revisions. Compile and test on NieR, including native C/C++ calls and installation entry points where affected. Keep implementation, validation, PR publication, merge, and release states distinct. Release preparation is tracked independently from publishing a version.
For material unresolved decisions, link the decision and its outcome here. Continue independent work while waiting for a decision or a required result.
Implementation issues
- #100
- #101
- #102
- #103
- #104
Source capability inventory
The inventory compares the public Python surface at the target revision with current C/C++ source. It identifies implementation work; runtime equivalence is established by each issue's acceptance evidence.
| Capability family | Current source assessment | Tracking |
|---|---|---|
| Distribution and native consumers | v0.1.9 recipe repair merged in #119. #206 and #212 establish accepted installed static/shared consumers on Windows Server 2022 x64 and Windows 11 Enterprise 10.0.26200 ARM64. #208 adds Intel macOS packaging; current main 62fbc0f also passes native Release staging, static/shared installed consumers and retained candidate identity checks on macOS 15.7.9 with Rust 1.99.1, as recorded in #103. #216 completes #214 with exact header-derived sets of 878 DLL exports and 878 import-library symbols on both Windows architectures. #174 records Windows artifact identities; #103 records macOS 15.7.9 Intel Release and 15.8.2 ARM64 Release static/shared data and ownership acceptance with retained candidate identities; neither minos metadata nor these tests establish an older macOS floor. The four current Linux Release candidate rows (Ubuntu 24.04 / Debian 12, x86_64 / native aarch64) have accepted installed and archive-extracted static/shared data and ownership execution on Rust 1.94.0; exact candidate identities and tested runtime limits are recorded in #103. The retained current ARM64 macOS Release candidate passed at source 62fbc0f in run 43181220854 with Rust 1.94.0, exactly 878 exports, 3,855 ARM64 static members (all minos 11.0), and verified archive SHA-256 af703a0f4d31af671152c8c8394e9866450f47a895a65ac8edf4e54102939bcc. All eight existing candidate rows have scoped native execution evidence; glibc 2.28 is adopted for future generic Linux packages, while author-maintained contribution #50 integration remains open. #217 completes #215 with the accepted combined static-CRT and strict-export contract on both Windows architectures; static consumers require Release /MT, and native loaded-module guards confirm the exercised OS-only dependency policy. These are candidate package results, not Go acceptance or a published release. |
#100, #103, #174 |
| C++ scan projection and filter | Native option semantics exposed and verified, merged in #125 | #106 |
| Scanner controls and introspection | Required scanner controls, introspection, C++ entry points and native Substrait aggregation merged (#123, #128, #134, #139, #145); NieR exact-source 617 Rust and five native consumers accepted | #107 completed |
| Full-text query trees | Six native typed query kinds merged in #126. LIST_ELEMENT runtime coverage merged in #177, completing #121 after independent SWE-2 review, exact-source NieR fmt/check/Clippy plus the focused Rust/native-oracle and C11/C++17 consumer, and all seven hosted checks. The merged tree exactly matches the tested integration source. #35 is complete for the delivered native query surface; last-token typeahead was withdrawn, not implemented. Fuzzy exact-prefix length retains its native meaning | #35, #104 |
| Vector/scalar index families and introspection | NGram/ZoneMap/BloomFilter merged in #138; MinHash index/search in #144; IVF_RQ and native vector build controls in #151; native trainer options, diagnostics, IVF models/partitions, search effort, prewarm and segment merging in #158 with exact-source Nier 702 ordinary Rust tests and all seven native consumers accepted. RTree #149 remains held under #153. Same-UUID metadata-file merge publication merged in #166 after Kimi review, exact-source Nier acceptance (710 ordinary Rust tests and all seven native consumers), static/shared CMake consumers and all seven hosted checks. The accepted tree combines #160 DataReplacement, #162 Blob writers and metadata publication. #205 adds accepted IVF_RQ/DOT indexed query/reopen coverage with independent expected values and a native scanner oracle; this leaves the RTree hold unchanged | #101, #110 |
| Distributed index build | E1/E2/E3/E5/E6 and physical merge are delivered. #207 delivers executed C/native 14.0.2 to Java 12.0.0 BTree v0 metadata decode, commit, reopen and indexed-query equivalence on NieR. #210 additionally delivers one executed L2 IVF_PQ v1 configuration with two fragment segments, Java commit/reopen, fixed expected queries and a Java one-shot baseline. These opt-in results cover non-stable-row-ID BTree v0 and that vector configuration; they do not establish general approximate recall or all index families. #213 adds executed simple-analyzer, ROW/block128/format2 FTS match/phrase/Boolean/rare-token interoperability against fixed expectations and a Java one-shot baseline. This is representative FTS acceptance, not general cross-version ranking equivalence. Java SDK / Doris production adapters, compatibility maintenance and actual integration/deployment acceptance are downstream responsibilities outside lance-c scope, not pending owner decisions or delivery blockers. The accepted examples and six adapter tests are retained. Cooperative cancellation depends on independently established Rust support; binding-originated native candidate work is retired and #55 is closed as not planned | #55, #101 |
| Version references, tags and branches | Versions/refs/tags and native branch lifecycle merged in #129/#135; concurrent-commit acceptance is recorded in #108; time/asof checkout is outside binding implementation until Lance independently supplies a native resolver; #108 is closed as not planned for that remaining scope | #108 |
| Fragment reads and metadata | Owned metadata, reads and deletion are accepted in #130/#140/#147; fragment creation and mutation publication are now accepted through #194/#196 under #112 | #109 completed; #112 completed |
| Dataset/schema/config/base-path metadata | Table/schema metadata, config, field metadata and snapshot inspection merged in #131/#127/#137; native config replacement, base paths and file enumeration merged in #146 with exact-source NieR acceptance (620 Rust tests and five native consumers); native merge/BatchUDF/checkpoints and all-five-callback synchronous independent reads merged in #150 with 644 Rust tests and five native consumers accepted. Independent in-memory snapshot handles merged in #168, closing #165; native schema ownership and Project transactions merged in #170 | #111 completed; #165 |
| Transactions, fragment publication, delta and SQL | Typed public native operation families, transaction/protobuf/history/single-batch commit, CommitLock, SQL/Delta, Overlay and fragment creation/mutation are accepted through #196. Final main 27b2754 tree matches the NieR combined integration: 589 C API tests, 4 mutation tests and 4 affected native consumer groups; prior applicable full suites and CMake evidence are retained. Detailed scope and limits are recorded in #112 |
#112 completed |
| Maintenance and lifecycle | Native cleanup/explain, validation and lifecycle statistics merged in #142; compaction/index-optimization plans, migration and truncate merged in #155 after exact-source Nier acceptance and all 10 hosted checks; native deep clone is accepted in #193 with cross-store, source-removal, snapshot/reference and real C11/C++17 reopen coverage; official beta20 shallow-clone repair was adopted through #224 at 29a2183e, with accepted public C local-directory execution from 27a97e2. The additive native shallow-clone and per-base reopen bindings are adopted in #226 (765dd9a2ec135cef9cdf5eb95bd93d73fa3b38e1), with independent SWE-2 review, accepted local/shared-memory public C/C++ execution, and all 10 checks passing on 5ed0ed0. The merged six-file binding increment equals the reviewed/tested source; #113 is complete under its explicit dataset-drop prerequisite disposition. Dataset drop remains outside binding implementation until Lance independently supplies a public core operation |
#113 |
| Native writer cleanup options | Native writer cleanup options/config merged in #127; manual maintenance scope is accepted in #113 | #118 |
| Blob descriptors, writes and bulk reads | Native by-address/range/buffer/close APIs merged in #148 with exact-source NieR acceptance (632 Rust tests and five native consumers); native descriptor builders, managed reuse and planned whole/range reads merged in #152 with 654 Rust tests and five native consumers accepted; packed/dedicated native writer lifecycles merged in #162 after SWE-2 review, exact-source Nier acceptance (705 ordinary Rust tests and all seven native consumers) and static/shared CMake consumers. Existing-fragment Packed/Dedicated DataReplacement publication merged in #172, with real C11/C++17 URI reopen and live NULL/empty readback accepted at exact head 9faf62a. New-row Packed/Dedicated Blob Append is accepted in #195 through native fragment metadata, typed Append and generic commit, with real C11/C++17 reopen and ownership coverage; standalone raw-reader #167 remains separate | #114 completed |
| Raw Lance file reader/writer/session | Native files/shared storage/providers and Arrow batch exchange merged in #154 after exact-source 692 ordinary Rust tests and all six native consumers, including multi-TU linkage and transfer-failure protection, passed. The binding delivery is complete; raw v2.2 Blob compatibility is repaired in official beta20 and accepted in candidate 27a97e2 through direct Rust, public C and C++ reader paths; #167 is resolved by #224 adoption at 29a2183e |
#115 completed; #167 |
| Session, storage and diagnostics | Native per-tier cache selection/inspection merged in #132; shared stores, accessors/providers, I/O statistics and raw-file cache isolation merged in #154. Native tokenizer/SIMD/process counters and dataset I/O statistics merged in #171 after independent review, exact-source Nier acceptance (725 ordinary Rust tests, seven native consumers and installed-header static/shared consumers) and all seven hosted checks. Plain-URI dataset open/write/staged-write/commit/batch-commit accessors merged in #178, completing #169 after Kimi review, Nier 739 ordinary Rust + eight native/static+shared consumers, and final hosted checks. Refresh/error/lifetime uses a loopback S3 endpoint; real-cloud authentication is unverified | #116, #169 completed |
| Namespace workflows | Native 54-operation bridge, directory/REST, managed dataset/provider integration, callbacks, metrics and REST adapter merged in #173. SWE-2 review, Nier full732+8/CMake and identity RED/GREEN accepted; hosted7/7 passed. Plain-URI dataset dynamic accessors merged separately in #178, completing #169. Shared-operation custom namespace dispatch was added in #197 without changing the legacy four-callback ABI | #51, #169 completed; #180 completed |
| MemWAL/LSM | Public C ABI and C++17 workflow merged in #179 as 1df77aa. Independent source review, Nier full acceptance and lifecycle/span/schema RED/GREEN probes passed, including real SSTable compaction and URI reopen. Recovered hosted Linux/macOS/MSRV/Clippy/Rustdoc checks passed. Native close-failure injection remains unverified, as recorded in #117 |
#117 completed |
| Core baseline | Official Lance v15.0.0-beta.20 (86fff5f4) and Rust 1.95 adopted through #224 (29a2183e), superseding the #122 baseline |
#105 |
Public source families include dataset.py, fragment.py, query.py, file.py, namespace.py and mem_wal.py.
Python convenience disposition
These entries describe host-language composition, not additional native features or new binding implementation tasks. They were checked against pinned pylance 40f15ed1b71b66950961b175829fdf17a763f108 and the existing C header at 07df7bd.
| Python entry | Existing binding path and boundary |
|---|---|
Dataset/fragment/scanner to_pandas |
Read native Arrow results through lance_scanner_to_arrow_stream, then let the host Arrow/pandas adapter construct its dataframe. Python's lazy Blob dataframe assembly is separate Python orchestration, not a new C dataframe or lazy-object API. Existing native Blob APIs remain available. |
LanceDataset.from_pydantic_model, pydantic_to_schema |
Python validates model instances and converts them to an Arrow table before writing. C/C++ callers supply an Arrow schema/stream to the existing native write APIs. Model validation, annotations and class-name-to-URI conventions belong to the host; no Pydantic runtime is added to C. |
| Dataset/fragment pickle hooks | Python serializes URI, options, version, manifest and scan settings; fragment restoration also carries the dataset and fragment ID. C/C++ applications can retain explicit URI/reference/options and reopen through native APIs, but opaque handles are not serializable. This does not promise Python-pickle compatibility or equivalent restoration from serialized manifest bytes after retention changes. No binding serialization policy is introduced. |
lance.torch dataset/loader adapters |
LanceDataset, SafeLanceDataset and loader composition own tensor conversion, sampling and worker orchestration in Python. C/C++ callers can consume existing Arrow scans/take operations in their framework adapters; tensor conversion and framework worker policy stay outside lance-c. This is not a claim of executed PyTorch interoperability. |
The pinned Python join raises NotImplementedError; it does not establish an implemented operation to reproduce. This disposition is a source mapping, not new runtime validation, a blanket claim of framework equivalence, or a request to create missing Rust capabilities.
RTree upstream release dependency
The official beta20 release contains the RTree reload fix, and its core15/Rust1.95 integration is now authorized. #153 retains the original C/native regression and acceptance record. PR #149 remains wholly held: core adoption does not authorize its implementation, merge, or a new RTree binding. The privately validated backport remains historical evidence. Independent work continues.
Raw Blob file reader prerequisite
#167 records a native v2.2 Blob footer reconstruction defect. C and direct Rust readers fail on the same C-written and native-written files, including an explicit Blob-column projection that reaches decoding. This prerequisite affects raw-file Blob readback. Packed/Dedicated dataset publication continues through its separate DataReplacement acceptance path. The repair and accepted raw-reader behavior are adopted in main through #224 at 29a2183e; historical failure evidence remains in #167. Existing functional scope is retained.
Independent in-memory snapshot handles are merged in #168, closing #165. Exact integration passed 711 ordinary Rust tests, all seven native consumers and static/shared CMake consumers. Native Schema/Project merged in #170 after independent Kimi review and Nier acceptance of 716 ordinary Rust tests, all seven native consumers and static/shared CMake consumers.
Native diagnostics and dataset-free FTS tokenization merged in #171, completing #116. The old-core raw v2.2 Blob limitation is recorded in #167 and lance-format/lance#10944. The later authorization covers adoption of the official beta20 repair in #224; the earlier preserve-pin/report-only decision no longer blocks that migration. Dataset Blob publication continues independently through #114.
Native dataset write options and actual native progress merged in #198; #203 completed the requested C11/C++ option, owner-lifetime and error-path acceptance, so #189 is closed. Ordinary scalar/vector index creation progress merged in #200 and closes #199; full index-family #110 acceptance remains separate. These deliveries do not imply Go validation.
Cross-SDK metadata acceptance
#207 merged as 930b02c27eb59f939ef4cf1dd227063c3f94460e, and #210 merged as 2d5fb1cf216f574144d8348f00ee90844fae4f22. NieR executed the public C/native 14.0.2 producer and Java 12.0.0 adapter/commit/reopen paths for two disjoint non-stable-row-ID BTree v0 segments and one L2 IVF_PQ v1 configuration (256 rows, two fragments, four partitions, two subvectors, four PQ bits). Both paths preserve metadata and publish one version. BTree filters and vector k-NN results match fixed expected values and Java one-shot baselines with actual index execution counters; five adapter JUnit tests pass. Independent Kimi review and all seven hosted checks accepted #210. Ordinary Cargo CI does not execute the opt-in Maven example.
Vector queries probe all partitions and rerank all 256 rows; this proves the recorded configuration's interoperability, not general approximate recall. Other configurations and general approximate recall or ranking equivalence are outside the evidence. #213 merged as 2ec0e158fd0ef3bf2346b59e71a5080044eaff02 and adds representative simple-analyzer FTS with ROW documents, block128, native-default posting format2 and data-file2.2: match, phrase, Boolean and rare-token queries all match independent expected IDs and a Java one-shot baseline with actual partition/cache evidence. NieR ran BTree, IVF_PQ and FTS together, plus six adapter tests; Kimi independently reviewed the identical merged tree. Java SDK / Doris production adapters, compatibility maintenance, Arrow/JNI integration and deployment end-to-end acceptance belong to downstream users; they are outside this maintenance scope and do not gate lance-c delivery. No downstream owner decision or eventual implementation by this task is pending. #55 was closed as not planned after the Rust-first scope decision; cooperative cancellation is not a pending implementation or native-feature task in this binding project. The fixture version pair and older Doris audits are historical evidence, not current downstream dependency facts. The original RFC design record is preserved.
Rust-first scope decision (2026-11-13)
The maintainer removed last_as_prefix from #35 and confirmed that lance-c is a binding project: new capabilities must originate in Lance, not in binding parity work. Native feature preparation for cancellation (#55), data-range caching (#71), time/asof resolution (#108) and dataset drop (#113) has stopped. Retained experiments are historical evidence, not an implementation or publication queue. Missing operations may be tracked as upstream prerequisites; existing Rust-backed deliveries remain accepted.
The maintainer subsequently authorized updating the accepted core15/Rust1.95 candidate to official v15.0.0-beta.20 (86fff5f40f299a2ff6abb0c10210451f27e605eb) and proceeding through lance-c integration, ready PR and merge after acceptance. This supersedes the earlier beta19 preparation-only limit; no further adoption decision is pending. The release contains the upstream raw Blob reader and shallow-clone fixes tracked in #167 and #161. Incremental source reviews and candidate runtime acceptance are complete. PR #224 merged at 29a2183e5f18504e1c55b29744115a7807fa4a11 on 2026-11-13T21:34:35Z after all 10 checks passed on e5879f68; the merge tree is identical to that accepted head. The retained 27a97e2 libraries keep their original identities; later header-only C++ fixes have separate consumer validation. Genuine BatchUDF V2 replay and core14 persisted transaction readback are adopted with this migration. Earlier beta19 C/Go results retain their original source/library identities. PR #149 remains wholly held, #50/#68 remain author-owned, Go modules remain unchanged, and no lance-c package publication is authorized.
Current remaining outcomes (2026-11-13)
Candidate 27a97e2f605ed597d9ca957daa8f6df55a96754b uses native 86fff5f40f299a2ff6abb0c10210451f27e605eb and Rust 1.95. NieR accepted 831 non-ignored tests, 14 C/C++/ABI consumer cases, explicit core14 attached/detached public-C transaction readback, Clippy/fmt and installed static/shared consumers. An earlier broad ignored invocation lacked the detached-fixture environment; its failure is retained and the explicit fixture invocation passed. Successor e5879f6 includes a C++ callback-cast fix with separate affected-consumer acceptance. These results do not claim a merged release or a new platform guarantee.
| Remaining capability/outcome | Next action / owner |
|---|---|
| Supported platform/install matrix (#103) | Policy and published-archive documentation merged in #225 (c9cffeab0df0267d139cae6c3110e42750ac13ff). Author aheev retains #50 workflow integration and has promised a weekend update; recheck 2026-11-16 09:18 UTC. No glibc 2.28 package has been published or accepted as an official release. |
| Async/Completion integration (#102) | Author jja725 asked for an update or explicit handoff; preserve #222 ABI coverage. |
| RTree (#110/#149) | Xuanwo must explicitly release the whole-PR hold before binding delivery; no competing implementation or repeated question. |
Previously accepted families and individual Python/native-prerequisite dispositions above remain valid. Retired binding-originated native work stays retired. Package publication and Go payload adoption are separate authorities.
- Lingua principale
- Rust
- Stelle
- 8
- Fork
- 17
- Merge medio
- 1h 14m
- PR unite (30g)
- 89
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di lance-format/lance-c
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 15/100
lance-format/lance-c#153 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
lance-format/lance-c#110 · 11 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
lance-format/lance-c#103 · 4 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 20/100
lance-format/lance-c#102 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di lance-format/lance-c
Issue simili
-
area:cli area:security bug priority:medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
rtk-ai/rtk#5127 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
status: new topic: ga4gh-sdk type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
comp-rbac
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
ClickHouse/ClickHouse#131875 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
googleworkspace/cli#984 ·
I maintainer di solito rispondono entro 1 giorno