You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To Reproduce
Steps to reproduce the behavior:
Enter the http://localhost:3000/shop-api screen and prepare 4 mutations that log in, insert, get and remove. Run these mutations one after another by pressing the play button. Vendure Server will crash.
Expected behavior
Vendure Server should not crash due to Postgresql in consecutive queries.
Environment (please complete the following information):
@vendure/core version: 2.2.4
Nodejs version v18.20.0
Database (mysql/postgres etc): postgresql
The text was updated successfully, but these errors were encountered:
The solution should not be to remove the @Transaction() decorator, since we do generally want mutations to run inside transactions. I'm not sure how it is that running the mutations one after the other causes the issue you reported. I'll see if I can reproduce.
If you run the addToWhishlist mutation twice then the server crashes with the given error.
in simple words
If the variant is already in the wishlist and you run the mutation again (trying to add a variant to wishlist when that variant is already in the wishlist) the server crashes
I developed the Wishlist plugin located at https://docs.vendure.io/guides/developer-guide/plugins/. When I successively click on the Login, AddtoWishlist, GetWishlist, RemoveFromWishlist mutations from the http://localhost:3000/shop-api screen, Vendure Server crashes and I get the error in the screenshot below.
To Reproduce
Steps to reproduce the behavior:
Enter the http://localhost:3000/shop-api screen and prepare 4 mutations that log in, insert, get and remove. Run these mutations one after another by pressing the play button. Vendure Server will crash.
Expected behavior
Vendure Server should not crash due to Postgresql in consecutive queries.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: