enso-bot[bot]

**Hubert Plociniczak** reports a new **STANDUP** for the provided date (2024-05-29): **Progress:** Still rewriting ModuleScope, also investigated regression in nightly. Created #10123 with a hotfix It should be finished by...

**Hubert Plociniczak** reports a new **STANDUP** for the provided date (2024-05-30): **Progress:** Investigating follow up for #10123, nightly still broken. Threw away some work on to start from scratch. Not...

**Hubert Plociniczak** reports a new **STANDUP** for the provided date (2024-05-31): **Progress:** Ditched most of the troubling API, leaving only a few places where builder is exposed. Few tests are...

**Hubert Plociniczak** reports a new **🔴 DELAY** for the provided date (2024-06-03): **Summary:** There is **6 days** delay in implementation of the [Avoid global compilation locks with visualizations to speedup...

**Hubert Plociniczak** reports a new **STANDUP** for the provided date (2024-06-03): **Progress:** Final cleanup to PR. It should be finished by 2024-06-06. **Next Day:** Next day I will be working...

**Hubert Plociniczak** reports a new **STANDUP** for yesterday (2024-06-04): **Progress:** Undrafted PR, addressing comments, testing. Reduced time. It should be finished by 2024-06-06. **Next Day:** Next day I will be...

**Hubert Plociniczak** reports a new **STANDUP** for the provided date (2024-06-05): **Progress:** Final changes to ModuleScope refactoring. Resurrecting Jackson replacement work in #10035. It should be finished by 2024-06-06. **Next...

**Ilya Bogdanov** reports a new **STANDUP** for the provided date (2024-04-15): **Progress:** Further bisecting inside the PR that caused the issue. It is enabled by dependency update, but the diff...

**Ilya Bogdanov** reports a new **STANDUP** for the provided date (2024-04-16): **Progress:** Trying to find the offending package without much success. Found a workaround: setting `polling: true` in vite config...

**Ilya Bogdanov** reports a new **STANDUP** for the provided date (2024-04-19): **Progress:** After some debugging, we found that the issue is caused by fsevents package becoming enabled (it was optional...