Documentation of QR bugged
See original GitHub issueThe Documentation of jax.numpy.linalg.qr
seems to be bugged.
The Documentation of numpy.linalg.qr
contains a bullet point list when explaining the mode
argument.
That seems to get lost when wrapping qr
in jax.numpy.linalg
The docstring in the onp implementation contains a blank line. Maybe that causes the problem?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
9 reasons Why Your QR Code is Not Working - Beaconstac blog
Even the most advanced QR Code scanners cannot scan QR Codes if not created correctly. Or was it the faulty QR Code generator?...
Read more >12 Reasons why your QR code is not working
QR codes are not working for a variety of reasons. These codes are developed to be scanned by smartphone gadgets.
Read more >Common QR Code Scanning Problems and How to Fix Them
Is your QR Code not working? Here is an overview on common QR Code scanning problems and how to solve them in this...
Read more >Unable to Scan QR Code? Here's How to Fix a QR Code.
QR Code Scanning Problems · iPhone Won't Scan QR Code: How to Fix · QR Code Not Working On Android: How to Fix...
Read more >Code of QR codes bugged? – Adobe InDesign
Code of QR codes bugged? I use ID 2023 on a mac. I want to generate a vCard and have to use v3.0...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It looks to me like the
qr
documentation is rendering correctly at head. Closing, since I assume this issue is now stale.I fixed a loophole in https://github.com/Jakob-Unfried/jax/commit/63d8608b8c25c531a55a77f14f9a19257d955344
Any ideas how to test this, without manually looking at every page of the docs…?