-
Notifications
You must be signed in to change notification settings - Fork 64
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
Validate document attachments at time of upload #19532
base: master
Are you sure you want to change the base?
Conversation
Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: lib/claim_documents/monitor.rb |
Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: lib/claim_documents/monitor.rb |
4fa46a2
to
207c8df
Compare
Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: lib/claim_documents/monitor.rb |
Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: lib/claim_documents/monitor.rb |
Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: spec/controllers/v0/claim_documents_controller_spec.rb |
73a4969
to
90b62ce
Compare
Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: spec/lib/claim_documents/monitor_spec.rb |
90b62ce
to
f6e2287
Compare
Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: spec/lib/claim_documents/monitor_spec.rb |
f6e2287
to
afbc386
Compare
Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: spec/lib/claim_documents/monitor_spec.rb |
afbc386
to
ecd15ee
Compare
ecd15ee
to
bc56c8b
Compare
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.
Looks like some tests are failing, and one question
|
||
def track_document_upload_failed(form_id, attachment_id, current_user, e) | ||
StatsD.increment("#{DOCUMENT_STATS_KEY}.failure", tags: ["form_id: #{form_id}"]) | ||
log_silent_failure({ form_id: form_id, attachment_id: attachment_id }, current_user&.user_account_uuid) |
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 silent failure? It notifies the user synchronously, right?
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.
I think this would be considered a silent failure, since submission failures due to attachment failures aren't properly being logged. And no, the similar log_silent_failure_avoided
function is the one that sends the email to the user when the parameter email_confirmed: true
is passed.
Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: spec/support/vcr_cassettes/uploads/validate_document.yml |
Generated by 🚫 Danger |
3af220b
to
b09b70c
Compare
b09b70c
to
39fff39
Compare
Summary
Related issue(s)
Testing done
Screenshots
Note: Optional
What areas of the site does it impact?
(Describe what parts of the site are impacted andifcode touched other areas)
Acceptance criteria
Requested Feedback
(OPTIONAL)What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?