electricdusk/rushlink
3
3
Fork 3
Code Issues 21 Pull Requests 2 Releases Activity

Add extra logging to panic recovery #61

New Issue
Closed
opened 2020-05-28 12:45:45 +02:00 by electricdusk · 0 comments
electricdusk commented 2020-05-28 12:45:45 +02:00
Owner
Copy Link

In #60, we cannot see what kind of request triggered the panic. We should add some logging to the panic recovery middleware, such that we can see what kind of request triggered the panic.

In #60, we cannot see what kind of request triggered the panic. We should add some logging to the panic recovery middleware, such that we can see what kind of request triggered the panic.
electricdusk added the
bug
 label 2020-05-28 12:45:45 +02:00
electricdusk self-assigned this 2020-05-28 12:45:51 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Uninteded behaviour

  
feature

Request for a feature to be implemented

  
good-beginner-bug

Bugs are probably easy to fix

  
needs-test

Needs a regression test

  
question

Question about the software

  
wontfix

Wont be resolved

No Label
bug
feature
good-beginner-bug
needs-test
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
electricdusk
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: electricdusk/rushlink#61
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?