Nex-N2.6

# Counting the 'r's in "strawberry" Let me go through the word letter by letter: **s - t - r - a - w - b - e - r - r - y** | Position | Letter | Is it 'r'? | |----------|--------|------------| | 1 | s | No | | 2 | t | No | | 3 | **r** | ✅ Yes (1) | | 4 | a | No | | 5 | w | No | | 6 | b | No | | 7 | e | No | | 8 | **r** | ✅ Yes (2) | | 9 | **r** | ✅ Yes (3) | | 10 | y | No | ## Answer: **3** The reason people often miscount is that the "berry" part contains a **double r** ("berr-y"), which is easy to overlook. So: - 1 'r' in "straw" - 2 'r's in "berry" - **Total: 3 r's** 🍓

## What's causing the error `users` is `undefined` at the moment the component renders, and you're calling `.map()` on it. Since `undefined` has no `.map` method, JavaScript throws the `TypeError`. This almost always happens for one of these reasons: 1. **The parent isn't passing the `users` prop** (forgot it, or a typo like `user` vs `users`). 2. **Data is fetched asynchronously** — the component renders before the fetch resolves, so `users` is still `undefined` on the first render. 3. **Wrong data shape** — e.g., the API returns `{ data: [...] }` but you pass the whole response object, or the state was initialized as `undefined`/`null` instead of an array. ## How to fix it ### 1. Add…

Here's a review of your function, grouped by category, followed by a suggested rewrite. ## What's already good - You set an explicit `timeout` (many people forget this — it prevents hangs). - There's basic retry logic, and success returns immediately. ## Issues **Correctness / robustness** - **Bare `except:` is dangerous.** It catches *everything*, including `KeyboardInterrupt` and `SystemExit`, and it silently swallows real bugs — e.g., if `r.json()` fails because the body isn't JSON, or if `item["active"]` doesn't exist (`KeyError`). Those get "retried" pointlessly and then vanish into `[]`. Catch specific exceptions instead. - **`[]` is ambiguous.** The caller can't tell "no active ite…