can I take this up?

Seems like this is an issue in the sphinx-hoverxref extension: readthedocs/sphinx-hoverxref#45.
If we can't wait for the upcoming release as mentioned in readthedocs/sphinx-hoverxref#45 (comment), we might want to try temporarily disabling it in our configuration.

If they have not released a fixed version by the time we are about to release Scrapy 2.1, we can change our documentation requirements temporarily to specify a Sphinx version older than 3, since we are not using anything specific of Sphinx 3 at the moment.

@anusha94 Given the circumstances, I think it makes sense for us to handle this from the core team.

If we can't wait for the upcoming release as mentioned in readthedocs/sphinx-hoverxref#45 (comment), we might want to try temporarily disabling it in our configuration

Hi! I'm one of the authors of sphinx-hoverxref. I've already released 0.2b that includes the fix for Sphinx 3.0. I took a look at the PR and saw that the new warnings made your build to fail (I'm sorry for that), and I created a new issue to take a deeper look at this at readthedocs/sphinx-hoverxref#58

Besides, I saw that you are using some custom roles/objects like :setting:, :signal: and others, and I wanted to let you know that you can enable hoverxref on those as well with the config hoverxref_roles. See https://sphinx-hoverxref.readthedocs.io/en/dirhtml/usage/#tooltip-on-custom-object

Happy that an amazing project like Scrapy is using this extension! Thanks for making Scrapy 😄

hey @elacuesta @Gallaecio I'm having the same issue, as I'm working on an issue regarding documentation. Can I be of any help to solve this issue?