Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pass through errors to client #30

Open
sushain97 opened this issue Apr 30, 2018 · 0 comments
Open

Pass through errors to client #30

sushain97 opened this issue Apr 30, 2018 · 0 comments
Labels
enhancement New feature or request gci

Comments

@sushain97
Copy link
Member

sushain97 commented Apr 30, 2018

The format should be an errors key that contains a mapping from file name to error type and description.

For any type of query, store in memory a mapping from package to a mapping from filename to error. If an error occurs while handling a particular file, set the value. If it goes through cleanly, unset the value.

For an async query that triggers an execution of stats, return nothing. For an async query that has some results, return the current mapping of relevant ones minus the ones in progress (since those errors could be stale).

For a sync query, the errors can just be the ones from that execution of stats if one is required and otherwise the current mapping of relevant ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request gci
Projects
None yet
Development

No branches or pull requests

1 participant