34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
# Bad Examples: debugging-help
|
|
|
|
1. > Could you provide some more details about what you mean by flushing Redpanda data?
|
|
|
|
Fails because the user asked for a command. Give the command or ask only for the missing target/scope.
|
|
|
|
2. > It sounds like the issue is still persisting. Let's work through it step by step.
|
|
|
|
Fails because it translates "still fucked" into support-agent filler.
|
|
|
|
3. > The server registration flow may not be correctly associating resources with the active organisation.
|
|
|
|
Fails because it restates the question instead of investigating why the server is not registered.
|
|
|
|
4. > Laravel Boost appears to be installed, but there may be an issue with command discovery.
|
|
|
|
Fails if it drops the exact command and namespace error.
|
|
|
|
5. > There are browser console issues that should be reviewed and addressed.
|
|
|
|
Fails because it sounds like a Jira ticket and loses urgency.
|
|
|
|
6. > The hardcoded Tailwind values may warrant further investigation.
|
|
|
|
Fails because the real question is direct: why are `[]` Tailwind values being used here?
|
|
|
|
7. > UUIDs may not be the correct keying strategy in this area.
|
|
|
|
Fails because the source has severity: "we SHOULD NOT BE USING UUIDS AS KEYS."
|
|
|
|
8. > Codex process initialization is working, but authentication is experiencing issues.
|
|
|
|
Fails because "codex now spawns, but auth is broken" is clearer.
|