David Moreau Simard
David Moreau Simard
@hritz220 I'm not sure I would call it a bug more so than how it just happens to work that way right now. I wouldn't be against making it work...
Hey @dericcrago and thanks for reaching out :) We're bumping django from 2.2 to 3.2 with the upcoming release of ara (1.6.0) and frankly, thumbs up to the Django maintainers...
We will learn about how complicated database migrations will be in due time :p To give a bit of perspective, ara 1.5.8 is the last release that will support python3.5...
Hey @flowerysong, thanks for the input and you're right, I agree. This originates from a user asking about why the modules were running N times for N hosts and perhaps...
Putting this in draft, I have no intention of merging it but keeping it opened as a reminder for now.
Yeah... paths with funny characters :( From the perspective of the callback:  I guess we should be able to reproduce the issue with an integration test...
Ran a playbook with that path and it worked ¯\\_(ツ)_/¯  Need to investigate some more but I'm not considering this a blocker for 1.5.0.
Running a playbook from ``/tmp/-ÅÑŚÌβŁÈ/playbook.yml`` worked fine with sqlite and postgresql but raised the exception in the original bug report when using mysql. There seems to be a certain amount...
With mariadb-server-10.3.27 on centos8 I'm able to reproduce the issue using charset ``latin1`` and collation ``latin1_swedish_ci`` but it works fine using ``utf8`` as charset and ``utf8_general_ci`` as collation without needing...
I wasn't able to figure out the right way to change the charset/collation on the database as well as the tables without causing a range of issues. What seems to...