workflow: move to http#2331
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
There was a problem hiding this comment.
2 issues found across 2 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="apps/workflows/src/index.ts">
<violation number="1" location="apps/workflows/src/index.ts:103">
P2: Changing lowestLevel from "debug" to "warning" makes `logger.debug(...)` calls no-ops for the "workflow" category. The `logger.debug("Request completed", ...)` in index.ts and `logger.debug("Upserted monitor status", ...)` in alerting.ts will never produce output.</violation>
<violation number="2" location="apps/workflows/src/index.ts:103">
P2: Changing from "debug" to "warning" (skipping "info") suppresses all info-level operational logs from console, including cron job start/completion, alerting triggers, and incident recovery messages. Consider "info" instead to keep operational visibility while reducing debug noise.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| { | ||
| category: "workflow", | ||
| lowestLevel: "debug", | ||
| lowestLevel: "warning", |
There was a problem hiding this comment.
P2: Changing lowestLevel from "debug" to "warning" makes logger.debug(...) calls no-ops for the "workflow" category. The logger.debug("Request completed", ...) in index.ts and logger.debug("Upserted monitor status", ...) in alerting.ts will never produce output.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/workflows/src/index.ts, line 103:
<comment>Changing lowestLevel from "debug" to "warning" makes `logger.debug(...)` calls no-ops for the "workflow" category. The `logger.debug("Request completed", ...)` in index.ts and `logger.debug("Upserted monitor status", ...)` in alerting.ts will never produce output.</comment>
<file context>
@@ -100,7 +100,7 @@ await configure({
{
category: "workflow",
- lowestLevel: "debug",
+ lowestLevel: "warning",
sinks: ["console"],
},
</file context>
| { | ||
| category: "workflow", | ||
| lowestLevel: "debug", | ||
| lowestLevel: "warning", |
There was a problem hiding this comment.
P2: Changing from "debug" to "warning" (skipping "info") suppresses all info-level operational logs from console, including cron job start/completion, alerting triggers, and incident recovery messages. Consider "info" instead to keep operational visibility while reducing debug noise.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/workflows/src/index.ts, line 103:
<comment>Changing from "debug" to "warning" (skipping "info") suppresses all info-level operational logs from console, including cron job start/completion, alerting triggers, and incident recovery messages. Consider "info" instead to keep operational visibility while reducing debug noise.</comment>
<file context>
@@ -100,7 +100,7 @@ await configure({
{
category: "workflow",
- lowestLevel: "debug",
+ lowestLevel: "warning",
sinks: ["console"],
},
</file context>
| lowestLevel: "warning", | |
| lowestLevel: "info", |
Uh oh!
There was an error while loading. Please reload this page.