Closed
Bug 1810789
Opened 2 years ago
Closed 2 years ago
[traceback] InvalidDocumentError: invalid type null not in ['string'] .ReleaseChannel in report view
Categories
(Socorro :: Webapp, defect, P2)
Socorro
Webapp
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: willkg, Assigned: willkg)
Details
Attachments
(1 file)
Sentry: https://sentry.io/organizations/mozilla/issues/3875731221/
Traceback:
InvalidDocumentError: invalid: .ReleaseChannel: type null not in ['string']
File "django/core/handlers/exception.py", line 47, in inner
response = get_response(request)
File "django/core/handlers/base.py", line 181, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "crashstats/crashstats/decorators.py", line 151, in inner
response = view(request, *args, **kwargs)
File "csp/decorators.py", line 19, in _wrapped
r = f(*a, **kw)
File "crashstats/crashstats/decorators.py", line 101, in inner
return view(request, *args, **kwargs)
File "crashstats/crashstats/views.py", line 109, in report_index
context["raw"] = raw_api.get(crash_id=crash_id)
File "crashstats/crashstats/models.py", line 794, in get
return reducer.traverse(data)
File "socorro/lib/libsocorrodataschema.py", line 413, in traverse
return self._traverse(schema_part=self.schema, document_part=document)
File "socorro/lib/libsocorrodataschema.py", line 483, in _traverse
new_doc[name] = self._traverse(
File "socorro/lib/libsocorrodataschema.py", line 445, in _traverse
raise InvalidDocumentError(
Example: https://crash-stats.mozilla.org/report/index/15a6fe69-f1e7-4cbb-b2a2-3427d0230111
This only happens if you don't have protected data access. That's when the reducer kicks in and walks the crash data.
Pretty sure the ReleaseChannel
is a null because the payload was json. Antenna should allow that. It gets fixed in processing. We probably need to fix the reducer to do something when it's reducing a document and the value type is invalid other than throw an exception.
Assignee | ||
Updated•2 years ago
|
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•2 years ago
|
||
Assignee | ||
Comment 2•2 years ago
|
||
I deployed this just now with bug #1839444. Marking as FIXED.
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•