Skip to content

fix(discord-bot): bump dfx to 1.0.16 so the gateway hears mentions - #475

Merged
patroza merged 1 commit into
fork/devfrom
fix/dfx-1.0.16-socket-writer
Sep 18, 2026
Merged

patroza merged 1 commit into
fork/devfrom
fix/dfx-1.0.16-socket-writer

Conversation

@patroza

@patroza patroza commented Sep 18, 2026

Copy link
Copy Markdown
Owner

After the Effect 4.0.0-rc.115 weld, Omegent looks healthy (REST slash registration, rehydrate) but never receives Discord gateway events.

dfx 1.0.15 still does writeRaw = yield* socket.writer then writeRaw(...). On rc.115 that throws TypeError: writeRaw is not a function (DiscordWS.ts:75), shard count stays 0, and mentions/slash go nowhere.

Bump catalog dfx 1.0.15 → 1.0.16 (writer.write + reader.pull). Test asserts the installed dfx is 1.0.16+.

Guest evidence on t3code-discord-bot at d16d055996: error at 10:27:14 UTC, then zero MESSAGE_CREATE while archived-thread REST noise continues.

Restart-only will not fix this. After merge the poller will deploy discord.

dfx 1.0.15 still calls Socket.writer as writeRaw. On Effect 4.0.0-rc.115
that throws TypeError: writeRaw is not a function, so the gateway never
IDENTIFYs. REST still works, which made the bot look healthy while
mentions and slash commands were deaf. 1.0.16 uses writer.write and
reader.pull.
@patroza
patroza marked this pull request as ready for review September 18, 2026 12:19
@patroza
patroza merged commit b4ad10f into fork/dev Sep 18, 2026
7 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant