Skip to content

chore(PM-2539): added timeout for prisma service #2

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 28, 2025
Merged

chore(PM-2539): added timeout for prisma service #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6437ae5
fix: added timeout for prisma
hentrymartin Oct 24, 2025
5854392
fix: added timeout for prisma
hentrymartin Oct 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .circleci/config.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,7 @@ workflows:
branches:
only:
- develop
- pm-2539

# Production builds are exectuted only on tagged commits to the
# master branch.
Expand Down
5 changes: 5 additions & 0 deletions src/shared/modules/global/prisma.service.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,11 @@ export class PrismaService

constructor(private readonly prismaErrorService?: PrismaErrorService) {
super({
transactionOptions: {
timeout: process.env.GROUPS_SERVICE_PRISMA_TIMEOUT
Copy link

@github-actions github-actions bot Oct 24, 2025

Choose a reason for hiding this comment

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

[❗❗ correctness]
Consider validating the environment variable GROUPS_SERVICE_PRISMA_TIMEOUT before parsing it. If the variable is not a valid number, parseInt will return NaN, which could lead to unexpected behavior. You might want to add a check to ensure the parsed value is a valid number and falls within an acceptable range.

? parseInt(process.env.GROUPS_SERVICE_PRISMA_TIMEOUT, 10)
: 10000,
},
log: [
{ level: 'query', emit: 'event' },
{ level: 'info', emit: 'event' },
Expand Down