[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-project-management.md personal/projects/personal-os/personal-os-remediation-plan-2026-11-18.md personal/projects/personal-os/personal-os-user-scenarios.md work/zoom-transcripts/2026-10-06 SRE Incidents 2026-10-06 21 21(GMT+6 00) SrYbgHxMSlWioRrr4PGz2Q/transcript.json work/zoom-transcripts/2026-10-06 SRE Incidents 2026-10-06 21 21(GMT+6 00) SrYbgHxMSlWioRrr4PGz2Q/transcript.md work/zoom-transcripts/index.json work/zoom-transcripts/sync-status.json
This commit is contained in:
1 parent
88d867b8ff
commit
54197636ea
9 files changed
+1058
-5
No files matched your search
+6
@@ -1202,3 +1202,9 @@
|
|||||||
- Два ревью #8163 отображались с пустым общим текстом. Первичный GitHub вернул отдельное замечание для каждого ID ревью. Обе записи содержат исходный коммит `55fee4ea905a93dd8ab1ed5b349be2dafcb5458a`, а текущая позиция комментариев соответствует более позднему коммиту `549d6eb2ae588a4f23c0b5558f0af33300285193`. Хронология связывает цитату с исходным SHA и точным временем ревью. [Первое замечание](https://github.com/duckduckgo/apple-browsers/pull/8163#discussion_r4613861033) · [Второе замечание](https://github.com/duckduckgo/apple-browsers/pull/8163#discussion_r4613871413)
|
- Два ревью #8163 отображались с пустым общим текстом. Первичный GitHub вернул отдельное замечание для каждого ID ревью. Обе записи содержат исходный коммит `55fee4ea905a93dd8ab1ed5b349be2dafcb5458a`, а текущая позиция комментариев соответствует более позднему коммиту `549d6eb2ae588a4f23c0b5558f0af33300285193`. Хронология связывает цитату с исходным SHA и точным временем ревью. [Первое замечание](https://github.com/duckduckgo/apple-browsers/pull/8163#discussion_r4613861033) · [Второе замечание](https://github.com/duckduckgo/apple-browsers/pull/8163#discussion_r4613871413)
|
||||||
- На живом портале при 1280 и 390 px дважды открыты обе карточки #8163, замечание #3727 и LGTM из #8188. У первых трёх проверены цитата, SHA и переход к отдельному комментарию. В #8188 первичный список замечаний пуст, в карточке сохранён общий текст. Связанная Asana-задача #8163 завершена, новый черновик статуса из этих ревью не возник. [История #8163](http://127.0.0.1:4317/#/work-history?date=2026-11-18&episode=github%3Aduckduckgo%2Fapple-browsers%238163%3Areview%3A5956496787) · [Замечание #3727](https://github.com/duckduckgo/duckduckgo-privacy-extension/pull/3727#discussion_r4599686819) · [Ревью #8188](https://github.com/duckduckgo/apple-browsers/pull/8188#pullrequestreview-5938186099) · [Задача Asana](https://app.asana.com/0/0/1220422645861893)
|
- На живом портале при 1280 и 390 px дважды открыты обе карточки #8163, замечание #3727 и LGTM из #8188. У первых трёх проверены цитата, SHA и переход к отдельному комментарию. В #8188 первичный список замечаний пуст, в карточке сохранён общий текст. Связанная Asana-задача #8163 завершена, новый черновик статуса из этих ревью не возник. [История #8163](http://127.0.0.1:4317/#/work-history?date=2026-11-18&episode=github%3Aduckduckgo%2Fapple-browsers%238163%3Areview%3A5956496787) · [Замечание #3727](https://github.com/duckduckgo/duckduckgo-privacy-extension/pull/3727#discussion_r4599686819) · [Ревью #8188](https://github.com/duckduckgo/apple-browsers/pull/8188#pullrequestreview-5938186099) · [Задача Asana](https://app.asana.com/0/0/1220422645861893)
|
||||||
- На контрольных данных отклонены другой ID ревью, другой автор, другой исходный SHA и редакция после отправки. Проверка хронологии и атрибуции прошла полностью, 13 из 13. Предложение черновика из результата IDE или агента без коммита ещё требует отдельного рабочего примера.
|
- На контрольных данных отклонены другой ID ревью, другой автор, другой исходный SHA и редакция после отправки. Проверка хронологии и атрибуции прошла полностью, 13 из 13. Предложение черновика из результата IDE или агента без коммита ещё требует отдельного рабочего примера.
|
||||||
|
|
||||||
|
## Частично заполненный Kick-off
|
||||||
|
|
||||||
|
- Из Asana прочитаны исходный шаблон, действующий Kick-off с пустым Next steps, его родительский проект и заполненный Android Kick-off. Ранее проверка срабатывала только на заглушку со ссылкой на шаблон. Теперь учитываются пустые секции и точные исходные подсказки внутри распознанного шаблона. [Шаблон](https://app.asana.com/0/0/332886249861503) · [Неполная карточка](https://app.asana.com/0/0/1220686885895588) · [Заполненная карточка](https://app.asana.com/0/0/1220735902739960)
|
||||||
|
- На изолированной копии с ролью Top Priority получено одно предложение и один раздел черновика Next steps. В очереди проверены точная ссылка, первое открытие и перезагрузка при 1280 и 390 px. После наполнения Next steps на копии действие исчезло. Заполненный Android Kick-off не вызвал предложения. Штатные проверки очереди прошли 12 из 12. Чужие проекты не включались в рабочий Top Priority и Asana не изменялась.
|
||||||
|
- Рабочий E5 `a5ff15cc-3200-4bda-9f1f-faf70a1ae8d3` успешно опубликовал очередь. Текущий iOS Kick-off по-прежнему содержит только исходную ссылку на шаблон. В рабочей очереди подтверждены один шаг, четыре раздела черновика и точная ссылка после первого открытия и перезагрузки при 1280 и 390 px. [Текущий Kick-off](https://app.asana.com/0/0/1220371473869152) · [Рабочая очередь](http://127.0.0.1:4317/#/task-queue?action=project-management%3Akickoff-content%3A1220371472571114%3A1220371473869152)
|
||||||
@@ -210,8 +210,8 @@
|
|||||||
101. В «Сегодня» при первом открытии и перезагрузке на двух ширинах проверены кнопка тренировки, оба варианта и предпросмотр из рабочего ActivityWatch. Запись, ожидание возвращения и отображение в истории пройдены на временных интервалах. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#отметка-похода-в-тренажёрный-зал)
|
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#решения-недельного-обзора-после-сохранения)
|
102. В «Неделе» видны последние сохранённые решения, время и состояние обзора. При смене источника пояснение доступно рядом с прежней записью. Сохранение, чтение файла решения и отказ устаревшей попытки проверены на отдельном наборе. В рабочем портале проверен исходный пустой раздел и два повтора с контрольным ответом для 1280 и 390 px. Реальная запись владельца отсутствовала. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#решения-недельного-обзора-после-сохранения)
|
||||||
103. D18-200 открыт. В живой очереди проверены фильтры, переход из «Недели», пять продолжений CPM, три реестра Asana и десять источников GitHub. На копии реальной карточки бенчмарков проверены явный результат, попадание в оба плана, исключение дубля и отзыв решения. Незакрытые TD, Ship Review и PR прошли оба плана на контрольных копиях из первоисточников. Поздний ответ владельца исключает конкретный отвеченный вопрос. Нумерованный ответ владельца по HTML-списку исключил три старых вопроса TD. Штатная модель выбрала открытый запрос по запуску iOS. В Ship Review проверено имя из первичного комментария. Полный проход свежего Current Objectives завершён для всех 393 записей. На копиях проверены применение и фильтр O‑B и O‑5. Разбор общего каталога идёт на копии по 12 источникам. К 20:35 по Бишкеку проверено 264 из 356 записей. Из них 26 предложены, 234 исключены, по четырём решение не определено. Открыты остальные записи и репозитории вне сохранённых связей, решения владельца и ответы свободной формы без однозначной связи. [План](personal-os-tasks.md) · [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#подтверждение-предложения-из-общего-каталога)
|
103. D18-200 открыт. В живой очереди проверены фильтры, переход из «Недели», пять продолжений CPM, три реестра Asana и десять источников GitHub. На копии реальной карточки бенчмарков проверены явный результат, попадание в оба плана, исключение дубля и отзыв решения. Незакрытые TD, Ship Review и PR прошли оба плана на контрольных копиях из первоисточников. Поздний ответ владельца исключает конкретный отвеченный вопрос. Нумерованный ответ владельца по HTML-списку исключил три старых вопроса TD. Штатная модель выбрала открытый запрос по запуску iOS. В Ship Review проверено имя из первичного комментария. Полный проход свежего Current Objectives завершён для всех 393 записей. На копиях проверены применение и фильтр O‑B и O‑5. Разбор общего каталога идёт на копии по 12 источникам. К 20:43 по Бишкеку проверено 280 из 356 записей. Из них 26 предложены, 250 исключены, по четырём решение не определено. Открыты остальные записи и репозитории вне сохранённых связей, решения владельца и ответы свободной формы без однозначной связи. [План](personal-os-tasks.md) · [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#подтверждение-предложения-из-общего-каталога)
|
||||||
104. D18-201 открыт. В живой очереди сверены Kick-off C-S-S с результатом Hack Phase, зависимость замеров, вопрос о скрытых страницах macOS и запрос Advisor. Для текущего Kick-off по iOS проверены дата, слот O‑B Weekly, общий тест с FE и форма подтверждения. Допуск того же шага в оба плана, смена версии и снятие решения прошли на изолированной копии. Реального решения в рабочем журнале пока нет. На копии CPM проверена настройка интервала DRI ↔ PA и ссылка на последнее обновление. Рабочий интервал пока не задан. Открыты адресное уведомление, рабочий календарь Outlook, пересечения без общей ссылки, Running и теги AoR. Назначение Advisor сохраняется после контрольного закрытия Kick-off для iOS и C-S-S. Закрытие самого проекта снимает шаг. Для встреч используются рабочий календарь и Asana. Чтение писем исключено. [Доказательства и этапы](personal-os-project-management.md)
|
104. D18-201 открыт. В живой очереди сверены Kick-off C-S-S с результатом Hack Phase, зависимость замеров, вопрос о скрытых страницах macOS и запрос Advisor. Для текущего Kick-off по iOS проверены дата, слот O‑B Weekly, общий тест с FE и форма подтверждения. На копии действующего частично заполненного Kick-off появляется только черновик Next steps. После штатного пересчёта живой iOS Kick-off сохранил четыре раздела для исходной заготовки. Допуск того же шага в оба плана, смена версии и снятие решения прошли на изолированной копии. Реального решения в рабочем журнале пока нет. На копии CPM проверена настройка интервала DRI ↔ PA и ссылка на последнее обновление. Рабочий интервал пока не задан. Открыты адресное уведомление, рабочий календарь Outlook, пересечения без общей ссылки, Running и теги AoR. Назначение Advisor сохраняется после контрольного закрытия Kick-off для iOS и C-S-S. Закрытие самого проекта снимает шаг. Для встреч используются рабочий календарь и Asana. Чтение писем исключено. [Доказательства и этапы](personal-os-project-management.md)
|
||||||
105. D18-202 открыт. В живой хронологии при 1280 и 390 px сверены время Zoom, слот Asana, интервал ActivityWatch, ревью GitHub #8188, черновик статуса из коммита, две созданные задачи и итоговый комментарий CPM. Два PR одного Tech Design различимы по заголовку и номеру, поиск по номеру работает. В раскрытии трёх замечаний GitHub сверены цитаты, точные ссылки и исходный SHA. Ревью с одним LGTM не показывает пустой блок замечаний. Реплики об обновлении TD видны внутри встречи 12 ноября с авторами и точным временем. Карточки плана по ним отсутствуют, пока цель не установлена. На встрече CPM 19 ноября сверены две существующие задачи, точные реплики, сроки и ссылки. На копии проверена поздняя локальная квитанция, на рабочем портале открыт существующий черновик. Записей создания из Personal OS в рабочем журнале нет. Остаются рабочее создание новой задачи из решения встречи или черновика Personal OS и черновики из результатов без Git-коммита. Единственная связанная локальная заметка имеет одну версию и семь рабочих связей. Поручение Exact tab/window matching сохраняется в истории 13 ноября и очереди после закрытия исходной нити. Снятие при публикации текста или закрытии цели проверено на копии. [План](personal-os-day-history.md) · [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#два-pr-одного-tech-design-в-хронологии)
|
105. D18-202 открыт. В живой хронологии при 1280 и 390 px сверены время Zoom, слот Asana, интервал ActivityWatch, ревью GitHub #8188, черновик статуса из коммита, две созданные задачи и итоговый комментарий CPM. Два PR одного Tech Design различимы по заголовку и номеру, поиск по номеру работает. В раскрытии трёх замечаний GitHub сверены цитаты, точные ссылки и исходный SHA. Ревью с одним LGTM не показывает пустой блок замечаний. Реплики об обновлении TD видны внутри встречи 12 ноября с авторами и точным временем. Карточки плана по ним отсутствуют, пока цель не установлена. На встрече CPM 19 ноября сверены две существующие задачи, точные реплики, сроки и ссылки. На копии проверена поздняя локальная квитанция, на рабочем портале открыт существующий черновик. Записей создания из Personal OS в рабочем журнале нет. Остаются рабочее создание новой задачи из решения встречи или черновика Personal OS и черновики из результатов без Git-коммита. Единственная связанная локальная заметка имеет одну версию и семь рабочих связей. Поручение Exact tab/window matching сохраняется в истории 13 ноября и очереди после закрытия исходной нити. Снятие при публикации текста или закрытии цели проверено на копии. [План](personal-os-day-history.md) · [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#два-pr-одного-tech-design-в-хронологии)
|
||||||
|
|
||||||
## Как закрывается проверка
|
## Как закрывается проверка
|
||||||
|
|||||||
@@ -17,6 +17,7 @@ Milestone **D18-201** добавляет в «Рабочую очередь» о
|
|||||||
- Сверить включение работы в применимые проекты, objective и секции, наличие требуемой категории, DRI и Project Advisor. Ссылки на актуальные правила обязательны. Учитывать отличие Hack Phase от формального начала проекта. Предложить Hack Phase, если для выбора подхода остаётся исследовательский вопрос, с коротким ожидаемым результатом.
|
- Сверить включение работы в применимые проекты, objective и секции, наличие требуемой категории, DRI и Project Advisor. Ссылки на актуальные правила обязательны. Учитывать отличие Hack Phase от формального начала проекта. Предложить Hack Phase, если для выбора подхода остаётся исследовательский вопрос, с коротким ожидаемым результатом.
|
||||||
- Перед Kick-off собрать параллельные проекты других людей во всех относящихся к делу objectives. Сравнить цели, компоненты, зависимости, владельцев, сроки и риск дублирования. Подготовить предметные вопросы, что можно убрать из скоупа, объединить, отложить или согласовать. Решения о сокращении остаются за DRI.
|
- Перед Kick-off собрать параллельные проекты других людей во всех относящихся к делу objectives. Сравнить цели, компоненты, зависимости, владельцев, сроки и риск дублирования. Подготовить предметные вопросы, что можно убрать из скоупа, объединить, отложить или согласовать. Решения о сокращении остаются за DRI.
|
||||||
- Прочитать актуальный шаблон Kick-off и существующую задачу. Предложить заполнение недостающих полей по первичным источникам, включая цель, критерии успеха, границы скоупа, связанный Task Timeline, риски, ускорители, открытые вопросы и участников. Уже заполненные поля переиспользовать. Сверить дочернюю связь, регистрацию Kick-off и публичное обсуждение.
|
- Прочитать актуальный шаблон Kick-off и существующую задачу. Предложить заполнение недостающих полей по первичным источникам, включая цель, критерии успеха, границы скоупа, связанный Task Timeline, риски, ускорители, открытые вопросы и участников. Уже заполненные поля переиспользовать. Сверить дочернюю связь, регистрацию Kick-off и публичное обсуждение.
|
||||||
|
- При частично заполненном шаблоне показать пустые разделы и черновик только для них. Пустая строка и исходная подсказка шаблона обозначают поле для заполнения. После появления рабочего текста действие закрывается. [Проверка](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#частично-заполненный-kick-off)
|
||||||
- Проверить дату и точное время в Asana. При отдельной встрече сверить Outlook-событие и приглашённых. При выборе слота в Weekly проверить явную привязку повестки, время, необходимую длительность и участников. Само наличие Weekly рядом по времени не подтверждает проведение Kick-off. Срок приглашения берётся из действующего шаблона и фактической даты.
|
- Проверить дату и точное время в Asana. При отдельной встрече сверить Outlook-событие и приглашённых. При выборе слота в Weekly проверить явную привязку повестки, время, необходимую длительность и участников. Само наличие Weekly рядом по времени не подтверждает проведение Kick-off. Срок приглашения берётся из действующего шаблона и фактической даты.
|
||||||
- Для отдельной встречи рабочий календарь Outlook служит источником события, времени и участников. Подтверждение оповещения или запроса обратной связи берётся из Asana. Доступ к почте для этих проверок исключён.
|
- Для отдельной встречи рабочий календарь Outlook служит источником события, времени и участников. Подтверждение оповещения или запроса обратной связи берётся из Asana. Доступ к почте для этих проверок исключён.
|
||||||
|
|
||||||
|
|||||||
@@ -979,6 +979,7 @@ Zoom используется для транскриптов состоявши
|
|||||||
|
|
||||||
- Черновик C-S-S использует результат существующей Hack Phase и уточняет, какое решение нужно для Task Timeline. В пересечениях отдельно показан связанный вопрос по скрытым страницам macOS с точной ссылкой Asana. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#результат-hack-phase-и-решение-по-скоупу-c-s-s)
|
- Черновик C-S-S использует результат существующей Hack Phase и уточняет, какое решение нужно для Task Timeline. В пересечениях отдельно показан связанный вопрос по скрытым страницам macOS с точной ссылкой Asana. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#результат-hack-phase-и-решение-по-скоупу-c-s-s)
|
||||||
- Подготовка начинается с подтверждённой карточки Kick-off, включая карточку без даты. Для текущего проекта по iOS в очереди есть предложение согласовать слот O‑B Weekly или отдельный созвон, черновик по описанию проекта, регистрация и проверка Advisor. Общий совет о пересечениях исключён. Для отдельной карточки требуется конкретная открытая работа. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#kick-off-без-даты-для-нового-top-priority)
|
- Подготовка начинается с подтверждённой карточки Kick-off, включая карточку без даты. Для текущего проекта по iOS в очереди есть предложение согласовать слот O‑B Weekly или отдельный созвон, черновик по описанию проекта, регистрация и проверка Advisor. Общий совет о пересечениях исключён. Для отдельной карточки требуется конкретная открытая работа. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#kick-off-без-даты-для-нового-top-priority)
|
||||||
|
- Частично заполненный Kick-off даёт одно действие со списком пустых разделов. Черновик охватывает эти разделы. Заполнение закрывает действие. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#частично-заполненный-kick-off)
|
||||||
- При подготовке Kick-off точная ссылка на тестовую страницу из критериев успеха сверяется со всеми открытыми записями Current Objectives. Для выбранного проекта отдельно проверяются владелец, статус, совпадение сроков и оба критерия. В Kick-off по iOS добавлен вопрос об общем прогоне с FE-проектом Shane и раздельной фиксации результатов. Пересечения без общей ссылки ещё требуют проверки. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#общий-тест-webcontent-memory-в-двух-проектах)
|
- При подготовке Kick-off точная ссылка на тестовую страницу из критериев успеха сверяется со всеми открытыми записями Current Objectives. Для выбранного проекта отдельно проверяются владелец, статус, совпадение сроков и оба критерия. В Kick-off по iOS добавлен вопрос об общем прогоне с FE-проектом Shane и раздельной фиксации результатов. Пересечения без общей ссылки ещё требуют проверки. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#общий-тест-webcontent-memory-в-двух-проектах)
|
||||||
- Для закрытого CPM подтверждён закреплённый итог. Его результаты доступны в карточке открытого решения по macOS. Проверка предлагает закрепить существующий итог, когда Asana явно подтверждает отсутствие закрепления. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#закреплённый-итог-cpm-и-открытое-решение)
|
- Для закрытого CPM подтверждён закреплённый итог. Его результаты доступны в карточке открытого решения по macOS. Проверка предлагает закрепить существующий итог, когда Asana явно подтверждает отсутствие закрепления. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#закреплённый-итог-cpm-и-открытое-решение)
|
||||||
- У предложения сопровождения с подтверждённым источником доступны решение и оценка времени. Расчёт повторно строит предложение из свежих данных, сверяет выбранную версию и использует существующие ограничения «Недели» и «Сегодня». Отменённое решение снимает допуск. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#подтверждённый-шаг-сопровождения-в-неделе-и-сегодня)
|
- У предложения сопровождения с подтверждённым источником доступны решение и оценка времени. Расчёт повторно строит предложение из свежих данных, сверяет выбранную версию и использует существующие ограничения «Недели» и «Сегодня». Отменённое решение снимает допуск. [Доказательства](personal-os-evidence/2026-11-19/follow-up-live-acceptance.md#подтверждённый-шаг-сопровождения-в-неделе-и-сегодня)
|
||||||
|
|||||||
@@ -752,6 +752,7 @@
|
|||||||
### U24.3 — Подготовка Kick-off по шаблону
|
### U24.3 — Подготовка Kick-off по шаблону
|
||||||
|
|
||||||
- Открыть реальную заготовку Kick-off и действующий шаблон. Сверить недостающие поля, прошлые решения, регистрацию и рекомендуемое наполнение. После записи на копии закрываются только реально заполненные контрольные пункты. Пустая будущая подзадача остаётся заготовкой до применимой стадии.
|
- Открыть реальную заготовку Kick-off и действующий шаблон. Сверить недостающие поля, прошлые решения, регистрацию и рекомендуемое наполнение. После записи на копии закрываются только реально заполненные контрольные пункты. Пустая будущая подзадача остаётся заготовкой до применимой стадии.
|
||||||
|
- На копии частично заполненной задачи открыть предупреждение о Next steps при 1280 и 390 px. Сверить ссылку на Kick-off и единственный раздел в черновике. После перезагрузки проверить представление. Заполнить этот раздел на копии и убедиться, что предложение исчезло. Повторить со строкой подсказки из шаблона и с полностью заполненной карточкой.
|
||||||
- Сверить Discussion items с разделом Result в связанной Hack Phase. Результат и открытый вопрос сохраняются при незакрытом исследовании и после его закрытия. В Next steps виден ожидаемый результат обсуждения для Task Timeline. Ссылка ведёт к исходному исследованию.
|
- Сверить Discussion items с разделом Result в связанной Hack Phase. Результат и открытый вопрос сохраняются при незакрытом исследовании и после его закрытия. В Next steps виден ожидаемый результат обсуждения для Task Timeline. Ссылка ведёт к исходному исследованию.
|
||||||
|
|
||||||
### U24.4 — Слот Kick-off, Midmortem или Postmortem
|
### U24.4 — Слот Kick-off, Midmortem или Postmortem
|
||||||
|
|||||||
+870
@@ -25,6 +25,876 @@
|
|||||||
"time": "21:23:00",
|
"time": "21:23:00",
|
||||||
"speaker": "Tomasz Patrzykat",
|
"speaker": "Tomasz Patrzykat",
|
||||||
"text": "Угу?"
|
"text": "Угу?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:23:01",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Uh, so we will need to go with a hotfix route, and with some expedite review, probably, uh… and given our experience, it it usually takes up to like half a day for the review, sometimes like even even quicker. So, as far as I'm aware."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:23:14",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Угу? Он Айос. Сайт, Онли? Лайк, Ноу Одер, Платформ?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:23:26",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Yeah, yeah, yeah, definitely. Definitely, iOS. Yeah, it's a native thing."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:23:28",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Дэфнетли, Окей?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:23:33",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "So I…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:23:33",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Он. Он, фиксинг?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:23:37",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Yeah, Alex, Alex is working on it here in the call."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:23:45",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Ангел, Кимятый Сезон?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:23:45",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Bye. Sorry? Yeah, as far as I'm aware, Alex has a fix already. We we just don't know if it if it fixes all the things like I. I know that. Bartek was was on a call before, and he managed to like reproduce it even in a in a like simpler scenario like, if if it still fixes the whole thing, then I I guess we we can."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:24:15",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Угу?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:24:16",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "safely say that we have a fix. So we we are just now trying to to to to check on the other thing. I I guess the the thing that Hassan found. And. Yep. Anything I missed, Alex?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:24:34",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "На стрели? Для следствие бирри бэйс?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:24:55",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Фикс, райт?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:24:55",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Okay, sorry."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:03",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Дэнни Шелфикс?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:03",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Go ahead, Alex."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:04",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Игос?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:06",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Alexis, I'm just happy."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:06",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Окей, Алекс, Окей?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:14",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "All right, so yeah, I'm looking at the logs here. Yeah, okay. There's a step that keeps replaying, the KI answer step. Is that the thing you saw, Alex, the fix you have there?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:21",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Дуй."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:30",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Apparently, it's failing to get on an exit path. Like it always keeps that state no matter what. Do you have the, um… The PR? Ready?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:43",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Депюар Бари?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:45",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Where's the fix?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:45",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Автофикс?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:45",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Не отопляры, Все?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:50",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Yes, indeed."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:25:50",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Санги? Mmhm. Okay, we're gonna try it here."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:26:49",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "It was always there, but… I didn't completely get it, because one of the demos that Bartek held, he had no guided screen at all. Basically, the screen that sets the, uh, the flag. the fire onboarding was complete is is made by the. You've got Express. You've got it button pressed. And if there is no button, the flag is never set and the loop is always there."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:27:23",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "But I didn't yet understand why the screen may be missing."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:27:24",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Окей?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:27:30",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Maybe it was recent change and I'm not aware of. Yeah, and uh… On-screen path. On the before I forget, choose to restore from sync. Resume onboarding, choose Duck AI, send the prompt, and go through the fire onboarding. And after the fire… There would be no, you've got this thing, yeah, and that's why it's synchronized, exactly. Foundation. And that's why all the users start experiencing."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:28:13",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Sorry. So what was the culprit? Hello!"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:28:16",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "The sync restoration path that was enabled recently, and that's why it's mentioned in the task. Uh, right. In the… in the bug task. And if you choose the sync restoration path. Uh, you… Got… now you've got this screen presented. Meaning the flag is never set. So that was the activating issue. Because the bug with the button was always there, but the users were always pressing the button. And now the button is gone, because when you…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:28:45",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Okay, and do you have a… do you do one…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:28:54",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Choose, uh, sync, restore from sync, restore using sync. On the \"Oh, before I forget\" screen. Right? So probably you choose the search path and restore from using sync."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:29:44",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Yeah, I'm gonna… installing our… I'm starting our fix here. See if I can… I could do station again. Um… And also I'm spinning an agent review because I previous think that my phone is just like."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:30:22",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yes, uh, it seems like it. Or I forget. Mmhmm. It's not the validated… the validated path, I'm just… Copying steps found. Yeah, here in the charts. At least, as it's said by Codex."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:31:50",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Эй Тэнкс?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:33:05",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "What is the behavior we want here? Like, if the user did not… Tap the fire button. Should that step be… repeated, as well? Like, we never want this to happen, right? Like, it doesn't matter what the user did or did not…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:33:19",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "You… the user… The user cannot miss that step. Every other controller is locked in that state."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:33:30",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "What if I… what if I kill the mid without…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:33:33",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "You would just return to the same screen."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:33:36",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Okay. All right, yeah, so I can't… I can't reproduce the issue again with Alex Pierre. Gonna try from scratch."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:33:46",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yeah, it's basically cleared as soon as you press the fire button."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:33:50",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Yeah, I saw the change there. But I'm trying from scratch again."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:33:58",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yeah, maybe the steps I just sent are not correct steps. I'm just trying to figure it out via cloud. The Sync Restore screen is called \"Let's Pick Up Where You Left Off\"."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:34:28",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Yeah, the two things the review here is saying, but I'll let you decide if it makes sense or not. One is the one that I called before. It found the same thing, but basically… If for some reason there's another entry point. um…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:34:47",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yeah, it's the same thing, anyways."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:34:47",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "On that screen, it's gonna miss it, yeah."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:34:50",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Because when you get to the fire onboarding state, it sets the flag, and when you hit the fire button, it resets the flag. So that's the entry and exit."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:34:50",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "And one of… And. Okay. And another one is just this saying that it's missing tests from the call points. I don't really mind this one."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:34:59",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "I would say. Yeah, it just makes the bug obvious for… it's just…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:35:08",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Okay, but…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:35:12",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Makes the bug inevitable for all the users who use the sync feature."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:35:21",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Okay, I'm trying again. So skip. Skip. Next. Type. Bye. Maybe it's the KI."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:35:35",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yeah, so set to returning user. Restart, press restore my stuff. And get through the onboarding. Um, whatever. I need to…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:36:03",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Okay, seems to be… I did the steps from scratch, at least the ones that Bortek reproduced seems to be working here."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:36:11",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yeah, that exact scenario is reproduced, if you omit the… We've got this button, we've got the screen, but if there is no screen, yeah, it's 100% reproducible, and it's obvious, and the fix should just fix the file onboarding."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:36:16",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Mm-mm."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:36:25",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "And uh… probably it's not up to us to fix the flow itself, it's just the… the flag issue. So, should I rebase it to the current release branch? Origin, release, iOS."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:36:42",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "One, all right. I was talking to Thomas, and. a… If we reverted that same thing, would it fix it, or would it just make it…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:36:56",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "No, it won't fix it. It would, uh, prevent the new users to get in. But if there is a feature flag for that flow, it should, uh… Make it."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:37:13",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "But would it still be valuable to do so? So…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:37:18",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Maybe. If there is a fish or flock, that's… So I don't know, I haven't produced the second path for the returning user."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:37:32",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Okay, would you be able to check that if there's a feature flag for that like, perhaps we could do it like 2 ways like we could disable the flag. To help. Like, new users not to get into the state, and we would, like, release the hotfix too. Uh, to fix the state for users that already are in the loop."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:37:58",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "No, the users that are already in the loop, they are… they cannot be…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:38:02",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "I know, I know. So for them, we'll release the hotfix. I'm just talking about new users, like whether like…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:38:03",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "fixed, but…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:38:07",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Я Эленто, Нью, Юзерс?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:38:08",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Whether changing like switching the flag would actually make it for for better for them, or."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:38:43",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Okay, uh, do you still need me for anything here? All good?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:38:48",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yes, there is Sync Auto Restore. And it's… Is it mentioned there?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:38:58",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "What is the problem with sync?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:38:58",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Report it. Hmm?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:39:02",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "What is the problem with sync?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:39:05",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "The second path that restores the data and the sink was mentioned as a trigger for the issue. The fixed app now uses the sync server. For chat history, only one sync is actually on. Fix context. Accumulated AI charts deleted. And… Sync Auto Restore."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:40:09",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Sorry, I'm not pulling. What is the issue related with syncing?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:40:13",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Sync restore, the sync restoration prompt, if we disable this feature flag, the sync restoration prompt should not appear. So, it means the user won't get through the sync restoration flow, and they won't get. the. Yes. Yes, but it's… But it's the common feature flag for all these encoders, not only for the onboarding."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:40:45",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "О?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:40:46",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "It does not disable sync, it disables automatic recovery of previously preserved sync account. Hide the \"Let's pick up where we left off\" button. And restore my stuff during onboarding. Remove the automatic restore path from sync settings. User must use QR code or recovery code or manual setup. So basically, this is automatic keychain recovery from keychain for reinstallers, and they have to… They have to sync up manually again. We can disable the whole flow, and it will mitigate this issue. But disabled synchro. They're restored with SYNCFLOW."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:41:37",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Возраисков. Дизайн Фул Сынг?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:41:41",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "The loss of the restoration we are seeing from the keychain item for installers."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:41:44",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Угу?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:41:53",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "So they will have to manually restore things. Or lose data, if… They have no access to the QR code anymore. At least until the next… Reinstall. That's not the case. So I'd say, uh, since… my opinion, that since it's not the really everyday use case scenario when… where you left off. The Duck or Yea chat. It may… it may be… And not a good user experience, but it's not a user breakage. And we should not remove, we should not lose user data."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:42:46",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Yeah, so. The the. Just make sure I understand here, like, we have two different problems, right? Like, one is this onboarding thing that keeps getting into a loop. This is the incident thing that we… like, you have the PR and it's done, right? Another one is this sync issue that I didn't understand very well, but basically, if you reinstall the app, there's still sync information there that it shouldn't be. Right? The second one."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:43:08",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "No."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:43:09",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Is it an incident as well? Is it something that needs to be part of this?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:43:12",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "No, it's, uh, it's the same, it's the same issue."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:43:16",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "So it's related to onboarding as well?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:43:19",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yes, so when you have… so how would they use… how the new users are getting into the loop? Because normally, and the issue was there for a while already, it was half a year since it was merged, but we've started receiving this incident only recently, with this sink restoration. It's a reaction, because…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:43:40",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Okay, so it… Okay, it feels like the other one is way more… pressing time-related, like, for us to fix as soon as possible, and this one is not. I don't know if I'm wrong here."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:43:51",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Депендских? Дат. С. Мои андрестанников Да Ищи? Инту, Дис? Он, ореваясь?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:44:10",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Everybody who is doing this in restoration."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:44:21",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Генджек?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:44:23",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "So… Yeah, so to reproduce this, I need to have, like, sync enable, and then… Delete the app, install the app again."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:44:34",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "No, uh, yes. Yes."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:44:39",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Okay."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:44:39",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Delete the app and reinstall again and restore from sync."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:44:47",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "So it doesn't occur to completely new users to DuckDuckGo?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:44:53",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Hm?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:44:54",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "It doesn't even."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:44:54",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Sure."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:44:56",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "New users to DuckDuckGo who never had an app before on their phone. This is not gonna be triggered for them. You're saying?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:45:04",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Uh, they shouldn't, in general. So it's only the case when you… you kill the app and they got this screen. But it's been there for a while already, and we haven't received a lot of feedback about it. Before. So it's the condition that you have… that you should have three, uh… 3 consequences, 3 cases, 3 events in a row. So, missing this… button then. Entering the Dakaria chat and. Restarting the app with Duck AI Chart active."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:45:44",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "So okay, okay, I need to double check. So you're saying, if I if I have a raw simulator. I shouldn't be able to even reproduce the issue."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:45:55",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Perfect."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:45:57",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Okay. I can check. Just to be double sure."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:46:03",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "So, in general, if you just press the… you've got this button. It won't be there. Yes. Yes. That's the case."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:46:58",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Ол. Пробэмс?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:47:00",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "I think, I think it fixes them. Uh, at least the one that… that incident reports were telling about right? Alex. And Fernando, like, you were checking it…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:47:13",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yes, who is, uh… who is getting to the screen? They will have to do the fire button thing again, but the next time it's fixed. It won't appear anymore."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:47:26",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Okay."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:47:31",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "And there is sync auto restore success excel. Use parameter source equals onboarding. And for users who only tapped restore my stuff. There is another pixel. Let me just check it. And…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:07",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Okay, just to, like, double check, so the fix that was linked here, like, 20 minutes ago, the iOS fix.ai fire on board registration loop 7147. This fixes the root cause that was exposing this incident, correct?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:24",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yes."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:25",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Where are we with releasing this?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:28",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "PR open against current internal orders."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:35",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Okay, Joey, are you blocked, or do you need, like, any help with that, or just, like, try to engage more people if needed?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:44",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "No, we will need Haniel, who is on the release rotation this week."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:48",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Increase."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:49",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Mm-hmm."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:50",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "To to to the hot fix process for us. So basically."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:56",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Okay."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:57",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Okay."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:58",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Could you ping him in the channel?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:58",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Включи, Пинхим, Индо, Инде, Ченнел?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:48:59",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Thank you. Hanyu, Hanyu was on the previous Zoom call. He just had to escape to some other meeting, but we can, like, someone… someone heard back, and…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:49:06",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Okay?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:49:11",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "and like the the there, there is a clear process and instruction how to how to do it. And so like, yeah, it should all be documented. So it should be fine, I I guess."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:49:24",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "So who can derive this, like releasing this?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:49:27",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Hanyu, I think. Like, that's the process, at least."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:49:30",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Yeah, but he's not dead."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:49:32",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Uh, I will, I will summon her. Just, just…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:49:35",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Okay, thank you."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:50:02",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Okay, I'm gonna…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:50:04",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "And for the…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:50:04",
|
||||||
|
"speaker": "Fernando Bunn",
|
||||||
|
"text": "Drop."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:50:06",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "For the prompt shown, I'm just looking at the board. And we've got, uh… 800 for the prompt shown. and hundred and sixty-nine daily. And… Onboarding restored. Dot. Strong and boldly. Restore Tap to Nick. Still… Okay. Okay. Oh, it's absorption. Yeah, here we go. 400 daily. On both Android and iPhone, unique links. Hi, Alice. iOS tablet and phone, 258 daily users going through the flow, supposedly, but not finishing. I think auto restore success. I'll do those. Click on to restore success. Success. I'm nervous. iOS phone 272, which kind of matches the… And… Pretty sure. State chapter. The source."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:51:40",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Could you share the board or what are you looking for?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:51:40",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Source. Uh, yes, one… one moment, any of these drinks? Next, uh… It's… Mm-hmm."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:51:59",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Honey, sorry, I brought you here. Quick context. So we have a fix."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:07",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Thank you."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:07",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Um, it's been, like, reviewed."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:09",
|
||||||
|
"speaker": "Hanyu Tang",
|
||||||
|
"text": "Has it merged? No, it's not worked. Okay."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:10",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "No, not yet. I think it's been reviewed by Fernando and Hassan. It's been proven to be working, and so we would be hot-fixing it."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:23",
|
||||||
|
"speaker": "Hanyu Tang",
|
||||||
|
"text": "Okay."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:24",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "Since you're on the release rotation, could you be, like, would you be willing to do it? there's a process, there's a process, like, described in the documentation, I can share the task, like, even, like, here."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:33",
|
||||||
|
"speaker": "Hanyu Tang",
|
||||||
|
"text": "Yeah. Okay, sure."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:39",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "And. to do it. Basically, it should be automated almost on every step. But yeah, like in in kind of case, like, feel free to like ping anyone for help."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:53",
|
||||||
|
"speaker": "Hanyu Tang",
|
||||||
|
"text": "Okay. Okay, yeah. Uh…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:57",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yeah, just…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:58",
|
||||||
|
"speaker": "Hanyu Tang",
|
||||||
|
"text": "Sorry, the PR is the fixed tax AI fire onboarding, right?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:52:59",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Good question. Yeah, but it's against the…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:03",
|
||||||
|
"speaker": "Hanyu Tang",
|
||||||
|
"text": "It should be merged… It should be merged. It should not be merged into. 7241, right? It should be merged into me."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:13",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Right."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:14",
|
||||||
|
"speaker": "Hanyu Tang",
|
||||||
|
"text": "Okay, yeah."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:14",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "But…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:14",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "It should be merged to the previous one, and I'm just trying to figure out how to…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:16",
|
||||||
|
"speaker": "Hanyu Tang",
|
||||||
|
"text": "Yeah, yeah."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:18",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "I think, basically, you need to start with the task, so, like, it tells you to, like, set up hotfix release branch from main, like, it happens all automatically, and then once it happens, once there's a branch."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:19",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "How to do this."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:32",
|
||||||
|
"speaker": "JŁ",
|
||||||
|
"text": "uh… done by… by CA… CI for you, you will basically, like, Alex will rebase his fix on top of that branch, which can be then merged, and… and, yeah, basically, then… And you can go step by step."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:48",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Okay, so I'm waiting for the signal."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:48",
|
||||||
|
"speaker": "Hanyu Tang",
|
||||||
|
"text": "Okay, yeah, I already started the process."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:53:51",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Okay, and the final question, so we have around 300 daily users, uh, getting to this state. Is it worth disabling the whole synchro restoration for those, or…"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:54:02",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Yeah, I think we should disable it, and then we'll, like, after hotfix, we'll just re-enable it. That should work, right? Because it should be then fixed."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:54:12",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Yes, and there should be a button in settings, I guess."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:54:16",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "So who can disable this?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:54:16",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Just in case. I can… Oh, pink, with a, with a. Where was the config? PR. In the chat, in the Metamorph later. I have to drop off for the mid-mortem now, and I'll do this. Disabling in parallel."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:54:39",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Okay, so I can put you as a DRI for disabling the flow, right?"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:54:40",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "Sounds good. Yep, yep."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:54:46",
|
||||||
|
"speaker": "Tomasz Patrzykat",
|
||||||
|
"text": "Okay, thank you."
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"time": "21:54:47",
|
||||||
|
"speaker": "Alex Martemyanov",
|
||||||
|
"text": "And waiting for a signal from Konya. Okay, thank you."
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
+174
@@ -15,3 +15,177 @@ source: "https://us01mynotes.zoom.us/SrYbgHxMSlWioRrr4PGz2Q"
|
|||||||
- **21:21:52 · JŁ:** Basically, it breaks trust in our capability of fire things, even though it fires for people, it gives perception it is the same chat, while it's not. It's actually like the same prompt being sent over and over again. And so so that that that's the short context. There, there is additional issue that one of our teammates can reproduce. so when they open the chat from onboarding it. it loads for a long time. It's not something that was reported by users, but this is what they see. Like, it takes up to one minute for the chat to load, and we don't know whether it's because of his location. Like, it's Hassan, who's located in Egypt.
|
- **21:21:52 · JŁ:** Basically, it breaks trust in our capability of fire things, even though it fires for people, it gives perception it is the same chat, while it's not. It's actually like the same prompt being sent over and over again. And so so that that that's the short context. There, there is additional issue that one of our teammates can reproduce. so when they open the chat from onboarding it. it loads for a long time. It's not something that was reported by users, but this is what they see. Like, it takes up to one minute for the chat to load, and we don't know whether it's because of his location. Like, it's Hassan, who's located in Egypt.
|
||||||
- **21:22:38 · JŁ:** So maybe it's some kind of connectivity thing like we we don't know. But but this is what we were able to to to see why they're reproducing. But yeah, so from our findings it's not possible to to be mitigated by disabling some feature flag.
|
- **21:22:38 · JŁ:** So maybe it's some kind of connectivity thing like we we don't know. But but this is what we were able to to to see why they're reproducing. But yeah, so from our findings it's not possible to to be mitigated by disabling some feature flag.
|
||||||
- **21:23:00 · Tomasz Patrzykat:** Угу?
|
- **21:23:00 · Tomasz Patrzykat:** Угу?
|
||||||
|
- **21:23:01 · JŁ:** Uh, so we will need to go with a hotfix route, and with some expedite review, probably, uh… and given our experience, it it usually takes up to like half a day for the review, sometimes like even even quicker. So, as far as I'm aware.
|
||||||
|
- **21:23:14 · Tomasz Patrzykat:** Угу? Он Айос. Сайт, Онли? Лайк, Ноу Одер, Платформ?
|
||||||
|
- **21:23:26 · JŁ:** Yeah, yeah, yeah, definitely. Definitely, iOS. Yeah, it's a native thing.
|
||||||
|
- **21:23:28 · Tomasz Patrzykat:** Дэфнетли, Окей?
|
||||||
|
- **21:23:33 · JŁ:** So I…
|
||||||
|
- **21:23:33 · Tomasz Patrzykat:** Он. Он, фиксинг?
|
||||||
|
- **21:23:37 · JŁ:** Yeah, Alex, Alex is working on it here in the call.
|
||||||
|
- **21:23:45 · Fernando Bunn:** Ангел, Кимятый Сезон?
|
||||||
|
- **21:23:45 · JŁ:** Bye. Sorry? Yeah, as far as I'm aware, Alex has a fix already. We we just don't know if it if it fixes all the things like I. I know that. Bartek was was on a call before, and he managed to like reproduce it even in a in a like simpler scenario like, if if it still fixes the whole thing, then I I guess we we can.
|
||||||
|
- **21:24:15 · Tomasz Patrzykat:** Угу?
|
||||||
|
- **21:24:16 · JŁ:** safely say that we have a fix. So we we are just now trying to to to to check on the other thing. I I guess the the thing that Hassan found. And. Yep. Anything I missed, Alex?
|
||||||
|
- **21:24:34 · Alex Martemyanov:** На стрели? Для следствие бирри бэйс?
|
||||||
|
- **21:24:55 · Tomasz Patrzykat:** Фикс, райт?
|
||||||
|
- **21:24:55 · Fernando Bunn:** Okay, sorry.
|
||||||
|
- **21:25:03 · Tomasz Patrzykat:** Дэнни Шелфикс?
|
||||||
|
- **21:25:03 · Fernando Bunn:** Go ahead, Alex.
|
||||||
|
- **21:25:04 · Alex Martemyanov:** Игос?
|
||||||
|
- **21:25:06 · Fernando Bunn:** Alexis, I'm just happy.
|
||||||
|
- **21:25:06 · Tomasz Patrzykat:** Окей, Алекс, Окей?
|
||||||
|
- **21:25:14 · Fernando Bunn:** All right, so yeah, I'm looking at the logs here. Yeah, okay. There's a step that keeps replaying, the KI answer step. Is that the thing you saw, Alex, the fix you have there?
|
||||||
|
- **21:25:21 · Tomasz Patrzykat:** Дуй.
|
||||||
|
- **21:25:30 · Fernando Bunn:** Apparently, it's failing to get on an exit path. Like it always keeps that state no matter what. Do you have the, um… The PR? Ready?
|
||||||
|
- **21:25:43 · Fernando Bunn:** Депюар Бари?
|
||||||
|
- **21:25:45 · Fernando Bunn:** Where's the fix?
|
||||||
|
- **21:25:45 · Fernando Bunn:** Автофикс?
|
||||||
|
- **21:25:45 · Alex Martemyanov:** Не отопляры, Все?
|
||||||
|
- **21:25:50 · Fernando Bunn:** Yes, indeed.
|
||||||
|
- **21:25:50 · Fernando Bunn:** Санги? Mmhm. Okay, we're gonna try it here.
|
||||||
|
- **21:26:49 · Alex Martemyanov:** It was always there, but… I didn't completely get it, because one of the demos that Bartek held, he had no guided screen at all. Basically, the screen that sets the, uh, the flag. the fire onboarding was complete is is made by the. You've got Express. You've got it button pressed. And if there is no button, the flag is never set and the loop is always there.
|
||||||
|
- **21:27:23 · Alex Martemyanov:** But I didn't yet understand why the screen may be missing.
|
||||||
|
- **21:27:24 · Tomasz Patrzykat:** Окей?
|
||||||
|
- **21:27:30 · Alex Martemyanov:** Maybe it was recent change and I'm not aware of. Yeah, and uh… On-screen path. On the before I forget, choose to restore from sync. Resume onboarding, choose Duck AI, send the prompt, and go through the fire onboarding. And after the fire… There would be no, you've got this thing, yeah, and that's why it's synchronized, exactly. Foundation. And that's why all the users start experiencing.
|
||||||
|
- **21:28:13 · JŁ:** Sorry. So what was the culprit? Hello!
|
||||||
|
- **21:28:16 · Alex Martemyanov:** The sync restoration path that was enabled recently, and that's why it's mentioned in the task. Uh, right. In the… in the bug task. And if you choose the sync restoration path. Uh, you… Got… now you've got this screen presented. Meaning the flag is never set. So that was the activating issue. Because the bug with the button was always there, but the users were always pressing the button. And now the button is gone, because when you…
|
||||||
|
- **21:28:45 · JŁ:** Okay, and do you have a… do you do one…
|
||||||
|
- **21:28:54 · Alex Martemyanov:** Choose, uh, sync, restore from sync, restore using sync. On the "Oh, before I forget" screen. Right? So probably you choose the search path and restore from using sync.
|
||||||
|
- **21:29:44 · Fernando Bunn:** Yeah, I'm gonna… installing our… I'm starting our fix here. See if I can… I could do station again. Um… And also I'm spinning an agent review because I previous think that my phone is just like.
|
||||||
|
- **21:30:22 · Alex Martemyanov:** Yes, uh, it seems like it. Or I forget. Mmhmm. It's not the validated… the validated path, I'm just… Copying steps found. Yeah, here in the charts. At least, as it's said by Codex.
|
||||||
|
- **21:31:50 · Tomasz Patrzykat:** Эй Тэнкс?
|
||||||
|
- **21:33:05 · Fernando Bunn:** What is the behavior we want here? Like, if the user did not… Tap the fire button. Should that step be… repeated, as well? Like, we never want this to happen, right? Like, it doesn't matter what the user did or did not…
|
||||||
|
- **21:33:19 · Alex Martemyanov:** You… the user… The user cannot miss that step. Every other controller is locked in that state.
|
||||||
|
- **21:33:30 · Fernando Bunn:** What if I… what if I kill the mid without…
|
||||||
|
- **21:33:33 · Alex Martemyanov:** You would just return to the same screen.
|
||||||
|
- **21:33:36 · Fernando Bunn:** Okay. All right, yeah, so I can't… I can't reproduce the issue again with Alex Pierre. Gonna try from scratch.
|
||||||
|
- **21:33:46 · Alex Martemyanov:** Yeah, it's basically cleared as soon as you press the fire button.
|
||||||
|
- **21:33:50 · Fernando Bunn:** Yeah, I saw the change there. But I'm trying from scratch again.
|
||||||
|
- **21:33:58 · Alex Martemyanov:** Yeah, maybe the steps I just sent are not correct steps. I'm just trying to figure it out via cloud. The Sync Restore screen is called "Let's Pick Up Where You Left Off".
|
||||||
|
- **21:34:28 · Fernando Bunn:** Yeah, the two things the review here is saying, but I'll let you decide if it makes sense or not. One is the one that I called before. It found the same thing, but basically… If for some reason there's another entry point. um…
|
||||||
|
- **21:34:47 · Alex Martemyanov:** Yeah, it's the same thing, anyways.
|
||||||
|
- **21:34:47 · Fernando Bunn:** On that screen, it's gonna miss it, yeah.
|
||||||
|
- **21:34:50 · Alex Martemyanov:** Because when you get to the fire onboarding state, it sets the flag, and when you hit the fire button, it resets the flag. So that's the entry and exit.
|
||||||
|
- **21:34:50 · Fernando Bunn:** And one of… And. Okay. And another one is just this saying that it's missing tests from the call points. I don't really mind this one.
|
||||||
|
- **21:34:59 · Alex Martemyanov:** I would say. Yeah, it just makes the bug obvious for… it's just…
|
||||||
|
- **21:35:08 · Fernando Bunn:** Okay, but…
|
||||||
|
- **21:35:12 · Alex Martemyanov:** Makes the bug inevitable for all the users who use the sync feature.
|
||||||
|
- **21:35:21 · Fernando Bunn:** Okay, I'm trying again. So skip. Skip. Next. Type. Bye. Maybe it's the KI.
|
||||||
|
- **21:35:35 · Alex Martemyanov:** Yeah, so set to returning user. Restart, press restore my stuff. And get through the onboarding. Um, whatever. I need to…
|
||||||
|
- **21:36:03 · Fernando Bunn:** Okay, seems to be… I did the steps from scratch, at least the ones that Bortek reproduced seems to be working here.
|
||||||
|
- **21:36:11 · Alex Martemyanov:** Yeah, that exact scenario is reproduced, if you omit the… We've got this button, we've got the screen, but if there is no screen, yeah, it's 100% reproducible, and it's obvious, and the fix should just fix the file onboarding.
|
||||||
|
- **21:36:16 · Fernando Bunn:** Mm-mm.
|
||||||
|
- **21:36:25 · Alex Martemyanov:** And uh… probably it's not up to us to fix the flow itself, it's just the… the flag issue. So, should I rebase it to the current release branch? Origin, release, iOS.
|
||||||
|
- **21:36:42 · JŁ:** One, all right. I was talking to Thomas, and. a… If we reverted that same thing, would it fix it, or would it just make it…
|
||||||
|
- **21:36:56 · Alex Martemyanov:** No, it won't fix it. It would, uh, prevent the new users to get in. But if there is a feature flag for that flow, it should, uh… Make it.
|
||||||
|
- **21:37:13 · JŁ:** But would it still be valuable to do so? So…
|
||||||
|
- **21:37:18 · Alex Martemyanov:** Maybe. If there is a fish or flock, that's… So I don't know, I haven't produced the second path for the returning user.
|
||||||
|
- **21:37:32 · JŁ:** Okay, would you be able to check that if there's a feature flag for that like, perhaps we could do it like 2 ways like we could disable the flag. To help. Like, new users not to get into the state, and we would, like, release the hotfix too. Uh, to fix the state for users that already are in the loop.
|
||||||
|
- **21:37:58 · Alex Martemyanov:** No, the users that are already in the loop, they are… they cannot be…
|
||||||
|
- **21:38:02 · JŁ:** I know, I know. So for them, we'll release the hotfix. I'm just talking about new users, like whether like…
|
||||||
|
- **21:38:03 · Alex Martemyanov:** fixed, but…
|
||||||
|
- **21:38:07 · Tomasz Patrzykat:** Я Эленто, Нью, Юзерс?
|
||||||
|
- **21:38:08 · JŁ:** Whether changing like switching the flag would actually make it for for better for them, or.
|
||||||
|
- **21:38:43 · Fernando Bunn:** Okay, uh, do you still need me for anything here? All good?
|
||||||
|
- **21:38:48 · Alex Martemyanov:** Yes, there is Sync Auto Restore. And it's… Is it mentioned there?
|
||||||
|
- **21:38:58 · Fernando Bunn:** What is the problem with sync?
|
||||||
|
- **21:38:58 · Alex Martemyanov:** Report it. Hmm?
|
||||||
|
- **21:39:02 · Fernando Bunn:** What is the problem with sync?
|
||||||
|
- **21:39:05 · Alex Martemyanov:** The second path that restores the data and the sink was mentioned as a trigger for the issue. The fixed app now uses the sync server. For chat history, only one sync is actually on. Fix context. Accumulated AI charts deleted. And… Sync Auto Restore.
|
||||||
|
- **21:40:09 · Fernando Bunn:** Sorry, I'm not pulling. What is the issue related with syncing?
|
||||||
|
- **21:40:13 · Alex Martemyanov:** Sync restore, the sync restoration prompt, if we disable this feature flag, the sync restoration prompt should not appear. So, it means the user won't get through the sync restoration flow, and they won't get. the. Yes. Yes, but it's… But it's the common feature flag for all these encoders, not only for the onboarding.
|
||||||
|
- **21:40:45 · Tomasz Patrzykat:** О?
|
||||||
|
- **21:40:46 · Alex Martemyanov:** It does not disable sync, it disables automatic recovery of previously preserved sync account. Hide the "Let's pick up where we left off" button. And restore my stuff during onboarding. Remove the automatic restore path from sync settings. User must use QR code or recovery code or manual setup. So basically, this is automatic keychain recovery from keychain for reinstallers, and they have to… They have to sync up manually again. We can disable the whole flow, and it will mitigate this issue. But disabled synchro. They're restored with SYNCFLOW.
|
||||||
|
- **21:41:37 · Tomasz Patrzykat:** Возраисков. Дизайн Фул Сынг?
|
||||||
|
- **21:41:41 · Alex Martemyanov:** The loss of the restoration we are seeing from the keychain item for installers.
|
||||||
|
- **21:41:44 · Tomasz Patrzykat:** Угу?
|
||||||
|
- **21:41:53 · Alex Martemyanov:** So they will have to manually restore things. Or lose data, if… They have no access to the QR code anymore. At least until the next… Reinstall. That's not the case. So I'd say, uh, since… my opinion, that since it's not the really everyday use case scenario when… where you left off. The Duck or Yea chat. It may… it may be… And not a good user experience, but it's not a user breakage. And we should not remove, we should not lose user data.
|
||||||
|
- **21:42:46 · Fernando Bunn:** Yeah, so. The the. Just make sure I understand here, like, we have two different problems, right? Like, one is this onboarding thing that keeps getting into a loop. This is the incident thing that we… like, you have the PR and it's done, right? Another one is this sync issue that I didn't understand very well, but basically, if you reinstall the app, there's still sync information there that it shouldn't be. Right? The second one.
|
||||||
|
- **21:43:08 · Alex Martemyanov:** No.
|
||||||
|
- **21:43:09 · Fernando Bunn:** Is it an incident as well? Is it something that needs to be part of this?
|
||||||
|
- **21:43:12 · Alex Martemyanov:** No, it's, uh, it's the same, it's the same issue.
|
||||||
|
- **21:43:16 · Fernando Bunn:** So it's related to onboarding as well?
|
||||||
|
- **21:43:19 · Alex Martemyanov:** Yes, so when you have… so how would they use… how the new users are getting into the loop? Because normally, and the issue was there for a while already, it was half a year since it was merged, but we've started receiving this incident only recently, with this sink restoration. It's a reaction, because…
|
||||||
|
- **21:43:40 · Fernando Bunn:** Okay, so it… Okay, it feels like the other one is way more… pressing time-related, like, for us to fix as soon as possible, and this one is not. I don't know if I'm wrong here.
|
||||||
|
- **21:43:51 · Tomasz Patrzykat:** Депендских? Дат. С. Мои андрестанников Да Ищи? Инту, Дис? Он, ореваясь?
|
||||||
|
- **21:44:10 · Alex Martemyanov:** Everybody who is doing this in restoration.
|
||||||
|
- **21:44:21 · Tomasz Patrzykat:** Генджек?
|
||||||
|
- **21:44:23 · Fernando Bunn:** So… Yeah, so to reproduce this, I need to have, like, sync enable, and then… Delete the app, install the app again.
|
||||||
|
- **21:44:34 · Alex Martemyanov:** No, uh, yes. Yes.
|
||||||
|
- **21:44:39 · Fernando Bunn:** Okay.
|
||||||
|
- **21:44:39 · Alex Martemyanov:** Delete the app and reinstall again and restore from sync.
|
||||||
|
- **21:44:47 · JŁ:** So it doesn't occur to completely new users to DuckDuckGo?
|
||||||
|
- **21:44:53 · Alex Martemyanov:** Hm?
|
||||||
|
- **21:44:54 · JŁ:** It doesn't even.
|
||||||
|
- **21:44:54 · Alex Martemyanov:** Sure.
|
||||||
|
- **21:44:56 · JŁ:** New users to DuckDuckGo who never had an app before on their phone. This is not gonna be triggered for them. You're saying?
|
||||||
|
- **21:45:04 · Alex Martemyanov:** Uh, they shouldn't, in general. So it's only the case when you… you kill the app and they got this screen. But it's been there for a while already, and we haven't received a lot of feedback about it. Before. So it's the condition that you have… that you should have three, uh… 3 consequences, 3 cases, 3 events in a row. So, missing this… button then. Entering the Dakaria chat and. Restarting the app with Duck AI Chart active.
|
||||||
|
- **21:45:44 · JŁ:** So okay, okay, I need to double check. So you're saying, if I if I have a raw simulator. I shouldn't be able to even reproduce the issue.
|
||||||
|
- **21:45:55 · Alex Martemyanov:** Perfect.
|
||||||
|
- **21:45:57 · JŁ:** Okay. I can check. Just to be double sure.
|
||||||
|
- **21:46:03 · Alex Martemyanov:** So, in general, if you just press the… you've got this button. It won't be there. Yes. Yes. That's the case.
|
||||||
|
- **21:46:58 · Tomasz Patrzykat:** Ол. Пробэмс?
|
||||||
|
- **21:47:00 · JŁ:** I think, I think it fixes them. Uh, at least the one that… that incident reports were telling about right? Alex. And Fernando, like, you were checking it…
|
||||||
|
- **21:47:13 · Alex Martemyanov:** Yes, who is, uh… who is getting to the screen? They will have to do the fire button thing again, but the next time it's fixed. It won't appear anymore.
|
||||||
|
- **21:47:26 · JŁ:** Okay.
|
||||||
|
- **21:47:31 · Alex Martemyanov:** And there is sync auto restore success excel. Use parameter source equals onboarding. And for users who only tapped restore my stuff. There is another pixel. Let me just check it. And…
|
||||||
|
- **21:48:07 · Tomasz Patrzykat:** Okay, just to, like, double check, so the fix that was linked here, like, 20 minutes ago, the iOS fix.ai fire on board registration loop 7147. This fixes the root cause that was exposing this incident, correct?
|
||||||
|
- **21:48:24 · Alex Martemyanov:** Yes.
|
||||||
|
- **21:48:25 · Tomasz Patrzykat:** Where are we with releasing this?
|
||||||
|
- **21:48:28 · Alex Martemyanov:** PR open against current internal orders.
|
||||||
|
- **21:48:35 · Tomasz Patrzykat:** Okay, Joey, are you blocked, or do you need, like, any help with that, or just, like, try to engage more people if needed?
|
||||||
|
- **21:48:44 · JŁ:** No, we will need Haniel, who is on the release rotation this week.
|
||||||
|
- **21:48:48 · Alex Martemyanov:** Increase.
|
||||||
|
- **21:48:49 · Tomasz Patrzykat:** Mm-hmm.
|
||||||
|
- **21:48:50 · JŁ:** To to to the hot fix process for us. So basically.
|
||||||
|
- **21:48:56 · Tomasz Patrzykat:** Okay.
|
||||||
|
- **21:48:57 · JŁ:** Okay.
|
||||||
|
- **21:48:58 · Tomasz Patrzykat:** Could you ping him in the channel?
|
||||||
|
- **21:48:58 · Tomasz Patrzykat:** Включи, Пинхим, Индо, Инде, Ченнел?
|
||||||
|
- **21:48:59 · JŁ:** Thank you. Hanyu, Hanyu was on the previous Zoom call. He just had to escape to some other meeting, but we can, like, someone… someone heard back, and…
|
||||||
|
- **21:49:06 · Tomasz Patrzykat:** Okay?
|
||||||
|
- **21:49:11 · JŁ:** and like the the there, there is a clear process and instruction how to how to do it. And so like, yeah, it should all be documented. So it should be fine, I I guess.
|
||||||
|
- **21:49:24 · Tomasz Patrzykat:** So who can derive this, like releasing this?
|
||||||
|
- **21:49:27 · JŁ:** Hanyu, I think. Like, that's the process, at least.
|
||||||
|
- **21:49:30 · Tomasz Patrzykat:** Yeah, but he's not dead.
|
||||||
|
- **21:49:32 · JŁ:** Uh, I will, I will summon her. Just, just…
|
||||||
|
- **21:49:35 · Tomasz Patrzykat:** Okay, thank you.
|
||||||
|
- **21:50:02 · Fernando Bunn:** Okay, I'm gonna…
|
||||||
|
- **21:50:04 · Alex Martemyanov:** And for the…
|
||||||
|
- **21:50:04 · Fernando Bunn:** Drop.
|
||||||
|
- **21:50:06 · Alex Martemyanov:** For the prompt shown, I'm just looking at the board. And we've got, uh… 800 for the prompt shown. and hundred and sixty-nine daily. And… Onboarding restored. Dot. Strong and boldly. Restore Tap to Nick. Still… Okay. Okay. Oh, it's absorption. Yeah, here we go. 400 daily. On both Android and iPhone, unique links. Hi, Alice. iOS tablet and phone, 258 daily users going through the flow, supposedly, but not finishing. I think auto restore success. I'll do those. Click on to restore success. Success. I'm nervous. iOS phone 272, which kind of matches the… And… Pretty sure. State chapter. The source.
|
||||||
|
- **21:51:40 · Tomasz Patrzykat:** Could you share the board or what are you looking for?
|
||||||
|
- **21:51:40 · Alex Martemyanov:** Source. Uh, yes, one… one moment, any of these drinks? Next, uh… It's… Mm-hmm.
|
||||||
|
- **21:51:59 · JŁ:** Honey, sorry, I brought you here. Quick context. So we have a fix.
|
||||||
|
- **21:52:07 · Alex Martemyanov:** Thank you.
|
||||||
|
- **21:52:07 · JŁ:** Um, it's been, like, reviewed.
|
||||||
|
- **21:52:09 · Hanyu Tang:** Has it merged? No, it's not worked. Okay.
|
||||||
|
- **21:52:10 · JŁ:** No, not yet. I think it's been reviewed by Fernando and Hassan. It's been proven to be working, and so we would be hot-fixing it.
|
||||||
|
- **21:52:23 · Hanyu Tang:** Okay.
|
||||||
|
- **21:52:24 · JŁ:** Since you're on the release rotation, could you be, like, would you be willing to do it? there's a process, there's a process, like, described in the documentation, I can share the task, like, even, like, here.
|
||||||
|
- **21:52:33 · Hanyu Tang:** Yeah. Okay, sure.
|
||||||
|
- **21:52:39 · JŁ:** And. to do it. Basically, it should be automated almost on every step. But yeah, like in in kind of case, like, feel free to like ping anyone for help.
|
||||||
|
- **21:52:53 · Hanyu Tang:** Okay. Okay, yeah. Uh…
|
||||||
|
- **21:52:57 · Alex Martemyanov:** Yeah, just…
|
||||||
|
- **21:52:58 · Hanyu Tang:** Sorry, the PR is the fixed tax AI fire onboarding, right?
|
||||||
|
- **21:52:59 · Alex Martemyanov:** Good question. Yeah, but it's against the…
|
||||||
|
- **21:53:03 · Hanyu Tang:** It should be merged… It should be merged. It should not be merged into. 7241, right? It should be merged into me.
|
||||||
|
- **21:53:13 · Alex Martemyanov:** Right.
|
||||||
|
- **21:53:14 · Hanyu Tang:** Okay, yeah.
|
||||||
|
- **21:53:14 · JŁ:** But…
|
||||||
|
- **21:53:14 · Alex Martemyanov:** It should be merged to the previous one, and I'm just trying to figure out how to…
|
||||||
|
- **21:53:16 · Hanyu Tang:** Yeah, yeah.
|
||||||
|
- **21:53:18 · JŁ:** I think, basically, you need to start with the task, so, like, it tells you to, like, set up hotfix release branch from main, like, it happens all automatically, and then once it happens, once there's a branch.
|
||||||
|
- **21:53:19 · Alex Martemyanov:** How to do this.
|
||||||
|
- **21:53:32 · JŁ:** uh… done by… by CA… CI for you, you will basically, like, Alex will rebase his fix on top of that branch, which can be then merged, and… and, yeah, basically, then… And you can go step by step.
|
||||||
|
- **21:53:48 · Alex Martemyanov:** Okay, so I'm waiting for the signal.
|
||||||
|
- **21:53:48 · Hanyu Tang:** Okay, yeah, I already started the process.
|
||||||
|
- **21:53:51 · Alex Martemyanov:** Okay, and the final question, so we have around 300 daily users, uh, getting to this state. Is it worth disabling the whole synchro restoration for those, or…
|
||||||
|
- **21:54:02 · Tomasz Patrzykat:** Yeah, I think we should disable it, and then we'll, like, after hotfix, we'll just re-enable it. That should work, right? Because it should be then fixed.
|
||||||
|
- **21:54:12 · Alex Martemyanov:** Yes, and there should be a button in settings, I guess.
|
||||||
|
- **21:54:16 · Tomasz Patrzykat:** So who can disable this?
|
||||||
|
- **21:54:16 · Alex Martemyanov:** Just in case. I can… Oh, pink, with a, with a. Where was the config? PR. In the chat, in the Metamorph later. I have to drop off for the mid-mortem now, and I'll do this. Disabling in parallel.
|
||||||
|
- **21:54:39 · Tomasz Patrzykat:** Okay, so I can put you as a DRI for disabling the flow, right?
|
||||||
|
- **21:54:40 · Alex Martemyanov:** Sounds good. Yep, yep.
|
||||||
|
- **21:54:46 · Tomasz Patrzykat:** Okay, thank you.
|
||||||
|
- **21:54:47 · Alex Martemyanov:** And waiting for a signal from Konya. Okay, thank you.
|
||||||
@@ -42,8 +42,8 @@
|
|||||||
"note_modified_at": "2026-10-06T15:56:27.185Z",
|
"note_modified_at": "2026-10-06T15:56:27.185Z",
|
||||||
"source_url": "https://us01mynotes.zoom.us/SrYbgHxMSlWioRrr4PGz2Q",
|
"source_url": "https://us01mynotes.zoom.us/SrYbgHxMSlWioRrr4PGz2Q",
|
||||||
"folder": "2026-10-06 SRE Incidents 2026-10-06 21 21(GMT+6 00) SrYbgHxMSlWioRrr4PGz2Q",
|
"folder": "2026-10-06 SRE Incidents 2026-10-06 21 21(GMT+6 00) SrYbgHxMSlWioRrr4PGz2Q",
|
||||||
"sha256": "05510fa603e25b751d587873a5634b8026d404c7c0da46a0b6b0f85a41740897",
|
"sha256": "c614bdf0e565eb8949b473ac558952700eb5cffb7c3fa14e21c74f0b1a6df8ff",
|
||||||
"cues": 3
|
"cues": 177
|
||||||
},
|
},
|
||||||
"gUhtLoqRTfSsTbZsann73A": {
|
"gUhtLoqRTfSsTbZsann73A": {
|
||||||
"title": "Jacek Łyp's Zoom Meeting 2026-10-06 20:44(GMT+6:00)",
|
"title": "Jacek Łyp's Zoom Meeting 2026-10-06 20:44(GMT+6:00)",
|
||||||
|
|||||||
@@ -1 +1 @@
|
|||||||
{"observed_at":"2026-11-20T13:42:57.639Z","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"}
|
{"observed_at":"2026-11-20T14:45:41.396Z","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"}
|
||||||
Reference in new issue
Block a user