microsoft/restler-fuzzer

improve diagnosability for parser failures

Open

#753 opened on May 5, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (329 forks)auto 404
help wanted

Repository metrics

Stars
 (2,929 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

The line in the network log that contains the parser failure needs to be easily identifiable. Currently, only the error is printed, for example:

2023-05-04 18:52:27.468: module 'inspect' has no attribute 'getargspec'

It would also be helpful to add the exception to speccov.json.

Contributor guide

Research direction
Look at the parser error handling code in the network log module. Identify where the error message is printed and modify it to include the line number or source of the failure. Also add the exception details to speccov.json by finding where that file is written.
Tech stack
python
Domain
api
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80