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

Release 2.4.0 #434

Merged
merged 30 commits into from
Oct 10, 2023
Merged

Release 2.4.0 #434

merged 30 commits into from
Oct 10, 2023

Conversation

mpgxvii
Copy link
Member

@mpgxvii mpgxvii commented Jun 23, 2023

mpgxvii and others added 13 commits March 24, 2023 11:39
- Use GithubClient inside GithubProtocolFetcherStrategy to improve readability and remove deplication.
- Use GithubService as a proxy for GithubClient in endpoint. This caches any values from the questionnaire.
- Created FunctionCache that caches the result of a throwing function for a given amount of time.
- Added more checks on the request being performed: number of bytes for content length, more strict URL validation (only https://api.github.com is allowed now instead of for example http://api.github.com.my.domain.
Cache questionnaires and standardize github client access
@mpgxvii mpgxvii mentioned this pull request Jul 12, 2023
blootsvoets and others added 8 commits September 20, 2023 09:54
HTTP/1.1 does less connection sharing, causing the requests to go
through without connection resets.
In the previous handling of events, event were handled
immediately during the transaction, in the same thread. This caused a
lot of delays, blocking the database threads. The EventListener annotations are replaced by
TransactionalEventListener to ensure that the previous transaction has
been committed before processing the event. It explicitly creates
a new transaction to avoid overlapping transactions. Finally, it enables
async processing to avoid the existing transaction threads being blocked.
Remove unused spring-data-rest dependency
Copy link
Member

@yatharthranjan yatharthranjan left a comment

Choose a reason for hiding this comment

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

LGTM, is this ready for release @mpgxvii ?

@mpgxvii
Copy link
Member Author

mpgxvii commented Oct 9, 2023

LGTM, is this ready for release @mpgxvii ?

@yatharthranjan Yes, but I want to include some changes before releasing: #443

@mpgxvii mpgxvii merged commit ae21553 into master Oct 10, 2023
6 checks passed
@mpgxvii mpgxvii deleted the release-2.4.0 branch October 10, 2023 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants