Anthony

> I think we can just start with extracting the main content of the file (we already do this for search) and just hash it as is. Yeah, I think...

I was expecting this PR to fail miserably, but seems it is either somehow okay or we don't have enough test coverage :shrug:

Hrm, seems the last remaining piece is whatever these failures are: ``` ------------------------------ Captured log call ------------------------------- WARNING django.request:log.py:241 I'm a Teapot: /projects/subproject/ ____________________ RedirectTests.test_subproject_root_url ____________________ self = def test_subproject_root_url(self):...

Thanks for that! I figured it had to be something around the URL changes too, I ended my day before getting into debugging at all though.

Here is a repository that reliable triggers this exception: https://github.com/boschresearch/bt_tools

I'm going to put this on next sprint so we don't forget about it. It's not a common bug, however the failure case isn't great as it is a silent...

Seems like that is just our logging though, not reporting/notification to the user. From the attached conversation, this is the build the user reported: https://app.readthedocs.org/projects/bt-tools/builds/25303128/ There's no failure mentioned there...

We should mention something to the user though, not just a generic failure. It indeed does not need to mention rclone, but does need to specifically call out what the...

Yeah, I'm not sure it's super important to give an exact error message for this scenario, just that we shouldn't give such a generic one. Something closer to: > There...

In that users can just use the standard CNAME with their own Cloudflare account? I guess we'll see. I had a user note that they had problems using their own...