Order Recovery not working in every case
Open
Nobody has claimed this yet.
feedback
- Dominant language
- C#
- Stars
- 7
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
If an order is submitted but there is an error (such as potentially dangerous characters detected <>), then the order isn't recovered. This may be because it thinks it successfully posted the order to the server and thinks it should be cleared out.
Jason Sylvestre on May 16, 2014 12:19 PM (0 comments) Public permalink
Votes: 1
Author: jsylvest
Voters: jsylvest
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by tracing order submission, server-error handling, and the logic that clears or retains an order; reproduce the failure with the described dangerous characters. Done means an order that fails submission remains available for recovery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100