summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorArun Isaac2022-07-19 14:55:42 +0530
committerArun Isaac2022-07-19 14:55:42 +0530
commit1474736c17c6905658cf3746ae35265de1a5c2d2 (patch)
tree7a74286391e16032b4cc0133935b525e15401ead
parentdb9a67ddba0cad8525d6af67c77080a2c3c9b77f (diff)
downloadgn-gemtext-1474736c17c6905658cf3746ae35265de1a5c2d2.tar.gz
Close too many SQL connections issue.
-rw-r--r--issues/sql-too-many-connections.gmi6
1 files changed, 6 insertions, 0 deletions
diff --git a/issues/sql-too-many-connections.gmi b/issues/sql-too-many-connections.gmi
index f8db41b..68ed23d 100644
--- a/issues/sql-too-many-connections.gmi
+++ b/issues/sql-too-many-connections.gmi
@@ -25,3 +25,9 @@ The function decorated with `@app.before_requests` is called before every reques
I started by checking whether the request is to a *static* or *js* endpoint, and if it is, we do not bother trying to create the engine in that case.
This does not resolve the issue per-se, but it does reduce a lot of the noise when logging.
+
+## Closing for now
+
+We have not been able to reproduce this issue for the last few months. I am closing it for now, but we may reopen it if it recurs.
+
+* closed