notifications  

Messages by Thread

• • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] feat: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
  • Re: [PR] refactor: add healthcheck manager to decouple upstream [apisix] via GitHub
• [PR] fix: broken mcp-bridge test cases [apisix] via GitHub
  • Re: [PR] fix: broken mcp-bridge test cases [apisix] via GitHub
• (apisix-dashboard) branch dependabot/npm_and_yarn/tanstack/react-query-5.82.0 deleted (was 2be342417) github-bot
• (apisix-dashboard) branch dependabot/npm_and_yarn/tanstack/react-query-5.83.0 created (now 1261db2a3) github-bot
• [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.83.0 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.83.0 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.83.0 [apisix-dashboard] via GitHub
• Re: [I] feat: Enhance `limit-count` Plugin to Support Aligned Time Windows [apisix] via GitHub
  • Re: [I] feat: Enhance `limit-count` Plugin to Support Aligned Time Windows [apisix] via GitHub
• (apisix-dashboard) branch dependabot/npm_and_yarn/eslint-9.30.1 deleted (was e3cfb2974) github-bot
• (apisix-dashboard) branch dependabot/npm_and_yarn/eslint-9.31.0 created (now 15880fdbe) github-bot
• [PR] chore(deps-dev): bump eslint from 9.25.1 to 9.31.0 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps-dev): bump eslint from 9.25.1 to 9.31.0 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps-dev): bump eslint from 9.25.1 to 9.31.0 [apisix-dashboard] via GitHub
• (apisix) branch master updated: feat: add support for extra_headers in forward-auth plugin (#12405) ashishtiwari
• (apisix-ingress-controller) branch doc/fix-doc-description-error updated (cf94078f -> 67340926) alinsran
• (apisix-ingress-controller) branch doc/fix-doc-description-error updated (5ec272a2 -> cf94078f) alinsran
• [I] bug: no default ingress class found [apisix-ingress-controller] via GitHub
  • Re: [I] bug: no default ingress class found [apisix-ingress-controller] via GitHub
  • Re: [I] bug: no default ingress class found [apisix-ingress-controller] via GitHub
  • Re: [I] bug: no default ingress class found [apisix-ingress-controller] via GitHub
  • Re: [I] bug: no default ingress class found [apisix-ingress-controller] via GitHub
  • Re: [I] bug: no default ingress class found [apisix-ingress-controller] via GitHub
• Re: [I] bug: Resource Injection in APISIX Ingress Controller test\e2e scaffold [apisix-ingress-controller] via GitHub
  • Re: [I] bug: Resource Injection in APISIX Ingress Controller test\e2e scaffold [apisix-ingress-controller] via GitHub
  • Re: [I] bug: Resource Injection in APISIX Ingress Controller test\e2e scaffold [apisix-ingress-controller] via GitHub
• [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
  • Re: [PR] fix(standalone): lack of configuration validation in api [apisix] via GitHub
• Re: [I] bug: Syncing an ApisixRoute object fails due to an unknown plugin error related to opentelemetry. [apisix-ingress-controller] via GitHub
  • Re: [I] bug: Syncing an ApisixRoute object fails due to an unknown plugin error related to opentelemetry. [apisix-ingress-controller] via GitHub
• Re: [PR] feat: Add description parameter to ApisixConsumer [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: Add description parameter to ApisixConsumer [apisix-ingress-controller] via GitHub
• Re: [PR] docs: add another install command example [apisix-helm-chart] via GitHub
• Re: [I] It is recommended to use GraalVM as the runtime for Java runtime [apisix-java-plugin-runner] via GitHub
• [I] feat: As a user, I want to have dependences up to date, so that security vulnerabilities will be patched [apisix] via GitHub
  • Re: [I] feat: As a user, I want to have dependences up to date, so that security vulnerabilities will be patched [apisix] via GitHub
  • Re: [I] feat: As a user, I want to have dependences up to date, so that security vulnerabilities will be patched [apisix] via GitHub
  • Re: [I] feat: As a user, I want to have dependences up to date, so that security vulnerabilities will be patched [apisix] via GitHub
• [PR] chore(deps): bump google.golang.org/grpc in /t/plugin/grpc-web [apisix] via GitHub
  • Re: [PR] chore(deps): bump google.golang.org/grpc in /t/plugin/grpc-web [apisix] via GitHub
• (apisix) branch master updated: docs: add dashboard ui tips (#12420) wenming
• [I] bug: route vars cannot be displayed or edited using new admin ui / dashboard [apisix] via GitHub
  • Re: [I] bug: route vars cannot be displayed or edited using new admin ui / dashboard [apisix] via GitHub
  • Re: [I] bug: route vars cannot be displayed or edited using new admin ui / dashboard [apisix] via GitHub
  • Re: [I] bug: route vars cannot be displayed or edited using new admin ui / dashboard [apisix] via GitHub
• (apisix-ingress-controller) branch master updated: fix: should not return when service type is ExternalName (#2468) ronething
• (apisix-ingress-controller) branch v2.0.0 updated: doc: recommended to use apisix-standalone mode for installation. (#2470) alinsran
• (apisix-ingress-controller) branch master updated: doc: recommended to use apisix-standalone mode for installation. (#2470) alinsran
• (apisix-ingress-controller) branch doc/update-getting-started updated (05982417 -> db4bae34) alinsran
• (apisix-ingress-controller) branch doc/update-getting-started updated (ccb30a6e -> 05982417) alinsran
• (apisix-ingress-controller) branch doc/update-getting-started updated (0bb4eeeb -> ccb30a6e) alinsran
• (apisix-ingress-controller) branch doc/update-getting-started updated (c152a357 -> 0bb4eeeb) alinsran
• [PR] docs: add dashboard ui tips [apisix] via GitHub
  • Re: [PR] docs: add dashboard ui tips [apisix] via GitHub
• (apisix-ingress-controller) branch doc/update-getting-started created (now c152a357) alinsran
  • (apisix-ingress-controller) 01/01: doc: install using apisix-standalone by default in the getting-started alinsran
• [PR] doc: install using apisix-standalone by default in the getting-started [apisix-ingress-controller] via GitHub
  • Re: [PR] doc: recommended to use apisix-standalone mode for installation. [apisix-ingress-controller] via GitHub
  • Re: [PR] doc: recommended to use apisix-standalone mode for installation. [apisix-ingress-controller] via GitHub
• (apisix) branch master updated: fix(request-validation): support Content-Type header with charset for urlencoded data (#12406) baoyuan
• Re: [I] bug: request-validation plugin is buggy when header 'Content-Type: application/x-www-form-urlencoded' has parameters [apisix] via GitHub
• [PR] feat: Add load test for 2000 ApisixRoutes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: Add load test for 2000 ApisixRoutes [apisix-ingress-controller] via GitHub
• (apisix) branch master updated: feat: add a global switch to disable upstream health check (#12407) ashishtiwari
• Re: [I] bug: zipkin plugin's traceId printed to accessLog are all escaped characters [apisix] via GitHub
• (apisix) branch master updated: fix: zipkin trace_id and span_id format in ngx_var (#12403) baoyuan
• (apisix) branch master updated: fix(consumer): missed consumer update due to wrong version in cache (#12413) ashishtiwari
• (apisix-helm-chart) branch master updated: chore: update ingress subcharts version for apisix (#849) alinsran
• (apisix-helm-chart) tag apisix-2.11.2 created (now a6a2e9d) github-bot
• Re: [I] request help: desperately a new release is needed. [apisix-java-plugin-runner] via GitHub
• [PR] chore: update ingress subcharts version for apisix [apisix-helm-chart] via GitHub
  • Re: [PR] chore: update ingress subcharts version for apisix [apisix-helm-chart] via GitHub
• (apisix-helm-chart) tag apisix-ingress-controller-1.0.2 created (now 57ce6c5) github-bot
• (apisix-helm-chart) branch master updated: chore: update apisix-ingress-controller to 2.0.0-rc2 (#848) alinsran
• [PR] chore: update apisix-ingress-controller to 2.0.0-rc2 [apisix-helm-chart] via GitHub
  • Re: [PR] chore: update apisix-ingress-controller to 2.0.0-rc2 [apisix-helm-chart] via GitHub
• [PR] Create store-secrets-in-vault.md [apisix] via GitHub
  • Re: [PR] docs: store secrets in vault [apisix] via GitHub
  • Re: [PR] docs: store secrets in vault [apisix] via GitHub
  • Re: [PR] docs: store secrets in vault [apisix] via GitHub
  • Re: [PR] docs: store secrets in vault [apisix] via GitHub
  • Re: [PR] docs: store secrets in vault [apisix] via GitHub
• [PR] fix: should not return when service type is ExternalName [apisix-ingress-controller] via GitHub
  • Re: [PR] fix: should not return when service type is ExternalName [apisix-ingress-controller] via GitHub
• Re: [I] bug: not getting the authorization token in header using openid-connect plugin [apisix] via GitHub
  • Re: [I] bug: not getting the authorization token in header using openid-connect plugin [apisix] via GitHub
• [I] help request: 以Apisix作为正向代理访问协议要求HTTP/2的接口提示HTTP/1.0错误 [apisix] via GitHub
  • Re: [I] help request: using APISIX as a forward proxy to access an interface that requires HTTP/2 prompts an HTTP/1.0 error [apisix] via GitHub
  • Re: [I] help request: using APISIX as a forward proxy to access an interface that requires HTTP/2 prompts an HTTP/1.0 error [apisix] via GitHub
  • Re: [I] help request: using APISIX as a forward proxy to access an interface that requires HTTP/2 prompts an HTTP/1.0 error [apisix] via GitHub
• [I] 关于apisix功能的问题 [apisix] via GitHub
  • Re: [I] help request: questions about APISIX AI proxy [apisix] via GitHub
  • Re: [I] help request: questions about APISIX AI proxy [apisix] via GitHub
• [I] True all-in-one mirror image [apisix] via GitHub
  • Re: [I] True all-in-one mirror image [apisix] via GitHub
  • Re: [I] request help: true all-in-one mirror image [apisix] via GitHub
• [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.82.0 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.82.0 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump @tanstack/react-query from 5.74.4 to 5.82.0 [apisix-dashboard] via GitHub
• [I] apisix 3.13 支持 customer 使用 "-" 但dashboard 3.0.1 还是做了前端校验 [apisix-dashboard] via GitHub
  • Re: [I] apisix 3.13 支持 customer 使用 "-" 但dashboard 3.0.1 还是做了前端校验 [apisix-dashboard] via GitHub
  • Re: [I] apisix 3.13 支持 customer 使用 "-" 但dashboard 3.0.1 还是做了前端校验 [apisix-dashboard] via GitHub
• Re: [I] help request: etcd comes with APISIX by default does not have an expiration policy configured [apisix] via GitHub
• (apisix-helm-chart) branch master updated: fix: add etcd auto compaction env (#841) baoyuan
• [PR] chore: refactor e2e-test [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: refactor e2e-test [apisix-ingress-controller] via GitHub
  • Re: [PR] chore: refactor e2e-test [apisix-ingress-controller] via GitHub
• (apisix-dashboard) tag notice created (now bee39c281) bzp2010
• Re: [I] feat: As a user, I want to dynamic set proxy-buffering parameter, so fit the SSE situation [apisix] via GitHub
• Re: [I] bug: does apisix support sse at now [apisix] via GitHub
  • Re: [I] bug: does apisix support sse at now [apisix] via GitHub
  • Re: [I] bug: does apisix support sse at now [apisix] via GitHub
  • Re: [I] bug: does apisix support sse at now [apisix] via GitHub
  • Re: [I] bug: does apisix support sse at now [apisix] via GitHub
  • Re: [I] bug: does apisix support sse at now [apisix] via GitHub
  • Re: [I] bug: does apisix support sse at now [apisix] via GitHub
  • Re: [I] bug: does apisix support sse at now [apisix] via GitHub
• [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
  • Re: [PR] fix(consumer): missed consumer update due to wrong version in cache [apisix] via GitHub
• [I] help request: APISIX SSL Integration in Kubernetes Environment [apisix] via GitHub
  • Re: [I] help request: APISIX SSL Integration in Kubernetes Environment [apisix] via GitHub
  • Re: [I] help request: APISIX SSL Integration in Kubernetes Environment [apisix] via GitHub
  • Re: [I] help request: APISIX SSL Integration in Kubernetes Environment [apisix] via GitHub
  • Re: [I] help request: APISIX SSL Integration in Kubernetes Environment [apisix] via GitHub
  • Re: [I] help request: APISIX SSL Integration in Kubernetes Environment [apisix] via GitHub
  • Re: [I] help request: APISIX SSL Integration in Kubernetes Environment [apisix] via GitHub

• Earlier messages
• Later messages