sillsdev / sillsdev/languageforge-lexbox
trace project reset from client side
Open
Nobody has claimed this yet.
📦 Lexbox
OpenTelemetry
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
right now a project reset via upload requires multiple web requests, they should all be under a single trace since it represents a single action from the user, this should give us better observability on those uploads
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
Start by tracing the client-side project reset flow triggered by an upload and identify the web requests that represent that single user action. Determine where the trace is created and how the requests are connected; done means the reset upload appears as one trace covering all of its requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100