CourseMigrator exceptions intended for users show up as 500 errors

Open
#378 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
backend

Research direction

Start by locating CourseMigrator and tracing how its exceptions become HTTP responses. Clarify whether the goal is to replace the exceptions, catch them, improve their messages, address the reported slowness, or all of these. Done should mean intended user errors no longer appear as 500 responses, with the performance target defined.

Written by the indexing model from the issue text.

Description

easy enhancement important

Migrate away from using the exceptions -- it's also slow.
Or at least catch them and show proper error messages

Dominant language
Ruby
Stars
51
Forks
42
Avg merge
1h 27m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from testmycode/tmc-server

All issues in testmycode/tmc-server

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.