notifications  

Messages by Thread

• • Re: [PR] fix(ai-proxy): catch malformed override endpoint in schema validation [apisix] via GitHub
• (apisix) branch master updated (6dd766418 -> 91e1d19d1) ashishtiwari
• [PR] ci: migrate docker image for testing to bitnamilegacy repo [apisix] via GitHub
  • Re: [PR] ci: migrate docker image for testing to bitnamilegacy repo [apisix] via GitHub
• [PR] chore: upgrade etcd chart to latest version and use latest image [apisix-helm-chart] via GitHub
  • Re: [PR] chore: upgrade etcd chart to latest version and use latest image [apisix-helm-chart] via GitHub
  • Re: [PR] chore: upgrade etcd chart to latest version and use latest image [apisix-helm-chart] via GitHub
  • Re: [PR] chore: upgrade etcd chart to latest version and use latest image [apisix-helm-chart] via GitHub
  • Re: [PR] chore: upgrade etcd chart to latest version and use latest image [apisix-helm-chart] via GitHub
• [PR] fix(plugin/redirect): ensure redirect when scheme is not `https` [apisix] via GitHub
  • Re: [PR] fix(plugin/redirect): ensure redirect when scheme is not `https` [apisix] via GitHub
• (apisix) branch master updated: fix(ai-proxy): set llm variables default value to 0 (#12549) baoyuan
• [I] feat: ksuid implementation on request-id plugin [apisix] via GitHub
  • Re: [I] feat: ksuid implementation on request-id plugin [apisix] via GitHub
  • Re: [I] feat: ksuid implementation on request-id plugin [apisix] via GitHub
  • Re: [I] feat: ksuid implementation on request-id plugin [apisix] via GitHub
  • Re: [I] feat: ksuid implementation on request-id plugin [apisix] via GitHub
  • Re: [I] feat: ksuid implementation on request-id plugin [apisix] via GitHub
  • Re: [I] feat: ksuid implementation on request-id plugin [apisix] via GitHub
  • Re: [I] feat: ksuid implementation on request-id plugin [apisix] via GitHub
  • Re: [I] feat: ksuid implementation on request-id plugin [apisix] via GitHub
  • Re: [I] feat: ksuid implementation on request-id plugin [apisix] via GitHub
• Re: [I] help request: memory leakage problem in Apisix GW [apisix] via GitHub
  • Re: [I] help request: memory leakage problem in Apisix GW [apisix] via GitHub
  • Re: [I] help request: memory leakage problem in Apisix GW [apisix] via GitHub
• (apisix) branch dependabot/go_modules/ci/pod/openfunction/function-example/test-body/gopkg.in/yaml.v3-3.0.1 created (now 9701c9edd) github-bot
• Re: [I] help request: OIDC state from argument does not match state restored from session [apisix] via GitHub
  • Re: [I] help request: OIDC state from argument does not match state restored from session [apisix] via GitHub
• [PR] chore(deps): bump gopkg.in/yaml.v3 from 3.0.0 to 3.0.1 in /ci/pod/openfunction/function-example/test-body [apisix] via GitHub
  • Re: [PR] chore(deps): bump gopkg.in/yaml.v3 from 3.0.0 to 3.0.1 in /ci/pod/openfunction/function-example/test-body [apisix] via GitHub
  • Re: [PR] chore(deps): bump gopkg.in/yaml.v3 from 3.0.0 to 3.0.1 in /ci/pod/openfunction/function-example/test-body [apisix] via GitHub
• [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: jsonschema.lua:46: attempt to call field 'find' (a nil value) [apisix-ingress-controller] via GitHub
• [PR] fix: add exptime to ewma shared dict items [apisix] via GitHub
  • Re: [PR] fix: add exptime to ewma shared dict items [apisix] via GitHub
• [I] big bug ! lua_shared_dict configuration item is object, not array! [apisix-helm-chart] via GitHub
  • Re: [I] big bug ! lua_shared_dict configuration item is object, not array! [apisix-helm-chart] via GitHub
• Re: [I] feat: test dashboard project [apisix] via GitHub
  • Re: [I] feat: test dashboard project [apisix] via GitHub
• Re: [PR] perf: support concurrent running of ADC [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch master updated: fix: hmac-auth plugin spec compatibility with latest apisix (#2528) ashishtiwari
• [I] bug: stream routes in the standalone API cannot be loaded correctly [apisix] via GitHub
• [PR] feat(ai-proxy): add new ctx variable for request llm model [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add new ctx variable for request llm model [apisix] via GitHub
• (apisix) branch master updated: fix(ai-proxy): check type of choices/usage/content fields before use it (#12548) ashishtiwari
• (apisix) branch master updated: fix(discovery/kubernetes): adjust id length (#12536) young
• [PR] feat: add upstream_response_time in ai-proxy [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add upstream_response_time in access log [apisix] via GitHub
• (apisix-ingress-controller) tag 2.0.0-rc4 created (now a23de408) alinsran
• (apisix-ingress-controller) branch v2.0.0 updated (666a9b01 -> a23de408) alinsran
• (apisix-ingress-controller) branch master updated: chore: v2.0.0-rc4 release (#2533) alinsran
• [PR] chore: v2.0.0-rc4 release [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: v2.0.0-rc4 release [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: v2.0.0-rc4 release [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: v2.0.0-rc4 release [apisix-ingress-controller] via GitHub
• [PR] Feat/xlayer [apisix] via GitHub
  • Re: [PR] Feat/xlayer [apisix] via GitHub
• (apisix-ingress-controller) branch master updated: fix: deadlock occurs when updating configuration fails (#2531) alinsran
• Re: [I] feat: optimize the UX of apisix-dashboard [apisix-dashboard] via GitHub
• [PR] feat: release ingress 2.0.0-rc4 [apisix-helm-chart] via GitHub
  • Re: [PR] feat: release ingress 2.0.0-rc4 [apisix-helm-chart] via GitHub
• (apisix-ingress-controller) branch master updated: chore: upgrade adc to 0.21.0 (#2532) alinsran
• (apisix-ingress-controller) branch master updated: chore: migrate redirect plugin e2e tests (#2529) ashishtiwari
• [PR] chore: upgrade adc to 0.21.0 [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: upgrade adc to 0.21.0 [apisix-ingress-controller] via GitHub
• [I] 有没有考虑优化下apisix-dashboard的交互页面啊 [apisix-dashboard] via GitHub
  • Re: [I] 有没有考虑优化下apisix-dashboard的交互页面啊 [apisix-dashboard] via GitHub
  • Re: [I] 有没有考虑优化下apisix-dashboard的交互页面啊 [apisix-dashboard] via GitHub
  • Re: [I] 有没有考虑优化下apisix-dashboard的交互页面啊 [apisix-dashboard] via GitHub
• (apisix-ingress-controller) branch master updated: chore: remove adc binary from dockerfile (#2530) alinsran
• [I] grafana service in example/docker-compose.yml version 7.3.7 is full of high profile vulnerabilities [apisix-docker] via GitHub
• [PR] feat: use `trusted_addresses` to handle `X-Forwarded-*` headers [apisix] via GitHub
  • Re: [PR] feat: use `trusted_addresses` to handle `X-Forwarded-*` headers [apisix] via GitHub
  • Re: [PR] feat: use `trusted_addresses` to handle `X-Forwarded-*` headers [apisix] via GitHub
  • Re: [PR] feat: use `trusted_addresses` to handle `X-Forwarded-*` headers [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
  • Re: [PR] fix: only trust `X-Forwarded-*` headers from `trusted_addresses` [apisix] via GitHub
• [I] 有没有考虑优化下apisix-dashboard的交互页面啊 [apisix] via GitHub
  • Re: [I] 有没有考虑优化下apisix-dashboard的交互页面啊 [apisix] via GitHub
  • Re: [I] 有没有考虑优化下apisix-dashboard的交互页面啊 [apisix] via GitHub
• [PR] fix(ai-proxy): set llm variables default value to 0 [apisix] via GitHub
  • Re: [PR] fix(ai-proxy): set llm variables default value to 0 [apisix] via GitHub
• [PR] fix(ai-proxy): check type of choices/usage/content fields before use it [apisix] via GitHub
  • Re: [PR] fix(ai-proxy): check type of choices/usage/content fields before use it [apisix] via GitHub
  • Re: [PR] fix(ai-proxy): check type of choices/usage/content fields before use it [apisix] via GitHub
  • Re: [PR] fix(ai-proxy): check type of choices/usage/content fields before use it [apisix] via GitHub
• (apisix) branch master updated (09f3d215e -> 08334a672) baoyuan
• [PR] fix: deadlock occurs when updating configuration fails [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: deadlock occurs when updating configuration fails [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: deadlock occurs when updating configuration fails [apisix-ingress-controller] via GitHub
• (apisix) branch master updated: feat(ai-proxy): add support for pushing logs in ai-proxy plugins (#12515) baoyuan
• [PR] chore: remove adc form dockerfile [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: remove adc binary from dockerfile [apisix-ingress-controller] via GitHub
• [PR] chore: migrate redirect plugin e2e tests [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: migrate redirect plugin e2e tests [apisix-ingress-controller] via GitHub
• [I] Upcoming changes to Bitnami images and charts [apisix-helm-chart] via GitHub
  • Re: [I] Upcoming changes to Bitnami images and charts [apisix-helm-chart] via GitHub
  • Re: [I] Upcoming changes to Bitnami images and charts [apisix-helm-chart] via GitHub
• [PR] fix: hmac-auth plugin spec compatibility with latest apisix [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: hmac-auth plugin spec compatibility with latest apisix [apisix-ingress-controller] via GitHub
• Re: [I] CRDs in apisix-ingress -controller helm chart do not match the CRDs in the corresponding version of the apisix-ingress-controller [apisix-helm-chart] via GitHub
• (apisix-ingress-controller) branch master updated: feat: support adc server mode (#2520) alinsran
• [I] bug: resource creation fails using authz-keycloak plugin [apisix] via GitHub
  • Re: [I] bug: resource creation fails using authz-keycloak plugin [apisix] via GitHub
  • Re: [I] bug: resource creation fails using authz-keycloak plugin [apisix] via GitHub
  • Re: [I] bug: resource creation fails using authz-keycloak plugin [apisix] via GitHub
  • Re: [I] bug: resource creation fails using authz-keycloak plugin [apisix] via GitHub
• [I] bug: update apisixroute's correct status when config stream rules [apisix-ingress-controller] via GitHub
  • Re: [I] bug: update apisixroute's correct status when config stream rules [apisix-ingress-controller] via GitHub
  • Re: [I] bug: update apisixroute's correct status when config stream rules [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch master updated: chore: migrate e2e tests for httproute basic (#2525) ashishtiwari
• (apisix) branch master updated: feat: add ai-aliyun-content-moderation plugin (#12530) ashishtiwari
• [I] request help: Ingress plugin annotations have no effect [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Ingress plugin annotations have no effect [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Ingress plugin annotations have no effect [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Ingress plugin annotations have no effect [apisix-ingress-controller] via GitHub
  • Re: [I] request help: Ingress plugin annotations have no effect [apisix-ingress-controller] via GitHub
• Re: [PR] More options for standalone configuration [apisix-helm-chart] via GitHub
• (apisix-ingress-controller) branch master updated (e5d831e4 -> 2a798d13) ashishtiwari
• (apisix-ingress-controller) branch master updated (eb7c06a6 -> e5d831e4) ashishtiwari
• (apisix-ingress-controller) branch Revolyssup-patch-1 deleted (was 34ed6a4f) ashishtiwari
• [PR] chore: migrate e2e tests for httproute basic [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: migrate e2e tests for httproute basic [apisix-ingress-controller] via GitHub
• [PR] chore: remove redundant backend traffic policy attachment [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: remove redundant backend traffic policy attachment [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch Revolyssup-patch-1 created (now 34ed6a4f) ashishtiwari
  • (apisix-ingress-controller) 01/01: chore: remove redundant backend traffic policy attachment ashishtiwari
• (apisix-ingress-controller) branch master updated: chore: migrate retries/timeout tests for apisixupstream (#2517) ashishtiwari
• (apisix-ingress-controller) branch fix-docs-stream deleted (was d5f56071) traky
• (apisix-ingress-controller) branch master updated: docs: mention stream is currently not supported in the CRD docs (#2522) traky
• [PR] fix(test): Unstable controllername assertion [apisix-ingress-controller] via GitHub
  • Re: [PR] fix(test): unstable controllername assertion [apisix-ingress-controller] via GitHub
• (apisix) branch master updated: feat: allow to use environment variables for openid-connect plugin (#11451) baoyuan
• Re: [I] feat: support client_secret in openid-connect plugin use secret [apisix] via GitHub
• [I] feat: As a user, I want to have a `base_uri` option added to `service`, so that I don't have to add `proxy_rewrite` plugin to every `route` [apisix] via GitHub
  • Re: [I] feat: As a user, I want to have a `base_uri` option added to `service`, so that I don't have to add `proxy_rewrite` plugin to every `route` [apisix] via GitHub
  • Re: [I] feat: As a user, I want to have a `base_uri` option added to `service`, so that I don't have to add `proxy_rewrite` plugin to every `route` [apisix] via GitHub
  • Re: [I] feat: As a user, I want to have a `base_uri` option added to `service`, so that I don't have to add `proxy_rewrite` plugin to every `route` [apisix] via GitHub
• [I] help request: Delayed and DEADLINE_EXCEEDED APISIX requests [apisix] via GitHub
  • Re: [I] help request: Delayed and DEADLINE_EXCEEDED APISIX requests [apisix] via GitHub
  • Re: [I] help request: Delayed and DEADLINE_EXCEEDED APISIX requests [apisix] via GitHub

• Earlier messages
• Later messages