Toutsu/GmRelayBot
1
1
Fork 0
Code Issues 18 Pull Requests 1 Actions Packages Projects Releases 85 Wiki Activity

fix(discord): cast COUNT to int for slash command list query #99

Closed
Toutsu wants to merge 0 commits from fix/discord-count-bigint-cast into main
pull from: fix/discord-count-bigint-cast
merge into: Toutsu:main
Conversation 1 Commits - Files Changed -
Toutsu commented 2026-05-26 10:11:16 +03:00
Owner
Copy Link
Copy Source

Summary

/listsessions в Discord возвращала ошибку материализации Dapper:

A parameterless default constructor or one matching signature (...) is required for GmRelay.DiscordBot.Features.Sessions.DiscordSessionListItemDto materialization

Root cause: PostgreSQL COUNT() возвращает bigint, а DiscordSessionListItemDto ожидает int для полей PlayerCount и WaitlistCount. Dapper 2.1.72 (без Dapper.AOT) не умеет кастить bigint→int при материализации record с positional constructor.

Fix: Добавлены ::int к обоим COUNT выражениям в SQL запросе.

Changes

  • DiscordListSessionsHandler.cs — COUNT(...)::int as PlayerCount, COUNT(...)::int as WaitlistCount
  • Версия синхронизирована до 3.0.6

Test plan

  • dotnet build src/GmRelay.DiscordBot — успешно
  • Полный test suite — 271/271 зеленых

Workflow

  • CI passes
  • Code review approved
  • Deployed
  • Release published
## Summary `/listsessions` в Discord возвращала ошибку материализации Dapper: > A parameterless default constructor or one matching signature (...) is required for `GmRelay.DiscordBot.Features.Sessions.DiscordSessionListItemDto` materialization **Root cause:** PostgreSQL `COUNT()` возвращает `bigint`, а `DiscordSessionListItemDto` ожидает `int` для полей `PlayerCount` и `WaitlistCount`. Dapper 2.1.72 (без Dapper.AOT) не умеет кастить bigint→int при материализации record с positional constructor. **Fix:** Добавлены `::int` к обоим `COUNT` выражениям в SQL запросе. ## Changes - `DiscordListSessionsHandler.cs` — `COUNT(...)::int as PlayerCount`, `COUNT(...)::int as WaitlistCount` - Версия синхронизирована до `3.0.6` ## Test plan - [x] `dotnet build src/GmRelay.DiscordBot` — успешно - [x] Полный test suite — 271/271 зеленых ## Workflow - [ ] CI passes - [ ] Code review approved - [ ] Deployed - [ ] Release published
Toutsu added 1 commit 2026-05-26 10:11:17 +03:00
fix(discord): cast COUNT to int for slash command list query
PR Checks / test-and-build (pull_request) Successful in 9m34s
Details
dd9337dd20 
PostgreSQL COUNT() returns bigint, but DiscordSessionListItemDto expects
int for PlayerCount and WaitlistCount. Dapper 2.1.72 in GmRelay.DiscordBot
(without Dapper.AOT) fails to materialize the record with bigint→int mismatch.
Added ::int casts to both COUNT expressions.

Bump version to 3.0.6.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Toutsu reviewed 2026-05-26 10:23:55 +03:00
Toutsu left a comment
Author
Owner
Copy Link
Copy Source

Approved. CI passed. Minimal and correct fix.

Approved. CI passed. Minimal and correct fix.
Toutsu closed this pull request 2026-05-26 16:06:28 +03:00
Some checks are pending
PR Checks / test-and-build (pull_request) Successful in 9m34s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
area:bot
Telegram bot and worker logic
 area:data
Database schema, migrations and persistence model
 area:discord
Discord bot service and Discord adapter
 area:infra
Infrastructure, runtime and deployment
 area:miniapp
Telegram Mini App dashboard
 area:platform
Platform-neutral abstractions and adapter boundaries
 area:shared
Shared domain and rendering contracts
 area:web
Blazor web dashboard
 in-progress
В работе (issue взят агентом)
 next-up
Recommended immediate backlog
 pending-approval
Ждёт согласования плана решения
 platform:discord
Discord-specific behavior or adapter work
 platform:multi
Cross-platform or platform-neutral work
 platform:telegram
Telegram-specific behavior or adapter work
 priority:p0
Critical priority
 priority:p0
Блокирующий приоритет: задача должна быть выполнена до признания решения production-ready
 priority:p1
High priority
 priority:p2
Medium priority
 priority:p3
Lower priority
 security
Security-sensitive work
 type:bug
Bug fix or corrective work
 type:chore
Maintenance and supporting work
 type:feature
New product functionality
 type:refactor
Structural change without direct feature growth
 type:test
Testing and coverage work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Toutsu
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Toutsu/GmRelayBot#99
Delete Branch "fix/discord-count-bigint-cast"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?