| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Early bailout if the command field is not specified in the POST request.
(Not doing this actually leads to an exception in the subsequent debug
because command is an Array and it can't be added to a String,
but ayway the early catch is cleaner error handling.)
Also add a TODO about a potential improvement for permission error handling.
|
|
When the user logs in, m.source is already a botuser.
|
|
It now interfaces with the webservice 'dispatch' feature
instead of the previous remotectl plugin, but the external API
remains the same, for compatibility with existing users.
|
|
When a star is added/removed, we get notified with a message
that has no number, title or link. The pseudo-sentence is also
very bare (X started/created/deleted, without an object).
Show the number of watchers and/or stars (as appropriate) to produce
a more meaningful phrase.
|
|
We do the actual fork as the last step, after redirecting the
standard I/O streams. This also ensures that no log messages
are shown on console _after_ forking.
|
|
We nil the internal variable, but we should not close the logger itself,
since this leads to STDERR being closed and the interpreter reopening it
for its own needs, or something like that, which ultimately leads to
the interpreter's warning appearing in console (probably due to ruby
itself reopening stderr to be able to output the messages).
If we simply nil the variable, the interpreter is content with sending
us the messages per our shenanigangs, and everything works just as
expected.
|
|
IO.write() takes an arbitrary number of argumens, that are converted to string
and joined on write. We should behave the same way.
Moreover, the returned value is the number of bytes, and this is bytesize
in modern Ruby.
|
|
|
|
Overriding (as we should do) the standard error write method when
daemonizing introduces a recursion in the logger, due to the
persistent presence of the console logger.
The solution is obviously to stop logging on console
after daemonization.
|
|
In 96d13521d the STDOUT/STDERR write overrides were replaced
by overrides to $stdout, but the second should have been to $stderr
(obviously).
|
|
There was an extra read.
|
|
Also add a TODO about a possible event-based output filter.
|
|
|
|
|
|
This plugin provides webhook support for GitHub and similar services,
through the webservice feature. Hosting services and output formats
can be customized through filters as usual.
|
|
|
|
Logging was broken when daemonizing, due to the logger thread being dead
after the fork. This can be solved by restarting the thread, if necessary
when setting the log file (which we conveniently do right after the fork).
|
|
|
|
|
|
|
|
Prevents errors about external_encoding not being defined for the gzip
stream in ruby 1.9+
|
|
|
|
build(deps): bump nokogiri from 1.11.1 to 1.11.4
|
|
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.11.1 to 1.11.4.
- [Release notes](https://github.com/sparklemotion/nokogiri/releases)
- [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md)
- [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.11.1...v1.11.4)
Signed-off-by: dependabot[bot] <support@github.com>
|
|
build(deps): bump mechanize from 2.7.6 to 2.7.7
|
|
build(deps-dev): bump oauth from 0.5.4 to 0.5.5
|
|
Bumps [oauth](https://github.com/oauth-xx/oauth-ruby) from 0.5.4 to 0.5.5.
- [Release notes](https://github.com/oauth-xx/oauth-ruby/releases)
- [Changelog](https://github.com/oauth-xx/oauth-ruby/blob/master/HISTORY)
- [Commits](https://github.com/oauth-xx/oauth-ruby/compare/v0.5.4...v0.5.5)
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Bumps [mechanize](https://github.com/sparklemotion/mechanize) from 2.7.6 to 2.7.7.
- [Release notes](https://github.com/sparklemotion/mechanize/releases)
- [Changelog](https://github.com/sparklemotion/mechanize/blob/master/CHANGELOG.rdoc)
- [Commits](https://github.com/sparklemotion/mechanize/compare/v2.7.6...v2.7.7)
Signed-off-by: dependabot[bot] <support@github.com>
|
|
build(deps): bump rack from 2.2.2 to 2.2.3
|
|
Bumps [rack](https://github.com/rack/rack) from 2.2.2 to 2.2.3.
- [Release notes](https://github.com/rack/rack/releases)
- [Changelog](https://github.com/rack/rack/blob/master/CHANGELOG.md)
- [Commits](https://github.com/rack/rack/compare/v2.2.2...2.2.3)
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
see #42
|
|
While loading a plugin in the manager using #load_botmodule_file this
will remember the directory of the file that is being loaded in
@next_plugin_path. In the plugin/BotModule initialization we set the
path in plugin_path of the plugin.
This was the only solution I could find to get this information in the
plugin. It is useful because this allows the plugin to know in which
directory it is located, it can then easily access data files stored
alongside the plugin.
Some built-in plugins (see #42) use the data/rbot/templates to copy
data files on bot load (see #repopulate_botclass_directory) into the
profile directory (~/.rbot/).
|
|
also related to #41 and #6
|
|
I never saw a plugin use this feature besides wof, IRC user objects should not hold
persistent data like this, I rather have the IRC interface clean. The
general idea is a good though, especially easier per-channel, per-user
data persistence.
|
|
|
|
yandex still works surprisingly enough
|
|
|
|
This is intended to make testing/mocking of the http client easier.
|
|
|
|
|
