-
Notifications
You must be signed in to change notification settings - Fork 0
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
Barebones Analysis Display + Audit Logs #144
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff, nice to see it coming together!
} else { | ||
s.logger.Info("poorly constructed analysis id", zap.String("path", string(aID)), zap.Error(err)) | ||
http.Error(w, http.StatusText(http.StatusNotFound), http.StatusNotFound) | ||
return | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a real issue we expect to happen? Generally I don't like to treat the entity ID prefixes as "load-bearing", they're simply a useful debugging/sanity checking tool. What's wrong with using db.IsErrNotFound
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question - I wanted to differentiate between them mostly for ease-of-debugging. There are some missing dependencies, and I'd like to distinguish in logs in such a way that we can alert about actual failures, and build in good filters for known missing deps.
my-data
page.view
button which allows a user to see the report, with a few failures.api
FileType enums