Using the documented way of creating links styled as buttons as seen in https://next.material-ui.com/guides/routing/#button adds wrong role on the rendered element. Specifically it adds role="button" making the link undiscoverable from google crawlers. I would at least hope that it was documented that I have to manually type `ro

Proof read transcribed code of UPDATE_PROGRAM against scans

Lines: 548
Page: 1386—1396 (10)

Reduced quality scans can be found here

• nvim --version:

NVIM v0.5.0-dev+1339-g5d9c56012
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/T
ools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe /DWIN32 /D_WINDOWS /W3 /MD /Zi /O2
/Ob1 /DNDEBUG /W3 -D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

npm-bcrypt package is only used in accounts-password and internally it falls back to bcryptjs which hasn't been updated in a while. So wouldn't it be better if we simply added a new npm dependency to accounts-password with bcrypt and deprecated

https://docs.scrapy.org/en/latest/topics/spiders.html#crawlspider has a warning block that includes the "New in version" line.

Both indenting the warning block (not sure what's the best practice for the indentation here; also, XMLFeedSpider below has the same block which should have the same indentation I think) and moving versionadded before it (I think I don't like it) will work but I don't

Describe the bug
Using xframe ALLOW-FROM throws error in console: Invalid 'X-Frame-Options' header encountered when loading 'https://api.dev.mysite.com/uploads/my-file.pdf': 'ALLOW-FROM dev.mysite.com' is not a recognized directive. The header will be ignored.

https://strapi.io/documentation/v3.x/concepts/middlewares.html#response-middlewares
instructions for xframe indicate `ALLOW-FR

Environment

Browsers: Chrome 91.0.4472.106
OS: Linux x86_64

Steps to reproduce

Two sections of the documentation are at odds with each other about whether "filled" type text fields can use the "prepend-icon" and "append-icon" props.

Expected Behavior

The two sections should be in agreement about the functionality; if one of them is just phrased badly, it should be

Description:

Whenever I change any of the room info (description, announcement, etc.) this resets the room setting which is supposed to hide system messages.

Steps to reproduce:

1. Go to "Room info" in a channel where you have privileges to change the room info.
2. Toggle on the "Hide system messages" setting. Confirm that this change itself is not posted in the channel.
3. Close