Denis Cornehl

> Instead of imposing this extra JS code in the front-end for everyone, why not instead increase what the GUI tests cover (not much currently)? I definitely see that the...

This definitely happens regularly, probably more often when our queue is longer:

small update here: While digging into this issue I discovered one thing: after a build, we're already fetching the release-data from crates.io, and updating our release-record with the yank-status from...

@Nemo157 from what I see in the comments this build failure was not a docs.rs issue? So we can close this? Or did this issue grow into "we need to...

From what I see this would involve rewriting the image-tags in the HTML, or hooking into rustdoc in how it generates the tags. Both would be (I think) subject to...

@maxdeviant I have a LSP usecase and would like to know if this should work at the moment, of after the language server selection feature. I want to add `ruff-lsp`...

> I tried killing `pyright` without luck too. > > ```json > "languages": { > "Python": { > "language_servers": ["ruff-lsp", "pylsp", "!pyright"] > } > } > ``` my understanding...

> It would be nice to be able to register arbitrary language servers simply by creating an entry for them under `"lsp"` and providing a path to a local binary....

when having multiple LSP it would be cool to be able to configure which to use for which use-case: - for formatting it's probably enough to select one - for...

Thank you for the report! Docs.rs currently only builds `x86_64-unknown-linux-gnu` natively and uses cross-compilation for all other targets (see [here](https://docs.rs/about/builds#cross-compiling)). I see you fixed this (e.g. worked around the limitation)...