Bump docker compose version in CI #2980
Merged
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found Additional details and impacted files@@ Coverage Diff @@
## master #2980 +/- ##
=======================================
Coverage 99.01% 99.01%
=======================================
Files 3 3
Lines 203 203
=======================================
Hits 201 201
Misses 2 2 ☔ View full report in Codecov by Sentry. |
azaslavsky
reviewed
Apr 19, 2024
azaslavsky
approved these changes
Apr 19, 2024
hubertdeng123
deleted the
hubertdeng123/upgrade-docker-compose-CI-version
branch
ngudbhav
added a commit
to KingsGambitLab/self-hosted-sentry
that referenced
this pull request
Apr 20, 2024
* feat: provide csrf settings information for sentry config (getsentry#2762) * feat: provide csrf settings information for sentry config * chore: trim trailing whitespace * build(deps): bump actions/setup-python from 4 to 5 (getsentry#2644) Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v4...v5) --- updated-dependencies: - dependency-name: actions/setup-python dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Hubert Deng <hubert.deng@sentry.io> * Fix groupedmessage indexing error (getsentry#2777) * fix groupedmessage indexing error * Check memcached backend in Django (getsentry#2778) Bail if using old memcached backend * release: 24.1.2 * build: Set master version to nightly #skip-changelog * fix: DB migration script (getsentry#2779) * use different approach to wait for postgres server * Tweak postgres indexing fix (getsentry#2792) * tweak postgres indexing fix * add exists constraint * build(deps): bump pre-commit/action from 3.0.0 to 3.0.1 (getsentry#2788) Bumps [pre-commit/action](https://github.com/pre-commit/action) from 3.0.0 to 3.0.1. - [Release notes](https://github.com/pre-commit/action/releases) - [Commits](pre-commit/action@v3.0.0...v3.0.1) --- updated-dependencies: - dependency-name: pre-commit/action dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * Bump nginx version (getsentry#2797) bump nginx version * release: 24.2.0 * build: Set master version to nightly #skip-changelog * use rust consumers in self-hosted * revert changes in 3067683 * chore: Use django ORM to perform sql commands (getsentry#2827) * use django orm * chore: provide clearer csrf url example (getsentry#2833) * Upgrade to FSL-1.1 (getsentry#2835) * simplify if for open-ai-suggestion (getsentry#2732) * simplify if for open-ai-suggestion * Add snuba rust consumers (getsentry#2831) * add snuba rust consumers * Enable proxy buffering in nginx (getsentry#2844) Enable proxy buffering Setting the proxy_buffering directive to “off” is a common mistake because it can cause performance issues and unexpected behavior in NGINX. When proxy buffering is disabled, NGINX receives a response from the proxied server and immediately sends it to the client without storing it in a buffer. This can cause problems if the response is large or if the connection between NGINX and the client is slow, because it can result in increased memory usage and potentially lead to request timeouts. To avoid this mistake, it is recommended to always enable proxy buffering in NGINX. * deps: bump maxmind/geoipupdate to 6.1.0 (getsentry#2859) https://github.com/maxmind/geoipupdate/releases/tag/v6.1.0 * increase postgres max_connections above 100 connections (getsentry#2740) * use default value and env for postgres max_connections * Integration test improvements (getsentry#2858) * integration test improvements * feat(spans): Ingest spans (getsentry#2861) * release: 24.3.0 * build: Set master version to nightly #skip-changelog * Remove duplicate feature flags (getsentry#2899) * feat: run outcomes-billing consumer (getsentry#2909) * Integration tests in python (getsentry#2892) * integration tests in python * Fix defunct java processes (getsentry#2914) revert kafka healthcheck change * Port backup tests to python (getsentry#2907) * port backup tests to python * feat(clickhouse): Added max_suspicious_broken_parts to the config.xml (getsentry#2853) * feat(clickhouse): Added max_suspicious_broken_parts to the config.xml * refactor(clickhouse): Set default max_suspicious_bronken_parts and Issue reference --------- Co-authored-by: Hubert Deng <hubert.deng@sentry.io> * Write Customization tests in python (getsentry#2918) * port everything integration test related to python * Bump ubuntu version for tests (getsentry#2923) * bump ubuntu version used for testing * get rid of codecov cli dependency * fix(spans): Adds organizations:standalone-span-ingestion flag to default config (getsentry#2936) Adds organizations:standalone-span-ingestion flag to default config * feat: adds group attributes consumer (getsentry#2927) adds group attributes consumer * Use python for e2e tests (getsentry#2953) * bump e2e action commit sha * release: 24.4.0 * build: Set master version to nightly #skip-changelog * Port last integration tests to python (getsentry#2966) * port custom ca cert test to python * Add example to docker compose version in problem report (getsentry#2959) * Use docker compose exec to create additional kafka topics (getsentry#2904) * chore(deps): bump memcached and redis to latest patch versions (getsentry#2973) * release: 24.4.1 * build: Set master version to nightly #skip-changelog * Add workstation configuration (getsentry#2968) * Add workstation configuration These are prebuilt docker images for spinning up a local self-hosted image on the Google Cloud Workstation project. While primarily intended for internal development at Sentry, in theory these can be used by anyone with GCWS project to create a fresh workstation for developing self-hosted via a remote VSCode connection. Users who have GCWS properly configured will be able to use the forthcoming `workstations ...` command in the `sentry` dev CLI to create, manage, and destroy one-off or long-lived workstations in either the pre-install or post-install configuration. Note that the `sentry workstations ...` CLI has not yet landed in the `sentry` repo - those changes are coming soon! Issue: getsentry/team-ospo#240 * Fix shfmt complaints * Upgrade postgres to 14.11 (getsentry#2975) chore(deps): bump postgres to latest 14 alpine version * Bump docker compose version in CI (getsentry#2980) * only rerun tests on v2.0.1 * change from http error to request error * use 3 retries like before * fix: backport changes --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Reinaldy Rafli <aldy505@proton.me> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Hubert Deng <hubert.deng@sentry.io> Co-authored-by: Chad Whitacre <chadwhitacre@sentry.io> Co-authored-by: getsentry-bot <bot@sentry.io> Co-authored-by: getsentry-bot <bot@getsentry.com> Co-authored-by: hubertdeng123 <hubertdeng123@gmail.com> Co-authored-by: Iven Schlenther <stossenhd@gmail.com> Co-authored-by: RexTim <73953915+RexTim@users.noreply.github.com> Co-authored-by: Victor <victorelec14@gmail.com> Co-authored-by: Erfan <37825504+erfantkerfan@users.noreply.github.com> Co-authored-by: Pierre Massat <pierre.massat@sentry.io> Co-authored-by: Jann Kleen <jann.kleen@gmail.com> Co-authored-by: Lyn Nagara <lyn.nagara@gmail.com> Co-authored-by: edwardgou-sentry <83961295+edwardgou-sentry@users.noreply.github.com> Co-authored-by: Stephen Cefali <scefali@sentry.io> Co-authored-by: Edgar Sanchez <edgar@sanchez.is> Co-authored-by: Steffen Zieger <me@saz.sh> Co-authored-by: Matthew T <20070360+mdtro@users.noreply.github.com> Co-authored-by: Alex Zaslavsky <azaslavsky@users.noreply.github.com>
ngudbhav
pushed a commit
to KingsGambitLab/self-hosted-sentry
that referenced
this pull request
Apr 20, 2024
* only rerun tests on v2.0.1 * change from http error to request error * use 3 retries like before
ngudbhav
pushed a commit
to KingsGambitLab/self-hosted-sentry
that referenced
this pull request
Apr 20, 2024
* only rerun tests on v2.0.1 * change from http error to request error * use 3 retries like before
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Played around trying to find a straightforward way to resolve the flaky errors we were seeing in testing. For docker compose versions v2.7.0 and v2.0.1 wasn't able to find anything substantial. Turns out the flaky errors we were seeing are resolved in later versions of docker, so for now it seems reasonable to only rerun tests for self-hosted on docker compose v2.0.1.