Travis Build Errors (In Progress) about nginx-ultimate-bad-bot-blocker

[mitchellkrogza]

Reverted all commits to last commit from this morning, all seems ok now. Travis did report issues of "Apt failures" earlier today which is probably what caused this. Those using auto update should get working copy of latest globalblacklist.conf shortly or you can try force an update to make sure you didn't get the empty file version that occured earlier today.

[mitchellkrogza]

Will check this again in the morning on my test repo before doing any more updates.

[mitchellkrogza]

@itoffshore No updates until Travis fixes their docker containers. Bash has been totally messed up in their latest updates to Travis.

Any "n" character in the output of any echo or printf statements or even variable name is being seen by Travis as a \n line break. What a mess.

https://blog.travis-ci.com/2017-06-21-trusty-updates-2017-Q2-launch

[itoffshore]

⬛ oh dear - one step forward 2 steps back

[mitchellkrogza]

Yip, something has gone horribly wrong with Travis. Hope they respond to me soon.

…

On 29 June 2017 at 19:18:40, Stuart Cardall ***@***.***) wrote: ⬛️ oh dear - one step forward 2 steps back — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#58 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJgARd4MXivQf0k4lIkKFNp0znMxEtx0ks5sI9xwgaJpZM4OH_Zk> .

[mitchellkrogza]

@itoffshore, finally found the culprit pushing out new generator scripts tomorrow and updates will commence.

[mitchellkrogza]

@itoffshore we are back online, did some major changes to scripts, all tested and working again. Can you believe in the end a simple IFS="\n" in the generate script caused all the headaches. In the end it led to some much better and cleaner scripting, so all good in the end 😄