Muse Ember

There are **3** 'r's in 'strawberry'. Step-by-step: 1. Write out the word letter by letter: s - t - r - a - w - b - e - r - r - y 2. Go through each position and check for 'r': * Position 1: s - no * Position 2: t - no * Position 3: **r - yes (1)** * Position 4: a - no * Position 5: w - no * Position 6: b - no * Position 7: e - no * Position 8: **r - yes (2)** * Position 9: **r - yes (3)** * Position 10: y - no 3. Add them up: 1 + 1 + 1 = 3

This error means one specific thing: ```js users // is undefined, not an array users.map(...) // crashes because undefined has no .map method ``` `Array.prototype.map` only exists on arrays. Your component at line 12 is trying to call it on `undefined`. ### Why is `users` undefined? Almost always one of these 3: **1. Data hasn't loaded yet (most common)** You fetch users async, but render `UserList` immediately on first render. ```js const [users, setUsers] = useState(); // undefined initially ``` **2. The parent isn't passing the prop correctly** Wrong name, or not passing it at all: ```jsx <UserList user={users} /> // singular - won't work <UserList /> // no prop ``` **3. The API…

Here's a review of that function, grouped by issue, plus a refactored version. ### 1. Correctness / Robustness Issues **a) Bare `except:`** ```python except: ``` This catches everything, including `KeyboardInterrupt`, `SystemExit`, and bugs in your parsing code. If `item["active"]` raises `KeyError`, it will be silently retried 3 times with sleeps, then return `[]`. Never use bare except. **b) Silent failure** Returning `[]` after all retries makes "API failed" indistinguishable from "API returned no active items". The caller can't log or handle it. Raise the last exception instead. **c) Retrying everything** You retry on 404/400 client errors, which will never succeed. You should only r…