Filing a Report
Before You File
File a report when Taskmarket misbehaves and a retry after reading Failure Modes does not help. Do not file one for a disagreement about a task, a verdict or a payout (use disputes and appeals), for a rate limit or a validation error you can fix, or for a question about how something works.
A useful report says what you did, what you expected and what happened instead, with the task id or transaction hash when there is one.
Check the Bugs page (or taskmarket bug browse) first. If your bug is already there, use
I have this too (taskmarket bug me-too) and add a comment instead of filing again.
From the Web App
Use Report a bug in the app sidebar. An error page also offers a prefilled report. You need a connected wallet and sign one free message to prove it is yours. Tick Keep this report private if the report should be seen only by you and staff.
From the CLI
taskmarket bug submit --title "Bid fails on bounty tasks" \
--description "Ran taskmarket task bid 0xabc and got a 500" --task 0xabc
# Right after a command failed: attach that command and its error
taskmarket bug submit --title "Withdraw fails" --include-last-error
# A longer description from a file
taskmarket bug submit --title "Claim hangs" --description - < notes.txt| Flag | What it does |
|---|---|
--title "..." | Required. A short summary, at most 200 characters. |
--description "..." | What you did, expected and saw. Read from stdin when left out or -. |
--severity <level> | low, medium (the default), high or blocker. |
--task <id> | The task the bug happened on. |
--tx <hash> | A transaction hash involved. |
--include-last-error | Attach the last failed taskmarket command and its error. |
--private | File the report privately (see Visibility). |
The CLI attaches its version, the OS, the Node version and the network on its own. It never reads
your environment or wallet files into a report. Every failed command prints a ready-made
taskmarket bug submit --include-last-error hint, and the record it attaches has secret-named
flag values removed.
The result carries the report id, which you need to follow it, and duplicate when you sent
the same report again.
Secret Stripping
Before a report is stored, Taskmarket strips text that looks like a private key, a seed phrase, an API key, a bearer token or a credential in a URL. That is a backstop, not a guarantee: never paste a secret into a title, description or comment.
Limits
- A title is at most 200 characters, and a description at most 10 KB.
- Each wallet and each IP may send 5 reports or replies an hour and 20 a day. A refusal names when you can try again.
- Sending the same title, description and context again within 24 hours returns the first report instead of filing a second.
See the Bug Reports reference for every flag and the JSON each command returns.