notifications  

Messages by Thread

• • Re: [PR] feat(ai-proxy): add native Anthropic endpoint support [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native Anthropic endpoint support [apisix] via GitHub
• [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
  • Re: [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
  • Re: [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
  • Re: [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
  • Re: [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
  • Re: [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
  • Re: [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
  • Re: [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
  • Re: [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
  • Re: [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
  • Re: [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
  • Re: [PR] fix(stream): initialize env and secret for TLS cert resolution [apisix] via GitHub
• Re: [PR] fix: Adding request-id header in case of empty header value in request [apisix] via GitHub
  • Re: [PR] fix: Adding request-id header in case of empty header value in request [apisix] via GitHub
  • Re: [PR] fix: Adding request-id header in case of empty header value in request [apisix] via GitHub
  • Re: [PR] fix: Adding request-id header in case of empty header value in request [apisix] via GitHub
  • Re: [PR] fix: Adding request-id header in case of empty header value in request [apisix] via GitHub
• (apisix) branch master updated: chore(deps-dev): bump @modelcontextprotocol/sdk in /t (#12870) baoyuan
• (apisix) branch dependabot/npm_and_yarn/t/modelcontextprotocol/sdk-1.25.2 deleted (was 7266128b9) baoyuan
• [I] bug: stream: $ENV:// / $secret:// TLS certs not resolved (missing core.env.init & apisix_secret.init_worker) [apisix] via GitHub
  • Re: [I] bug: stream: $ENV:// / $secret:// TLS certs not resolved (missing core.env.init & apisix_secret.init_worker) [apisix] via GitHub
  • Re: [I] bug: stream: $ENV:// / $secret:// TLS certs not resolved (missing core.env.init & apisix_secret.init_worker) [apisix] via GitHub
  • Re: [I] bug: $ENV and $secret SSL cert references not working in Stream TLS mode [apisix] via GitHub
  • Re: [I] bug: $ENV and $secret SSL cert references not working in Stream TLS mode [apisix] via GitHub
  • Re: [I] bug: $ENV and $secret SSL cert references not working in Stream TLS mode [apisix] via GitHub
• [PR] fix: relax frontend validation for multi-auth plugin [apisix-dashboard] via GitHub
  • Re: [PR] fix: relax frontend validation for multi-auth plugin [apisix-dashboard] via GitHub
• [I] [Question] Why does APISIX require cluster-wide access to Kubernetes Secret resources? [apisix-helm-chart] via GitHub
• Re: [PR] fix: change consul event module to shared dict [apisix] via GitHub
  • Re: [PR] fix: change consul event module to shared dict [apisix] via GitHub
• [I] multi-auth-Plugin schema validation incorrect [apisix-dashboard] via GitHub
  • Re: [I] multi-auth-Plugin schema validation incorrect [apisix-dashboard] via GitHub
  • Re: [I] multi-auth-Plugin schema validation incorrect [apisix-dashboard] via GitHub
  • Re: [I] multi-auth-Plugin schema validation incorrect [apisix-dashboard] via GitHub
  • Re: [I] multi-auth-Plugin schema validation incorrect [apisix-dashboard] via GitHub
  • Re: [I] multi-auth-Plugin schema validation incorrect [apisix-dashboard] via GitHub
  • Re: [I] multi-auth-Plugin schema validation incorrect [apisix-dashboard] via GitHub
• [PR] feat: support vertex-ai [apisix] via GitHub
  • Re: [PR] feat: support vertex-ai [apisix] via GitHub
  • Re: [PR] feat: support vertex-ai [apisix] via GitHub
  • Re: [PR] feat: support vertex-ai [apisix] via GitHub
  • Re: [PR] feat: support vertex-ai [apisix] via GitHub
  • Re: [PR] feat: support vertex-ai [apisix] via GitHub
  • Re: [PR] feat: support vertex-ai [apisix] via GitHub
• [I] bug: String environment variable value is casted if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
  • Re: [I] bug: String environment variable value is casted tonumber if contains a number in standalone mode [apisix] via GitHub
• [PR] fix: append apisix_request_id on access_log_format [apisix] via GitHub
  • Re: [PR] feat: support `apisix_request_id` variable with request-id plugin [apisix] via GitHub
  • Re: [PR] feat: support `apisix_request_id` variable with request-id plugin [apisix] via GitHub
  • Re: [PR] feat: support `apisix_request_id` variable with request-id plugin [apisix] via GitHub
• (apisix-ingress-controller) branch master updated: fix: ensure upstream scheme is set only if not already defined in HTTP route translation (#2691) ronething
• (apisix) branch master updated: fix: eliminate deepcopy when destroying prometheus (#12905) baoyuan
• [PR] change: remove lua-resty-worker-events [apisix] via GitHub
  • Re: [PR] change: remove lua-resty-worker-events [apisix] via GitHub
  • Re: [PR] change: remove lua-resty-worker-events [apisix] via GitHub
  • Re: [PR] change: remove lua-resty-worker-events [apisix] via GitHub
  • Re: [PR] change: remove lua-resty-worker-events [apisix] via GitHub
  • Re: [PR] change: remove lua-resty-worker-events [apisix] via GitHub
  • Re: [PR] change: remove lua-resty-worker-events [apisix] via GitHub
  • Re: [PR] change: remove lua-resty-worker-events [apisix] via GitHub
  • Re: [PR] change: remove lua-resty-worker-events [apisix] via GitHub
  • Re: [PR] change: remove lua-resty-worker-events [apisix] via GitHub
• [I] Support for Non-Authentication Plugins in ApisixConsumer CRD [apisix-ingress-controller] via GitHub
  • Re: [I] Support for Non-Authentication Plugins in ApisixConsumer CRD [apisix-ingress-controller] via GitHub
  • Re: [I] Support for Non-Authentication Plugins in ApisixConsumer CRD [apisix-ingress-controller] via GitHub
  • Re: [I] Support for Non-Authentication Plugins in ApisixConsumer CRD [apisix-ingress-controller] via GitHub
  • Re: [I] Support for Non-Authentication Plugins in ApisixConsumer CRD [apisix-ingress-controller] via GitHub
• Re: [I] feat: support mcp server base on apisix ,provide some current api as mcp tools [apisix] via GitHub
• [I] help request: Unclear if memory leak or something else in luajit process [apisix] via GitHub
  • Re: [I] help request: Unclear if memory leak or something else in luajit process [apisix] via GitHub
  • Re: [I] help request: Unclear if memory leak or something else in luajit process [apisix] via GitHub
  • Re: [I] help request: Unclear if memory leak or something else in luajit process [apisix] via GitHub
  • Re: [I] help request: Unclear if memory leak or something else in luajit process [apisix] via GitHub
• Re: [PR] Added proxy protocol support settings [apisix-helm-chart] via GitHub
  • Re: [PR] Added proxy protocol support settings [apisix-helm-chart] via GitHub
• [I] bug: bug,Why does the overall average response time for long connections (keep-alive) exceed that for short connections (close) in performance tests? [apisix] via GitHub
  • Re: [I] bug: bug,Why does the overall average response time for long connections (keep-alive) exceed that for short connections (close) in performance tests? [apisix] via GitHub
  • Re: [I] bug: bug,Why does the overall average response time for long connections (keep-alive) exceed that for short connections (close) in performance tests? [apisix] via GitHub
  • Re: [I] bug: bug,Why does the overall average response time for long connections (keep-alive) exceed that for short connections (close) in performance tests? [apisix] via GitHub
• [PR] fix(conf): correct AI plugin priority comments in config.yaml.example [apisix] via GitHub
  • Re: [PR] fix(conf): correct AI plugin priority comments in config.yaml.example [apisix] via GitHub
  • Re: [PR] fix(conf): correct AI plugin priority comments in config.yaml.example [apisix] via GitHub
• (apisix) branch docs-improve-ai-prmopt-template deleted (was 2f38aa3db) yilialin
• [I] help request: Cross-namespace communication issue [apisix-ingress-controller] via GitHub
  • Re: [I] help request: Cross-namespace communication issue [apisix-ingress-controller] via GitHub
  • Re: [I] help request: Cross-namespace communication issue [apisix-ingress-controller] via GitHub
• (apisix) branch master updated: docs: improve `ai-prompt-template` plugin docs (#12897) wenming
• [I] bug: the metric expiration feature supported in the latest version seems to cause the metric output to lose parts of the list that have been expired and re-added. [apisix] via GitHub
  • Re: [I] bug: the metric expiration feature supported in the latest version seems to cause the metric output to lose parts of the list that have been expired and re-added. [apisix] via GitHub
  • Re: [I] bug: the metric expiration feature supported in the latest version seems to cause the metric output to lose parts of the list that have been expired and re-added. [apisix] via GitHub
  • Re: [I] bug: the metric expiration feature supported in the latest version seems to cause the metric output to lose parts of the list that have been expired and re-added. [apisix] via GitHub
  • Re: [I] bug: the metric expiration feature supported in the latest version seems to cause the metric output to lose parts of the list that have been expired and re-added. [apisix] via GitHub
  • Re: [I] bug: the metric expiration feature supported in the latest version seems to cause the metric output to lose parts of the list that have been expired and re-added. [apisix] via GitHub
• [PR] docs: small fix helm command [apisix-helm-chart] via GitHub
• [PR] feat(ai-proxy): add native support for Anthropic provider [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native support for Anthropic provider [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native support for Anthropic provider [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native support for Anthropic provider [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native support for Anthropic provider [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native support for Anthropic provider [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native support for Anthropic provider [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native support for Anthropic provider [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native support for Anthropic provider [apisix] via GitHub
  • Re: [PR] feat(ai-proxy): add native support for Anthropic provider [apisix] via GitHub
• [I] help request: failed to execute adc command [apisix-ingress-controller] via GitHub
  • Re: [I] help request: failed to execute adc command [apisix-ingress-controller] via GitHub
  • Re: [I] help request: failed to execute adc command [apisix-ingress-controller] via GitHub
  • Re: [I] help request: failed to execute adc command [apisix-ingress-controller] via GitHub
• Re: [PR] feat: adds support for nginx variables in service_name param [apisix] via GitHub
  • Re: [PR] feat: adds support for nginx variables in service_name param [apisix] via GitHub
• Re: [I] request help: why the location in response header that returned by APISIX has the 9443 port? [apisix] via GitHub
  • Re: [I] request help: why the location in response header that returned by APISIX has the 9443 port? [apisix] via GitHub
  • Re: [I] request help: why the location in response header that returned by APISIX has the 9443 port? [apisix] via GitHub
• Re: [I] help request: why apisix dont update healthcheck upstream ip when upstream ip is no use [apisix] via GitHub
  • Re: [I] help request: why apisix dont update healthcheck upstream ip when upstream ip is no use [apisix] via GitHub
• [I] help request: 503 errors triggered when scaling down an upstream with traffic-split weight 0 [apisix] via GitHub
  • Re: [I] help request: 503 errors triggered when scaling down an upstream with traffic-split weight 0 [apisix] via GitHub
  • Re: [I] help request: 503 errors triggered when scaling down an upstream with traffic-split weight 0 [apisix] via GitHub
  • Re: [I] help request: 503 errors triggered when scaling down an upstream with traffic-split weight 0 [apisix] via GitHub
  • Re: [I] help request: 503 errors triggered when scaling down an upstream with traffic-split weight 0 [apisix] via GitHub
  • Re: [I] help request: 503 errors triggered when scaling down an upstream with traffic-split weight 0 [apisix] via GitHub
  • Re: [I] help request: 503 errors triggered when scaling down an upstream with traffic-split weight 0 [apisix] via GitHub
• (apisix-helm-chart) tag apisix-2.12.6 created (now 7e5b8df) github-bot
• (apisix-helm-chart) branch chore/update_dependency deleted (was 0fa4d43) ronething
• (apisix-helm-chart) branch master updated: chore: upgrade dependency apisix-ingress-controller to 1.1.1 (#933) ronething
• (apisix-helm-chart) branch chore/update_dependency updated (68a2aaf -> 0fa4d43) ronething
• [PR] chore: upgrade dependency apisix-ingress-controller to 1.1.1 [apisix-helm-chart] via GitHub
  • Re: [PR] chore: upgrade dependency apisix-ingress-controller to 1.1.1 [apisix-helm-chart] via GitHub
• (apisix-helm-chart) branch chore/update_dependency created (now 68a2aaf) ronething
  • (apisix-helm-chart) 01/01: chore: upgrade dependency apisix-ingress-controller to 1.1.1 ronething
• (apisix-helm-chart) branch gh-pages updated: Update index.yaml github-bot
  • (apisix-helm-chart) branch gh-pages updated: Update index.yaml github-bot
  • (apisix-helm-chart) branch gh-pages updated: Update index.yaml github-bot
  • (apisix-helm-chart) branch gh-pages updated: Update index.yaml github-bot
• (apisix-helm-chart) tag apisix-ingress-controller-1.1.1 created (now a7ae1ad) github-bot
• (apisix-helm-chart) branch chore/upgrade_ingress deleted (was 486ecd4) ronething
• (apisix-helm-chart) branch master updated: chore: release apisix-ingress-controller 2.0.1 (#932) ronething
• (apisix) branch master updated: fix(limit-req): ensure safe eviction of keys in redis (#12911) baoyuan
• [PR] chore: release apisix-ingress-controller 2.0.1 [apisix-helm-chart] via GitHub
  • Re: [PR] chore: release apisix-ingress-controller 2.0.1 [apisix-helm-chart] via GitHub
• (apisix-helm-chart) branch chore/upgrade_ingress created (now 486ecd4) ronething
  • (apisix-helm-chart) 01/01: chore: release apisix-ingress-controller 2.0.1 ronething
• Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
  • Re: [PR] fix: WebSocket load balancing imbalance with least_conn after upstream scaling [apisix] via GitHub
• Re: [I] Fixing APISIX to work without anyuid for SCC in openshift [apisix-docker] via GitHub
  • Re: [I] Fixing APISIX to work without anyuid for SCC in openshift [apisix-docker] via GitHub
  • Re: [I] Fixing APISIX to work without anyuid for SCC in openshift [apisix-docker] via GitHub
• Re: [I] help request: Plugins do not work propely [apisix-ingress-controller] via GitHub
  • Re: [I] help request: Plugins do not work propely [apisix-ingress-controller] via GitHub
• Re: [PR] fix: plugin not add args, original args will lost [apisix] via GitHub
  • Re: [PR] fix: plugin not add args, original args will lost [apisix] via GitHub
  • Re: [PR] fix: plugin not add args, original args will lost [apisix] via GitHub
• Re: [I] bug: Modifying the weight to 0 in APISIx version 3.9.1, there are still requests to be forwarded [apisix] via GitHub
  • Re: [I] bug: Modifying the weight to 0 in APISIx version 3.9.1, there are still requests to be forwarded [apisix] via GitHub
  • Re: [I] bug: Modifying the weight to 0 in APISIx version 3.9.1, there are still requests to be forwarded [apisix] via GitHub
• [I] Do not support handling the forwarding through the OpenAI method. [apisix] via GitHub
  • Re: [I] Do not support handling the forwarding through the SDK method. [apisix] via GitHub
  • Re: [I] Do not support handling the forwarding through the SDK method. [apisix] via GitHub
  • Re: [I] Do not support handling the forwarding through the SDK method. [apisix] via GitHub
• [I] Can plugin configurations support "inheritance" from higher levels with partial property overrides, instead of complete replacement? [apisix] via GitHub
  • Re: [I] Can plugin configurations support "inheritance" from higher levels with partial property overrides, instead of complete replacement? [apisix] via GitHub
• [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
  • Re: [PR] feat: support port-based routing for Gateway API routes [apisix-ingress-controller] via GitHub
• (apisix) branch docs-improve-ai-prmopt-template updated (4cacdfd77 -> 2f38aa3db) traky
• (apisix-ingress-controller) branch master updated: docs: add `apisix.apache.org/parameters-namespace` to annotation doc (#2702) traky
• (apisix-ingress-controller) branch parameters-namespace deleted (was 1217fbc4) traky
• (apisix-ingress-controller) branch parameters-namespace updated (adc58ae0 -> 1217fbc4) traky
• (apisix-ingress-controller) branch parameters-namespace updated (c1ae645a -> adc58ae0) traky

• Earlier messages
• Later messages