Broken Link Detected

[github-actions[bot]]

Summary

Status	Count
🔍 Total	6323
✅ Successful	6097
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	211
❓ Unknown	2
🚫 Errors	13

Errors per input

Errors in community.md

• https://twitter.com/PingCAP: Failed: HTTP status client error (403 Forbidden) for url (https://twitter.com/PingCAP)

Errors in adopters.md

• https://pingcap.com/case-studies/why-we-chose-an-htap-database-over-mysql-for-horizontal-scaling-and-complex-queries/: Failed: HTTP status client error (404 Not Found) for url (https://en.pingcap.com/case-studies/why-we-chose-an-htap-database-over-mysql-for-horizontal-scaling-and-complex-queries/)
• https://pingcap.com/blog/2017-08-08-tidbforyuanfudao/: Failed: HTTP status client error (404 Not Found) for url (https://en.pingcap.com/blog/2017-08-08-tidbforyuanfudao/)
• https://pingcap.com/case-studies/choose-a-mysql-alternative-over-vitess-and-crdb-to-scale-out-our-databases-on-k8s: Failed: HTTP status client error (404 Not Found) for url (https://en.pingcap.com/case-studies/choose-a-mysql-alternative-over-vitess-and-crdb-to-scale-out-our-databases-on-k8s)
• https://pingcap.com/case-studies/2017-05-22-Comparison-between-MySQL-and-TiDB-with-tens-of-millions-of-data-per-day: Failed: HTTP status client error (404 Not Found) for url (https://en.pingcap.com/case-studies/2017-05-22-Comparison-between-MySQL-and-TiDB-with-tens-of-millions-of-data-per-day)
• https://pingcap.com/case-studies/no-sharding-no-etl-use-scale-out-mysql-alternative-to-store-160-tb-of-data: Failed: HTTP status client error (404 Not Found) for url (https://en.pingcap.com/case-studies/no-sharding-no-etl-use-scale-out-mysql-alternative-to-store-160-tb-of-data)
• https://pingcap.com/case-studies/why-we-migrated-from-exadata-to-a-scale-out-htap-database-for-near-real-time-analytics: Failed: HTTP status client error (404 Not Found) for url (https://en.pingcap.com/case-studies/why-we-migrated-from-exadata-to-a-scale-out-htap-database-for-near-real-time-analytics)
• https://pingcap.com/case-studies/how-we-use-a-distributed-database-to-achieve-horizontal-scaling-without-downtime: Failed: HTTP status client error (404 Not Found) for url (https://en.pingcap.com/case-studies/how-we-use-a-distributed-database-to-achieve-horizontal-scaling-without-downtime)

Errors in support.md

• https://twitter.com/PingCAP: Failed: HTTP status client error (403 Forbidden) for url (https://twitter.com/PingCAP)

Errors in dm/dm-worker-configuration-file.md

• file:///github/workspace/dm/http:/127.0.0.1:8261,http:/127.0.0.1:8361,http:/127.0.0.1:8461: Failed: Cannot find file file:///github/workspace/dm/http:/127.0.0.1:8261,http:/127.0.0.1:8361,http:/127.0.0.1:8461

Errors in tiup/tiup-mirror.md

• https://tiup-mirror.example.com/: Failed: error sending request for url (https://tiup-mirror.example.com/): error trying to connect: dns error: failed to lookup address information: Name or service not known

Errors in dm/dm-master-configuration-file.md

• file:///github/workspace/dm/http:/127.0.0.1:8291,master2=http:/127.0.0.1:8292,master3=http:/127.0.0.1:8293: Failed: Cannot find file file:///github/workspace/dm/http:/127.0.0.1:8291,master2=http:/127.0.0.1:8292,master3=http:/127.0.0.1:8293

Errors in dm/deploy-a-dm-cluster-using-binary.md

• file:///github/workspace/dm/http:/192.168.0.4:8291,master2=http:/192.168.0.5:8291,master3=http:/192.168.0.6:8291: Failed: Cannot find file file:///github/workspace/dm/http:/192.168.0.4:8291,master2=http:/192.168.0.5:8291,master3=http:/192.168.0.6:8291

Full Github Actions output

[shichun-0415]

Cover by https://github.com/pingcap/docs/issues/8631.