René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Fix scoring endpoint HTTP behavior","articleBody":"\r\n1. Scoring endpoint should return json, not stringified json\r\n\r\n```\r\ncurl -H \"Authorization: Bearer $token\" $scoringUri \\\r\n  -d '{\"data\":[[1,2,3,4,5,6,7,8,9,10],[10,9,8,7,6,5,4,3,2,1]]}' \\\r\n  -H Content-type:application/json\r\n```\r\n\r\nReturns:\r\n\r\n```\r\n\"{\\\"result\\\": [5113.099642122809, 3713.6329271385334]}\"\r\n```\r\n\r\nExpected:\r\n```\r\n{\"result\": [5113.099642122809, 3713.6329271385334]}\r\n```\r\n\r\nProbably we should avoid json.dumps() in:\r\nhttps://github.com/microsoft/MLOpsPython/blob/41ea9b7765183eca83cf3f193e69777858709d35/code/scoring/score.py#L46\r\n\r\n2. Scoring endpoint should not return 200 in case of error\r\n\r\nExceptions are swallowed at\r\nhttps://github.com/microsoft/MLOpsPython/blob/41ea9b7765183eca83cf3f193e69777858709d35/code/scoring/score.py#L47\r\n\r\nThe code should not only return the error message but also set an appropriate HTTP return code.\r\n","author":{"url":"https://github.com/algattik","@type":"Person","name":"algattik"},"datePublished":"2019-11-25T15:28:59.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/110/MLOpsPython/issues/110"}