pull fix branches from the line, restore bug, repair, test pass, merge branches

1. if there is no dependency problem that can't be rolled back, then 2
2. Quick rollback, quick rollback, quick rollback.
3. if present, evaluate the cost of solving the problem and the cost of rolling back the dependency together. If the rollback cost is low. Then 2
4. check the online log according to the phenomenon and locate the cause of the problem. If there is no log, try to find a way 2
5. find the problem based on the error log or phenomenon review code.
6. none of the above can locate the problem. I can only?

try to reproduce the problem in the test environment, find out the solution
first propose the scope of influence, fix the plan, report to the boss, raise the severity of the problem, and whether it needs to be corrected immediately.
after the boss agrees to amend it, select the free time online code to notify the relevant third-party personnel that the bug, may be restarted.
find out what's wrong with the system, throw it out and give a draft fix.
develop an improvement plan and point out how to avoid such problems later.

if you answer above, the interview will generally be satisfactory, but it is actually another matter.

there is already a problem. The first step must be to roll back the release. Wait for you to locate and fix it before publishing that the user has run out

changing bug is the best way

do you know where bug is?

are you on-line testing?