HAI-3593 Run attachment fixes asynchronically#1147
Merged
umeetiusbaar merged 1 commit intodevfrom Oct 21, 2025
Merged
Conversation
Test Results 422 files ±0 1 errors 421 suites ±0 2m 54s ⏱️ +3s For more details on these parsing errors, see this check. Results for commit cf099aa. ± Comparison against base commit a12d85d. |
|
HAITATON-HANKE-SERVICE branch is deployed to platta: https://haitaton-hanke-service-pr1147.dev.hel.ninja 🚀🚀🚀 |
|
umeetiusbaar
deleted the
HAI-3593/fix-startup-crash-when-fixing-attachment-filenames
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Run attachment fixes asynchronically in order to prevent timeouts in startup due to large number of attachments and pod health probes.
Jira Issue: https://helsinkisolutionoffice.atlassian.net/browse/HAI-3593
Type of change
Instructions for testing
Application starts and logs attachment fix process
Checklist:
or other location:
Other relevant info
Please describe here if there is e.g. some requirements for this change or
other info that the tester/user needs to know.