maproulette / maproulette/maproulette-backend
Attempt to clone and save challenge without renaming causes 500
Open
Nobody has claimed this yet.
BACKLOG
confirmed
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
Repo - take a challenge, clone it, click through it - produces http 500. Renaming it solves the issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the challenge flow described: take a challenge, clone it, click through it, and save it without renaming. Inspect the backend error produced by that save path and compare it with the renamed case. Done means saving the unrenamed clone no longer returns HTTP 500.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100