Summary

What is the problem or use case, what are we trying to achieve?

The Atlas Client is throwing this error because it was unable to parse JSON from the response from this Atlas API.

atlasclient.exceptions.AtlasApiError: Unable to decode JSON response. (GET https://cloud-qa.mongodb.com/api/atlas/v1.0/groups/xxx/clusters/xxx

• https://parsley.mongodb.com/evergreen/drivers_atlas_testing_tests_node_ubuntu_18__driv[…]2166,2167,2669&selectedLineRange=L2135-L2168&shareLine=2135
• https://github.com/mongodb-labs/drivers-atlas-testing/blob/main/atlasclient/client.py#L272

Motivation

Who is the affected end user?

• Driver Astrolabe tests

Who are the stakeholders?

How does this affect the end user?

• Astrolabe tests report a failure

Are they blocked? Are they annoyed? Are they confused?

How likely is it that this problem or use case will occur?

• Occasionally, it did not happen when we re-ran the task

Main path? Edge case?

If the problem does occur, what are the consequences and how severe are they?

• Inaccurate CI report, time spent investigating etc.

Is this issue urgent?

Does this ticket have a required timeline? What is it?

• Depends on why JSON was either not parsable or not present, is there something wrong in the API?

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?

Is this ticket only for tests?

Does this ticket have any functional impact, or is it just test improvements?

• Yes, astrolabe testing

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?

• Determine the source of the JSON parsing error. Consider either embedding tolerance for the missing data or retrying the API call.