I receive the following log with no context in production no details about closed transaction

[Raynos]

Bug description

The log statement gives me no context other then a postgres transaciton was closed.

See prisma/prisma-engines#3391

Adding more context in the transaction prisma engine would really help.

How to reproduce

Expected behavior

No response

Prisma information

// Add your schema.prisma

// Add your code using Prisma Client

Environment & setup

• OS:
• Database:
• Node.js version:

Prisma Version

[janpio]

What other information would you expect?

[Raynos]

I don't know what other information is available about the database transaction, anything could be helpful.

What operation was trying to run when we found the transaction was closed.

The actual SQL source code of the transaction,

Whether its a $queryRaw or $queryRawUnsafeor$executeRaw` or a part of $transaction or $transactionCb

Whether its a method like upsert or createMany with many nested connectOrCreate and had an internal transaction as part of the ORM implementation details.

Anything that helps me figure out which part of my business logic caused a failed transaction.

[janpio]

Wouldn't that be more a thing you figure out via a try catch block around your $transaction call? Or are you looking for information which part of the transaction was the last that was executed before the error occurred?

[aqrln]

As @janpio said above, the kind of information you are interested in is something that the engine doesn't really know a lot about on this level, this would be something that's best solved on the Prisma Client side. Much of the information you are asking about should already be in the error message — is that not the case for you?

As for the engine-side state that is relevant here, the log line you get means that we can't provide information about whether the operation failed because the transaction had already been committed or rolled back, or if it had expired (and what amount of time elapsed since the start of the transaction compared to the declared transaction timeout in the latter case) because it has already been evicted from the LRU cache. You can increase the size of that cache by setting the CLOSED_TX_CACHE_SIZE environment variable to some higher value than the default 100 closed transactions.

[Raynos]

I am using the prisma error logging events ( https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#log )

With code like

basePrisma.$on('error', event => {
  perWorkerMetrics.increment('soundxyz.prisma.db-error', 1);

  // Some errors are designed to retry. Downgrade to warn
  if (event.message.includes(ERROR_WRITE_CONFLICT_RETRYABLE)) {
    moduleLogger.warn(
      {
        eventMessage: event.message,
        err: {
          message: event.message,
        },
        eventTarget: event.target,
        rawEvent: event,
      },
      'Got a retry-safe error from prisma client library',
    );
  } else if (
    event.message.includes(ERROR_CHECK_NOTIFICATION_OVERLAP_CONSTRAINT)
  ) {
    return;
  } else {
    moduleLogger.error(
      {
        eventMessage: event.message,
        err: {
          message: event.message,
        },
        eventTarget: event.target,
        rawEvent: event,
      },
      'Got an error from prisma client library',
    );
  }
});

In this context I have not instrumented every single one of the 2000 reads & writes a novel try / catch and a novel logger error.

Also the error bubbling of promises & try catch means that in my HTTP handler I also have zero context.

Since the API is promise based and error bubbling based I expect all the useful meta data to exist as fields on the error class.

[Raynos]

What I receive in production logs looks like a rust exception wrapped in a javascript error with zero extra Prisma client context.

[Raynos]

You can increase the size of that cache by setting the CLOSED_TX_CACHE_SIZE environment variable to some higher value than the default 100 closed transactions.

Please put that in the error object, that's really really useful and valuable information.

[Raynos]

Can I set that progmatically without having to set an environment variable ? as a parameter into the prisma client class ?