Romain Bazile

This issue still exists in the latest version.

The suggested regex could even be changed to `.*\.\([0-9]*\|gz\)$` to match any files whose names ends with either numbers or `gz` (to match on files like `error.log.1` for example)

Also, the command `> /var/log/logfile.log` can be replace with `sudo find mnt/var/log/ -type f -regex '.*\.log$' -exec truncate -s0 {} +` which I think is more suited to a script.

There is also a similar bug with the `#` character.

Just to confirm, I have the exact same issue with Scaleway. Running algo from Linux. Running the tip of master with a clean config. Offending file appears to be [algo/roles/cloud-scaleway/tasks/main.yml':...

I did some debugging, and I realized that no organisation data is fetched: ``` TASK [cloud-scaleway : organization] ********************************************************************************************************************************************** ok: [localhost] => { "msg": { "changed": false, "failed": false, "scaleway_organization_info":...

I'm not sure the build failure has anything to do with my changes. The failure happens during a call to `sideNav.getChannelFromSpotlight('rocket.cat').waitForVisible(5000);` in `09-channel.js`. What can I do to fix that?

I pulled and merged the changes from Rocket.Chat/develop, I hope it will help with the build failure.

The build failure is now related to badwords management. This PR add supports for horizontal rules via `___`, `---` or `***`. Bad words are replaced by `*`, thus creating a...

Mmmmmm, for some reason, it worked on my local tests, but not when deployed. Oh well, `x` it is then.