Fix for handler for postgres #3992
Conversation
…s for connection leakage Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
…ar and kanon db Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
… to close soon Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
… cleanup-calls
Signed-off-by: Vinay Singh <vinay@verid.id>
… cleanup-calls
Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
|
@vinaysingh8866 The logging from the scenario tests has been merged. Could you update this branch please? Hopefully we can see what the current error is now. |
There's this error on start up occurring. I'm not exactly sure what to make of it? |
|
@jamshale -- I'm wondering if it would be worth making a separate GHA for the Kanon test(s) so that we can separate a fail of that test from the rest of the integration tests. Much easier to see the error we're trying to address, and when to ignore a test failure. |
That's probably a good idea. I can do that. I did open a PR to reduce the log level on the other tests which will help a bit. |
|
I opened another PR to only log the failing tests. Same error there but easier to find. https://github.com/openwallet-foundation/acapy/actions/runs/20606367604/job/59182868970?pr=4005 |
Signed-off-by: Vinay Singh <vinay@verid.id>
… cleanup-calls
Signed-off-by: Vinay Singh <vinay@verid.id>
… cleanup-calls
Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
Signed-off-by: Vinay Singh <vinay@verid.id>
|
@jamshale updated the code with the fixes can you try running the tests multiple times and see if any issue happens again. |
|
|
I'm not sure if this has completely solved the problem or not but I have run the scenario tests 8 times now without a fail. I'm going to merge this and we can monitor it. If it does fail at some point we should be able to determine the cause 🤞 |


No description provided.