Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Durable providers are unable to recover from errors being thrown #13953

Open
1 of 15 tasks
dberardo-com opened this issue Sep 9, 2024 · 1 comment
Open
1 of 15 tasks
Labels
needs triage This issue has not been looked into

Comments

@dberardo-com
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

the issue is described here and it is still relevant: #11664

Minimum reproduction code

check here: #11664

Steps to reproduce

No response

Expected behavior

durable provider should be decached and retried next time.

it would be nice if this is the default behavior even after the creation of the provider, i.e. in case of exceptions along its life

Package

  • I don't know. Or some 3rd-party package
  • @nestjs/common
  • @nestjs/core
  • @nestjs/microservices
  • @nestjs/platform-express
  • @nestjs/platform-fastify
  • @nestjs/platform-socket.io
  • @nestjs/platform-ws
  • @nestjs/testing
  • @nestjs/websockets
  • Other (see below)

Other package

No response

NestJS version

10.1.3

Packages versions

  "@nestjs/typeorm": "^10.0.0",

Node.js version

16

In which operating systems have you tested?

  • macOS
  • Windows
  • Linux

Other

No response

@dberardo-com dberardo-com added the needs triage This issue has not been looked into label Sep 9, 2024
@micalevisk
Copy link
Member

here's a minimum reproduction of this: https://gitlab.com/micalevisk/nestjs-issue-11664

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage This issue has not been looked into
Projects
None yet
Development

No branches or pull requests

2 participants