[BLOG] Add hypothesis-array-api

[MarsBarLee]

Link to blog post, successful build.

Links to other Quansight blogs:

There is no need to check for Blog2Blog links due to updated website build.

Text styling

• The blog is written with plain language (where relevant).
• If there are headers, they use the proper header tags in order to do so (with only one level-one header).
• All links describe where they link to (for example, check the Quansight labs website).
• Any kind of styling that the author uses (for example, bold for emphasis) is consistent throughout the blog.

Non-text contents

• All content is represented as text (for example, images need alt text and videos need captions or descriptive transcripts).
• If there are emojis, there are not more than three in a row.
• Don't use flashing gifs or videos.
• If it were to be read as plain text, the blog still makes sense and no information is missing.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
consulting	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 9, 2023 at 6:46PM (UTC)
labs	❌ Failed (Inspect)			Feb 9, 2023 at 6:46PM (UTC)

[MarsBarLee]

I'm getting the Vercel build error: error [Error: [next-mdx-remote] error compiling MDX:

Full error message:

Unexpected character `0` (U+0030) after attribute name, 
expected a character that can start an attribute name, such as
a letter, `$`, or `_`; `=` to initialize a value; or the end of the tag

  316 |     >       assert nxp.all(a[1:] >= a[:-1])
  317 |     E       assert Array(False, dtype=bool)
> 318 |     E        +  where Array(False, dtype=bool) = <function all at 0x7f2d48cc2430>(Array([ 52,  78, 104, 130, 156, 182, 208, 234,   4], dtype=uint8) >= Array([ 26,  52,  78, 104, 130, 156, 182, 208, 234], dtype=uint8))
      |                                                                   ^
  319 |     E        +    where <function all at 0x7f2d48cc2430> = nxp.all
  320 |

Link to error

The context is showing the result of some code. Link to this section in the old blog website.

Similar problem to #647: output of code blocks formatted as plain text, not in code blocks, causing problems to Vercel