pingcap / blog

https://pingcap.com/blog/
49 stars 43 forks source link

Broken Link Detected #799

Open github-actions[bot] opened 2 years ago

github-actions[bot] commented 2 years ago

Errors were reported while checking the availability of links.


Issues found in 18 inputs. Find details below.

[pingcap-successfully-completes-soc-2-type-1-examination-for-tidb-cloud.md]:
✗ [404] https://docs.pingcap.com/tidbcloud/beta/tidb-cloud-intro | Network error: Not Found

[chaos-mesh-your-chaos-engineering-solution-for-system-resiliency-on-kubernetes.md]:
✗ [404] https://github.com/kubernetes-sigs/kind/releases/download/v0.6.1/kind-$(uname)-amd64 | Network error: Not Found

[announcing-tidb-1.0-release.md]:
✗ [500] http://www.yoozoo.com/aboutEn | Network error: Internal Server Error

[what-is-new-and-improved-in-tidb-docs.md]:
✗ [403] https://docs.pingcap.com/tidbcloud/beta | Network error: Forbidden
✗ [404] https://docs.pingcap.com/tidb/stable/whats-new-in-tidb-4.0 | Network error: Not Found

[tidb-operator-source-code-reading-4-implement-component-control-loop.md]:
✗ [ERROR] http://${domain}:2380/ | The given URI is invalid: http://${domain}:2380/
✗ [ERROR] http://0.0.0.0:2379/ | Network error: No status code
✗ [ERROR] http://0.0.0.0:2380/ | Network error: No status code
✗ [ERROR] http://${domain}:2379/ | The given URI is invalid: http://${domain}:2379/

[building-a-large-scale-distributed-storage-system-based-on-raft.md]:
✗ [404] https://www.cs.cmu.edu/~srini/15-440/lectures/12-gfs_hdfs_spanner.pdf | Network error: Not Found

[autotikv-tikv-tuning-made-easy-by-machine-learning.md]:
✗ [404] https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automatic-tuning | Network error: Not Found

[how-to-migrate-data-from-amazon-aurora-mysql-to-tidb-cloud.md]:
✗ [404] https://docs.pingcap.com/tidbcloud/beta/set-up-vpc-peering-connections | Network error: Not Found

[chaos-mesh-remake-one-step-closer-toward-chaos-as-a-service.md]:
✗ [404] https://vector.dev/docs/reference/transforms/wasm/ | Network error: Not Found

[pingcapers-make-their-debut-at-vldb.md]:
✗ [403] https://tokyo.vldb2020.org/ | Network error: Forbidden

[tidb-cloud-managed-sql-at-scale-on-aws-and-gcp.md]:
✗ [403] https://docs.pingcap.com/tidbcloud/beta | Network error: Forbidden

[get-started-with-juicefs-using-tikv.md]:
✗ [404] https://github.com/juicedata/juicefs/releases/download/v$%7BJFS_LATEST_TAG%7D/juicefs-$%7BJFS_LATEST_TAG%7D-linux-amd64.tar.gz | Network error: Not Found

[announcing-tidb-as-a-service-fully-managed-tidb-offering.md]:
✗ [403] https://docs.pingcap.com/tidbcloud/beta | Network error: Forbidden

[how-to-deploy-tidb-on-google-cloud-platform-part-1.md]:
✗ [403] https://www.cyberciti.biz/faq/how-to-find-my-public-ip-address-from-command-line-on-a-linux/ | Network error: Forbidden

[tidb-cloud-in-public-preview.md]:
✗ [404] https://docs.pingcap.com/tidbcloud/beta/tidb-cloud-quickstart | Network error: Not Found

[how-to-efficiently-stress-test-pod-memory.md]:
✗ [404] https://manpages.ubuntu.com/manpages/artful/man1/stress-ng.1.html#:~:text=is%20not%20available.-,--vm-bytes%20N,-mmap%20N%20bytes | Network error: Not Found

[squashed-bugs-served-hot-and-fresh-with-failure-rate-heatmaps.md]:
✗ [ERROR] http://${tidb-server-ip}:43222/trace/df6bfbff | The given URI is invalid: http://${tidb-server-ip}:43222/trace/df6bfbff

[scale-out-database-powers-china-letgo-with-reduced-maintenance-costs.md]:
✗ [404] https://docs.pingcap.com/tidb/stable/whats-new-in-tidb-4.0 | Network error: Not Found

🔍 5016 Total ✅ 4854 OK 🚫 23 Errors (HTTP:23|Unknown:5) 💤 134 Excluded

Full Github Actions output

ran-huang commented 2 years ago

Closing the following issues because 1) some are false alarms 2) all broken links are included in this issue. https://github.com/pingcap/blog/issues/780 https://github.com/pingcap/blog/issues/781 https://github.com/pingcap/blog/issues/782 https://github.com/pingcap/blog/issues/783 https://github.com/pingcap/blog/issues/784 https://github.com/pingcap/blog/issues/785 https://github.com/pingcap/blog/issues/786 https://github.com/pingcap/blog/issues/787 https://github.com/pingcap/blog/issues/788 https://github.com/pingcap/blog/issues/789 https://github.com/pingcap/blog/issues/790 https://github.com/pingcap/blog/issues/791 https://github.com/pingcap/blog/issues/792 https://github.com/pingcap/blog/issues/793 https://github.com/pingcap/blog/issues/794 https://github.com/pingcap/blog/issues/795 https://github.com/pingcap/blog/issues/796 https://github.com/pingcap/blog/issues/797 https://github.com/pingcap/blog/issues/798

ran-huang commented 2 years ago

All broken links on docs.pingcap.com are fixed in https://github.com/pingcap/docs/pull/8503, https://github.com/pingcap/docs-cn/pull/9350, https://github.com/tidbcloud/dbaas-docs/pull/195, etc. The rest of the broken links will be fixed by the content team. /cc @dcalvin

ran-huang commented 2 years ago

Also, the broken link checker is disabled in https://github.com/pingcap/blog/pull/800:

Disable the scheduled link checker because the blog content is now maintained on WordPress instead of GitHub. The content team will use a new plugin to check broken links.