Skip to content

Conversation

ilidemi
Copy link
Contributor

@ilidemi ilidemi commented Oct 15, 2025

Chasing DB errors is getting ridiculous lately, adding spew logging that looks like this:

(*utils.connectionError)(0x14000e024c0)({
  message: (string) (len=25) "connection pool exhausted",
  wrapped: (*connpostgres.queryExecutionError)(0x14000e024a0)({
    query: (string) (len=33) "SELECT * FROM users WHERE id = $1",
    wrapped: (*errors.errorString)(0x140008136b0)({
      s: (string) (len=15) "network timeout"
    })
  })
})

@ilidemi ilidemi enabled auto-merge (squash) October 15, 2025 16:10
Comment on lines 466 to 469
loggerFunc(errError,
slog.String("stack", inErrWithStack),
slog.String("type", reflect.TypeOf(inErr).String()),
slog.String("spew", errSpew.Sdump(inErr)))
Copy link
Contributor

Choose a reason for hiding this comment

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

good idea 👍

@ilidemi ilidemi changed the title Classify mongo conn pool error, spew full structure for all errors Spew full structure for all flow_errors Oct 15, 2025
@ilidemi ilidemi disabled auto-merge October 16, 2025 03:13
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.

3 participants