fix: correct log-tail server resolution, drop unrelated Networks gating

- Log tail for failed-deployment classification now checks the app's
  current buildServer before falling back to its server, matching the
  buildServerId-then-serverId precedence used everywhere else in the
  codebase (application.ts, drop.ts, directory.ts, patch-repo.ts).
- Removes a stale !isCloud gate on the Networks tab that this branch
  had reintroduced from before Mauricio removed it in daba2d7fb
  (Networks is intentionally shown in cloud now) — unrelated to this
  PR's scope, docker.tsx's Networks tab/content now matches canary.
This commit is contained in:
Narciso
2026-08-13 12:03:38 -04:00
parent c741ff36c0
commit 95b1afc2c2
2 changed files with 7 additions and 11 deletions
@@ -1096,8 +1096,10 @@ export const findFailedDeploymentsCentralized = async (
failed,
LOG_TAIL_CONCURRENCY,
async (deployment) => {
// Same buildServerId-then-serverId precedence used app-wide (application.ts, drop.ts, etc.)
const serverId =
deployment.buildServer?.serverId ||
deployment.application?.buildServer?.serverId ||
deployment.server?.serverId ||
deployment.application?.server?.serverId ||
deployment.compose?.server?.serverId ||