Quirin Hardy Zießler
Quirin Hardy Zießler
@manuel-sommer same for me. Only on debug I get some errors regarding mailhog but everything runs fine. Can be closed imo.
The question is: Is this useful? In my eyes not. Engagements should reflect only one single repository. So I would rather suggest to remove the irritating repo uri input from...
@valentijnscholten I agree with you, this is probably possible. But as most user don't host there own DB and instead are running on e.g. AWS Aurora putting another possible bottleneck...
It should. So far from my understanding we need to go through all functions and define if they are read only or not and then define the required DB conn...
@Maffooch I am aware of the widespread use of SQ and this is also why I opened this PR against bugfix. During testing I saw my import time dropping about...
@Maffooch any updates here?
No worries @Maffooch. According to the dedupe of SQ and your statement this meets my changes. I can also prepare the same PR against the latest dev version. However I...
@jsayerascb just tried it out and noticed the same behavior. However if I use the "re-upload" function from a test, the issue does not appear and the findings are getting...
So this could be considered a hot fix for the issue. However imo it should be working the way you did initially as well. The only two solution to achieve...
Will you create a PR then?