Skip to content

feat(graph-db): add openGauss backend and memory integration - #2616

Closed
SleepySuke wants to merge 28 commits into
MemTensor:dev-v2.0.37from
SleepySuke:feat/opengauss-backend-v2.0.37
Closed

SleepySuke wants to merge 28 commits into
MemTensor:dev-v2.0.37from
SleepySuke:feat/opengauss-backend-v2.0.37

Conversation

@SleepySuke

@SleepySuke SleepySuke commented Nov 11, 2026 •

Copy link
Copy Markdown

Description

This PR adds openGauss backend support to MemOS as part of internal feature development, targeting dev-v2.0.37.

It integrates AGE graph storage, native vector retrieval, and BM25 full-text search with the existing memory components, API, and Scheduler.

Related Issue / Task: N/A — internally planned feature development with no associated issue or task number.

Main changes

  • Add openGauss configuration validation, factory registration, environment settings, and connection pooling.
  • Implement scoped node and relationship operations, graph traversal, metadata filtering, vector search, BM25 search, and SQL LIKE lookup.
  • Support memory counts, capacity management, snapshot export, atomic import, and scoped clearing.
  • Add optional Dashboard range selection through all_cubes and exclude_cube_id, with documentation and OpenAPI schema updates.
  • Improve resource ownership and shutdown ordering across API, Cube, Tree memory, and Scheduler components.
  • Preserve Cube identity during search and distinct identities for working and long-term memory pairs.
  • Propagate required storage failures through search and Feedback instead of treating failures as successful empty results.

DependenciesFixes #2616

  • openGauss Enterprise with AGE and native DataVec/BM25 capabilities.
  • psycopg2-binary >=2.9.13,<3.0.0, included in the optional tree-mem and all extras.

Enable the backend with GRAPH_DB_BACKEND=opengauss and configure the corresponding OPENGAUSS_* connection settings. The database and required extensions must be provisioned before use.

Behavior changes and limitations

  • Empty Dashboard categories return empty lists instead of synthetic empty Cube buckets.
  • Non-openGauss backends reject explicit non-null values for the new Dashboard range fields.
  • Required storage errors propagate to callers. Multi-step Feedback updates are not a single transaction.
  • Database-level semantic deduplication, conflict detection, and node merging remain unsupported.
  • Full service E2E, Java client integration, real-model validation, and production-scale performance testing remain follow-up work.

Type of change

  • New feature
  • Bug fix
  • Refactor
  • Documentation update

How Has This Been Tested?

Latest recorded local validation:

  • Full repository suite with real openGauss integration enabled: 2771 passed, 9 skipped, 45 warnings.
  • Unit and integration tests cover scoped storage, retrieval, rollback, backup/restore, Dashboard responses, memory identities, Feedback failures, and concurrent shutdown.
  • A separate local HTTP smoke test passed with real openGauss and controlled model assembly, covering Dashboard results, graceful shutdown, and database session cleanup.
  • Ruff checks and formatting passed.

Integration tests use openGauss 7.0.0 with AGE 1.0.0. Test fixtures provision disposable databases and roles; application operations run with an ordinary database role.

To reproduce, configure MEMOS_OPENGAUSS_TEST_CONFIG with a JSON OpenGaussGraphDBConfig for a test administrator, then run:

poetry install --extras all --with dev --with test
make format
make test

OpenAPI was exported using the repository's component fixtures. Standard make openapi remains blocked in the local environment by missing InternetRetriever model configuration.

These results describe local validation. Hosted CI and full service E2E are not claimed as complete.

  • Unit Test
  • Test Script Or Test Steps
  • Pipeline Automated API Test

Checklist

  • I have performed a self-review of the final PR diff
  • I have commented code in hard-to-understand areas
  • I have added tests covering the new functionality and fixes
  • I have included backend setup and behavior documentation in this PR
  • I have assigned or mentioned the reviewer

Issue/task linkage: N/A — no associated issue or internal task number.

Reviewer Checklist

  • Confirmed the implementation scope and behavior changes
  • Made sure required checks passed
  • Reviewed the provided tests and validation results

Add a strict OpenGaussGraphDBConfig for connection settings, logical
tenant scopes, and bounded connection-pool configuration.

Validate required credentials, port and timeout boundaries, positive
embedding dimensions, and ordered pool limits. Require a tenant scope
for shared databases and preserve explicitly supplied scope values.

Add 105 parameter cases covering valid and invalid configuration,
JSON/YAML round trips, hidden password repr, driver-independent imports,
and existing backend configuration selection.

Validation:
- make format
- poetry run pytest tests/configs tests/graph_dbs -q
  (237 passed; 3 existing opt-in Neo4j integration cases not enabled)
- New configuration class: 26 statements and 6 branch exits covered,
  with zero missing statements or branch exits
- pre-commit checks for both changed files passed
Add an internal node store with scoped business identities, stable native
graphids, atomic batch upserts, ordered reads and row-locked partial updates.
Reject incompatible layouts without deleting data.

Prepare ordinary-role AGE sessions through a bounded psycopg2 pool. Preserve
driver causes, roll back failures and close owned connections deterministically.
Check server session cleanup within a fixed deadline after client close.

Add GraphDBError and declare psycopg2-binary in tree-mem/all extras.
Keep the incomplete backend out of the public factories.

Validate 107 unit cases and 29 live openGauss integration cases.
Config/graph regression: 373 passed, 3 existing skips.
Full suite: 1207 passed, 9 existing skips, with live openGauss enabled
and Hugging Face restricted to the local cache.
Pool/store statement and branch coverage: 100%, with no new exclusions.
Add native directed typed relationships, scoped edge/neighbor queries,
and atomic deletion of a node and all its incident edges.
Serialize graph mutations to preserve edge uniqueness and prevent deletion races.

Delete incident edges with AGE and node label rows with SQL in one transaction,
preserving trigger and permission failure rollback behavior. Bind business
values and validate relationship identifiers before borrowing a connection.

Add 73 unit cases and 17 live integration cases for directions, scope,
self/parallel edges, concurrency, special values and rollback.
Cumulative config/graph regression: 463 passed, 3 existing skips.
Full suite: 1297 passed, 9 existing skips, with live openGauss enabled
and Hugging Face restricted to the local cache.
Pool/store statement and branch coverage: 100%, with no new exclusions.
Add directed shortest paths with deterministic tie breaking and a strict
five-hop bound. Return complete two-way neighborhood nodes and induced
edges, preserving native direction, parallel edge types and self-loops.

Rank active non-reasoning/non-working memories by unique tag overlap,
with scoped exclusions, deterministic ties and optional vector projection.
Reject malformed tag data and invalid inputs instead of returning false success.

Add 86 unit cases and 21 live integration cases for traversal, projections,
scope, special strings, tag filtering and permission failure recovery.
Cumulative config/graph regression: 570 passed, 3 existing skips.
Full suite: 1404 passed, 9 existing skips, with live openGauss enabled
and Hugging Face restricted to the local cache.
Pool/store statement and branch coverage: 100%, with no new exclusions.
Consolidate the connection pool, AGE node/graph operations and filters in
OpenGaussGraphDB, following the existing PostgreSQL and PolarDB layout.
Create the pool in __init__ and keep filter parameters local to each call.

Include scoped metadata/type queries, atomic conditional deletion and
soft-delete/restore visibility tests. Preserve AGE fractional-number
round trips and the existing transaction, isolation and error contracts.

Keep unfinished BaseGraphDB methods abstract and factory registration
pending. Replace the private connection and storage modules with
opengauss.py; test-only concrete support raises for every unfinished
capability.

Validation: 398 storage/graph unit tests and 125 real openGauss integration
tests; configs/graph_dbs 760 passed, 3 existing skips; full suite 1594 passed,
9 existing skips. opengauss.py has 100% statement and branch coverage.
Formatting, applicable hooks and lock checks passed; temporary resources 0.
Add DataVec cosine retrieval with normalized scores, scoped filters,
thresholds, projection and compatible Cube completion. Validate HNSW
indexes through 2000 dimensions and use exact search up to 16000 dimensions.
Replace underfilled vector candidates with one identically filtered query.

Add native BM25 OR retrieval with raw scores and TAAT candidate scoring,
including requests above 200 results. Validate the owned text index and
recover its verified failed-write state with one REINDEX and one read retry.
Keep unrelated errors explicit and never replay writes.

Validate real GraphMemoryRetriever completion, filtering, rollback,
concurrent recovery, index permissions, cancellation and timeouts. Keep
factory registration pending the remaining maintenance and consumer APIs.

Validation: make format; applicable hooks; poetry check --lock;
configs/graph_dbs/retriever: 966 passed, 3 existing skips;
make test: 1794 passed, 9 existing skips, including all 170 openGauss IT;
backend statement
and branch coverage: 100% (869 statements, 358 branch exits).

This message describes the complete current workspace delta from 86ef67b.
Add scoped grouping, memory counts, existence checks, and oldest-memory
eviction to OpenGaussGraphDB. Count all statuses and keep numeric AGE groups
consistent with transaction-local sort aggregation.

Lock a fixed candidate set, validate every timestamp, then remove incident
edges and nodes in batches of at most 500 within one transaction. Preserve
concurrent inserts for a later cleanup and propagate transaction failures
without retrying writes.

Cover ordinary-role database behavior, public vector/BM25 visibility,
multibatch rollback, concurrent writers, cancellation, connection replacement,
commit/return failures, and real MemoryManager/Reorganizer boundaries.

Centralize transactional cursors and optional UTC/advisory setup. Compose
named SQL fragments with collision checks and reusable bindings, and separate
grouping validation, query construction, and result decoding.

Validate with 741 backend unit tests and 226 real openGauss integration tests.
The full suite passes 2040 tests with 9 existing skips; the complete openGauss
module has 100% statement and branch coverage.

Factory registration and the eight remaining abstract methods stay pending.
Select strictly activated memories of the requested type and Cube without
same-Cube PARENT adjacency in one SQL snapshot. Preserve deterministic order,
optional embeddings, scoped graph identities and existing transaction errors.

Request embeddings from Reorganizer and verify real partitioning, summaries
and PARENT writes with controlled model services. Keep the remaining seven
abstract methods pending and factory wiring unchanged.

Validation: make format; enabled openGauss make test: 2115 passed, 9 existing
skips. Full opengauss.py statements/branches and modified optimize_structure
function reach 100%. Temporary databases, roles and test/application sessions
are zero after the run.
Add explicit cross-Cube reads with preserved node and edge ownership, global
pagination, filtering and stable ordering. Keep ordinary exports scoped to
the configured Cube. Counts, nodes and induced edges share one read-only
REPEATABLE READ transaction; later borrowers return to read-write defaults.

Validation: 40 Red to Green tests; 1407 passed / 3 existing skips in affected
configuration, graph and textual-memory regression with real openGauss.
Full opengauss.py: 1060 statements and 446 branch exits covered, no omissions.
make format and git diff --check pass.
Validate graph input before borrowing, preserve existing node identities and
merge edges in one transaction. Reject missing endpoints without partial
imports. Clear a fixed locked Cube set in 500-node blocks and retain shared
schema and other Cubes; drop_database clears only its configured scope.

Validation: 43 Red to Green tests plus commit uncertainty, cancellation,
physical scope and concurrency cases. Related real-database regression:
1456 passed, 3 existing skips. Full opengauss.py: 1123 statements and 482
branch exits covered. make format and git diff --check pass.
Resolve unique Cube ownership and reject ambiguous IDs. Add atomic scoped
soft deletion, recovery and batch hard deletion while preserving other node
properties, vectors and relations.

Validation: 38 initial Red/Green cases, 3 concurrent transaction cases;
1497 passed and 3 existing skips in affected regression. The full backend
has 1172/1172 statements and 496/496 branches covered; make format passes.
Implement scoped one-hop outgoing context queries. Explicitly reject semantic
deduplication, conflict detection and merging with named capability errors;
keep application MMR independent. All tests now use the production class.

Validation: 6 initial Red cases; 8 targeted Green cases including structure.
Full make test with real openGauss: 2246 passed, 9 unchanged existing skips.
Backend coverage: 1183/1183 statements and 496/496 branches; changed
Reorganizer function: 48/48 statements and 24/24 branches. make format and
git diff --check pass. Temporary databases, roles and sessions: zero.
Exercise batch hard deletion under permission denial, last-block timeout
and actual driver cancellation. Verify full rollback, preserved deletion
records, replacement connections and search visibility after recovery.

Validation: 30 targeted real-database tests pass; final make test reports
2249 passed with the same 9 existing skips. Full backend statement and
branch coverage remains 100%; make format and git diff --check pass.
Restore read-only component mappings and leave close state with resource owners. Quiesce recovery before draining current and retired executors; reject self-close before entering terminal state. Preserve concurrent close results, retryable cleanup, explicit Cube initialization, and diagnostic logs.
Preserve primary IDs and derive stable Working IDs with working_binding. Submit each pair in one batch transaction on openGauss, propagate write failures, and preserve input result order across both add paths. Reuse binding cleanup rules and protect historical self-bindings. Cover rollback, retries, concurrent writes, capacity cleanup, and default Feedback with real database tests.
Preserve committed feedback records when optional answer generation fails and
expose answer_status. Propagate required processing and queue failures without
falling back to ordinary add; preserve complete multi-Cube result objects.

Build missing Feedback from the borrowed Cube dependencies, retain explicit
injections, and reject late initialization after close. Reject the unsafe
internal process startup path and inherited Scheduler use; provide an
independent worker entry point that constructs resources in the child.

Validate keep_latest strings against an explicit 64-character bound before
conversion or connection acquisition, preserving zero and arbitrary int values.

Validation: make format; real openGauss make test (2950 passed, 9 skipped);
100% statements/branches for changed functions and all opengauss.py;
real Redis/spawn worker, socket HTTP and resource-release smoke checks.
Standard make openapi remains blocked by existing reader model config; the
fixture-exported application schema matches docs/openapi.json.
@Memtensor-AI Memtensor-AI added area:api 云服务 / FastAPI / OpenAPI / MCP area:core MOS 编排层 / 框架底座 / 跨模块问题 area:database graph_db + vector_db | 图数据库与向量数据库 area:docs 文档、示例 area:memcube GeneralMemCube / cube 生命周期 / cube 配置 labels Nov 11, 2026
@Memtensor-AI Memtensor-AI added area:memory 记忆存储、检索、更新、召回逻辑 area:scheduler 调度模块 status:in-progress Someone or AI is working on it | 人工或 AI 正在处理 labels Nov 11, 2026
@Memtensor-AI

Memtensor-AI commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator

🤖 Open Code Review

Target: PR #2616
Task: b81b4299e3e95d49
Base: dev-v2.0.37
Head: feat/opengauss-backend-v2.0.37
Head SHA: 9362d28b4d57a328ca114d6398f02a0345459c67

🔍 OpenCodeReview found 14 issue(s) in this PR.

⚠️ Review warnings (16)

  • semantic groups split by file count and complete diff byte size; all selected files remain in coverage
  • bounded analysis finalized with explicit task_done after reviewing all group files
  • bounded analysis finalized with explicit task_done after reviewing all group files
  • bounded analysis finalized with explicit task_done after reviewing all group files
  • bounded analysis finalized with explicit task_done after reviewing all group files
  • bounded analysis finalized with explicit task_done after reviewing all group files
  • bounded analysis finalized with explicit task_done after reviewing all group files
  • bounded analysis finalized with explicit task_done after reviewing all group files
  • bounded analysis finalized with explicit task_done after reviewing all group files
  • bounded analysis finalized with explicit task_done after reviewing all group files
  • … 6 additional warning(s) omitted.

1. src/memos/api/config.py (L965)

The new helper advertises user_id: str | None, but several dispatched getters cannot handle None: get_neo4j_community_config/get_neo4j_shared_config/get_noshared_neo4j_config (and get_polardb_config only guards it) call user_id.replace('-', '') unguarded. So get_graph_db_config(None) with the default neo4j-community backend raises AttributeError: 'NoneType' object has no attribute 'replace' instead of a clear configuration error. This matters because the refactored build_graph_db_config also accepts str | None and forwards the value here, and tests already call it with None. Either normalize None into a concrete fallback (matching get_opengauss_config's None default) or reject None explicitly with a descriptive error.

💡 Suggested Change

Before:

        return {"backend": backend, "config": getters[backend](user_id=user_id)}

After:

        if user_id is None:
            user_id = "default"
        return {"backend": backend, "config": getters[backend](user_id=user_id)}

2. src/memos/api/handlers/add_handler.py (L108-L109)

The try block wraps client-input handling, not just the feedback write: _check_messages(messages) (pydantic ValidationError) and max(i for ... if d["role"] == "user") (ValueError when no user-role message is present) both raise on malformed requests. Converting all of those into HTTPException(500, "Feedback processing failed") reports invalid client input as a server error, so callers cannot distinguish a bad request from a real backend failure. Consider narrowing the try to cube_view.feedback_memories(...) (or mapping validation errors to 4xx) while keeping the 500 for genuine processing failures.


3. src/memos/api/handlers/memory_handler.py (L557-L558)

GetMemoryDashboardRequest.all_cubes is documented as "omitted/null or false selects one Cube", yet this check rejects the request whenever all_cubes is not None, i.e. an explicit all_cubes=false is treated as an unsupported "explicit Cube range" on non-openGauss backends. Since false is just the default single-Cube selection, it should not require openGauss support. Only all_cubes is True (or an actual exclusion) needs to be rejected here.

💡 Suggested Change

Before:

        if get_mem_req.all_cubes is not None or get_mem_req.exclude_cube_id is not None:
            raise ValueError("This graph backend does not support explicit Cube ranges")

After:

        if get_mem_req.all_cubes is True or get_mem_req.exclude_cube_id is not None:
            raise ValueError("This graph backend does not support explicit Cube ranges")

4. src/memos/graph_dbs/opengauss.py (L1599-L1600)

get_structure_optimization_candidates matches status with _build_equal_condition(["status"], "activated"), which only matches rows where the status key is explicitly present and set to "activated". This backend treats a missing status as activated everywhere else (_filter_status uses CASE ... ELSE '"activated"', get_subgraph uses .get("status", "activated"), get_neighbors_by_tag likewise), and nodes without status can exist (see get_grouped_counts output containing {"status": None}). Such nodes are therefore silently excluded from the Reorganizer's candidate set and never get structured. Use the same default-activated predicate here.

💡 Suggested Change

Before:

                self._build_equal_condition(["memory_type"], scope, prefix="memos_type"),
                self._build_equal_condition(["status"], "activated", prefix="memos_status"),

After:

                self._build_equal_condition(["memory_type"], scope, prefix="memos_type"),
                self._filter_status("activated"),

5. src/memos/mem_scheduler/base_scheduler.py (L516)

The borrowed-cube feedback path constructs SimpleMemFeedback without pref_feedback=True, while both other construction sites (init_components() and component_init.py) explicitly pass it. SimpleMemFeedback.__init__ defaults pref_feedback=False, so preference feedback is silently disabled whenever a cube is borrowed (mem_cube set via init_mem_cube without an explicit feedback server). Add pref_feedback=True for consistency.

💡 Suggested Change

Before:

        return SimpleMemFeedback(**dependencies)

After:

        dependencies["pref_feedback"] = True
        return SimpleMemFeedback(**dependencies)

6. src/memos/mem_scheduler/base_scheduler.py (L376)

The new close sequence releases RabbitMQ, the dispatcher monitor, consumers, the dispatcher and self.components, but never releases the scheduler-owned SchedulerGeneralMonitor (self.monitor) or the Redis module. SchedulerGeneralMonitor.close() exists to close the per-user query/working/activation-memory DB managers and has no other caller, and RedisSchedulerModule.redis_close() is likewise never called (while auto_initialize_redis() can even spawn a local redis-server). These resources leak on shutdown. Add guarded releases, e.g. self.monitor.close() and, when the scheduler owns the connection, self.redis_close().


7. src/memos/mem_scheduler/base_mixins/queue_ops.py (L304)

After the join(timeout=5.0) above times out, this branch keeps the still-alive _consumer_thread reference. A later BaseScheduler.start_consumer() clears _stop_event and then start_consumer() unconditionally does self._consumer_thread = ContextThread(...), so the old consumer (which observes both _running=True and a cleared stop event) resumes alongside the new one, producing two consumers and duplicate processing. Either treat a still-alive thread as an error before allowing restart, or check _consumer_thread.is_alive() in start_consumer/avoid clearing the stop event while the old thread is alive.


8. src/memos/mem_scheduler/base_mixins/queue_ops.py (L290-L291)

With BaseSchedulerConfig.scheduler_startup_mode now typed as Literal["thread"], scheduler_startup_mode can never be STARTUP_BY_PROCESS (config .get reads the validated field, and DEFAULT_STARTUP_MODE is "thread"). This raise ConfigurationError(...) branch and the STARTUP_BY_PROCESS/_consumer_process handling in stop_consumer and _join_consumers are unreachable. Remove the process-mode code or keep a single validation at config level.


9. src/memos/mem_scheduler/base_scheduler.py (L370-L372)

This block duplicates the three statements just above (self._running = False, self._stop_event.set(), and dispatcher_monitor.begin_close()) already executed before acquiring _initialization_lock. The duplication adds no behavior and makes it unclear which reset is authoritative; keep only the post-lock refresh that is actually needed after an in-flight initialization.


10. src/memos/mem_scheduler/task_schedule_modules/handlers/feedback_handler.py (L31-L32)

Removing the per-message try/except means a single invalid message aborts the whole batch: process_single_feedback now raises ValueError for non-dict/invalid-JSON content, which BaseSchedulerHandler.process_grouped_messages re-raises, so the loop stops and the dispatcher marks the task failed. Because the dispatcher acks every message of the batch in _create_task_wrapper's finally (even on failure, see dispatcher.py:281-297), the feedback messages that follow the bad one are acknowledged and dropped permanently. Previously each message was isolated. Consider processing all messages, collecting the first/aggregated error, and raising only after the loop so valid feedback in the same batch is still applied while the failure is still surfaced to the dispatcher.


11. src/memos/configs/mem_scheduler.py (L32-L35)

The description contradicts the field itself: the field only accepts "thread", yet the description talks about "independent process workers inside the child". Since this text is surfaced in generated API docs, users will be misled about what the mode does. Please describe the actual behavior (scheduler runs its consumer in a thread inside the current process) and, ideally, why process startup is no longer allowed.

💡 Suggested Change

Before:

    scheduler_startup_mode: Literal["thread"] = Field(
        default="thread",
        description="Create independent process workers inside the child; runtime resources cannot be inherited.",
    )

After:

    scheduler_startup_mode: Literal["thread"] = Field(
        default="thread",
        description="Startup mode for the scheduler consumer; only in-process thread startup is supported.",
    )

12. src/memos/mem_cube/general.py (L58-L60)

The docstring promises that memories "subsequently replaced" are also closed, but _owned_memories is only populated inside __init__; the text_mem/act_mem/para_mem/pref_mem setters assign _xxx_mem without appending to _owned_memories and without closing the previous instance. So a memory injected or swapped in after construction is never closed by close(), and the instance it replaced leaks. Either register/replace ownership in the setters or drop the claim from the docstring so the ownership contract matches the implementation.


13. src/memos/mem_scheduler/memory_manage_modules/enhancement_pipeline.py (L200)

The loop index from enumerate is never used in this comprehension; it is dead code introduced with this line.

💡 Suggested Change

Before:

            text_memories = "\n".join([f"- {mem}" for i, mem in enumerate(memories)])

After:

            text_memories = "\n".join([f"- {mem}" for mem in memories])

14. src/memos/memories/textual/tree.py (L544-L545)

This makes a missing file a hard failure (the previous implementation logged a warning and returned). That is fine for TreeTextMemory used standalone, but GeneralMemCube.load() calls load() for every configured memory type, and GeneralMemCube.dump(memory_types=[...]) lets a cube be persisted with only a subset of the files. Restoring such a partial cube (or an older cube directory that never had a pref_mem file) now aborts init_from_dir() with MemoryError, whereas it previously succeeded. All sibling implementations (textual/general.py, naive.py, preference.py) still treat "file not found" as a no-op, so the cube-level behaviour is also inconsistent. Please either keep FileNotFoundError tolerant at the cube level (e.g. only raise for corrupt content), or make the other text-memory backends strict as well so the contract is uniform.

Generated by cloud-assistant via Open Code Review.

@Memtensor-AI

Copy link
Copy Markdown
Collaborator

⚠️ Automated Test Results: ENV ISSUE

The test environment encountered an issue that requires manual attention.

Details: Executor error: unsupported_lock/profile: changed poetry.lock requires its lock installer adapter
Branch: feat/opengauss-backend-v2.0.37

Tested source: 1b3218395388d3a7e473af2f045aab38e4214020
Tested base: 3a16e5fe3048a209f722806f4123fa2e533588fd
Tested commit: 1b3218395388d3a7e473af2f045aab38e4214020
These results apply only to this immutable source/base snapshot.

@Memtensor-AI

Copy link
Copy Markdown
Collaborator

⚠️ Automated Test Results: ENV ISSUE

The test environment encountered an issue that requires manual attention.

Details: Required runtime dependency is unavailable. Automated validation remains blocked.
[tests/graph_dbs/test_opengauss_candidates_consumers.py] collection_dependency_skipped: ('/data/test-workspaces/b81b4299e3e95d49/repo/tests/graph_dbs/test_opengauss_integration.py', 25, "Skipped: could not import 'psycopg2': No module named 'psycopg2'")

[tests/graph_dbs/test_opengauss_candidates_integration.py] collection_dependency_skipped: ('/data/test-workspaces/b81b4299e3e95d49/repo/tests/graph_dbs/test_opengauss_integration.py', 25, "Skipped: could not import 'psycopg2': No module named 'psycopg2'")

[tests/graph_dbs/test_opengauss_capacity_consumers.py] collection_dependency_skipped: ('/data/test-workspaces/b81b4299e3e95d49/repo/tests/graph_dbs/test_opengauss_integration.py', 25, "Skipped: could not import 'psycopg2': No module named 'psycopg2'")

[tests/graph_dbs/test_opengauss_capacity_integration.py] collection_dependency_skipped: ('/data/test-workspaces/b81b4299e3e95d49/repo/tests/graph_dbs/test_opengauss_integration.py', 25, "Skipped: could not import 'psycopg2': No module named 'psycopg2'")

[tests/graph_dbs/test_opengauss_consumers_integration.py] collection_dependency_skipped: ('/data/test-workspaces/b81b4299e3e95d49/repo/tests/graph_dbs/test_opengauss_integration.py', 25, "Skipped: could not import 'psycopg2': No module named 'psycopg2'") [advisory, non-gating] AI-generated tests on branch test/auto-gen-b81b4299e3e95d49-20261111183758: 348/348 passed — these do NOT affect the PR verdict; review the branch manually.
Branch: feat/opengauss-backend-v2.0.37

Tested source: 9362d28b4d57a328ca114d6398f02a0345459c67
Tested base: 3a16e5fe3048a209f722806f4123fa2e533588fd
Tested commit: 9362d28b4d57a328ca114d6398f02a0345459c67
These results apply only to this immutable source/base snapshot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:api 云服务 / FastAPI / OpenAPI / MCP area:core MOS 编排层 / 框架底座 / 跨模块问题 area:database graph_db + vector_db | 图数据库与向量数据库 area:docs 文档、示例 area:memcube GeneralMemCube / cube 生命周期 / cube 配置 area:memory 记忆存储、检索、更新、召回逻辑 area:scheduler 调度模块 status:in-progress Someone or AI is working on it | 人工或 AI 正在处理

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants