Re: Mysql OperationalError on close() "fixed"

On Sun, Mar 24, 2019 at 01:41:31PM -0400, John P. Rouillard wrote:
> Hi all:
> 
> I have forced the version of the mysqlclient library installed via pip
> to be 1.3.13. Pip was installing version 1.3.14. This "solves" the
> issue with an exception being thrown during a close() operation.

Is this the same problem we're seing in Travis?

> Joseph gave me a clue a couple of weeks back by noting that there were
> no roundup code changes between a passing and a failing travis-ci run.
> 
> Note that the tests are still not passing.

I had looked into the errors some time ago and it's still on my todo
list to dig this up (I think I had written up what I found in some
email, seems not to the roundup list(s)). The problems look as if they
can be fixed by tweaking some mysql settings.

> Ralf, did you forget to check in the test code changes to match your
> changes to rest.py? The changes that have been made to the rest code
> was not reflected in test/rest_common. So the tests are still looking
> for old style (without links, file content being reported as content)
> output.

No, I didn't look at the tests yet. I will do more this week and hope to
have passing tests again soon.

> Also should we also be testing rest output in various modes
> (@vebose=1,2,3) just to make sure we get good code coverage?
Yes.

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: [email protected]