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

ci: provide arm64 image #6803

Conversation

aldy505
Copy link
Contributor

@aldy505 aldy505 commented Jan 22, 2025

Effort for getsentry/self-hosted#1585

This PR changed the DockerHub publishing workflow. We don't depend on the GCB anymore. Rather, we depend on GHCR now.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

AbhiPrasad and others added 6 commits January 21, 2025 12:52
ref getsentry/team-sdks#116

This PR implements a new client discard reason for `buffer_overflow`.
This will be used to track when the internal breadcrumbs buffer
overflows for the new logs product that we are working on. This is
documented in develop here:
getsentry/sentry-docs#12395

I also went ahead and added code comments that describes what all the
different client discard reasons mean. This is done in commit
b3dcd67, while the actual change to add
the `buffer_overflow` discard reason was added in
dd25dde.

Note: The reason we have `buffer_overflow` as a separate item to
`queue_overflow` is that in the future when we send log items in
envelopes we'll increment `queue_overflow` for the transport queue. We
want to differentiate between the transport queue and the internal
buffer explicitly.

---------

Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
Fixes SNUBA-6R7

Wish there was a way for snuba to auto generate a schema based on the
[kafka schema
type.](https://github.com/getsentry/sentry-kafka-schemas/blob/main/schemas/snuba-uptime-results.v1.schema.json)
missed this when typing the message.
@aldy505 aldy505 requested a review from a team as a code owner January 22, 2025 01:20
@aldy505
Copy link
Contributor Author

aldy505 commented Jan 22, 2025

Just saw #6800 after opened this PR, let's just hold this for a while until that got merged.

@aldy505 aldy505 changed the base branch from master to fix/snuba-race-conditions January 22, 2025 08:30
@aldy505 aldy505 requested review from a team as code owners January 22, 2025 08:30
@aldy505
Copy link
Contributor Author

aldy505 commented Jan 22, 2025

This is borked :/

Closing the PR until #6800 got merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants