unoverse 0.1.104 → 0.1.105

package/operator/ansible/playbooks/test-connectivity.yml

@@ -167,15 +167,28 @@
     # PACKAGES_PATH any more and docker-compose.yml has no such volume, so the check could
     # only ever report 0 and tell the operator to run a command that would not fix it.
 
+    # SINCE THE SERVICES RESTARTED, NOT SINCE FIVE MINUTES AGO.
+    #
+    # A first setup necessarily boots the services before the schema exists — migrations run
+    # THROUGH the unoverse container, so there is nothing to run them in until it is up — and
+    # db-setup restarts everything afterwards. A fixed five-minute window straddles that
+    # restart and reports the pre-migration errors as if they were current: every first
+    # deploy ended with 'relation "memories" does not exist' in red, describing a state that
+    # had already been fixed two minutes earlier by this very playbook.
+    #
+    # The question is "is anything wrong NOW", so the window starts when the services did.
     - name: "[12/14] Check for errors in service logs"
       shell: |
         cd /opt/gravity
-        ERRORS=$(docker compose logs --tail=50 --since=5m 2>&1 | grep -iE 'error|fatal|panic|does not exist|ECONNREFUSED' | grep -v 'NOGROUP' | tail -10)
+        # Newest container start: everything before it belongs to a previous run.
+        SINCE=$(docker compose ps -q 2>/dev/null | xargs -r docker inspect -f '{{.State.StartedAt}}' 2>/dev/null | sort | tail -1)
+        [ -n "$SINCE" ] || SINCE=5m
+        ERRORS=$(docker compose logs --tail=50 --since="$SINCE" 2>&1 | grep -iE 'error|fatal|panic|does not exist|ECONNREFUSED' | grep -v 'NOGROUP' | tail -10)
         if [ -n "$ERRORS" ]; then
           echo "$ERRORS"
           exit 1
         else
-          echo "No recent errors"
+          echo "No errors since the services started"
         fi
       register: log_errors
       ignore_errors: yes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.104",
+  "version": "0.1.105",
   "description": "The Unoverse front door — create a Studio project, a universe, or a client app, and launch Studio.",
   "license": "SEE LICENSE IN README.md",
   "type": "module",