@oondemand/oon-core-back 0.7.20 → 0.7.22

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oondemand/oon-core-back",
-  "version": "0.7.20",
+  "version": "0.7.22",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/oondemand/oon-platform.git",

package/src/core/middlewares/error.js

@@ -75,6 +75,20 @@ const errorMiddleware = (error, req, res, next) => {
     });
   }
 
+  // Erro comum com statusCode 4xx explícito (ex.: "Token inválido ou
+  // expirado." com 401): responde com esse status em vez de virar 500, para
+  // o cliente poder voltar ao login.
+  if (Number.isInteger(error.statusCode) && error.statusCode >= 400 && error.statusCode < 500) {
+    const code = typeof error.code === "string" && error.code ? error.code : `HTTP_${error.statusCode}`;
+    const message = String(error.message || "Requisição recusada.");
+    return helpers.sendErrorResponse({
+      res,
+      statusCode: error.statusCode,
+      error: { code, message, ...(requestId ? { requestId } : {}) },
+      message,
+    });
+  }
+
   const databaseFailure = databaseError(error);
   if (databaseFailure) {
     const { statusCode, ...details } = databaseFailure;

package/src/delivery/runtime.js

@@ -209,10 +209,13 @@ spec:
     spec:
       serviceAccountName: oon-runtime
       terminationGracePeriodSeconds: ${TERMINATION_GRACE_SECONDS}
+      # DoNotSchedule: com ScheduleAnyway as 2 réplicas de Apps globais ficaram
+      # no mesmo nó. Com maxSkew 1 o pod extra do rolling update ainda cabe e,
+      # com um único nó, o desvio é zero e nada fica pendente.
       topologySpreadConstraints:
         - maxSkew: 1
           topologyKey: kubernetes.io/hostname
-          whenUnsatisfiable: ScheduleAnyway
+          whenUnsatisfiable: DoNotSchedule
           labelSelector:
             matchLabels: { app.kubernetes.io/name: ${context.appCode} }
       imagePullSecrets: [{ name: ${infra.REGISTRY_PULL_SECRET_NAME || "ghcr-oon"} }]