Skip to content

[world-postgres] Hide also "info" logs from Graphile Worker by default#1171

Merged
VaguelySerious merged 2 commits intovercel:mainfrom
rovo89:patch-1
Feb 24, 2026
Merged

[world-postgres] Hide also "info" logs from Graphile Worker by default#1171
VaguelySerious merged 2 commits intovercel:mainfrom
rovo89:patch-1

Conversation

@rovo89
Copy link
Copy Markdown
Contributor

@rovo89 rovo89 commented Feb 23, 2026

Graphile Worker is very chatty, reporting every completed task (steps and flows) with all details as info messages.

Additionally, it also reports during startup that it failed to load its crontab. Devs shouldn't see a failure message in their server logs for something that isn't even used for workflows.

Graphile Worker is very chatty, reporting every completed task (steps and flows) with all details as `info` messages.

Additionally, it also reports during startup that it failed to load its crontab. Devs shouldn't see a failure message in their server logs for something that isn't even used for workflows.

Signed-off-by: Robert Vollmer <rovo89@users.noreply.github.com>
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 23, 2026

🦋 Changeset detected

Latest commit: bd3e576

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@workflow/world-postgres Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Feb 23, 2026

@rovo89 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

@rovo89
Copy link
Copy Markdown
Contributor Author

rovo89 commented Feb 23, 2026

@VaguelySerious If you look at the latest E2E and benchmark tests, you'll see that they contain an insane amount of debug and info lines. This PR hides the info messages as well, but I assume you have DEBUG env set in the tests? Might need a different variable for these logs then...

Signed-off-by: Robert Vollmer <rovo89@users.noreply.github.com>
Copy link
Copy Markdown
Member

@VaguelySerious VaguelySerious left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Yes tests are using DEBUG=1 by default

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants