From 6ea62582db9a59101157a27465ea4e6a68661814 Mon Sep 17 00:00:00 2001 From: Alexey Martemyanov Date: Fri, 20 Nov 2026 17:07:09 +0600 Subject: [PATCH] [2026-11-20] eagle: personal/projects/personal-os/personal-os-evidence/2026-11-19/follow-up-live-acceptance.md personal/projects/personal-os/personal-os-production-acceptance.md personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md personal/projects/personal-os/personal-os-tasks.md personal/projects/personal-os/personal-os-user-scenarios.md work/zoom-transcripts/index.json work/zoom-transcripts/sync-status.json work/zoom-transcripts/undated Michal Smaga's Personal Meeting Room rJFn9D3lRJmnlCMSomhPsw/transcript.json work/zoom-transcripts/undated Michal Smaga's Personal Meeting Room rJFn9D3lRJmnlCMSomhPsw/transcript.md --- .../2026-11-19/follow-up-live-acceptance.md | 6 + .../personal-os-production-acceptance.md | 2 +- ...personal-os-remediation-plan-2026-11-18.md | 1 + .../projects/personal-os/personal-os-tasks.md | 2 + .../personal-os/personal-os-user-scenarios.md | 2 + work/zoom-transcripts/index.json | 4 +- work/zoom-transcripts/sync-status.json | 2 +- .../transcript.json | 285 ------------------ .../transcript.md | 57 ---- 9 files changed, 15 insertions(+), 346 deletions(-) diff --git a/personal/projects/personal-os/personal-os-evidence/2026-11-19/follow-up-live-acceptance.md b/personal/projects/personal-os/personal-os-evidence/2026-11-19/follow-up-live-acceptance.md index f11692b6..e42073f3 100644 --- a/personal/projects/personal-os/personal-os-evidence/2026-11-19/follow-up-live-acceptance.md +++ b/personal/projects/personal-os/personal-os-evidence/2026-11-19/follow-up-live-acceptance.md @@ -1067,3 +1067,9 @@ - Прямой полный обход Asana подтвердил 392 открытые записи Current Objectives, проект бенчмарков в O-B и миграцию DNR в O-A. На живом портале панель охвата с числом и ссылкой открыта и перезагружена при 1280 и 390 px. В том же чтении показаны четыре архивных репозитория GitHub. [Current Objectives](https://app.asana.com/0/72649045549333/list) · [Рабочая очередь](http://127.0.0.1:4317/#/task-queue) - На отдельной копии использованы две реальные карточки и ответы локальной модели. Состояние частичного охвата выставлено для контрольного прогона. Прежний код помечал разбор готовым и сохранял его. Новый код сохраняет предпросмотр, показывает неполный обход и возвращает 409 на применение из старой вкладки. После восстановления охвата обе записи использованы повторно, без нового вызова модели. Первое открытие, перезагрузка и переход к применению проверены при 1280 и 390 px. Модель исключила DNR и удержала бенчмарки на сверке из-за отсутствия подтверждённого следующего шага. Полный проход модели по 392 карточкам остаётся открытым. - На той же копии «Повторить разбор» проверен через редактор категории. Готовый разбор начал новую обработку обеих записей. Проверка состояния отдельно подтвердила сохранение применённых совпадений. В новом контрольном ответе выяснилось, что модель может смешать сравнение Apple с Safari и других платформ с Chrome. Следующий шаг по бенчмаркам требует проверки против этих пар из исходного описания. [Бенчмарки](https://app.asana.com/0/0/1220371385779934) + +## Предложение по бенчмаркам из Asana + +- Первичная карточка подтверждает сравнение iOS и macOS с Safari, Android и Windows с Chrome, по скорости загрузки и памяти. Модель дважды возвращала совпадение с точной цитатой без шага. Попытка получить шаг только через инструкцию подставляла Chrome для Apple. Теперь для явно заданных сравнений шаг строится из цитируемой строки. Два прогона локальной модели на двух реальных карточках дали точные пары и исключили миграцию DNR. [Бенчмарки](https://app.asana.com/0/0/1220371385779934) · [Миграция DNR](https://app.asana.com/0/0/1216262985473637) +- На изолированной категории штатный агентный повтор и применение показали предложение, источник и дату проекта 18 декабря. Открытие и перезагрузка проверены дважды при 1280 и 390 px. При публикации первый перезапуск оставил портал недоступным. Сервис запущен повторно, рабочая очередь открылась при первом входе и перезагрузке на обеих ширинах. [Рабочая очередь](http://127.0.0.1:4317/#/task-queue) +- На копии полного каталога новый обход Asana сохранил 392 входа. Пакет после отметки 8 из 392 превысил 180 секунд, прогресс остался на 8. В рабочую категорию владельца этот проход не записывался. diff --git a/personal/projects/personal-os/personal-os-production-acceptance.md b/personal/projects/personal-os/personal-os-production-acceptance.md index 023505b2..6178b24a 100644 --- a/personal/projects/personal-os/personal-os-production-acceptance.md +++ b/personal/projects/personal-os/personal-os-production-acceptance.md @@ -210,7 +210,7 @@ 101. В «Сегодня» при первом открытии и перезагрузке на двух ширинах проверены кнопка тренировки, оба варианта и предпросмотр из рабочего ActivityWatch. Запись, ожидание возвращения и отображение в истории пройдены на временных интервалах. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#отметка-похода-в-тренажёрный-зал) 102. В «Неделе» видны последние сохранённые решения, время и состояние обзора. При смене источника пояснение доступно рядом с прежней записью. Сохранение, чтение файла решения и отказ устаревшей попытки проверены на отдельном наборе. В рабочем портале проверен исходный пустой раздел и два повтора с контрольным ответом для 1280 и 390 px. Реальная запись владельца отсутствовала. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#решения-недельного-обзора-после-сохранения) -103. D18-200 открыт. В живой «Рабочей очереди» при 1280 и 390 px проверены фильтры, переход из «Недели», пять продолжений CPM, три реестра Asana и десять источников GitHub. На отдельных рабочих входах проверены повтор после тайм-аута и восстановление неполного охвата с сохранением разбора. Остаются репозитории без сохранённой связи, полный разбор 392 записей и путь принятого предложения в оба плана. [План](personal-os-tasks.md) · [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#частичный-обход-источников-категории) +103. D18-200 открыт. В живой «Рабочей очереди» при 1280 и 390 px проверены фильтры, переход из «Недели», пять продолжений CPM, три реестра Asana и десять источников GitHub. На отдельных рабочих входах проверены восстановление неполного охвата, точный шаг по бенчмаркам и дата проекта. Остаются репозитории без сохранённой связи, полный разбор 392 записей и путь принятого предложения в оба плана. [План](personal-os-tasks.md) · [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#предложение-по-бенчмаркам-из-asana) 104. D18-201 открыт. В живой очереди сверены Kick-off с результатом Hack Phase, регистрация, зависимость замеров, вопрос о скрытых страницах macOS и отправленный запрос Advisor по C-S-S. Два действия из закрытого Postmortem CPM ждут фиксации решения по DNR и анализа данных 4 декабря. Открыты рабочий календарь Outlook, перебор остальных проектов, контроль ритма DRI ↔ PA, правила Running и теги AoR и передача предложений в планы. [Доказательства и этапы](personal-os-project-management.md) 105. D18-202 открыт. В живой хронологии при 1280 и 390 px сверены время Zoom, отдельный слот Asana, интервал ActivityWatch, ревью GitHub #8188, черновик статуса из коммита и две реальные задачи, созданные в Asana. Остаются рабочее создание из черновика Personal OS, происхождение нескольких подтверждённых действий из одного эпизода и черновики из результатов без Git-коммита. [План](personal-os-day-history.md) · [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#реально-созданные-задачи-в-хронологии) diff --git a/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md b/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md index 676a16d0..82e8833e 100644 --- a/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md +++ b/personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md @@ -959,6 +959,7 @@ Zoom используется для транскриптов состоявши - Режимы поиска по Current Objectives и общим ревью опубликованы. С живой очередью сверены три реестра Asana и десять источников GitHub, включая четыре найденных по рабочим связям. Архивные репозитории и непривязанные форки исключены из кандидатов. Остались покрытие репозиториев вне сохранённых связей, проход по правилу владельца и проверка принятого предложения в обеих проекциях плана. [Назначение, этапы реализации и пример категории](personal-os-tasks.md) · [Сценарии](personal-os-user-scenarios.md#u23--рабочая-очередь-и-источники-планов) - В удержанных продолжениях CPM видны действия из описаний, даты Asana и различие флагов по платформе. Для разбора категорий проверено возобновление пакета после тайм-аута с сохранением прогресса. - Предпросмотр категории показывает проверенные записи и неполный обход отдельно. При восстановлении источника совпавшие версии используются повторно. Новая версия результата применяется после проверки области и всех входов. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#частичный-обход-источников-категории) +- В предложениях по бенчмаркам проверенные пары платформ и браузеров берутся из процитированного описания. Дата проекта показана с подписью источника. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#предложение-по-бенчмаркам-из-asana) ### D18-201 · Сопровождение работ после загрузки источников diff --git a/personal/projects/personal-os/personal-os-tasks.md b/personal/projects/personal-os/personal-os-tasks.md index f456740a..ef01692f 100644 --- a/personal/projects/personal-os/personal-os-tasks.md +++ b/personal/projects/personal-os/personal-os-tasks.md @@ -93,4 +93,6 @@ GitHub проверяется по настроенным репозитория «Повторить разбор» для готового предпросмотра заново проверяет записи. Применённые совпадения остаются доступны до применения следующего результата. Продолжение после прерывания использует сохранённый прогресс. +Для бенчмарков с явно записанными парами платформ и браузеров следующий шаг использует эти пары из цитируемой строки Asana. Срок проекта помечен как дата Asana. В профильном примере iOS и macOS сверяются с Safari, Android и Windows с Chrome. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#предложение-по-бенчмаркам-из-asana) + [Требование D18-200](personal-os-remediation-plan-2026-11-18.md#d18-200--рабочая-очередь-и-asana-tasks) · [Сценарии U23](personal-os-user-scenarios.md#u23--рабочая-очередь-и-источники-планов) diff --git a/personal/projects/personal-os/personal-os-user-scenarios.md b/personal/projects/personal-os/personal-os-user-scenarios.md index df5c7ecd..81bbae18 100644 --- a/personal/projects/personal-os/personal-os-user-scenarios.md +++ b/personal/projects/personal-os/personal-os-user-scenarios.md @@ -703,6 +703,8 @@ - Пройти полный и частичный обход доступных objectives и реестров, GitHub, Zoom и Mattermost. В частичном проходе проверить непрочитанную страницу, недоступную карточку и восстановление после отказа. Отсутствие совпадений отличается от непроверенной области. Загруженные подтверждённые карточки остаются доступными с отметкой свежести. - Довести проверку всех найденных записей в частичном снимке. Предпросмотр сохраняет примеры и показывает состояние источника. После восстановления того же входа проверить переход к применению с сохранением прогресса. Попытка применить неполный снимок через старую вкладку получает отказ. +- Для кандидата с измерениями сверить, что шаг сохраняет явно записанные пары платформ и браузеров, а дата из Asana подписана как срок проекта. + ### U23.12 — Неоднозначное описание категории - Ввести расплывчатое и противоречивое описание. Сверить, какие условия распознаны, какие объекты удержаны и какие уточнения доступны. До явного сохранения подтверждённые версии очереди и планов сохраняются. Для сохранённой категории повтор старого входа восстанавливает ту же выборку и объяснения. diff --git a/work/zoom-transcripts/index.json b/work/zoom-transcripts/index.json index 82fdc59e..8ddf99ae 100644 --- a/work/zoom-transcripts/index.json +++ b/work/zoom-transcripts/index.json @@ -140,8 +140,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": "2ce68e4460a37f8959864b9fdcc3721e6c266919d4e0827b26a4cfe71badec52", - "cues": 60 + "sha256": "f3e5c2853765d464fa0cfa41680e4f8088504a9458dc95c2259a03d2f9440f9d", + "cues": 3 }, "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 289d59bd..f771529e 100644 --- a/work/zoom-transcripts/sync-status.json +++ b/work/zoom-transcripts/sync-status.json @@ -1 +1 @@ -{"observed_at":"2026-11-20T10:35:02.907Z","scanned":33,"imported":0,"skipped":33,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":88,"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":88,"gaps":[],"recovered_transcripts":0,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"} \ No newline at end of file +{"observed_at":"2026-11-20T11:06:53.063Z","scanned":33,"imported":1,"skipped":32,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":88,"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":88,"gaps":[],"recovered_transcripts":0,"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 b3691e7a..8cbe8697 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 @@ -25,291 +25,6 @@ "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 e9023fdf..17c56b09 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,60 +15,3 @@ 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.