Repository navigation
Conversation
|
Hy @jason810496 |
potiuk
added
the
closed because of open PR limit
|
Hello @Kunal8954 - thank you for your contributions to Apache Airflow! The Airflow community has introduced a limit of 5 open pull requests at a time for contributors without write access to the repository. You currently have 8 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:
These pull requests stay open because maintainers are already engaged in them - they count towards your limit:
This is not a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are. What we ask you to do is to make your first prioritization decision: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack. Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst. Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting |
Add a callback-based
Stats.observable_gauge(name, callback, description=...)API to the Stats observability interface. Instead of a caller pushing a value at a moment in time (the existingStats.gauge), a callback is registered once and the metrics SDK invokes it on its own export/collection cadence, guaranteeing a fresh "current state" sample every collection cycle.Implemented in the OpenTelemetry backend (
SafeOtelLogger) viacreate_observable_gauge: the user callback receives the collection timeout and yields(value, attributes)tuples, which are converted to OTelObservationobjects internally. Callback exceptions are handled by the OTel SDK (logged, do not crash collection).Stats.gaugeand all other existing Stats methods are unchanged and fully backward compatible.On non-OTel backends (StatsD, Datadog) and when no backend is configured,
observable_gaugeis a silent no-op — those backends do not support observable instruments. The prek metrics-registry hook is updated to classifyobservable_gaugeas typegauge.Validation:
Statsclass, description passthrough, no-op behavior) — all passgit diff --check: cleancloses: #72885
Was generative AI tooling used to co-author this PR?
Generated-by: big-pickle following the guidelines