You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Narrative:
As a developer, I would like for the alert channel to stay clean and meaningful. The fact that every deploy results in repeated connection errors as such:
OperationalError
could not connect to server: Connection refused
Is the server running on host "production-gcloud-sqlproxy" (10.0.10.54) and accepting
TCP/IP connections on port 5432?
both potentially obscures more critical issues and generally points to imprecision in the deployment process.
Acceptance Criteria:
These errors no longer happen on deploy.
Implementation Notes:
The solution for this will probably dovetail with that for #1 given the fact that they are both transient deployment errors.
The text was updated successfully, but these errors were encountered:
Datamance
added
bug
Something isn't working
scoping
Still in the scoping stage - need to figure out what actual work needs to be done
labels
Sep 3, 2020
Narrative:
As a developer, I would like for the alert channel to stay clean and meaningful. The fact that every deploy results in repeated connection errors as such:
both potentially obscures more critical issues and generally points to imprecision in the deployment process.
Acceptance Criteria:
Implementation Notes:
The solution for this will probably dovetail with that for #1 given the fact that they are both transient deployment errors.
The text was updated successfully, but these errors were encountered: