Marko Kreen
Marko Kreen
I have not had time to work on new features for next release. Currently I'm still cleaning up stuff for 1.7.1. After that is released I will look at new...
Thank you for excellent report. The problem should be fixed by PR #96 that just got merged.
This is not good enough to apply as-is. Please find out what sort of exception instance caused the problem, then you can reopen the issue with specific problem we can...
This fails with RAR3 paths on Linux. I will try the approach in #96 next.
Thanks for the report!
2.5 i think. It seems non-trivial to get that logic to work on 2.4, but as you dont use it anyway, you can simply comment out the line in handlers/**init**.py...
Thanks for report and good analysis. Fixed in GIT with _make_event() in consumer classes. Alternative would be to have _event_class, but that is not good unless shared somehow with walker....
we don't have walker there. The right fix is to use RetryableEvent. I did some reorg too, to make stuff more obvious next time. Please test.
Both of connect strings should have host= also in connect string. Giving connect string without it is usually a bug. Not always - toy installations in single machine - but...
I added error for that case. But then people complained who had testenv in single machine. So I downgraded it to warning: self.log.warning('No host= in public connect string, bad idea')...