before
```
% travis lint .travis.yml
Warnings for .travis.yml:
[x] value for notifications section is empty, dropping
[x] in notifications section: unexpected key on_success, dropping
[x] in notifications section: unexpected key on_failure, dropping
```
now:
```
Hooray, .travis.yml looks valid :)
```
See also ProgVal/Supybot-plugins#217
Squashed commit of the following:
commit aa8823331ebccebdca83810545b167deb2e6303e
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Tue Jul 15 20:47:29 2014 +0300
.travis.yml: remove duplicate x
commit ef3b363aa6b692c771733f1b4a9d352c9224f3d0
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sun Jul 13 22:32:10 2014 +0300
.travis.runonce.bash: add spaces
commit 004905729f954b5368510098fa2cac2a7181964a
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sun Jul 13 22:28:48 2014 +0300
.travis.runonce.bash: pipe msgcheck to true
commit d5bdeac5f7754c9443c983f374d41a2f9bc0d1b3
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sun Jul 13 11:04:40 2014 +0300
.travis.runonce.bash: remove RTFD
There is now hook for it at GitHub.
commit e1dab24f0f6f1c406b2284298a2e8ab3908bdc23
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 12 23:34:14 2014 +0300
.travis.runonce.bash: care about exit status
This excludes msgcheck, because it's over-sensitive and always returns
exit value which logic I don't remember unless everything is correct
according to it.
Oh and the behaviour before this commit allows everything to fail
without having exit code which shows that it failed and we wouldn't
notice any failures in near future.
If I understand correctly, this makes the build fail when one build fails without having to wait for all builds to finish.
This might abort building for those which haven't finished yet, but we probably want to know that build fails as soon as one build fails.
Allowing Anonymous.say to send a message to either a nick or an
(implicit) channel through the use of first('nick', 'inChannel') changed
the behavior of the command by making it impossible for 'inChannel' to
take effect.
This meant that any previous users of the command that expected "say
some text" to send "some text" to the current channel would instead try
to send "text" to the user "some". Depending on the value of
conf.plugins.Anonymous.allowPrivateTarget, this would result in either
an error or a strange message to a random user.
Creating a new tell command solves this issue as Anonymous.channel now
goes back to its simple 'inChannel' wrapper.
Signed-off-by: James McCoy <vega.james@gmail.com>
* msgcheck now doesn't cause false-alarms with Limnoria specific things.
* remove the broken if which never gets executed by Travis
* These commits have already been build invidually so [SKIP CI]
Squashed commit of the following:
commit 3b528b5f103500d9cfa62e3442d7c977ee7c6259
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 10:24:02 2014 +0300
.travis.runonce.bash: fix travis check
* Install sphinx & msgcheck on same line.
* Don't install sphinx twice.
commit aca2040807b082a1b1f74be4f8f3917407dd4e3c
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 01:12:10 2014 +0300
.travis.runonce.bash: use sudo in travis
commit 00b8d9d0b269679867d3ef2d730274d6b0d1701b
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 01:08:51 2014 +0300
Revert ".travis.runonce.bash: improvising"
This reverts commit 373471845cd2a1ebfc615fe0eb253ac5f169ec67.
commit 373471845cd2a1ebfc615fe0eb253ac5f169ec67
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 01:00:52 2014 +0300
.travis.runonce.bash: improvising
I hope this also works with Travis, but I have no idea does whereis
usually check $HOME/.local/bin …
commit 1a8f54f337455dbb3e5643ce8fa9735183edcd79
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 00:46:16 2014 +0300
Revert ".travis.runonce.bash: adjust $PATH"
This reverts commit dc096462798499270e78ed7aa596dade938796a4.
commit dc096462798499270e78ed7aa596dade938796a4
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 00:37:13 2014 +0300
.travis.runonce.bash: adjust $PATH
If something is already installed elsewhere, pip won't reinstall it.
commit bd34aae08a8a739c7f6ecd8db685dc81ac3acf7d
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 00:25:56 2014 +0300
.travis.runonce.bash: use full paths
for applications installed to $HOME/.local
commit 643878c2f94cbe9f7244a4d8df7463ed25af2275
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 00:24:20 2014 +0300
Fix Python 2.6 build
Move msgcheck & sphinx to .travis.runonce.bash so 2.6 doesn't fail to
msgcheck requiring Python 2.6.
commit 2fbb279ac2
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 00:19:30 2014 +0300
fix .travis.yml
commit cc1ccb15a0
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 00:08:12 2014 +0300
.travis.runonce.bash: add msgcheck
&& requirements.txt: add msgcheck & forgotten sphinx.
commit a2d910d2f5
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 00:03:41 2014 +0300
.travis.runonce.bash: add forgotten sphinx
commit cdd564f115
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Sat Jul 5 00:01:14 2014 +0300
Break .travis.yml to two files
* .travis.yml = the primary Travis config file.
* .travis.runonce.bash = the script which we want to run only once per
build.
commit 6c3d2dfcd2
Merge: ebf244237d8a54
Author: Valentin Lorentz <progval+github@progval.net>
Date: Fri Jul 4 19:06:47 2014 +0200
Merge pull request #755 from Mkaysi/services
Services: default NickServ and ChanServ to NickServ and ChanServ.
commit ebf2442dbc
Merge: 3f9b10cc534e82
Author: Valentin Lorentz <progval+github@progval.net>
Date: Mon Jun 30 13:27:34 2014 +0200
Merge pull request #762 from Mkaysi/nickauth
NickAuth: update l10n-fi & messages.pot .
commit c534e824f0
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Mon Jun 30 14:22:34 2014 +0300
NickAuth: update l10n-fi & messages.pot .
[SKIP CI]
commit 3f9b10cc59
Merge: 607e5e038b933a
Author: Valentin Lorentz <progval+github@progval.net>
Date: Mon Jun 30 13:17:13 2014 +0200
Merge pull request #761 from nyuszika7h/fix-nickauth-nick-list-error
NickAuth: fix error message in !list
commit 38b933aee9
Author: nyuszika7h <nyuszika7h@gmail.com>
Date: Mon Jun 30 09:50:43 2014 +0200
NickAuth: fix previous commit
I'm too used to JavaScript.
commit 8e97ad3707
Author: nyuszika7h <nyuszika7h@gmail.com>
Date: Mon Jun 30 09:47:55 2014 +0200
NickAuth: fix error message in !list
commit 37d8a545e9
Author: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Fri Jun 6 13:54:26 2014 +0300
Services: default NickServ and ChanServ to NickServ and ChanServ.
* Most of networks have services with this name.
* I can only name QuakeNet from those that don't, but the default
configuration exludes it.
* If this plugin is loaded in Supybot-wizard, it asks for nicknames of
NickServ and ChanServ.
[SKIP CI] because this is `git commit --amend` and the build already
passed.
Using Raise=True was only papering over the real problem in the nested
command error handling. The actual issue is that we were trying to
return an IrcMsg from NestedCommandsIrcProxy.__init__. Dropping
Raise=True and moving return to its own line is the correct fix and
resolves the test failure in testMaximumNestingDepth.
This commit reverts 7838cae3bc
Signed-off-by: James McCoy <vega.james@gmail.com>
freecode.com, nee freshmeat.net, is now a completely static site. Since
it is no longer allowing updates, no need to worry about pushing
information about Supybot releases to it.
Signed-off-by: James McCoy <vega.james@gmail.com>
* Change default separator to `|` as used by Topic plugin.
* Show links with manual calling and automatic announcement.
* In most of cases we want to know where does new RSS feed title point to...
The (faulty) detection of recursive Aliases was removed in
a656fd0693, claiming that "our nesting
limit will catch issues now." However, nested Aliases weren't actually
increasing the nesting level.
Actually increasing the nesting level when an alias is executed restores
the intended behavior. Additionally, limiting the size of the
expanded arguments to an alias prevents exponential growth of memory
usage for certain malicious inputs/aliases.
Signed-off-by: James McCoy <vega.james@gmail.com>