Using 'yarn amo', the homepage does not load correctly.
See original GitHub issueThe different sections on the home page, i.e.: “Most Popular Extensions” does not show any extensions when viewing it from the homepage.
The URL request at http://olympia.dev/api/v3/addons/search/?app=firefox&appversion=58.0&page_size=4&sort=hotness&type=extension&lang=en-US
returns a 200 however the loading text never goes away.
It would be nice to make sure these sections work as they are a part of the integration tests.
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
reactjs - I can't open website on local by using "yarn start"
1 Answer 1 ... In Next.js there is none react-router-dom (and its BrowserRouter, etc.). It has its own router solution and it is...
Read more >Getting started with web-ext | Firefox Extension Workshop
This command displays the device ID for your connected Android device or devices. If you don't see a list of device IDs, make...
Read more >Why Won't This Web Site Load Correctly (and How Can I Fix It)?
Dear Lifehacker, My cable company's web site doesn't work in Chrome, and it's really annoying. What's going on and how can I fix...
Read more >How to Build a Full Stack NFT Marketplace - V2 (2022)
When you run the deploy script command (while using the IPv6) you'll have to use that 'hardhat' modifier for the network vs localhost...
Read more >AMO YARN - Facebook
just now, we would love it if you could share our post. The club will launch in January 2023. Each Month we will...
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
Actually, I got this figured out. Looks like I wasn’t assigning a user to the generated collection.
This is likely because there is no data being returned by these requests on a new docker instance; our code should be smarter and catch it but it likely is assuming an empty result set means still loading (as this never happens in production) 😢