fix(status): separate listener programmed state from HTTPRoute Accepted condition by apkatsikas · Pull Request #9129 · envoyproxy/gateway

apkatsikas · 2026-05-31T13:47:58Z

What type of PR is this?
fix

What this PR does / why we need it:

When a route is attached to a listener that has a missing TLS certificate ref, Envoy Gateway was incorrectly setting Accepted: False with reason NoReadyListeners on the route. The ListenerSet and its listener entry both correctly remain Accepted: True in this scenario; only the listener's Programmed condition is False.

Route acceptance reflects binding validity: whether the route matches a listener by hostname, allowedRoutes, and sectionName. The Gateway API spec defines valid reasons for Accepted: False on a route (NotAllowedByListeners, NoMatchingListenerHostname, NoMatchingParent, etc.); none reference listener programmed state. There is no spec-defined route condition that represents listener readiness, and the listener's own Programmed: False is sufficient to surface the unready state.

This change:

Removes the HasReadyListener block that set Accepted: False / NoReadyListeners on routes when no listeners were programmed. Routes with a valid binding now correctly reach Accepted: True regardless of listener programmed state.
Extends the same fix to processTCPRouteParentRefs and processUDPRouteParentRefs, which had the same conflation: accepted was only set to true after IsReady() succeeded, causing valid TCPRoute/UDPRoute bindings to an unprogrammed listener to receive Accepted: False / UnsupportedValue with a misleading "Multiple routes on the same listener" message.
Updates golden file test expectations to reflect the corrected behavior. Tests that previously asserted Accepted: False now assert Accepted: True, which is the correct expected state; they continue to validate listener-level conditions which are unchanged.

Which issue(s) this PR fixes:

Fixes #9128 #9012

Release Notes: Yes

netlify · 2026-05-31T13:48:03Z

✅ Deploy Preview for cerulean-figolla-1f9435 ready!

Name	Link
🔨 Latest commit	`ec91119`
🔍 Latest deploy log	https://app.netlify.com/projects/cerulean-figolla-1f9435/deploys/6a2ac6d9a0ecb2000868e0a5
😎 Deploy Preview	https://deploy-preview-9129--cerulean-figolla-1f9435.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

chatgpt-codex-connector

💡 Codex Review

gateway/internal/gatewayapi/route.go

Line 2295 in ee64be4

metav1.ConditionTrue,

Preserve Accepted for unprogrammed TCP/UDP listeners

When the only allowed listener is unprogrammed, this shared path now records Accepted=True for every route kind, but processUDPRouteParentRefs and processTCPRouteParentRefs still leave their local accepted flag false until listener.IsReady() succeeds; they then overwrite the condition with Accepted=False / UnsupportedValue and the misleading "Multiple routes on the same ... listener" message. This means the readiness/acceptance split is only correct for HTTP/GRPC/TLS, while valid TCPRoute/UDPRoute bindings to an unprogrammed listener still report rejected with the wrong reason; either those route-specific fallbacks need to distinguish unready listeners, or this shared change should not apply to those route kinds.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

codecov · 2026-05-31T13:58:02Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.86%. Comparing base (b96a2d3) to head (ec91119).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9129      +/-   ##
==========================================
- Coverage   74.90%   74.86%   -0.04%     
==========================================
  Files         252      252              
  Lines       40797    40781      -16     
==========================================
- Hits        30559    30531      -28     
- Misses       8154     8165      +11     
- Partials     2084     2085       +1

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

apkatsikas · 2026-05-31T15:10:04Z

💡 Codex Review

gateway/internal/gatewayapi/route.go

Line 2295 in ee64be4

metav1.ConditionTrue,

Preserve Accepted for unprogrammed TCP/UDP listeners

When the only allowed listener is unprogrammed, this shared path now records Accepted=True for every route kind, but processUDPRouteParentRefs and processTCPRouteParentRefs still leave their local accepted flag false until listener.IsReady() succeeds; they then overwrite the condition with Accepted=False / UnsupportedValue and the misleading "Multiple routes on the same ... listener" message. This means the readiness/acceptance split is only correct for HTTP/GRPC/TLS, while valid TCPRoute/UDPRoute bindings to an unprogrammed listener still report rejected with the wrong reason; either those route-specific fallbacks need to distinguish unready listeners, or this shared change should not apply to those route kinds.
ℹ️ About Codex in GitHub

862efed

apkatsikas · 2026-05-31T17:22:39Z

/retest

apkatsikas · 2026-05-31T18:12:14Z

/retest

zirain · 2026-06-01T01:06:23Z

@codex review

chatgpt-codex-connector · 2026-06-01T01:08:44Z

Codex Review: Didn't find any major issues. Bravo.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

zhaohuabing · 2026-06-06T07:14:33Z

  Added support for authorization path match.

 bug fixes: |
+  Fixed HTTPRoute Accepted condition being set to False when an attached listener is not programmed due to a missing TLS certificate ref; listener programmed state is now correctly separated from route acceptance.


Nit: can we also mention other Route types that are affected by this PR?

zhaohuabing · 2026-06-06T07:17:34Z

Nit: can we remove NoReadyListeners example in site/content/en/latest/tasks/operations/egctl.md ?

zhaohuabing · 2026-06-06T07:38:49Z

@@ -63,9 +63,9 @@ tlsRoutes:
    parents:


Nit: the filename says “not attaching,” but the route status is now Accepted=True.
Can we rename the file to tlsroute-with-tls-listener-missing-mode.in(out).yaml?

zhaohuabing

LGTM, with a few non-blocking nits.

apkatsikas · 2026-06-06T12:29:27Z

Nit: can we remove NoReadyListeners example in site/content/en/latest/tasks/operations/egctl.md ?

65734cd

arkodg · 2026-06-08T01:55:45Z

    '@type': type.googleapis.com/envoy.admin.v3.RoutesConfigDump
 ```
-
-### Validating Gateway API Configuration


why is this being deleted, output will need to be revised

That example demonstrated a scenario where an HTTPRoute is Accepted: False due to NoReadyListeners, which this PR prevents from occurring. Per @zhaohuabing suggestion I removed it rather than revising it, since the example's premise no longer applies.

arkodg · 2026-06-08T01:56:42Z

ooc, as an application owner, how am I supposed to now know if the listener is working as expected, which will decide if the route works or not

apkatsikas · 2026-06-08T02:39:44Z

ooc, as an application owner, how am I supposed to now know if the listener is working as expected, which will decide if the route works or not

The listener's Programmed condition on the Gateway or ListenerSet is the right place to check listener health, imo.

arkodg · 2026-06-08T03:05:59Z

ooc, as an application owner, how am I supposed to now know if the listener is working as expected, which will decide if the route works or not

The listener's Programmed condition on the Gateway or ListenerSet is the right place to check listener health, imo.

an app dev might not have access to a gateway namespace

apkatsikas · 2026-06-08T03:27:57Z

ooc, as an application owner, how am I supposed to now know if the listener is working as expected, which will decide if the route works or not

The listener's Programmed condition on the Gateway or ListenerSet is the right place to check listener health, imo.

an app dev might not have access to a gateway namespace

Yes, that is true and a good point. I put a query out to the sig-network-gateway-api channel on the Kubernetes Slack.

…ed condition Remove the NoReadyListeners block that set Accepted: False on routes when no listeners were programmed. Route acceptance reflects binding validity; listener programmed state is already tracked by the listener's own conditions. Signed-off-by: apkatsikas <[email protected]>

…e Accepted condition Routes with a valid binding to an unprogrammed listener now correctly reach Accepted=True regardless of listener readiness. Moves accepted=true and IncrementAttachedRoutes before the IsReady check so the Accepted condition reflects binding validity only, consistent with the HTTPRoute fix and the Gateway API spec. Signed-off-by: apkatsikas <[email protected]>

…nflicted listener Signed-off-by: apkatsikas <[email protected]>

Signed-off-by: apkatsikas <[email protected]>

…dition fix release note Signed-off-by: apkatsikas <[email protected]>

Signed-off-by: apkatsikas <[email protected]>

apkatsikas · 2026-06-11T12:39:47Z

ooc, as an application owner, how am I supposed to now know if the listener is working as expected, which will decide if the route works or not

The listener's Programmed condition on the Gateway or ListenerSet is the right place to check listener health, imo.

an app dev might not have access to a gateway namespace

Yes, that is true and a good point. I put a query out to the sig-network-gateway-api channel on the Kubernetes Slack.

Response from Kubernetes team/Nick Young:

I personally always expected app devs to have read access to Gateway, yes
There should be nothing in the gateway that is secret
Mechanically, I expected that app devs would be granted RBAC to read Gateways across either all namespaces, or at least dedicated infra namespaces where the relevant Gateways are provisioned

@arkodg any remaining concerns on this PR?

Signed-off-by: Arko Dasgupta <[email protected]>

arkodg · 2026-06-11T14:29:49Z

thanks for getting this clarified in upstream @apkatsikas !

…ed condition (envoyproxy#9129) * fix(status): separate listener programmed state from HTTPRoute Accepted condition Remove the NoReadyListeners block that set Accepted: False on routes when no listeners were programmed. Route acceptance reflects binding validity; listener programmed state is already tracked by the listener's own conditions. Signed-off-by: apkatsikas <[email protected]> * fix(status): separate listener programmed state from TCPRoute/UDPRoute Accepted condition Routes with a valid binding to an unprogrammed listener now correctly reach Accepted=True regardless of listener readiness. Moves accepted=true and IncrementAttachedRoutes before the IsReady check so the Accepted condition reflects binding validity only, consistent with the HTTPRoute fix and the Gateway API spec. Signed-off-by: apkatsikas <[email protected]>

* fix rate limit validation on K8s 1.36 (#9166) fixi: rate limit validation on K8s 1.36 Starting with K8s 1.36 the int range and maximum are validated against each other, which breaks the BTP tests. This can be fixed validating the field as uint32. Signed-off-by: Clemens Beck <[email protected]> Co-authored-by: Clemens Beck <[email protected]> (cherry picked from commit a21fd29) Signed-off-by: jukie <[email protected]> * fix(validation): allow IPv6 to be specific in loadBalancerSourceRanges (#9050) * fix(validation): allow IPv6 to be specific in loadBalancerSourceRanges and loadBalancerIP Signed-off-by: Marc 'risson' Schmitt <[email protected]> (cherry picked from commit 3c1d7b9) Signed-off-by: jukie <[email protected]> * fix: allow Backend TLS to disable ALPN with an empty list (#9162) * Fixed Backend TLS to disable upstream ALPN instead of inheriting EnvoyProxy BackendTLS defaults. Signed-off-by: Huabing Zhao <[email protected]> * add test case for envoyproxy without tls Signed-off-by: Huabing Zhao <[email protected]> * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <[email protected]> Signed-off-by: Huabing (Robin) Zhao <[email protected]> * address comments Signed-off-by: Huabing Zhao <[email protected]> --------- Signed-off-by: Huabing Zhao <[email protected]> Signed-off-by: Huabing (Robin) Zhao <[email protected]> Co-authored-by: Copilot Autofix powered by AI <[email protected]> (cherry picked from commit 21eb101) Signed-off-by: jukie <[email protected]> * fix(gatewayapi): sort api key auth credentials (#9042) * fix(gatewayapi): sort api key auth credentials Signed-off-by: Alexej Disterhoft <[email protected]> * docs(release-notes): add api key auth fix note Signed-off-by: Alexej Disterhoft <[email protected]> --------- Signed-off-by: Alexej Disterhoft <[email protected]> Signed-off-by: Alexej Disterhoft <[email protected]> Signed-off-by: zirain <[email protected]> Co-authored-by: Arko Dasgupta <[email protected]> Co-authored-by: zirain <[email protected]> (cherry picked from commit b96a2d3) Signed-off-by: jukie <[email protected]> * fix(status): separate listener programmed state from HTTPRoute Accepted condition (#9129) * fix(status): separate listener programmed state from HTTPRoute Accepted condition Remove the NoReadyListeners block that set Accepted: False on routes when no listeners were programmed. Route acceptance reflects binding validity; listener programmed state is already tracked by the listener's own conditions. Signed-off-by: apkatsikas <[email protected]> * fix(status): separate listener programmed state from TCPRoute/UDPRoute Accepted condition Routes with a valid binding to an unprogrammed listener now correctly reach Accepted=True regardless of listener readiness. Moves accepted=true and IncrementAttachedRoutes before the IsReady check so the Accepted condition reflects binding validity only, consistent with the HTTPRoute fix and the Gateway API spec. Signed-off-by: apkatsikas <[email protected]> (cherry picked from commit e9c3ac5) Signed-off-by: jukie <[email protected]> * fix: reject ExternalName Service as a route backend (#9190) fix: reject Service as a route backend Signed-off-by: Huabing Zhao <[email protected]> Signed-off-by: Huabing (Robin) Zhao <[email protected]> (cherry picked from commit ee16b3f) Signed-off-by: jukie <[email protected]> * fix(status): fall back to service externalIPs for Gateway addresses (#9209) When the Envoy service is of type LoadBalancer but no load balancer controller assigns an ingress address (e.g. bare-metal clusters), the Gateway status had no addresses and stayed Programmed=False with reason AddressNotAssigned, even when reachable addresses were configured via spec.externalIPs (e.g. through an EnvoyProxy service patch). Use spec.externalIPs as a fallback when the load balancer ingress list is empty. Ingress addresses keep priority when present, so behavior is unchanged for clusters with a working load balancer controller. Fixes #8987 Signed-off-by: Jules Dutel <[email protected]> (cherry picked from commit f2c0921) Signed-off-by: jukie <[email protected]> * fix: don't duplicate ValidatingAdmissionPolicy in install.yaml (#9182) * Fix duplicate VAP in install.yaml Signed-off-by: jukie <[email protected]> * Add regression check and release notes Signed-off-by: jukie <[email protected]> --------- Signed-off-by: jukie <[email protected]> (cherry picked from commit 332081c) Signed-off-by: jukie <[email protected]> * fix(listenerset): implement hostname conflict listener precedence (#9192) * fix(listenerset): implement hostname conflict listener precedence - In Gateway, multiple listeners with the same hostname all get marked Conflicted (no winner). In ListenerSet, a Gateway-owned listener wins over ListenerSet listeners; among ListenerSet listeners the first in processing order wins. - Conflicted ListenerSet listeners now get Accepted=False and Programmed=False with the conflict reason (HostnameConflict or ProtocolConflict), matching the Gateway API conformance expectation. - AttachedListenerSets on the Gateway status is now incremented only for ListenerSets that have at least one accepted listener, aligning with the spec definition of "successfully attached". Signed-off-by: zirain <[email protected]> * ListenerSet conflict Signed-off-by: zirain <[email protected]> * fix and improve message Signed-off-by: zirain <[email protected]> * better display gateway listener Signed-off-by: zirain <[email protected]> --------- Signed-off-by: zirain <[email protected]> (cherry picked from commit 9271654) Signed-off-by: jukie <[email protected]> * fix: correct the config hot reload validation order (#9214) Co-authored-by: Nimisha Mehta <[email protected]> (cherry picked from commit 7e4492d) Signed-off-by: jukie <[email protected]> * feat(helm): add CRDs dependency toggle (#8850) * feat(helm): add CRDs dependency toggle Allow skipping installation of the `crds` dependency on the gateway-helm chart by providing a conditional `crds.enabled` variable. This boolean defaults to `true` and toggles the inclusion of the dependency on the parent chart. ref: #8560 Signed-off-by: Gaston Festari <[email protected]> * docs: update Helm installation steps Use the `crds.enabled` variable in the examples instead of the `--skip-crds` flag. Update crds.enabled variable description. Co-authored-by: Huabing (Robin) Zhao <[email protected]> Signed-off-by: Gaston Festari <[email protected]> --------- Signed-off-by: Gaston Festari <[email protected]> Signed-off-by: Huabing (Robin) Zhao <[email protected]> Co-authored-by: Huabing (Robin) Zhao <[email protected]> (cherry picked from commit 62e01ce) Signed-off-by: jukie <[email protected]> * fix: validate API Key auth ExtractFrom (#9250) * fix: validate API Key auth ExtractFrom Signed-off-by: Huabing (Robin) Zhao <[email protected]> * add test Signed-off-by: Huabing (Robin) Zhao <[email protected]> * update Signed-off-by: Huabing (Robin) Zhao <[email protected]> * update Signed-off-by: Huabing (Robin) Zhao <[email protected]> * update Signed-off-by: Huabing (Robin) Zhao <[email protected]> --------- Signed-off-by: Huabing (Robin) Zhao <[email protected]> (cherry picked from commit 50b1339) Signed-off-by: jukie <[email protected]> * fix: XRateLimitHeadersOptionDisabled constant value must match CRD enum (#9224) * fix: XRateLimitHeadersOptionDisabled constant value must match CRD enum The constant held "Disabled" but the CRD enum specifies "Off", causing xRateLimitHeaders: "Off" to silently fall through the translator switch and always emit X-RateLimit headers. Fixes #9223 Signed-off-by: gianniskt <[email protected]> * fix: XRateLimitHeadersOptionDisabled constant value must match CRD enum The constant held "Disabled" but the CRD enum specifies "Off", causing xRateLimitHeaders: "Off" to silently fall through the translator switch and always emit X-RateLimit headers. Fixes #9223 Signed-off-by: gianniskt <[email protected]> * fix: add release note for XRateLimitHeadersOptionDisabled fix Signed-off-by: gianniskt <[email protected]> --------- Signed-off-by: gianniskt <[email protected]> Signed-off-by: Ioannis Koutroumpis <[email protected]> (cherry picked from commit 43c9d8e) Signed-off-by: jukie <[email protected]> * fix(ratelimit): shared global ratelimit with cost not working (#9245) * fix(ratelimit): shared global ratelimit with cost not working Signed-off-by: zirain <[email protected]> * fix Signed-off-by: zirain <[email protected]> * fix mixed shared rule Signed-off-by: zirain <[email protected]> * add e2e Signed-off-by: zirain <[email protected]> --------- Signed-off-by: zirain <[email protected]> (cherry picked from commit 7997791) Signed-off-by: jukie <[email protected]> * fix(gatewayapi): http retry without backoff (#9238) * fix http retry without backoff Signed-off-by: zirain <[email protected]> * release notes Signed-off-by: zirain <[email protected]> --------- Signed-off-by: zirain <[email protected]> (cherry picked from commit 4872e53) Signed-off-by: jukie <[email protected]> * fix: panic with empty deploy (#9365) Signed-off-by: zirain <[email protected]> (cherry picked from commit 42a0c2c) Signed-off-by: jukie <[email protected]> * chore: restore current.yaml after cherry-picks The cherry-picked bug-fix commits appended their release-note entries to release-notes/current.yaml. Those notes are already finalized in release-notes/v1.8.2.yaml, so restore current.yaml to its prior state to avoid duplicating them in the next release cycle. Signed-off-by: jukie <[email protected]> * [release-1.8] bump ratelimit image to 1e50889b Bump the Envoy Ratelimit image from ff287602 to 1e50889b in source and the gateway-helm chart, and note the bump under security updates in the v1.8.2 release notes. Signed-off-by: jukie <[email protected]> * testdata Signed-off-by: jukie <[email protected]> * fix: use int64 format for ratelimit Requests field (#9377) Signed-off-by: jukie <[email protected]> --------- Signed-off-by: Clemens Beck <[email protected]> Signed-off-by: jukie <[email protected]> Signed-off-by: Marc 'risson' Schmitt <[email protected]> Signed-off-by: Huabing Zhao <[email protected]> Signed-off-by: Huabing (Robin) Zhao <[email protected]> Signed-off-by: Alexej Disterhoft <[email protected]> Signed-off-by: Alexej Disterhoft <[email protected]> Signed-off-by: zirain <[email protected]> Signed-off-by: apkatsikas <[email protected]> Signed-off-by: Jules Dutel <[email protected]> Signed-off-by: Gaston Festari <[email protected]> Signed-off-by: gianniskt <[email protected]> Signed-off-by: Ioannis Koutroumpis <[email protected]> Co-authored-by: Clemens Beck <[email protected]> Co-authored-by: Clemens Beck <[email protected]> Co-authored-by: Marc 'risson' Schmitt <[email protected]> Co-authored-by: Huabing (Robin) Zhao <[email protected]> Co-authored-by: Copilot Autofix powered by AI <[email protected]> Co-authored-by: Alexej Disterhoft <[email protected]> Co-authored-by: Arko Dasgupta <[email protected]> Co-authored-by: zirain <[email protected]> Co-authored-by: Andrew Katsikas <[email protected]> Co-authored-by: jvlxz <[email protected]> Co-authored-by: Mengjia Liang <[email protected]> Co-authored-by: Nimisha Mehta <[email protected]> Co-authored-by: Gaston Festari <[email protected]> Co-authored-by: Ioannis Koutroumpis <[email protected]>

apkatsikas requested a review from a team as a code owner May 31, 2026 13:47

chatgpt-codex-connector Bot reviewed May 31, 2026

View reviewed changes

This was referenced May 31, 2026

Listenersets apkatsikas/k8s-tf-bootstrap#1

Merged

Update after https://github.com/envoyproxy/gateway/pull/9129 is hopefully merged apkatsikas/k8s-tf-bootstrap#2

Closed

zhaohuabing reviewed Jun 6, 2026

View reviewed changes

zhaohuabing previously approved these changes Jun 6, 2026

View reviewed changes

zhaohuabing requested a review from a team June 6, 2026 07:40

zhaohuabing added the cherrypick/release-v1.8.2 label Jun 6, 2026

apkatsikas dismissed zhaohuabing’s stale review via 65734cd June 6, 2026 12:28

apkatsikas requested a review from zhaohuabing June 6, 2026 12:29

zhaohuabing previously approved these changes Jun 6, 2026

View reviewed changes

apkatsikas mentioned this pull request Jun 6, 2026

HTTPRoute set to Accepted: False when listener has missing TLS certificate #9128

Closed

zirain force-pushed the fix/route-accepted-no-ready-listeners branch from 65734cd to 4f647cb Compare June 7, 2026 01:16

zirain previously approved these changes Jun 7, 2026

View reviewed changes

arkodg reviewed Jun 8, 2026

View reviewed changes

apkatsikas added 5 commits June 9, 2026 09:35

test(e2e): update merge_gateways to expect route Accepted=True for co…

514e157

…nflicted listener Signed-off-by: apkatsikas <[email protected]>

test(status): update test names

5f6d180

Signed-off-by: apkatsikas <[email protected]>

docs: mention GRPCRoute, TLSRoute, TCPRoute, UDPRoute in Accepted con…

1ff7528

…dition fix release note Signed-off-by: apkatsikas <[email protected]>

docs: remove NoReadyListeners example from egctl task

8edd0c2

Signed-off-by: apkatsikas <[email protected]>

zirain force-pushed the fix/route-accepted-no-ready-listeners branch from 4f647cb to 8edd0c2 Compare June 9, 2026 01:35

Merge branch 'main' into fix/route-accepted-no-ready-listeners

ec91119

Signed-off-by: Arko Dasgupta <[email protected]>

arkodg dismissed stale reviews from zhaohuabing and zirain via ec91119 June 11, 2026 14:29

arkodg merged commit e9c3ac5 into envoyproxy:main Jun 11, 2026
10 checks passed

Uh oh!

Conversation

apkatsikas commented May 31, 2026 • edited by zhaohuabing Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

netlify Bot commented May 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for cerulean-figolla-1f9435 ready!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

codecov Bot commented May 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

apkatsikas commented May 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

💡 Codex Review

Uh oh!

apkatsikas commented May 31, 2026

Uh oh!

apkatsikas commented May 31, 2026

Uh oh!

zirain commented Jun 1, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jun 1, 2026

Uh oh!

zhaohuabing Jun 6, 2026

Choose a reason for hiding this comment

Uh oh!

apkatsikas Jun 6, 2026

Choose a reason for hiding this comment

Uh oh!

zhaohuabing commented Jun 6, 2026

Uh oh!

zhaohuabing Jun 6, 2026

Choose a reason for hiding this comment

Uh oh!

apkatsikas Jun 6, 2026

Choose a reason for hiding this comment

Uh oh!

zhaohuabing left a comment

Choose a reason for hiding this comment

Uh oh!

apkatsikas commented Jun 6, 2026

Uh oh!

arkodg Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

apkatsikas Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

arkodg Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

arkodg commented Jun 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

apkatsikas commented Jun 8, 2026

Uh oh!

arkodg commented Jun 8, 2026

Uh oh!

apkatsikas commented Jun 8, 2026

Uh oh!

apkatsikas commented Jun 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

arkodg commented Jun 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

apkatsikas commented May 31, 2026 •

edited by zhaohuabing

Loading

netlify Bot commented May 31, 2026 •

edited

Loading

codecov Bot commented May 31, 2026 •

edited

Loading

apkatsikas commented May 31, 2026 •

edited

Loading

arkodg commented Jun 8, 2026 •

edited

Loading

apkatsikas commented Jun 11, 2026 •

edited

Loading