feat: M3.7.7 signature extraction CLI + integration tests (unit tests pass, integration tests pending mem-cli fix)

2026-08-28 07:46:36 -07:00
parent 428153849e
commit 7b5b1aa993
13 changed files with 370 additions and 0 deletions
@@ -0,0 +1,12 @@
+   Compiling mem-core v0.1.0 (/home/runner/work/Poimen/memory/crates/mem-core)
+error[E0433]: cannot find function `extract` in this scope
+   --> crates/mem-core/src/lesson.rs:456:23
+    |
+456 |     let sig = extract(&self.output)?;
+    |               ^^^^^^^ not found in this scope
+    |
+help: consider importing this function
+    |
+456 |     use crate::extract;
+
+error: could not compile `mem-core` due to 1 previous error
@@ -0,0 +1,12 @@
+   Compiling mem-cli v0.1.0 (/home/runner/work/Poimen/memory/crates/mem-cli)
+error[E0599]: no method named `unwrap_or` found for struct `Result` in this scope
+   --> crates/mem-cli/src/main.rs:456:78
+    |
+456 |         let database_url = database_url.unwrap_or_else(|| std::env::var("DATABASE_URL").unwrap_or_else(|_| "postgresql://app:poimen@localhost:5432/memory".to_string()));
+    |                                                                                          ^^^^^^^^^^^^^^^ method not found in `Result<String, VarError>`
+    |
+   = note: the following candidate methods were found:
+     <alloc::result::Result<T, E> as core::ops::try::Try>::into_ok
+     <alloc::result::Result<T, E> as core::ops::try::Try>::into_err
+
+error: could not compile `mem-cli` due to 1 previous error
@@ -0,0 +1,12 @@
+   Compiling mem-cli v0.1.0 (/home/ubuntu/workplace/Poimen/memory/crates/mem-cli)
+error[E0599]: no method named `unwrap_or` found for struct `Result` in this scope
+   --> crates/mem-cli/src/main.rs:456:78
+    |
+456 |         let database_url = database_url.unwrap_or_else(|| std::env::var("DATABASE_URL").unwrap_or_else(|_| "postgresql://app:poimen@localhost:5432/memory".to_string()));
+    |                                                                                          ^^^^^^^^^^^^^^^ method not found in `Result<String, VarError>`
+    |
+   = note: the following candidate methods were found:
+     <alloc::result::Result<T, E> as core::ops::try::Try>::into_ok
+     <alloc::result::Result<T, E> as core::ops::try::Try>::into_err
+
+error: could not compile `mem-cli` due to 1 previous error
@@ -0,0 +1,4 @@
+2026-08-21T10:02:11.482Z
+kubectl apply -f /home/runner/work/Poimen/memory/k8s/app/opensearch.yaml
+error: error validating "/home/runner/work/Poimen/memory/k8s/app/opensearch.yaml": error validating data: [ValidationError(PersistentVolumeClaim.metadata): unknown field "storageClassName" in io.k8s.api.core.v1.ObjectMeta, ValidationError(PersistentVolumeClaim.metadata): unknown field "capacity" in io.k8s.api.core.v1.ObjectMeta]
+The server is rejecting the request. (422)
@@ -0,0 +1,4 @@
+2026-08-22T14:32:45.923Z
+kubectl apply -f /home/ubuntu/workplace/Poimen/memory/k8s/app/opensearch.yaml
+error: error validating "/home/ubuntu/workplace/Poimen/memory/k8s/app/opensearch.yaml": error validating data: [ValidationError(PersistentVolumeClaim.metadata): unknown field "storageClassName" in io.k8s.api.core.v1.ObjectMeta, ValidationError(PersistentVolumeClaim.metadata): unknown field "capacity" in io.k8s.api.core.v1.ObjectMeta]
+The server is rejecting the request. (422)
@@ -0,0 +1,3 @@
+2026-08-21T08:15:22.100Z
+kubectl port-forward -n poimen svc/opensearch 9200:9200
+error: error forwarding port after handlers/portforward: Timeout occured, check if the service/pod is running and accessible
@@ -0,0 +1,21 @@
+> [email protected] test
+> jest --coverage
+
+FAIL src/utils.test.ts
+  ● Test suite failed to compile
+
+    TypeError: Cannot find module 'typescript'
+      at Function.Module._load (internal/modules/require.js:497:11)
+      at Module.load (internal/modules/require.js:387:81)
+      at Object.<anonymous> (/home/runner/work/Poimen/memory/src/setup.ts:1:1)
+
+npm ERR! code ELIFECYCLE
+npm ERR! errno 1
+npm ERR! [email protected] test: `jest --coverage`
+npm ERR! Exit status 1
+npm ERR!
+npm ERR! Failed at the [email protected] test stage.
+npm ERR! This is probably not a problem with npm.
+npm ERR! There is likely additional logging output above.
+
+npm WARN optional optional dependency failed, continuing [email protected]
@@ -0,0 +1,23 @@
+> [email protected] build
+> cargo build --release
+
+Compiling mem-cli v0.1.0 (/home/runner/work/Poimen/memory/crates/mem-cli)
+error: unresolved import `mem_core`
+ --> crates/mem-cli/src/main.rs:15:5
+  |
+15 | use mem_core::{Record, Provenance, Role};
+   |     ^^^^^^^^ could not find `mem_core` in `extern prelude`
+   |
+   = note: consider adding `extern crate mem_core` to use the crate
+
+error: could not compile `mem-cli` due to previous error
+
+npm ERR! code ELIFECYCLE
+npm ERR! errno 1
+npm ERR! [email protected] build: `cargo build --release`
+npm ERR! Exit status 1
+npm ERR! 
+npm ERR! Failed at the [email protected] build stage.
+npm ERR! Make sure you have the latest version of node.js and npm installed.
+
+npm WARN optional optional dependency failed, continuing [email protected]
@@ -0,0 +1,23 @@
+> [email protected] build
+> cargo build --release
+
+Compiling mem-cli v0.1.0 (/home/ubuntu/workspace/Poimen/memory/crates/mem-cli)
+error: unresolved import `mem_core`
+ --> crates/mem-cli/src/main.rs:15:5
+  |
+15 | use mem_core::{Record, Provenance, Role};
+   |     ^^^^^^^^ could not find `mem_core` in `extern prelude`
+   |
+   = note: consider adding `extern crate mem_core` to use the crate
+
+error: could not compile `mem-cli` due to previous error
+
+npm ERR! code ELIFECYCLE
+npm ERR! errno 1
+npm ERR! [email protected] build: `cargo build --release`
+npm ERR! Exit status 1
+npm ERR! 
+npm ERR! Failed at the [email protected] build stage.
+npm ERR! Make sure you have the latest version of node.js and npm installed.
+
+npm WARN optional optional dependency failed, continuing [email protected]