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

fix(timeout): Increase timeouts (DEV-536) #2005

Merged
merged 5 commits into from Feb 21, 2022
Merged

Conversation

irinaschubert
Copy link
Collaborator

@irinaschubert irinaschubert commented Feb 17, 2022

resolves DEV-536

@irinaschubert irinaschubert self-assigned this Feb 18, 2022
@irinaschubert irinaschubert marked this pull request as ready for review Feb 18, 2022
@irinaschubert irinaschubert requested a review from subotic as a code owner Feb 18, 2022
@sonarcloud
Copy link

@sonarcloud sonarcloud bot commented Feb 18, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

mpro7
mpro7 approved these changes Feb 18, 2022
Copy link
Collaborator

@mpro7 mpro7 left a comment

IMO these changes should be reverted once the data are in the place.

Copy link
Collaborator

@BalduinLandolt BalduinLandolt left a comment

I still think it's an anti-pattern to have a config that needs to be changed in the repo and only takes effect after doing a release... but for now, that's what we have, so the PR is ok

@irinaschubert irinaschubert merged commit f1f8005 into main Feb 21, 2022
14 checks passed
@irinaschubert irinaschubert deleted the wip/DEV-536-increase-timeouts branch Feb 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants