AOSSIE-Org / AOSSIE-Org/DebateAI

[BUG]: Fix missing fmt.Sprintf argument in debate bot opening-statement prompt

Open Beginner friendly
#491 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
84
Forks
198
Avg merge
2d 19h
Merged PRs (30d)
30

Description

### Bug Description

The opening-statement prompt in backend/services/debatevsbot.go contains 13 %s format placeholders but supplies only 12 arguments to fmt.Sprintf.

This causes Go’s vet check to fail and may insert the formatting artifact %!s(MISSING) into prompts sent to the Gemini model. As a result, the AI receives malformed instructions, potentially reducing the quality of its opening statements.

### Steps to Reproduce

1. Clone and open the DebateAI repository.

2. Navigate to the backend directory:
cd backend

3. Run the services test command:
go test ./services

4. Observe the following error:
services/debatevsbot.go:191:4: fmt.Sprintf format %s reads arg #13, but call has 12 args
FAIL arguehub/services

5. Inspect the opening-statement fmt.Sprintf call in backend/services/debatevsbot.go and confirm that the format string has more placeholders than supplied arguments.

### Logs and Screenshots

Image

Image

### Environment Details

_No response_

### Impact

Medium - Feature works but has issues

### Code of Conduct

- [x] I have joined the [Discord server](https://discord.gg/hjUhu33uAn) and will post updates there
- [x] I have searched existing issues to avoid duplicates

Contributor guide

No contributing guide indexed for this repository

Research direction

Open backend/services/debatevsbot.go and inspect the opening-statement fmt.Sprintf call around the reported line, comparing its 13 placeholders with the supplied arguments. Run cd backend && go test ./services; done means the format-check failure is resolved and the services tests pass without a missing-format artifact.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
90/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.