diff --git a/personal/projects/personal-os/personal-os-first-day.md b/personal/projects/personal-os/personal-os-first-day.md index 07fae0bb..c39b0123 100644 --- a/personal/projects/personal-os/personal-os-first-day.md +++ b/personal/projects/personal-os/personal-os-first-day.md @@ -31,7 +31,7 @@ ## Где смотреть неделю и сбои - [Weekly Review](http://127.0.0.1:4317/#/weekly-review) показывает распределение работы, ревью и резерва по дням. В плане дня пометка **Из недельного плана** показывает, какие действия пришли из этой раскладки. Здесь же видны обязательства, которые не помещаются к сроку. Удержанный недельный план показывает причину и ждёт пересчёта. -- В **Из обсуждений → Свежесть обсуждений** видно, сколько архивных пакетов ждут полного чтения и сколько готовы к первому разбору. +- В **Из обсуждений → Свежесть обсуждений** видно, сколько архивных пакетов ждут полного чтения и сколько готовы к первому разбору. Раскройте **Причины неполного чтения**, чтобы увидеть пробелы источника. - Если уведомление о плане не пришло, откройте [план напрямую](http://127.0.0.1:4317/#/my-tasks?plan=1). В **Приёмке пилота** отдельно видны запрос и подтверждение доставки. Для постоянного показа настройка на Mac находится в **Системные настройки → Уведомления → Personal OS → Постоянно**. - Если локальная страница не открывается на рабочем Mac, либо актуальный план не появился после штатного пересчёта, зафиксируйте время, страницу и текст статуса. При передаче достаточно сообщения об ошибке без содержимого рабочих карточек. diff --git a/personal/projects/personal-os/personal-os-fixes-2026-11-13.md b/personal/projects/personal-os/personal-os-fixes-2026-11-13.md index 25cbb066..6831f999 100644 --- a/personal/projects/personal-os/personal-os-fixes-2026-11-13.md +++ b/personal/projects/personal-os/personal-os-fixes-2026-11-13.md @@ -2,6 +2,14 @@ Состояние: **исполнение продолжается; полная приёмка пока не подтверждена**. Основание — [аудит 17 проблем](personal-os-implementation-audit-2026-11-13.md). Этот журнал описывает исправления после исходного аудита; старые проверки сохранены как история. +## 17 ноября, после 12:37 по Бишкеку — диагностика чтения архивных веток + +- Из 3 033 сохранённых снимков Mattermost восстановлено 1 737 веток. Срез 12:31:19 показал 234 полностью сверенные ветки, 874 последних ответа 404, 619 веток без квитанции полного чтения, 10 с изменениями после чтения и 6 без загруженного корня. Причины могут пересекаться. За 26 проходов 17 ноября в журнале есть 311 ответов 404 и одно успешное полное чтение. Это квитанции того же штатного источника. Ответ 404 не позволяет заключить, что обязательств в обсуждении не было. +- Причины неполноты добавлены в квитанции снимка и в «Из обсуждений → Свежесть обсуждений → Причины неполного чтения». Показываются счётчики по типам. В повторе порядка загрузки более старый полный снимок раньше затирал новый текст и скрывал новый ответ. Он теперь сохраняет новые события и удерживает статус полноты до перечитывания. Штатный доступ Mattermost остаётся read-only. +- Прошли 338 тестов Python и 29 целевых тестов Node, включая браузерное открытие причин. Рабочий GET после наблюдателя `01a1e832-b702-4b1e-8286-110e3c59e144` (захват 12:39:12) вернул 864 архивных пакета с 404, 619 без квитанции, 10 изменившихся и 6 без корня. Единица счёта здесь архивный пакет. Квитанция `discussion-thread-gaps-20261117.json`. Открытый шаг — проверить продвижение повторной загрузки и отдельно установить причину устойчивых 404. Для прямой проверки Outlook и показа уведомления рабочий сеанс в 12:37 заблокирован. +- Проверка переносимости из экспорта ветки обнаружила отсутствие обещанного `config.example.json`. Добавлен шаблон с вымышленными различимыми GID и инструкцией для чистого запуска. Рабочая конфигурация не изменялась. +- В чистом экспорте отобранного дерева с шаблоном вместо рабочей конфигурации прошли 338 тестов Node и 338 Python. Пропущено 56 Node-проверок, включая интеграционные с дополнительными условиями запуска. Квитанция `checkpoint-test-20261117.log`. Резервные копии БД, локальные квитанции и сгенерированный отчёт времени остаются локальными. + ## 17 ноября, после 12:26 по Бишкеку — состояние источника сигналов общения - Локальная очередь не показывала, подключён ли источник общения. После отключения старая подсказка оставалась активной до исходного срока. Теперь GET показывает выключенный, ожидающий сводки или подключённый источник. Активная подсказка видна только при совпадении источника с тем, на котором она возникла. В ответе отсутствуют тексты реплик. diff --git a/personal/projects/personal-os/personal-os-production-acceptance.md b/personal/projects/personal-os/personal-os-production-acceptance.md index c8727396..c15b1f15 100644 --- a/personal/projects/personal-os/personal-os-production-acceptance.md +++ b/personal/projects/personal-os/personal-os-production-acceptance.md @@ -11,9 +11,13 @@ ## Объём оставшейся реализации и проверок - Неделя и день рассчитываются из одной ревизии в штатном E5. Проверка решения по карьерной возможности и её включения в план прошла на изолированном контуре. Нужны подходящее рабочее основание и выбор владельца для живого прохода. Для подготовки к встрече уже работает кнопка в Weekly Review. Автоматическая подготовка ждёт подтверждённого источника встречи. -- Довести полноту архива обсуждений. Штатный разбор оставил 1 493 архивных пакета в ожидании полного чтения и сократил очередь первого разбора со 182 до 174. Следующая правка — показать причины неполного чтения и проверить продвижение повторного чтения по архивным корням. Claims проверяются по текущему методу, точному входу и сохранению реальных решений. +- Довести полноту архива обсуждений. Штатный разбор оставил 1 493 архивных пакета в ожидании полного чтения и сократил очередь первого разбора со 182 до 174. В очереди добавлены причины неполноты. Ответ Mattermost 404 удерживается как пробел источника. Claims проверяются по текущему методу, точному входу и сохранению реальных решений. - Завершить проверку реальных источников и первого дня. Нужны разрешённый ответ Outlook free/busy, нативный показ уведомления, пользовательский запрос личному Telegram-боту, вечерняя сверка, фактическая полезность сигналов и пять реальных рабочих дней. Для сигнала общения остаётся подключить согласованный локальный источник. [Инструкция и демонстрация первого рабочего дня](personal-os-first-day.md) +## 17 ноября, после 12:37 по Бишкеку — причины неполного чтения Mattermost + +- Локальное воспроизведение архива дало 234 полностью сверенные ветки из 1 737. Для 874 последняя загрузка вернула 404, у 619 отсутствует квитанция полного чтения. Десять веток изменились после чтения. Отдельные причины могут совпадать у одного пакета. Штатный снимок 12:39 вернул те же категории в рабочем API по архивным пакетам. Старый снимок больше не заменяет новую версию записи. Mac остаётся заблокирован. [Журнал исправлений](personal-os-fixes-2026-11-13.md) + ## 17 ноября, после 12:26 по Бишкеку — состояние сигналов общения - Рабочий API и интерфейс показывают, что анализ общения с агентами выключен. При отключении или смене источника прежняя активная подсказка исчезает из локальной очереди. Подключение реального источника и полезность подсказок предстоит проверить. Штатный E5 `c3b0ef42-f99a-4ff0-9bb5-cfe2266aefe8` снова подтвердил общую ревизию дня и недели. [Журнал исправлений](personal-os-fixes-2026-11-13.md) diff --git a/work/zoom-transcripts/index.json b/work/zoom-transcripts/index.json index 016faecc..b1cd0955 100644 --- a/work/zoom-transcripts/index.json +++ b/work/zoom-transcripts/index.json @@ -122,8 +122,8 @@ "note_modified_at": "2026-11-12T10:14:13.001Z", "source_url": "https://us01mynotes.zoom.us/rJFn9D3lRJmnlCMSomhPsw", "folder": "undated Michal Smaga's Personal Meeting Room rJFn9D3lRJmnlCMSomhPsw", - "sha256": "95c17a300c3de74483cc899f8d8cb9b878ee47d0bd952ff62c5f89c507c3c5ca", - "cues": 3 + "sha256": "55727e14d28c8dfe03f20623c696d1e756da52b8e985ccafe454a70f04c58693", + "cues": 60 }, "DLwAbUQ_RZ6X_D63xiX_Ww": { "title": "Max Tsoy's Personal Meeting Room", diff --git a/work/zoom-transcripts/sync-status.json b/work/zoom-transcripts/sync-status.json index 4793b24e..a5ed2e07 100644 --- a/work/zoom-transcripts/sync-status.json +++ b/work/zoom-transcripts/sync-status.json @@ -1 +1 @@ -{"observed_at":"2026-11-17T06:09:17.535Z","scanned":29,"imported":1,"skipped":28,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":84,"complete":true,"terminal_cursor":true},{"name":"Shared with me","pages":1,"notes":0,"complete":true,"terminal_cursor":true},{"name":"Starred","pages":1,"notes":0,"complete":true,"terminal_cursor":true}],"discovered":84,"gaps":[],"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"} \ No newline at end of file +{"observed_at":"2026-11-17T06:40:42.593Z","scanned":29,"imported":1,"skipped":28,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":84,"complete":true,"terminal_cursor":true},{"name":"Shared with me","pages":1,"notes":0,"complete":true,"terminal_cursor":true},{"name":"Starred","pages":1,"notes":0,"complete":true,"terminal_cursor":true}],"discovered":84,"gaps":[],"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"} \ No newline at end of file diff --git a/work/zoom-transcripts/undated Michal Smaga's Personal Meeting Room rJFn9D3lRJmnlCMSomhPsw/transcript.json b/work/zoom-transcripts/undated Michal Smaga's Personal Meeting Room rJFn9D3lRJmnlCMSomhPsw/transcript.json index d4567fcd..79921b2b 100644 --- a/work/zoom-transcripts/undated Michal Smaga's Personal Meeting Room rJFn9D3lRJmnlCMSomhPsw/transcript.json +++ b/work/zoom-transcripts/undated Michal Smaga's Personal Meeting Room rJFn9D3lRJmnlCMSomhPsw/transcript.json @@ -23,6 +23,291 @@ "time": "16:15:28", "speaker": "Michal Smaga", "text": "Okay. So without matching, we may not see all the issues. Because it's, like…" + }, + { + "time": "16:15:36", + "speaker": "Alex Martemyanov", + "text": "I don't… Yes, uh…" + }, + { + "time": "16:15:39", + "speaker": "Michal Smaga", + "text": "Because if you have two tabs for the same domain, one may load, and if one fails, you will get, like, the the error won't be reported. Right?" + }, + { + "time": "16:15:47", + "speaker": "Alex Martemyanov", + "text": "Yes, kind of it. So basically, we could keep the same matching algorithm if we receive it twice. for the same URL, just consider it healthy, and, uh, not report. It would… it would work, basically. So… But yeah, this is an extra mile." + }, + { + "time": "16:16:07", + "speaker": "Michal Smaga", + "text": "And in the matching… And the matching would require, like, the web extension change as well, right?" + }, + { + "time": "16:16:14", + "speaker": "Alex Martemyanov", + "text": "Yes. So, the changes to send the… to send the window ID and all the window IDs." + }, + { + "time": "16:16:16", + "speaker": "Michal Smaga", + "text": "Just to report the…" + }, + { + "time": "16:16:22", + "speaker": "Alex Martemyanov", + "text": "In the sequence that we've got them." + }, + { + "time": "16:16:25", + "speaker": "Michal Smaga", + "text": "Yeah, yeah." + }, + { + "time": "16:16:26", + "speaker": "Alex Martemyanov", + "text": "So we could match to arrays. in how the web extension IDs given in order, and how they were accessed from the upside in the same order, but different IDs." + }, + { + "time": "16:16:35", + "speaker": "Michal Smaga", + "text": "Okay. Yeah, but this is kind of, like, an optional, or do you suggest doing that? Okay." + }, + { + "time": "16:16:44", + "speaker": "Alex Martemyanov", + "text": "Yeah, yeah, this is an optional. I'm gonna comment in the design for matching, and it probably won't be included in the pull request I'm gonna open soon." + }, + { + "time": "16:16:50", + "speaker": "Michal Smaga", + "text": "Okay." + }, + { + "time": "16:16:56", + "speaker": "Alex Martemyanov", + "text": "So, currently, there is two… To ready ones." + }, + { + "time": "16:17:00", + "speaker": "Michal Smaga", + "text": "Two PRs, yeah." + }, + { + "time": "16:17:03", + "speaker": "Alex Martemyanov", + "text": "To be ours mostly or not to. I think it's only one, right? Second one is not there yet." + }, + { + "time": "16:17:13", + "speaker": "Michal Smaga", + "text": "No, there are two." + }, + { + "time": "16:17:15", + "speaker": "Alex Martemyanov", + "text": "There is two. Okay, probably the second one maybe not pushed. I'll just check a bit later." + }, + { + "time": "16:17:22", + "speaker": "Michal Smaga", + "text": "There's remove diagnostics and remove ineffective fixes." + }, + { + "time": "16:17:33", + "speaker": "Alex Martemyanov", + "text": "Yeah, let me just check it quickly. If it's up to date. Yeah, so remove, uh, remove fixes, the first one. It removes the feature flags and the fixes that weren't there, so it's mostly removal. It shouldn't be nothing complicated. Yeah, the second one is also actual. It removes the metrics. So, it's meant to be merged." + }, + { + "time": "16:18:06", + "speaker": "Michal Smaga", + "text": "Okay, so… so there will be, like, a third… there will be a third one for the… for the permanent ones. Okay." + }, + { + "time": "16:18:09", + "speaker": "Alex Martemyanov", + "text": "There will be third one re-adding. Yes, yes. So, and I'm…" + }, + { + "time": "16:18:13", + "speaker": "Michal Smaga", + "text": "I've started setting up the testing for the PR, so I'll be reviewing it shortly, so we have it merged soon. Uh, yeah, other than that, I will catch up on the tech design and to see, like, uh, if I understood them correctly. And yeah." + }, + { + "time": "16:18:31", + "speaker": "Alex Martemyanov", + "text": "Okay, okay, great. Thanks." + }, + { + "time": "16:18:33", + "speaker": "Michal Smaga", + "text": "So do you have anything, like, blocking you for moving forward to the third one, or…" + }, + { + "time": "16:18:40", + "speaker": "Alex Martemyanov", + "text": "Not really. Uh, so I was investigating, uh, how to… how to match it exactly, how far should we go. Probably we shouldn't, uh, go with it on the start PR." + }, + { + "time": "16:18:40", + "speaker": "Michal Smaga", + "text": "We need to…" + }, + { + "time": "16:18:52", + "speaker": "Alex Martemyanov", + "text": "And it could be totally optional." + }, + { + "time": "16:18:56", + "speaker": "Michal Smaga", + "text": "Yeah. I I I would discover the the index thing for, like, it's good that you have, like, research. It's so, like, doing, like, some kind of, like, a brain dump of, like, the approach or, like, having, like, some spec for it. I think, maximum." + }, + { + "time": "16:18:56", + "speaker": "Alex Martemyanov", + "text": "And, yeah." + }, + { + "time": "16:19:13", + "speaker": "Michal Smaga", + "text": "Drop the link to, like, earlier discussion that we had, like, earlier this year, like, uh… We were figuring out that it wasn't, like, easily possible, so we we kind of, like, moved away from it. So maybe it would be worthy to to to, like, follow up it separately." + }, + { + "time": "16:19:28", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm." + }, + { + "time": "16:19:29", + "speaker": "Michal Smaga", + "text": "Uh, on Tuesday, like, Russell was asking about the scope of the project and, like, when we finish up, so I would probably, like. Focus on like, like, like. Basically, focus on wrapping stuff up and, like, probably having a post-mortem, like, next week. So so I think this is, like, of a priority. And, yeah, and setting up the, like, the yeah. Just just wrap up the project, and probably we can do some additional work after that." + }, + { + "time": "16:20:00", + "speaker": "Alex Martemyanov", + "text": "Yeah, okay. Okay, so I will just, my main question or my main point here was to think on the metric and how it works. So basically, we load a page, and uh… we report it after we close the tab, or if we navigate somewhere else. And if… The page was alive, was up for more than 30 seconds. So we had enough time for extension to load, and it didn't receive any CPM messages. It would be reported as broken. you… It should probably give us a general idea if how the trend is going." + }, + { + "time": "16:20:43", + "speaker": "Michal Smaga", + "text": "And if you close the tab or navigate away within the 30 seconds, we don't report it, like, for nothing, right?" + }, + { + "time": "16:20:52", + "speaker": "Alex Martemyanov", + "text": "Oh. I think so. Yeah." + }, + { + "time": "16:20:59", + "speaker": "Michal Smaga", + "text": "I'll check… yeah, I'll try to give you the feedback on the tech design, so probably, like, this is something that we want to…" + }, + { + "time": "16:20:59", + "speaker": "Alex Martemyanov", + "text": "So we can…" + }, + { + "time": "16:21:07", + "speaker": "Michal Smaga", + "text": "like, clarify this week, so, like, probably Monday you can, like, implement the… Sorry. Eat precisely, and then we are good, I think." + }, + { + "time": "16:21:18", + "speaker": "Alex Martemyanov", + "text": "Yeah, so it's most ready here locally, and I think today, later today, I'm going to open. Open it up and ping you and update the tech designs. So, yeah, there is some exception for the reporting, like a page or private pages." + }, + { + "time": "16:21:30", + "speaker": "Michal Smaga", + "text": "Okay." + }, + { + "time": "16:21:37", + "speaker": "Alex Martemyanov", + "text": "Alright. Or session restoration, or back navigation, or history navigation, so basically the ones that, uh, loaded from cache, and we had some… problems with them and race conditions." + }, + { + "time": "16:21:50", + "speaker": "Michal Smaga", + "text": "Okay." + }, + { + "time": "16:21:50", + "speaker": "Alex Martemyanov", + "text": "And then… But for general navigations, and yeah, so there's page lifetime, let's… It should be more than 30 seconds. If we had it two times in a row for different tabs, it means, like, permanent breakage of the extension." + }, + { + "time": "16:22:07", + "speaker": "Michal Smaga", + "text": "And for the page restoration, do you detect it and act differently?" + }, + { + "time": "16:22:07", + "speaker": "Alex Martemyanov", + "text": "Should give… Uh, it's me, uh… So we have this wait time before navigation, so we expect the extension to load. And it's limited for 5 seconds, but if it takes longer, it may still load after the page loads from cache, and it means it won't go through the page deload path and… Won't activate the extension. So, the… CPM won't be fired up and CUTIBRANCE won't be handled sometimes." + }, + { + "time": "16:22:46", + "speaker": "Michal Smaga", + "text": "Mm-hmm. Yeah." + }, + { + "time": "16:22:48", + "speaker": "Alex Martemyanov", + "text": "Thank you. It was, uh, like, our best effort, and it seems unreasonable to keep it… to keep it waiting longer than 5 seconds for users, uh, to extend this type of… this startup time. But there are still some reports. It seems like it went slightly down, but not really fixing all the cases. But those are not permanent, mostly." + }, + { + "time": "16:23:18", + "speaker": "Michal Smaga", + "text": "Okay, yeah. Hmmm…" + }, + { + "time": "16:23:25", + "speaker": "Alex Martemyanov", + "text": "Yeah, that should be it, I guess." + }, + { + "time": "16:23:29", + "speaker": "Michal Smaga", + "text": "Okay. So, I'm off to to testing the PRs and and let you know." + }, + { + "time": "16:23:33", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm." + }, + { + "time": "16:23:34", + "speaker": "Michal Smaga", + "text": "Cool. If you have anything I can help you with, uh, just feel free to ping me. And…" + }, + { + "time": "16:23:35", + "speaker": "Alex Martemyanov", + "text": "Okay, thanks." + }, + { + "time": "16:23:41", + "speaker": "Michal Smaga", + "text": "Maybe if there's, like, we need another discussion with Max or whatever, like, we can, like, chat later or tomorrow morning." + }, + { + "time": "16:23:50", + "speaker": "Alex Martemyanov", + "text": "Sure, I'll ping him the task center. Thank you, Anthony." + }, + { + "time": "16:23:53", + "speaker": "Michal Smaga", + "text": "Okay, cool. Thank you." + }, + { + "time": "16:23:56", + "speaker": "Alex Martemyanov", + "text": "Okay. Yep. Thank you." } ] } diff --git a/work/zoom-transcripts/undated Michal Smaga's Personal Meeting Room rJFn9D3lRJmnlCMSomhPsw/transcript.md b/work/zoom-transcripts/undated Michal Smaga's Personal Meeting Room rJFn9D3lRJmnlCMSomhPsw/transcript.md index 17c56b09..e9023fdf 100644 --- a/work/zoom-transcripts/undated Michal Smaga's Personal Meeting Room rJFn9D3lRJmnlCMSomhPsw/transcript.md +++ b/work/zoom-transcripts/undated Michal Smaga's Personal Meeting Room rJFn9D3lRJmnlCMSomhPsw/transcript.md @@ -15,3 +15,60 @@ source: "https://us01mynotes.zoom.us/rJFn9D3lRJmnlCMSomhPsw" - **16:14:12 · Michal Smaga:** read the text. designs yet. So I have, like, maybe a dumb question. Like, why is the the the, like, figuring out the specific top index and, like, matching the tops required for that? - **16:14:23 · Alex Martemyanov:** Basically, I was trying to make it as stable as possible to… To make it, like, live permanently there. And, uh, as Max told, we have, uh, some problem on, or maybe false positives, uh, for, uh, unmatched tab, so the matching is done by URL, basically. And if you open the same tab twice, with the same URL, it would be ambiguous at that point. And uh… so in the previous metrics, it's used to… Um, reports, like, uh, healthy, if, uh, we have… two consequently awaiting tabs. So, one could be unhealthy, but we won't report it anyways if we receive the message twice. But to make it kind of 100% bulletproof, and as well in other places, if we match exactly the web extension tab against the actual tab, it would. - **16:15:28 · Michal Smaga:** Okay. So without matching, we may not see all the issues. Because it's, like… +- **16:15:36 · Alex Martemyanov:** I don't… Yes, uh… +- **16:15:39 · Michal Smaga:** Because if you have two tabs for the same domain, one may load, and if one fails, you will get, like, the the error won't be reported. Right? +- **16:15:47 · Alex Martemyanov:** Yes, kind of it. So basically, we could keep the same matching algorithm if we receive it twice. for the same URL, just consider it healthy, and, uh, not report. It would… it would work, basically. So… But yeah, this is an extra mile. +- **16:16:07 · Michal Smaga:** And in the matching… And the matching would require, like, the web extension change as well, right? +- **16:16:14 · Alex Martemyanov:** Yes. So, the changes to send the… to send the window ID and all the window IDs. +- **16:16:16 · Michal Smaga:** Just to report the… +- **16:16:22 · Alex Martemyanov:** In the sequence that we've got them. +- **16:16:25 · Michal Smaga:** Yeah, yeah. +- **16:16:26 · Alex Martemyanov:** So we could match to arrays. in how the web extension IDs given in order, and how they were accessed from the upside in the same order, but different IDs. +- **16:16:35 · Michal Smaga:** Okay. Yeah, but this is kind of, like, an optional, or do you suggest doing that? Okay. +- **16:16:44 · Alex Martemyanov:** Yeah, yeah, this is an optional. I'm gonna comment in the design for matching, and it probably won't be included in the pull request I'm gonna open soon. +- **16:16:50 · Michal Smaga:** Okay. +- **16:16:56 · Alex Martemyanov:** So, currently, there is two… To ready ones. +- **16:17:00 · Michal Smaga:** Two PRs, yeah. +- **16:17:03 · Alex Martemyanov:** To be ours mostly or not to. I think it's only one, right? Second one is not there yet. +- **16:17:13 · Michal Smaga:** No, there are two. +- **16:17:15 · Alex Martemyanov:** There is two. Okay, probably the second one maybe not pushed. I'll just check a bit later. +- **16:17:22 · Michal Smaga:** There's remove diagnostics and remove ineffective fixes. +- **16:17:33 · Alex Martemyanov:** Yeah, let me just check it quickly. If it's up to date. Yeah, so remove, uh, remove fixes, the first one. It removes the feature flags and the fixes that weren't there, so it's mostly removal. It shouldn't be nothing complicated. Yeah, the second one is also actual. It removes the metrics. So, it's meant to be merged. +- **16:18:06 · Michal Smaga:** Okay, so… so there will be, like, a third… there will be a third one for the… for the permanent ones. Okay. +- **16:18:09 · Alex Martemyanov:** There will be third one re-adding. Yes, yes. So, and I'm… +- **16:18:13 · Michal Smaga:** I've started setting up the testing for the PR, so I'll be reviewing it shortly, so we have it merged soon. Uh, yeah, other than that, I will catch up on the tech design and to see, like, uh, if I understood them correctly. And yeah. +- **16:18:31 · Alex Martemyanov:** Okay, okay, great. Thanks. +- **16:18:33 · Michal Smaga:** So do you have anything, like, blocking you for moving forward to the third one, or… +- **16:18:40 · Alex Martemyanov:** Not really. Uh, so I was investigating, uh, how to… how to match it exactly, how far should we go. Probably we shouldn't, uh, go with it on the start PR. +- **16:18:40 · Michal Smaga:** We need to… +- **16:18:52 · Alex Martemyanov:** And it could be totally optional. +- **16:18:56 · Michal Smaga:** Yeah. I I I would discover the the index thing for, like, it's good that you have, like, research. It's so, like, doing, like, some kind of, like, a brain dump of, like, the approach or, like, having, like, some spec for it. I think, maximum. +- **16:18:56 · Alex Martemyanov:** And, yeah. +- **16:19:13 · Michal Smaga:** Drop the link to, like, earlier discussion that we had, like, earlier this year, like, uh… We were figuring out that it wasn't, like, easily possible, so we we kind of, like, moved away from it. So maybe it would be worthy to to to, like, follow up it separately. +- **16:19:28 · Alex Martemyanov:** Mm-hmm. +- **16:19:29 · Michal Smaga:** Uh, on Tuesday, like, Russell was asking about the scope of the project and, like, when we finish up, so I would probably, like. Focus on like, like, like. Basically, focus on wrapping stuff up and, like, probably having a post-mortem, like, next week. So so I think this is, like, of a priority. And, yeah, and setting up the, like, the yeah. Just just wrap up the project, and probably we can do some additional work after that. +- **16:20:00 · Alex Martemyanov:** Yeah, okay. Okay, so I will just, my main question or my main point here was to think on the metric and how it works. So basically, we load a page, and uh… we report it after we close the tab, or if we navigate somewhere else. And if… The page was alive, was up for more than 30 seconds. So we had enough time for extension to load, and it didn't receive any CPM messages. It would be reported as broken. you… It should probably give us a general idea if how the trend is going. +- **16:20:43 · Michal Smaga:** And if you close the tab or navigate away within the 30 seconds, we don't report it, like, for nothing, right? +- **16:20:52 · Alex Martemyanov:** Oh. I think so. Yeah. +- **16:20:59 · Michal Smaga:** I'll check… yeah, I'll try to give you the feedback on the tech design, so probably, like, this is something that we want to… +- **16:20:59 · Alex Martemyanov:** So we can… +- **16:21:07 · Michal Smaga:** like, clarify this week, so, like, probably Monday you can, like, implement the… Sorry. Eat precisely, and then we are good, I think. +- **16:21:18 · Alex Martemyanov:** Yeah, so it's most ready here locally, and I think today, later today, I'm going to open. Open it up and ping you and update the tech designs. So, yeah, there is some exception for the reporting, like a page or private pages. +- **16:21:30 · Michal Smaga:** Okay. +- **16:21:37 · Alex Martemyanov:** Alright. Or session restoration, or back navigation, or history navigation, so basically the ones that, uh, loaded from cache, and we had some… problems with them and race conditions. +- **16:21:50 · Michal Smaga:** Okay. +- **16:21:50 · Alex Martemyanov:** And then… But for general navigations, and yeah, so there's page lifetime, let's… It should be more than 30 seconds. If we had it two times in a row for different tabs, it means, like, permanent breakage of the extension. +- **16:22:07 · Michal Smaga:** And for the page restoration, do you detect it and act differently? +- **16:22:07 · Alex Martemyanov:** Should give… Uh, it's me, uh… So we have this wait time before navigation, so we expect the extension to load. And it's limited for 5 seconds, but if it takes longer, it may still load after the page loads from cache, and it means it won't go through the page deload path and… Won't activate the extension. So, the… CPM won't be fired up and CUTIBRANCE won't be handled sometimes. +- **16:22:46 · Michal Smaga:** Mm-hmm. Yeah. +- **16:22:48 · Alex Martemyanov:** Thank you. It was, uh, like, our best effort, and it seems unreasonable to keep it… to keep it waiting longer than 5 seconds for users, uh, to extend this type of… this startup time. But there are still some reports. It seems like it went slightly down, but not really fixing all the cases. But those are not permanent, mostly. +- **16:23:18 · Michal Smaga:** Okay, yeah. Hmmm… +- **16:23:25 · Alex Martemyanov:** Yeah, that should be it, I guess. +- **16:23:29 · Michal Smaga:** Okay. So, I'm off to to testing the PRs and and let you know. +- **16:23:33 · Alex Martemyanov:** Mm-hmm. +- **16:23:34 · Michal Smaga:** Cool. If you have anything I can help you with, uh, just feel free to ping me. And… +- **16:23:35 · Alex Martemyanov:** Okay, thanks. +- **16:23:41 · Michal Smaga:** Maybe if there's, like, we need another discussion with Max or whatever, like, we can, like, chat later or tomorrow morning. +- **16:23:50 · Alex Martemyanov:** Sure, I'll ping him the task center. Thank you, Anthony. +- **16:23:53 · Michal Smaga:** Okay, cool. Thank you. +- **16:23:56 · Alex Martemyanov:** Okay. Yep. Thank you.