EOD. Most of migration competitions are migrated to the new model. Some are still ongoing
Wave
Dev Team Chat
Generate Summary
Choose a timeframe to see summary coverage.
Drops
-
-
EOD: the after-hours scroll from @[prxt0] October 9, 2026 Done - [FE] [PR #4201](https://github.com/6529-Collections/6529seize-frontend/pull/4201) Fix E2E readiness and dependency installation - Issue: Browser coverage can start before startup access; Fix: Wait for the required interactive state. - [BE] [PR #2141](https://github.com/6529-Collections/6529seize-backend/pull/2141) Bound subscription cache eviction and recover failed invalidations - [FE] [PR #4204](https://github.com/6529-Collections/6529seize-frontend/pull/4204) Restore authenticated Wave typing indicators - Issue: Wave typing notifications stopped reaching users; Fix: Authenticate the dedicated wave listener before subscribing. In-Flight - [BE] [PR #2143](https://github.com/6529-Collections/6529seize-backend/pull/2143) Automate Drop Forge launches with AWS KMS and durable EMMA jobs - Issue: Drop Forge claim initialization; Fix: Implement a manually armed. - [FE] [PR #4207](https://github.com/6529-Collections/6529seize-frontend/pull/4207) Sync Drop Forge automation contracts and alert mentions - Issue: new Drop Forge backend introduces launch/preparation contracts and an; Fix: Synchronize OpenAPI/generated models from. - [BE] [PR #1979](https://github.com/6529-Collections/6529seize-backend/pull/1979) Route ordinary backend Ethereum reads through configurable RPC - Issue: Ordinary Ethereum reads still derived Alchemy URLs from the API key; Fix: Route ordinary mainnet blocks. - [Core] [PR #240](https://github.com/6529-Collections/6529-core/pull/240) Sync latest frontend into desktop renderer - Summary: Update the bundled renderer to frontend main 8f1197d07a5517e69eb9e4b8ac554a593fbfaff4 (checked 2026-10-09). - [BE] [PR #2111](https://github.com/6529-Collections/6529seize-backend/pull/2111) Persist WebSocket delivery with capability-aware durable retries - [FE] [PR #4128](https://github.com/6529-Collections/6529seize-frontend/pull/4128) Opt into durable WebSocket delivery and reject stale updates - [BE] [PR #2140](https://github.com/6529-Collections/6529seize-backend/pull/2140) Use device video posters with backend generation as fallback - Issue: Chat needs a lightweight preview before Play; Fix: Accept a small JPEG captured on the device during video upload. - [FE] [PR #4178](https://github.com/6529-Collections/6529seize-frontend/pull/4178) Reduce mobile background work and make chat videos click-to-play - Issue: Mobile background activity consumes battery; Fix: Pause unnecessary mobile work. Notes - All three features—Alchemy RPC, WebSocket updates, and Mobile App Battery & Video/Poster updates—are good to go. Holding off deployment until Monday morning. - Started briefly on Drop Forge Launch automation.
-
gm. got the whole staging migrated yesterday. now migrating prod
-
gm. still sick, but keep prompting something
-
gmgm continuing from above
-
EOD: dispatches from @[prxt0]'s command center October 8, 2026 Done - [FE] [PR #4197](https://github.com/6529-Collections/6529seize-frontend/pull/4197) Prevent desktop layout flash on mobile web startup - Issue: Opening 6529.io in a mobile browser briefly displays the desktop sidebar; Fix: Prepare the mobile web shell during HTML parsing. In-Flight - [BE] [PR #1979](https://github.com/6529-Collections/6529seize-backend/pull/1979) Route ordinary backend Ethereum reads through configurable RPC - Issue: Ordinary Ethereum reads still derived Alchemy URLs from the API key; Fix: Route ordinary mainnet blocks. - [BE] [PR #2111](https://github.com/6529-Collections/6529seize-backend/pull/2111) Persist WebSocket delivery with capability-aware durable retries - [FE] [PR #4201](https://github.com/6529-Collections/6529seize-frontend/pull/4201) Fix staging access and navigation E2E readiness - [BE] [PR #2141](https://github.com/6529-Collections/6529seize-backend/pull/2141) Bound subscription cache eviction and recover failed invalidations - [Core] [PR #240](https://github.com/6529-Collections/6529-core/pull/240) Sync latest frontend into desktop renderer - Summary: Update the bundled renderer to frontend main f9c1ff656be2352794bd3cd33210e5027ee2e474 (checked 2026-10-08). - [FE] [PR #4128](https://github.com/6529-Collections/6529seize-frontend/pull/4128) Opt into durable WebSocket delivery and reject stale updates - [FE] [PR #4178](https://github.com/6529-Collections/6529seize-frontend/pull/4178) Reduce mobile background work and make chat videos click-to-play - Issue: Mobile media and chat background work consume battery; Fix: Pause unnecessary work. - [BE] [PR #2140](https://github.com/6529-Collections/6529seize-backend/pull/2140) Generate preview images for uploaded chat videos
-
**EOD – 8 October** **Live** - Confirmed Waves usage tracking reaches Mixpanel and created a dashboard showing which controls people see, use and return to. **WIP** - Built the Dev Team monitoring dashboard for frontend and backend errors, with high-priority issues, spikes and 30-day history. Local tests and desktop/mobile checks passed; deployment is pending. - Merged two Release Coordinator fixes: wait for GitHub to finish checking a merge, and allow approved test retries while preserving earlier results. **Investigated** - Early usage data shows Active Votes and Leaderboard getting the most use. More history is needed before deciding what to hide or remove. - The failed long-post browser test passed when rerun without code changes. A temporary testing problem looks more likely, but the original cause remains unconfirmed. **Next** - Retry the long-post release through fresh checks, staging and then production. It remains stopped before deployment. - Commit the latest monitoring additions and deploy the backend before the frontend.
-
@devs6529 trying to fix staging e2e please dont fix anything about it in another branch i have a PR to do this all together maybe tell your agents to keep in mind this PR https://github.com/6529-Collections/6529seize-frontend/pull/4201 and not redo any work done here
-
no hurry, but let me know when its done
-
i think (and hope and pray) that this is fixed now following the merging of this pr https://github.com/6529-Collections/6529seize-frontend/pull/4201 🤞
-
-
-
@[GelatoGenesis] could you please do one of these? i need to be able machine read sentry better
-
i escalated you to manager. knock yourself out
-
-
gm. rehearsing through migrations in staging (and hopefully get to prod)
-
gm. still not feeling good. but doing "one task" prompting and whatever i am able. sitting around is jut boring...
-
BOD. forgot to write yesterday's eod: improved network group and rep/nic forms, made profile collected easier to browse on mobile, added usage tracking, fixed the iphone artwork zoom. Today i'm continuing with mixpanel and ux tasks
-
gmgm continuing on open tasks just a brief outline of the three main things i been working on because it's quite the long running tasks: - Alchemy: Migrating backend Ethereum reads to a configurable RPC provider, fixing ENS lookups, and validating transaction discovery and pricing -- the idea is that instead of alchemy sdk or whatever we use RPC URLs where applicable so that transitioning to another RPC URL is just a matter of changing env - WebSockets: Reworking WebSocket delivery with durable queues and retries so temporary failures don’t lose updates, plus frontend safeguards against delayed updates overwriting newer state. - Mobile App: Reducing mobile battery drain, making chat videos click-to-play, and adding video thumbnails. -- the theory is that when landing on a chat a bunch of videos all start loading together and especially on mobile (but i think there's impact on desktops too just people realize this less) theres too much downloading and battery usage - working on making this not autoplay and also create a poster to show instead of a black square before users click on to actually play the videos
-
EOD: the evening rollup of @[prxt0]'s adventures October 7, 2026 Done - [BE] [PR #2138](https://github.com/6529-Collections/6529seize-backend/pull/2138) Fix S3 image gateway fallback and zero-byte recovery - Issue: S3 image downloads treated an empty HTTP 200 response as success; Fix: Validate nonempty image bytes. - [BE] [PR #2137](https://github.com/6529-Collections/6529seize-backend/pull/2137) Synchronize automatic subscription quantities with eligibility - [FE] [PR #4175](https://github.com/6529-Collections/6529seize-frontend/pull/4175) Restore manual subscription quantity when eligibility recovers - Issue: A manual subscription quantity of 11 is visually clamped to 10; Fix: Cap only the rendered dropdown value with the current eligibility. In-Flight - [BE] [PR #1979](https://github.com/6529-Collections/6529seize-backend/pull/1979) Route ordinary backend Ethereum reads through configurable RPC - Issue: Ordinary Ethereum reads still derived Alchemy URLs from the API key; Fix: Route ordinary mainnet blocks. - [FE] [PR #4128](https://github.com/6529-Collections/6529seize-frontend/pull/4128) Prevent delayed WebSocket updates from restoring stale state - Issue: Delayed WebSocket delivery can overwrite a newer edit or NFT preview; Fix: Reject older drop revisions in live state and query caches. - [BE] [PR #2111](https://github.com/6529-Collections/6529seize-backend/pull/2111) Persist WebSocket delivery from business commit through durable retries - Issue: Production outbound WebSocket sends were being throttled; Fix: Persist delivery intent in a transactional MySQL outbox. - [BE] [PR #2140](https://github.com/6529-Collections/6529seize-backend/pull/2140) Generate preview images for uploaded chat videos - Issue: Chat videos wait for Play to save downloading and decoding; Fix: Generate one JPEG from the first frame in the existing MediaConvert job. - [Core] [PR #240](https://github.com/6529-Collections/6529-core/pull/240) Sync latest frontend into desktop renderer - Summary: Update the bundled renderer to frontend main 4203aaf54fcdf9793743efffa183fbffee28ebfe (checked 2026-10-07). - [FE] [PR #4178](https://github.com/6529-Collections/6529seize-frontend/pull/4178) Reduce mobile background work and make chat videos click-to-play - Issue: Mobile app battery complaints exposed unnecessary background work; Fix: Require explicit playback in chat message lists on every device.
-
need to wrap up for today. a family event. but i've been working on two things both of which are in flight: 1. wave tabs organisation. concept is finally clear and first implementation is done. agents are working on getting it to staging 2. old waves migrator. its done and tested locally. also in flight to staging so i could start testing there
-
looking into the s3 issue
-
gm. continuing with wip tasks
-
gmgm prioritising closing open tasks
-
gm. starting from visuals. tabs related to competitions need better separation from general wave tabs.
-
gm I am bit of sick, getting day off mostly and resting. Doing some prompting thru phone for tasks what dont need visuals checkups (release bus etc)
-
## EOD — 6 October ### Deployed - Shipped the simpler Chat Wave creation flow: a visible creation entry, two screens instead of five, draft recovery and copy-link confirmation. - Shipped clearer competition submissions with better confirmation, recovery and direct access to **My submissions**. The matching production deployment and browser checks passed. ### WIP - Built the protected monitoring foundation across the frontend and backend. Dev Team members can enter, while signed-out users, nonmembers and proxy sessions are blocked; focused tests and local builds pass. It remains local and uncommitted. - Built the first privacy-safe Wave usage measurement pilot. All checks pass, but the PR is open and behind the latest `main`. - Added an optional public **Your plan** field for Additional Action submissions. Saving and display were verified with a real staging submission, and all PR checks pass. - Added on-demand explanations for restricted Wave submissions without cluttering the chat. The PR is open and its final checks are still running. - Drafted safer vote-allocation setup with clearer choices, examples and fresh-wave recovery. Backend enforcement and full validation are still unfinished. - Merged several Release Coordinator safety updates covering approved workflow versions and clean cancellation of interrupted staging preparation. ### Blocked / next - The fresh long-post release passed its feature checks, but GitHub rejected the Coordinator’s staging preparation. Staging and production are unchanged; investigate the tool error, fix it through review, then resume the same release. - Finish the monitoring commits and PR, refresh the measurement branch, and complete backend enforcement and tests for vote allocation.
-
EOD: what @[prxt0] pushed, polished, and poked at today October 6, 2026 Done - [BE] [PR #2135](https://github.com/6529-Collections/6529seize-backend/pull/2135) Replace deprecated Etherscan randomizer lookup with Sourcify In-Flight - [BE] [PR #2137](https://github.com/6529-Collections/6529seize-backend/pull/2137) Synchronize automatic subscription quantities with eligibility - [FE] [PR #4175](https://github.com/6529-Collections/6529seize-frontend/pull/4175) Restore manual subscription quantity when eligibility recovers - Issue: A manual subscription quantity of 11 is visually clamped to 10; Fix: Cap only the rendered dropdown value with the current eligibility. - [FE] [PR #4178](https://github.com/6529-Collections/6529seize-frontend/pull/4178) Reduce mobile background work and make chat videos click-to-play - Issue: Mobile app battery complaints exposed unnecessary background work; Fix: Require explicit playback in chat message lists on every device. - [Core] [PR #240](https://github.com/6529-Collections/6529-core/pull/240) Sync latest frontend into desktop renderer - Summary: Update the bundled renderer to frontend main 46b1deff32bec67b4f07a12bbc634064d6ab220a (checked 2026-10-06). - [BE] [PR #2111](https://github.com/6529-Collections/6529seize-backend/pull/2111) Persist WebSocket delivery from business commit through durable retries - Issue: Production outbound WebSocket sends were being throttled; Fix: Persist delivery intent in a transactional MySQL outbox. - [BE] [PR #1979](https://github.com/6529-Collections/6529seize-backend/pull/1979) Route ordinary backend Ethereum reads through configurable RPC - Issue: Ordinary Ethereum reads still derived Alchemy URLs from the API key; Fix: Route ordinary mainnet blocks. - [FE] [PR #4128](https://github.com/6529-Collections/6529seize-frontend/pull/4128) Prevent delayed WebSocket updates from restoring stale state - Issue: Delayed WebSocket delivery can overwrite a newer edit or NFT preview; Fix: Reject older drop revisions in live state and query caches.
-
EOD Completed - Added homepage engagement tracking to understand which sections people see and which actions they use. - Improved Wave sidebar controls, mobile keyboard handling, and navigation between the Wave list and conversations. - Simplified Network filtering with visible categories, clearer selected criteria, and easier navigation on smaller screens. - Refined REP and NIC dialogs and profile buttons with clearer spacing and more consistent controls. WIP - Improving mobile Collected browsing with clearer filters, readable artwork cards, and return navigation that preserves your place.
-
@[punk6529] i'd like to run a couple things by you a) tested with teexels and 6529er yesterday the admin feature on manifold and we figured we can basically automate the whole process of initializing and updating claims - i'd like to start working on this as soon as I wrap up open thing b) for subscriptions eligibility currently we use 'number of full current season sets' which is a bit silly because say of card 2 of a season its like the number of card1 copies you have so someone can get idk x50 of card1 of the season and basically be allowed to get 50 per card for that season and future seasons - i believe this is not the way it should work alternative suggestion: have the first 3 cards of the season use eligibility of last seasons full sets and card4 and after use current season sets - please let me know what you think about this
-
i realize the purpose of this design is to encourage new adopters but idk sounds a bit unfair probably not sure :slightly_frowning_face:
-
-
gmgm continuing with my open tickets
-
gm. continuing with open tasks
-
gm. continue with attacking e2e instability
-
gm. i keep going with my wips
-
## EOD — 5 October ### Deployed - Made wallet consolidation easier to find from the profile, with a clear **Add another wallet** action and better instructions. Existing backend, authentication and signing logic stayed unchanged; the production deployment and matching browser checks passed. ### WIP - Simplified Chat Wave creation from five screens to two, added a visible creation entry, draft recovery and copy-link confirmation. Desktop and mobile staging tests passed, and all PR checks are green. - Building a clearer competition-submission experience with **My submissions**, better confirmation and error states, and responsive controls. The implementation is still local; automated checks and the PR are next. - Merged the Release Coordinator’s release board, safe cleanup flow and improved workflow waiting. Sandbox tests proved both a normal release and successful recovery from a forced failure. - Rebuilt Gelato’s report into a strict issue list: only two clearly identical pairs were combined, while the other cases stayed separate. ### Investigated - Reproduced intermittent NFT activity failures on staging and production: requests occasionally returned HTTP 504 after about 29 seconds. After the backend change, 12/12 direct checks passed, although intermittent failures are not fully ruled out. - Completed the first feature-usage audit. Current tracking cannot reliably show which controls are unused, and a possible Mixpanel URL/referrer privacy issue needs resolving before the measurement pilot. ### Blocked / next - A fresh long-post release ticket is ready, but deployment is paused because the frontend test workflow changed beyond the Coordinator’s approved version. Update and review that version first, then continue the isolated release. - Finish the competition-submission work and start the privacy-safe feature tracking pilot.
-
**EOD — 5 October** **Deployed** - Restored each wave’s remembered tab and put Chat first in Memes wave navigation, so switching waves preserves where you left off. [Production confirmed](https://github.com/6529-Collections/6529seize-frontend/actions/runs/37324509642). - Fixed slow NFT activity loading with smaller queries and read-replica routing. Sampled production requests completed in under a second, and the previously failing activity test passed. [Production confirmed](https://github.com/6529-Collections/6529seize-backend/actions/runs/37303876663). **In progress** - Fixed score popovers covering the wave-search close button. Validated on staging with all 10 search tests passing; not yet in production. - Fixed production canaries selecting outdated deployments and checking pages before data was ready. Merged and passed staging validation; production deployment is still running. **Investigated** - Traced remaining Museum E2E failures to intermittent external image loading, affecting both staging and production. - Investigated sidebar hydration failures; the test’s tight loading window is a likely contributor, but the diagnosis remains provisional. **Blocked / next** - Complete production rollout validation and address the remaining E2E failures. The broader production suite is still red. Or to sum up. E2E is really flaky, fixed some of it, wil fix the rest tomorrow
-
EOD: a tidy little dispatch from @[prxt0] October 5, 2026 Done - [BE] [PR #2134](https://github.com/6529-Collections/6529seize-backend/pull/2134) Allow creator owner and admins to track Drop Forge claim actions - Issue: An approved creator admin can operate claims on-chain; Fix: Authorize configured claims admins. - [FE] [PR #4160](https://github.com/6529-Collections/6529seize-frontend/pull/4160) Manage creator admins and expand Drop Forge Launch access - Issue: Drop Forge needs an owner-first view of creator-contract admins; Fix: Add Contract Admins below the Craft/Launch cards. - [FE] [PR #4161](https://github.com/6529-Collections/6529seize-frontend/pull/4161) Fix missing Next Drop artwork on mobile - Issue: Next Drop artwork disappears on phone browsers; Fix: Keep the drop image content wrapper in normal flow below 1024px. - [BE] [PR #2129](https://github.com/6529-Collections/6529seize-backend/pull/2129) Expose publication timestamps for all drop metadata - [FE] [PR #4137](https://github.com/6529-Collections/6529seize-frontend/pull/4137) Fix publication dates in Wave drop structured data - Issue: Google Search Console reported invalid discussion-forum items; Fix: Use the genuine drop.created_at timestamp from backend PR #2129. - [BE] [PR #2128](https://github.com/6529-Collections/6529seize-backend/pull/2128) Explain operational failures and verified retry state in alerts In-Flight - [BE] [PR #2135](https://github.com/6529-Collections/6529seize-backend/pull/2135) Replace deprecated Etherscan randomizer lookup with Sourcify - [FE] [PR #4128](https://github.com/6529-Collections/6529seize-frontend/pull/4128) Prevent delayed WebSocket updates from restoring stale state - Issue: Delayed WebSocket delivery can overwrite a newer edit or NFT preview; Fix: Reject older drop revisions in live state and query caches. - [BE] [PR #1979](https://github.com/6529-Collections/6529seize-backend/pull/1979) Route ordinary backend Ethereum reads through configurable RPC - Issue: Ordinary Ethereum reads still derived Alchemy URLs from the API key; Fix: Route ordinary mainnet blocks. - [Core] [PR #240](https://github.com/6529-Collections/6529-core/pull/240) Sync latest frontend into desktop renderer - Summary: Update the bundled renderer to frontend main 691f5774623b37aa8f2379e409148a1625df28c7 (checked 2026-10-05). - [BE] [PR #2111](https://github.com/6529-Collections/6529seize-backend/pull/2111) Persist WebSocket delivery from business commit through durable retries - Issue: Production outbound WebSocket sends were being throttled; Fix: Persist delivery intent in a transactional MySQL outbox.
-
EOD WIP Simplified Network filtering so all eight options are visible and easier to use on desktop and mobile. Next: visual review. Refined the REP and NIC dialogs with clearer layouts and one-point amount controls. Next: finish visual review.
-
yea saw the staging e2e not working on it currently i think gelato might be
-
Staging e2e tests are failing bc of this
-
@[GelatoGenesis] @[prxt0] someone aware of this issue and is fixing it or can look into it?
-
looking into it
-
let me know when its fixed
-
I now know what the issue is with somewhat high confidence. Fix it self can take hour or so until in prod.
-
this one's fixed now.
-
is prod e2e failure not related?
-
-
-
-
-
### Intermittent NFT activity timeout — staging and production The Memes card activity sometimes stays on **“Loading NFT activity…”** beyond 20 seconds. Reproduced on card #3 desktop on both sites: the activity GET eventually returned **HTTP 504 after ~29 seconds**. Later attempts returned 200 in ~1.4–1.7 seconds. Reproduction steps: 1. Open a fresh desktop Chrome private window; no wallet login needed. 2. Open [production card #3](https://6529.io/the-memes/3?focus=activity&locale=de-DE) or [staging card #3](https://staging.6529.io/the-memes/3?focus=activity&locale=de-DE) using existing staging access. 3. Confirm **History → Card Activity** is selected. In DevTools → Network, filter for `nft-activity`. 4. Observe whether loading clears within 20 seconds. The issue is intermittent; a subsequent successful visit does not establish a fix. Relevant request: ```text GET /api/nft-activity contract=0x33FD426905F149f8376e227d0C9D3340AaD17aF1 token_id=3 filter=all page_size=25 ``` Failed request windows on **2026-10-05, UTC**, for API/gateway log correlation: | Environment | Request started | HTTP 504 received | |---|---|---| | Staging | 08:30:48.800 | 08:31:17.863 | | Production | 08:31:21.331 | 08:31:50.669 | Across 24 sequential checks of cards #1–#3, there were 22 successful loads and these two timeouts. Mobile passed, although production card #3 took 17.8 seconds to display its table once. Frontend versions: staging `31d6155`; production `45b7a46`. No 429s or browser JavaScript errors were observed. **Backend/gateway cause remains unconfirmed; faster repeat visits do not prove a cache issue.**
-
summary of @[GelatoGenesis] findings
-
gm. multicomp migration
-
gm 1. release bus 2. gelato frontend report of users "complains". its pretty good, doing some sense of it 3. i have some mentions from users (and punk) about few issues. taking these
-
gm. getting back on track with everything
-
gmgm started yesterday working on some changes about admins on minting contract requested by 6529er will prioritize this and then continue with rest of open tasks
-
EOD: the small-but-mighty ledger of @[prxt0]'s day October 4, 2026 In-Flight - [BE] [PR #2134](https://github.com/6529-Collections/6529seize-backend/pull/2134) Allow creator owner and admins to track Drop Forge claim actions - Issue: An approved creator admin can operate claims on-chain; Fix: Authorize configured claims admins. - [FE] [PR #4160](https://github.com/6529-Collections/6529seize-frontend/pull/4160) Manage creator admins and expand Drop Forge Launch access - Issue: Drop Forge needs an owner-first view of creator-contract admins; Fix: Add Contract Admins below the Craft/Launch cards. - [FE] [PR #4161](https://github.com/6529-Collections/6529seize-frontend/pull/4161) Fix missing Next Drop artwork on mobile - Issue: Next Drop artwork disappears on phone browsers; Fix: Keep the drop image content wrapper in normal flow below 1024px.
-
## EOD — 2 October ### WIP - Moved the long Wave post work forward: fixed a test race and got all 23 checks green on PR #4120. The PR remains open and has not reached production. - Improved the Release Coordinator: merged the reviewed workflow refresh and the staging-aware release flow. Also built the release board and safe cleanup flow; this work is tested but still local and unmerged. ### Investigated - A real staging release failed because the desktop activity page stayed loading. The Coordinator handled this correctly: it restored the previous staging version, reran the checks successfully, and left production untouched. This was good real-world proof that recovery works. - Reviewed Gelato’s public-wave report, organized 154 groups of 6529 feedback into 15 product areas, created an interactive overview, and started identifying the highest-priority improvements. ### Blocked / next - Investigate the activity-page loading failure before attempting the release again. - Refresh PR #4120 against the latest `main`, then run a fresh release cycle. - Finish and merge the Release Coordinator board and cleanup improvements.
-
EOD: today's trail of breadcrumbs from @[prxt0] October 2, 2026 Bossman had no visible repo adventures today.
-
EOD: - Spent the whole day building the migration mechanisms for old waves. Really dangerous things so took it very seriously. I will start migrating on monday - Went through last months user issues in all public chats. Composed an analysis. Did some initial discussion with simo about this. There are definietly things to take from there and improve
-
gm doing more real repos tests with release bus and building some monitoring dashboard for it on side planning to take some feedback and look into sentry errors
-
gm. continuing with old comp migration and going through users problems for last month
-
EOD – 1 October 2026 WIP - Improved Release Coordinator so it can retest older PRs against current code, safely refresh approved CI workflows, and upload missing merged files. All three updates were merged and passed their checks. - Resumed the long-post release. The combined frontend tests passed, but the release stopped before staging because three deployment and testing files had changed since approval. Nothing reached staging or production. Blocked / next - Review and approve the changed frontend workflow files, then resume only the existing long-post release.
-
EOD: the daily artifact pile from @[prxt0] October 1, 2026 Done - [Core] new version released: [v0.3.14](https://github.com/6529-Collections/6529-core/actions/runs/36829013023). - [BE] [PR #2130](https://github.com/6529-Collections/6529seize-backend/pull/2130) Handle large Core release-note histories without imported frontend commits - [Core] [PR #238](https://github.com/6529-Collections/6529-core/pull/238) v0.3.14 In-Flight - [Core] [PR #240](https://github.com/6529-Collections/6529-core/pull/240) Sync latest frontend into desktop renderer - Summary: Sync Core renderer with frontend main at b0af0a37cb1cdca38c3e15cc89a9b55ebc27816c (checked 2026-10-01).
-
EOD Like I said, worked on the followups of multi-competitions. There's still a lot to do there to make the experience good. Today I worked on how default competitions are chosen and how old competitions play into all of it. There is a PR in flight. Also fixed the about section of waves. It had some design issues plus it had lost its pinned drop.
Loading more drops...