notifications  

Messages by Thread

• (apisix) branch dependabot/github_actions/apache/skywalking-eyes-0.8.0 updated (18b921f66 -> ef3f5244b) github-bot
• Re: [PR] chore(deps): bump apache/skywalking-eyes from 0.6.0 to 0.8.0 [apisix] via GitHub
  • Re: [PR] chore(deps): bump apache/skywalking-eyes from 0.6.0 to 0.8.0 [apisix] via GitHub
• (apisix) branch dependabot/github_actions/actions/checkout-5 deleted (was aec5af5ef) baoyuan
• (apisix) branch master updated (f995b57df -> 31aa48f18) baoyuan
• Re: [PR] chore(deps): bump actions/checkout from 4 to 5 [apisix] via GitHub
• (apisix) branch dependabot/github_actions/actions/github-script-8 deleted (was 24e64b828) github-bot
• Re: [PR] chore(deps): bump actions/github-script from 7 to 8 [apisix] via GitHub
  • Re: [PR] chore(deps): bump actions/github-script from 7 to 8 [apisix] via GitHub
• Re: [I] after run pnpm dev, 404 errors on the frontend pages [apisix-dashboard] via GitHub
  • Re: [I] after run pnpm dev, 404 errors on the frontend pages [apisix-dashboard] via GitHub
• Re: [I] help request: pnpm dev启动前端后，如何启动后端？ [apisix-dashboard] via GitHub
  • Re: [I] help request: pnpm dev启动前端后，如何启动后端？ [apisix-dashboard] via GitHub
• (apisix-dashboard) branch master updated: fix: mask sensitive fields (#3251) young
• Re: [I] bug: Sensitive keys and tokens are visible in the APISIX Dashboard [apisix-dashboard] via GitHub
• (apisix-dashboard) branch master updated: test: add E2E tests for plugin metadata resource (#3247) young
• (apisix-dashboard) branch dependabot/npm_and_yarn/types/qs-6.14.0 deleted (was bd0f23a28) github-bot
• Re: [PR] chore(deps-dev): bump @types/qs from 6.9.18 to 6.14.0 [apisix-dashboard] via GitHub
  • Re: [PR] chore(deps-dev): bump @types/qs from 6.9.18 to 6.14.0 [apisix-dashboard] via GitHub
• (apisix-dashboard) branch master updated: test(e2e): Add E2E tests for consumer and credentials (#3243) young
• (apisix-dashboard) branch master updated: test: add E2E tests for protos (#3244) young
• (apisix-dashboard) branch master updated: test(plugin_configs): add comprehensive E2E tests for plugin configs resource (#3246) young
• (apisix-dashboard) branch master updated: test: add E2E tests for global rules (#3248) young
• (apisix-dashboard) branch master updated: test: add E2E tests for SSLs (#3087) (#3249) young
• (apisix-dashboard) branch master updated (2d7e1947b -> b28b8841f) young
• Re: [I] help request: ApisixTLS applies SSL certificate not populated even it says Accepted [apisix-ingress-controller] via GitHub
  • Re: [I] help request: ApisixTLS applies SSL certificate not populated even it says Accepted [apisix-ingress-controller] via GitHub
  • Re: [I] help request: ApisixTLS applies SSL certificate not populated even it says Accepted [apisix-ingress-controller] via GitHub
• [I] Upper level reverse proxy `X-Forwarded-*` headers cleared by APISIX [apisix-helm-chart] via GitHub
  • Re: [I] Upper level reverse proxy `X-Forwarded-*` headers cleared by APISIX [apisix-helm-chart] via GitHub
  • Re: [I] Upper level reverse proxy `X-Forwarded-*` headers cleared by APISIX [apisix-helm-chart] via GitHub
  • Re: [I] Upper level reverse proxy `X-Forwarded-*` headers cleared by APISIX [apisix-helm-chart] via GitHub
• Re: [I] bug: /status/ready endpoint always returns 503 in file-driven standalone mode [apisix] via GitHub
  • Re: [I] bug: /status/ready endpoint always returns 503 in file-driven standalone mode [apisix] via GitHub
  • Re: [I] bug: /status/ready endpoint always returns 503 in file-driven standalone mode [apisix] via GitHub
  • Re: [I] bug: /status/ready endpoint always returns 503 in file-driven standalone mode [apisix] via GitHub
  • Re: [I] bug: /status/ready endpoint always returns 503 in file-driven standalone mode [apisix] via GitHub
  • Re: [I] bug: /status/ready endpoint always returns 503 in file-driven standalone mode [apisix] via GitHub
  • Re: [I] bug: /status/ready endpoint always returns 503 in file-driven standalone mode [apisix] via GitHub
• Re: [I] bug: upstream in route domain ip changes not been detected and use the old ip [apisix] via GitHub
  • Re: [I] bug: upstream in route domain ip changes not been detected and use the old ip [apisix] via GitHub
  • Re: [I] bug: upstream in route domain ip changes not been detected and use the old ip [apisix] via GitHub
  • Re: [I] bug: upstream in route domain ip changes not been detected and use the old ip [apisix] via GitHub
  • Re: [I] bug: upstream in route domain ip changes not been detected and use the old ip [apisix] via GitHub
• (apisix) branch master updated (00f18aa1d -> f995b57df) baoyuan
• [PR] fix: mcp-bridge test cases [apisix] via GitHub
  • Re: [PR] fix: mcp-bridge test cases [apisix] via GitHub
• [I] 3.14.0 Unable to switch to Chinese [apisix-dashboard] via GitHub
  • Re: [I] 3.14.0 Unable to switch to Chinese [apisix-dashboard] via GitHub
  • Re: [I] 3.14.0 Unable to switch to Chinese [apisix-dashboard] via GitHub
• (apisix-ingress-controller) branch dependabot/go_modules/golang.org/x/crypto-0.45.0 created (now 679882d0) github-bot
• [PR] chore(deps): bump golang.org/x/crypto from 0.37.0 to 0.45.0 [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/crypto from 0.37.0 to 0.45.0 [apisix-ingress-controller] via GitHub
  • Re: [PR] chore(deps): bump golang.org/x/crypto from 0.37.0 to 0.45.0 [apisix-ingress-controller] via GitHub
• (apisix) branch revolyssup/standalone-validate deleted (was fec1b1afd) alinsran
• (apisix) branch revolyssup/standalone-validate created (now fec1b1afd) alinsran
  • (apisix) 01/02: update conmments alinsran
  • (apisix) 02/02: Merge branch 'master' into revolyssup/standalone-validate alinsran
• Re: [I] 404 Route Not Found in apisix 3.6.1 [apisix] via GitHub
• [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug/request help: ingress-controller crash looping in OpenShift 4.19 (rc5 in standalone api-driven mode) [apisix-ingress-controller] via GitHub
• [I] help request: How to download the latest version of Apisix RPM [apisix] via GitHub
  • Re: [I] help request: How to download the latest version of Apisix RPM [apisix] via GitHub
  • Re: [I] help request: How to download the latest version of Apisix RPM [apisix] via GitHub
  • Re: [I] help request: How to download the latest version of Apisix RPM [apisix] via GitHub
• Re: [I] bug: The HTTP stream issue in a reverse proxy scenario [apisix] via GitHub
  • Re: [I] bug: The HTTP stream issue in a reverse proxy scenario [apisix] via GitHub
  • Re: [I] bug: The HTTP stream issue in a reverse proxy scenario [apisix] via GitHub
• Re: [I] bug: 503 errors occur after restarting APISIX when using Consul and APISIX both in Docker [apisix] via GitHub
• [I] bug: templates/configmap.yaml rendering error causes Pod run abnormally (RC5 in standalone mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: templates/configmap.yaml rendering error causes Pod run abnormally (RC5 in standalone mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: templates/configmap.yaml rendering error causes Pod run abnormally (RC5 in standalone mode) [apisix-ingress-controller] via GitHub
  • Re: [I] bug: templates/configmap.yaml rendering error causes Pod run abnormally (RC5 in standalone mode) [apisix-ingress-controller] via GitHub
• [PR] fix: support extra_lua_path in test framework [apisix] via GitHub
  • Re: [PR] fix: support extra_lua_path in test framework [apisix] via GitHub
  • [PR] fix: support extra_lua_path in test framework [apisix] via GitHub
  • Re: [PR] fix: support extra_lua_path in test framework [apisix] via GitHub
  • Re: [PR] fix: support extra_lua_path in test framework [apisix] via GitHub
  • Re: [PR] fix: support extra_lua_path in test framework [apisix] via GitHub
  • Re: [PR] fix: support extra_lua_path in test framework [apisix] via GitHub
  • Re: [PR] fix: support extra_lua_path in test framework [apisix] via GitHub
  • Re: [PR] fix: support extra_lua_path in test framework [apisix] via GitHub
  • Re: [PR] fix: support extra_lua_path in test framework [apisix] via GitHub
  • Re: [PR] fix: support extra_lua_path in test framework [apisix] via GitHub
• [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix-ingress-controller] via GitHub
  • Re: [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix-ingress-controller] via GitHub
  • Re: [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix-ingress-controller] via GitHub
  • Re: [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix-ingress-controller] via GitHub
  • Re: [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix-ingress-controller] via GitHub
  • Re: [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix-ingress-controller] via GitHub
  • Re: [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix-ingress-controller] via GitHub
  • Re: [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix-ingress-controller] via GitHub
  • Re: [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix-ingress-controller] via GitHub
• Re: [I] 🚀 Support for k8s.apisix.apache.org/headers and rewrite-uri annotations missing in v1.8.4 [apisix-ingress-controller] via GitHub
  • Re: [I] 🚀 Support for k8s.apisix.apache.org/headers and rewrite-uri annotations missing in v1.8.4 [apisix-ingress-controller] via GitHub
  • Re: [I] 🚀 Support for k8s.apisix.apache.org/headers and rewrite-uri annotations missing in v1.8.4 [apisix-ingress-controller] via GitHub
• [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
  • Re: [I] cannot access admin [apisix-dashboard] via GitHub
• [I] help request: ApisixRoute CRDs not syncing to APISIX data plane; routes work only if created via UI/Admin API [apisix] via GitHub
• [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
  • Re: [I] request help: ApisixGlobalRule Not Working in API-driven Standalone Mode [apisix-ingress-controller] via GitHub
• [PR] Update common.json [apisix-dashboard] via GitHub
  • Re: [PR] Update common.json [apisix-dashboard] via GitHub
  • Re: [PR] feat(i18n): add Chinese (zh) language translations [apisix-dashboard] via GitHub
  • Re: [PR] feat(i18n): add Chinese (zh) language translations [apisix-dashboard] via GitHub
  • Re: [PR] feat(i18n): add Chinese (zh) language translations [apisix-dashboard] via GitHub
  • Re: [PR] feat(i18n): add Chinese (zh) language translations [apisix-dashboard] via GitHub
  • Re: [PR] feat(i18n): add Chinese (zh) language translations [apisix-dashboard] via GitHub
• [PR] eat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
  • Re: [PR] feat(limit-count): add sliding window support for redis-based policies [apisix] via GitHub
• [I] Add support Oracle OCI Vault for Secrets Mangement [apisix] via GitHub
  • Re: [I] Add support Oracle OCI Vault for Secrets Mangement [apisix] via GitHub
• [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
  • Re: [PR] fix: ensure UI directory is created when building debian-dev image [apisix] via GitHub
• [I] change of etcd.image.registry triggers ERROR [apisix-helm-chart] via GitHub
  • Re: [I] change of etcd.image.registry triggers ERROR [apisix-helm-chart] via GitHub
• [I] help request: Why create a consumer and enable authentication plugins for this consumer. Then enable this plugin for one of the routes as well. The log in the rewrite method in the code will be printed twice [apisix] via GitHub
  • Re: [I] help request: Why create a consumer and enable authentication plugins for this consumer. Then enable this plugin for one of the routes as well. The log in the rewrite method in the code will be printed twice [apisix] via GitHub
  • Re: [I] help request: Why create a consumer and enable authentication plugins for this consumer. Then enable this plugin for one of the routes as well. The log in the rewrite method in the code will be printed twice [apisix] via GitHub
  • Re: [I] help request: Why create a consumer and enable authentication plugins for this consumer. Then enable this plugin for one of the routes as well. The log in the rewrite method in the code will be printed twice [apisix] via GitHub
  • Re: [I] help request: Why create a consumer and enable authentication plugins for this consumer. Then enable this plugin for one of the routes as well. The log in the rewrite method in the code will be printed twice [apisix] via GitHub
• [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: [PR] fix: plugin not add args, original args will lost [apisix] via GitHub
• Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
  • Re: [PR] feat: add route search form with 9 filter fields [apisix-dashboard] via GitHub
• (apisix-ingress-controller) branch master updated: feat: support deployment of multiple data plane modes (#2647) alinsran
• (apisix-dashboard) branch master updated: feat: add Turkish (tr) language support (#3252) baoyuan
• [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
  • Re: [I] bug: Two requests returned differently [apisix] via GitHub
• [PR] Feature/ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub
  • Re: [PR] feat: ai rate limiting redis support [apisix] via GitHub

• Earlier messages
• Later messages