notifications  

Messages by Thread

• (apisix-dashboard) branch dependabot/github_actions/apache/skywalking-eyes-a62f574f0eb113e306a860014d7ce38aea00f78d created (now 47939d68d) github-bot
• [PR] chore(deps): bump apache/skywalking-eyes from 9f0a5c0571ed1a0c13a16808cd8f59bc22f03883 to a62f574f0eb113e306a860014d7ce38aea00f78d [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 9f0a5c0571ed1a0c13a16808cd8f59bc22f03883 to a62f574f0eb113e306a860014d7ce38aea00f78d [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 9f0a5c0571ed1a0c13a16808cd8f59bc22f03883 to a62f574f0eb113e306a860014d7ce38aea00f78d [apisix-dashboard] via GitHub
• Re: [I] bug: Upstream HealthCheck Issue - Unhealthy Upstream doesn't be excluded temporarily [apisix] via GitHub
• Re: [I] bug: (3.10.0) SSL ENV secret does not work in key value (encrypted field not compatible with secret env engine?) [apisix] via GitHub
• Re: [I] bug: proxy-mirror plugin not work [apisix] via GitHub
  • Re: [I] bug: proxy-mirror plugin not work [apisix] via GitHub
• Re: [I] help request: unable to sync apisix upstream and route crd using name same as kubernetes service [apisix] via GitHub
• [PR] chore(deps): bump sigs.k8s.io/gateway-api from 0.8.0 to 1.3.0 [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump sigs.k8s.io/gateway-api from 0.8.0 to 1.3.0 [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump sigs.k8s.io/gateway-api from 0.8.0 to 1.3.0 [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump sigs.k8s.io/gateway-api from 0.8.0 to 1.3.0 [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch dependabot/go_modules/sigs.k8s.io/gateway-api-1.3.0 created (now 4846ba95) github-bot
• [PR] chore(deps): bump github.com/slok/kubewebhook/v2 from 2.5.0 to 2.7.0 [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump github.com/slok/kubewebhook/v2 from 2.5.0 to 2.7.0 [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump github.com/slok/kubewebhook/v2 from 2.5.0 to 2.7.0 [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump github.com/slok/kubewebhook/v2 from 2.5.0 to 2.7.0 [apisix-ingress-controller] via GitHub
• (apisix-ingress-controller) branch dependabot/go_modules/github.com/slok/kubewebhook/v2-2.7.0 created (now 5db31b49) github-bot
• (apisix) branch master updated: chore(docker): update etcd config (#12328) young
• (apisix) branch master updated: fix(docker): install libyaml in arm64 (#12329) young
• (apisix-website) branch fix-metadata-of-configure-apisix-in-a-single-command deleted (was 5140fe07238) yilialin
• (apisix-website) branch master updated: fix: metadata of configure apisix in a single command (#1924) yilialin
• [PR] fix: metadata of configure apisix in a single command [apisix-website] via GitHub
  • Re: [PR] fix: metadata of configure apisix in a single command [apisix-website] via GitHub
• (apisix-website) branch fix-metadata-of-configure-apisix-in-a-single-command created (now 5140fe07238) yilialin
  • (apisix-website) 01/01: fix: metadata of configure apisix in a single command yilialin
• Re: [PR] chore(deps): bump golang.org/x/net from 0.23.0 to 0.38.0 in /test/e2e [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/net from 0.23.0 to 0.38.0 in /test/e2e [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/net from 0.23.0 to 0.38.0 in /test/e2e [apisix-ingress-controller] via GitHub
• Re: [PR] chore(deps): bump golang.org/x/net from 0.17.0 to 0.38.0 in /test/e2e/testbackend [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/net from 0.17.0 to 0.38.0 in /test/e2e/testbackend [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/net from 0.17.0 to 0.38.0 in /test/e2e/testbackend [apisix-ingress-controller] via GitHub
• (apisix-dashboard) branch master updated: fix(stream_routes): show server_addr instead of name (#3121) baoyuan
• (apisix-dashboard) branch master updated: fix(stream_routes): rm upstream when has service_id (#3120) baoyuan
• (apisix-dashboard) branch master updated: feat: support delete all stream routes (#3119) baoyuan
• (apisix-dashboard) branch master updated: fix(stream_routes): `protocol` related JSONInput config (#3118) baoyuan
• [I] bug: mcp-bridge plugin is not working with docker run command [apisix] via GitHub
  • Re: [I] bug: mcp-bridge plugin is not working with docker run command [apisix] via GitHub
  • Re: [I] bug: mcp-bridge plugin is not working with docker run command [apisix] via GitHub
  • Re: [I] bug: mcp-bridge plugin is not working with docker run command [apisix] via GitHub
  • Re: [I] bug: mcp-bridge plugin is not working with docker run command [apisix] via GitHub
  • Re: [I] bug: mcp-bridge plugin is not working with docker run command [apisix] via GitHub
  • Re: [I] bug: mcp-bridge plugin is not working with docker run command [apisix] via GitHub
  • Re: [I] bug: mcp-bridge plugin is not working with docker run command [apisix] via GitHub
  • Re: [I] bug: mcp-bridge plugin is not working with docker run command [apisix] via GitHub
• Re: [PR] Fix: APISIX Dashboard "etcd not connected" issue in Docker Compose setup [apisix-docker] via GitHub
  • Re: [PR] Fix: APISIX Dashboard "etcd not connected" issue in Docker Compose setup [apisix-docker] via GitHub
  • Re: [PR] Fix: APISIX Dashboard "etcd not connected" issue in Docker Compose setup [apisix-docker] via GitHub
• Re: [I] apisix dashboard - docker - panic: runtime error: invalid memory address or nil pointer dereference [apisix-dashboard] via GitHub
• Re: [I] help request: failed to check the configuration of plugin multi-auth err: openid-connect plugin is not supported [apisix] via GitHub
  • Re: [I] help request: failed to check the configuration of plugin multi-auth err: openid-connect plugin is not supported [apisix] via GitHub
• Re: [I] feat: support client_secret in openid-connect plugin use secret [apisix] via GitHub
  • Re: [I] feat: support client_secret in openid-connect plugin use secret [apisix] via GitHub
• (apisix) branch dependabot/go_modules/t/grpc_server_example/golang.org/x/net-0.33.0 deleted (was eb0b8732d) github-bot
• Re: [PR] chore(deps): bump golang.org/x/net from 0.7.0 to 0.33.0 in /t/grpc_server_example [apisix] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/net from 0.7.0 to 0.33.0 in /t/grpc_server_example [apisix] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/net from 0.7.0 to 0.33.0 in /t/grpc_server_example [apisix] via GitHub
• Re: [PR] chore(deps): bump golang.org/x/crypto from 0.14.0 to 0.35.0 [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/crypto from 0.14.0 to 0.35.0 [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/crypto from 0.14.0 to 0.35.0 [apisix-ingress-controller] via GitHub
• Re: [PR] chore(deps): bump golang.org/x/crypto from 0.21.0 to 0.35.0 in /test/e2e [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/crypto from 0.21.0 to 0.35.0 in /test/e2e [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/crypto from 0.21.0 to 0.35.0 in /test/e2e [apisix-ingress-controller] via GitHub
• [I] Blank plugin page on new Standalone Plugin or Consumer/Route Plugin sections in the dashboard. [apisix-dashboard] via GitHub
  • Re: [I] Blank plugin page on new Standalone Plugin or Consumer/Route Plugin sections in the dashboard. [apisix-dashboard] via GitHub
  • Re: [I] Blank plugin page on new Standalone Plugin or Consumer/Route Plugin sections in the dashboard. [apisix-dashboard] via GitHub
  • Re: [I] Blank plugin page on new Standalone Plugin or Consumer/Route Plugin sections in the dashboard. [apisix-dashboard] via GitHub
  • Re: [I] Blank plugin page on new Standalone Plugin or Consumer/Route Plugin sections in the dashboard. [apisix-dashboard] via GitHub
  • Re: [I] Blank plugin page on new Standalone Plugin or Consumer/Route Plugin sections in the dashboard. [apisix-dashboard] via GitHub
  • Re: [I] Blank plugin page on new Standalone Plugin or Consumer/Route Plugin sections in the dashboard. [apisix-dashboard] via GitHub
• [I] Remove `DES-CBC3-SHA` from TLS Ciphers [apisix-helm-chart] via GitHub
  • Re: [I] Remove `DES-CBC3-SHA` from TLS Ciphers [apisix-helm-chart] via GitHub
  • Re: [I] Remove `DES-CBC3-SHA` from TLS Ciphers [apisix-helm-chart] via GitHub
• [PR] Make TLS ciphers configurable for ApiSix Helm Chart [apisix-helm-chart] via GitHub
• (apisix-ingress-controller) branch next updated: fix(ci): use ubuntu-latest for running ci (#2407) ronething
• Re: [I] bug: The command "apisix reload" sometimes causes the plugin's sock file to disappear [apisix] via GitHub
  • Re: [I] bug: The command "apisix reload" sometimes causes the plugin's sock file to disappear [apisix] via GitHub
• [I] request help: Dashboard plugin configuration is lost after CRD-based ApisixRoute updates — need best practice for sync and separation of responsibilities [apisix-ingress-controller] via GitHub
• [PR] fix(ci): use ubuntu-latest for running ci [apisix-ingress-controller] via GitHub
  • Re: [PR] fix(ci): use ubuntu-latest for running ci [apisix-ingress-controller] via GitHub
• [PR] fix(docker): install libyaml in arm64 [apisix] via GitHub
  • Re: [PR] fix(docker): install libyaml in arm64 [apisix] via GitHub
• (apisix-ingress-controller) branch next updated: chore(ci): change trigger branch ronething
• (apisix-website) branch master updated: docs: add redirect rules for APISIX 3.2 docs to netlify (#1923) juzhiyuan
• (apisix-website) branch LiteSun-patch-1 deleted (was 26c1bcb0f5b) juzhiyuan
• (apisix-dashboard) branch master updated: fix(JSONInput): toObject logic (#3117) young
• (apisix-website) branch LiteSun-patch-1 updated (23ccf4b8da8 -> 26c1bcb0f5b) sunyi
• [PR] chore(docker): update etcd version [apisix] via GitHub
  • Re: [PR] chore(docker): update etcd config [apisix] via GitHub
  • Re: [PR] chore(docker): update etcd config [apisix] via GitHub
• (apisix-website) branch LiteSun-patch-1 created (now 23ccf4b8da8) sunyi
  • (apisix-website) 01/01: Update .htaccess sunyi
• [PR] Update .htaccess [apisix-website] via GitHub
  • Re: [PR] docs: add redirect rules for APISIX 3.2 docs to netlify [apisix-website] via GitHub
• [PR] fix(stream_routes): show server_addr instead of name [apisix-dashboard] via GitHub
  • Re: [PR] fix(stream_routes): show `server_addr`, `server_port` instead of `name` [apisix-dashboard] via GitHub
• [PR] fix(stream_routes): rm upstream when has service_id [apisix-dashboard] via GitHub
  • Re: [PR] fix(stream_routes): rm `upstream` when has `service_id` [apisix-dashboard] via GitHub
• [PR] feat: support delete all stream routes [apisix-dashboard] via GitHub
  • Re: [PR] feat: support delete all stream routes [apisix-dashboard] via GitHub
  • Re: [PR] feat: support delete all stream routes [apisix-dashboard] via GitHub
  • Re: [PR] feat: support delete all stream routes [apisix-dashboard] via GitHub
• [PR] fix(stream_routes): protocol related JSONInput [apisix-dashboard] via GitHub
  • Re: [PR] fix(stream_routes): `protocol` related JSONInput config [apisix-dashboard] via GitHub
• (apisix-website) branch master updated: blog: add configure-apisix-in-a-single-command-with-apisix-mcp (#1921) yilialin
• [PR] fix(stream_routes): logic for processing data [apisix-dashboard] via GitHub
  • Re: [PR] fix(stream_routes): logic for processing data [apisix-dashboard] via GitHub
  • Re: [PR] fix(JSONInput): toObject logic [apisix-dashboard] via GitHub
• Re: [I] help request: The plugin configuration in the route did not disable the global plugin. [apisix] via GitHub
  • Re: [I] help request: The plugin configuration in the route did not disable the global plugin. [apisix] via GitHub
• [PR] chore(deps): bump docker/setup-qemu-action from 1 to 3 [apisix] via GitHub
  • Re: [PR] chore(deps): bump docker/setup-qemu-action from 1 to 3 [apisix] via GitHub
  • Re: [PR] chore(deps): bump docker/setup-qemu-action from 1 to 3 [apisix] via GitHub
• (apisix) branch dependabot/github_actions/docker/setup-qemu-action-3 created (now 71468e775) github-bot
• (apisix) branch dependabot/github_actions/actions/setup-node-4.4.0 created (now e185221c1) github-bot
• (apisix) branch dependabot/github_actions/actions/setup-node-4.3.0 deleted (was 36aa39480) github-bot
• (apisix) branch dependabot/github_actions/docker/login-action-3 created (now deca81ab9) github-bot
• [PR] chore(deps): bump docker/setup-buildx-action from 1 to 3 [apisix] via GitHub
  • Re: [PR] chore(deps): bump docker/setup-buildx-action from 1 to 3 [apisix] via GitHub
  • Re: [PR] chore(deps): bump docker/setup-buildx-action from 1 to 3 [apisix] via GitHub
• (apisix) branch dependabot/github_actions/docker/setup-buildx-action-3 created (now 946d10ade) github-bot
• Re: [PR] chore(deps): bump actions/setup-node from 4.0.2 to 4.3.0 [apisix] via GitHub
  • Re: [PR] chore(deps): bump actions/setup-node from 4.0.2 to 4.3.0 [apisix] via GitHub
• [PR] chore(deps): bump docker/login-action from 1 to 3 [apisix] via GitHub
  • Re: [PR] chore(deps): bump docker/login-action from 1 to 3 [apisix] via GitHub
  • Re: [PR] chore(deps): bump docker/login-action from 1 to 3 [apisix] via GitHub
• [PR] chore(deps): bump actions/setup-node from 4.0.2 to 4.4.0 [apisix] via GitHub
  • Re: [PR] chore(deps): bump actions/setup-node from 4.0.2 to 4.4.0 [apisix] via GitHub
• [PR] docs: remove slack invite link [apisix-website] via GitHub
  • Re: [PR] docs: remove slack invite link [apisix-website] via GitHub
  • Re: [PR] docs: remove slack invite link [apisix-website] via GitHub
• [I] bug: apisix load high [apisix] via GitHub
  • Re: [I] bug: apisix load high [apisix] via GitHub
  • Re: [I] bug: apisix load high [apisix] via GitHub
  • Re: [I] bug: apisix load high [apisix] via GitHub
  • Re: [I] bug: apisix load high [apisix] via GitHub
  • Re: [I] bug: apisix load high [apisix] via GitHub
  • Re: [I] bug: apisix load high [apisix] via GitHub
  • Re: [I] bug: apisix load high [apisix] via GitHub
• [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
  • Re: [PR] fix(workflow): use runners with different architectures instead of QEMU [apisix] via GitHub
• Re: [PR] feat: override nginx http lua shared dict configurations (#690) [apisix-helm-chart] via GitHub
• (apisix-dashboard) branch master updated: test: routes in services (#3112) juzhiyuan
• 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: [I] bug: Syncing an ApisixRoute object fails due to an unknown plugin error related to opentelemetry. [apisix-ingress-controller] via GitHub
• Re: [I] bug: a bug cannot deploy `service-control.yaml` with helm in charts-2.10.0 [apisix-ingress-controller] via GitHub
  • Re: [I] bug: a bug cannot deploy `service-control.yaml` with helm in charts-2.10.0 [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] feat: Add description parameter to ApisixConsumer [apisix-ingress-controller] via GitHub
• [I] bug: limit-count plugins don't recognize the redis_port as integer [apisix] via GitHub
  • Re: [I] bug: limit-count plugins don't recognize the redis_port as integer [apisix] via GitHub
• (apisix-ingress-controller) branch dependabot/go_modules/test/e2e/github.com/gavv/httpexpect/v2-2.17.0 deleted (was 8ff66102) github-bot
• (apisix-ingress-controller) branch dependabot/go_modules/github.com/stretchr/testify-1.10.0 deleted (was 728cc931) github-bot
• [I] bug: APISIX does not respect updated plugin priorities when using the CORS and limit-count plugins [apisix] via GitHub
  • Re: [I] bug: APISIX does not respect updated plugin priorities when using the CORS and limit-count plugins [apisix] via GitHub
  • Re: [I] bug: APISIX does not respect updated plugin priorities when using the CORS and limit-count plugins [apisix] via GitHub
  • Re: [I] bug: APISIX does not respect updated plugin priorities when using the CORS and limit-count plugins [apisix] via GitHub
  • Re: [I] bug: APISIX does not respect updated plugin priorities when using the CORS and limit-count plugins [apisix] via GitHub
• [I] help request: Is it possible for grpc-transcode plugin to handle grpc stream? [apisix] via GitHub
  • Re: [I] help request: Is it possible for grpc-transcode plugin to handle grpc stream? [apisix] via GitHub
  • Re: [I] help request: Is it possible for grpc-transcode plugin to handle grpc stream? [apisix] via GitHub
  • Re: [I] help request: Is it possible for grpc-transcode plugin to handle grpc stream? [apisix] via GitHub
  • Re: [I] help request: Is it possible for grpc-transcode plugin to handle grpc stream? [apisix] via GitHub
• [I] bug: apisix reload error [apisix] via GitHub
  • Re: [I] bug: apisix reload error [apisix] via GitHub
  • Re: [I] bug: apisix reload error [apisix] via GitHub
  • Re: [I] bug: apisix reload error [apisix] via GitHub
  • Re: [I] bug: apisix reload error [apisix] via GitHub
• Re: [I] help request: I want to send JSON data from apisix to kafka topic but not able to do it, can anyone assist. [apisix] via GitHub
  • Re: [I] help request: I want to send JSON data from apisix to kafka topic but not able to do it, can anyone assist. [apisix] via GitHub
  • Re: [I] help request: I want to send JSON data from apisix to kafka topic but not able to do it, can anyone assist. [apisix] via GitHub
  • Re: [I] help request: I want to send JSON data from apisix to kafka topic but not able to do it, can anyone assist. [apisix] via GitHub
  • Re: [I] help request: I want to send JSON data from apisix to kafka topic but not able to do it, can anyone assist. [apisix] via GitHub
• (apisix) branch dependabot/github_actions/apache/skywalking-eyes-0.7.0 deleted (was 10b794b21) github-bot
• Re: [PR] chore(deps): bump apache/skywalking-eyes from 0.6.0 to 0.7.0 [apisix] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 0.6.0 to 0.7.0 [apisix] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 0.6.0 to 0.7.0 [apisix] via GitHub
• Re: [I] bug: zipkin plugin throw exception(span already finished) while use plugin [apisix] via GitHub
  • Re: [I] bug: zipkin plugin throw exception(span already finished) while use plugin [apisix] via GitHub
• Re: [I] bug: wrong request forwarded to the upstream server [apisix] via GitHub
• (apisix-dashboard) branch master updated: feat(services): filter routes/stream_routes by `service_id` (#3111) young
• [I] Se sigue con el mismo problema [apisix-dashboard] via GitHub
  • Re: [I] Se sigue con el mismo problema [apisix-dashboard] via GitHub
  • Re: [I] Se sigue con el mismo problema [apisix-dashboard] via GitHub

• Earlier messages
• Later messages