Update from head #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates google-api-client to 0.13 along with GoogleCalendarPublishAgent and GoogleTranslationAgent to newer API signatures. In preparation for including a google-cloud-bigquery gem and Agent which would otherwise have dependency version mismatches. May break backwards compatibility for the GoogleCalendarPublishAgent due to Google's new preferred authentication method. PKCS12 keys are no longer support by the gem, in favor of RSA private keys / JSON key files. The new API no longer uses a discovery method and implements methods in Ruby, adopting snake case names for object keys. So `dateTime` becomes `date_time`. `time_zone` also appears to now be required.
Fix conditional event_description. Should check for `merge` instead of `merged`.
Add validations for `mode` values in EventFormattingAgent
* Keep X events to make Digest from Added a configuration option to save a fixed number of events for the Digest. Currently all received events are purged when an event is emitted by this agent. This option allows received events to be remembered and reused for future Digests. * added validate_options for new config Added a check to prevent negative numbers, which would cause breakage. Also gave an upper limit at 999, just to set a sane maximum. * removed unnecessary while loop As suggested by @dsander here: #2041 (comment) * Updated name of feature and description * ensure retained_events is an Integer * typo in check if retained events is int * specs for digest_agent * removed validate as integer * removed check for integer status * Rspec mostly working Got rspec mostly working. The #'working?' check for events received in last few days is failing for me, but it was failing for other agents too on my setup. Likely a local problem, so lets see if this passes the automated builds. * removed comments ack. forgot about those
This allows to merge the contents of the the emitted event into the received event by setting this option to `merge`.
Add `output_mode` to PostAgent
It now additionally allows to use `sticky`, `priority` and `callback_url`. The Agent is now `FormConfigurable` and supports Liquid in all options. `register_growl` had to be moved inside of the `events` loop to allow Liquid interpolation for the previously static `growl_*` options. #2018
Update google-api-client and Google agents
Add more options to the GrowlAgent
Increase `username` max length to 190 characters. #2059
Enrich ImapFolderAgent payload
for debugging purposes there should be a logging output. however the pushover does not have a log output. i added a simple logging output.
add logging output for pushover agent
Hashie `>= 3.5.0` warns when build in methods are overridden. Omniauth 'fixed' the warning by silencing the logger.
Upgrade jquery.jsoneditor to handle null values
Change urls in default scenario from HTTP to HTTPS
2.4.2, 2.3.5 and 2.2.8 are out. Specifying "2.4" and "2.3" still does not work on Travis. 😞
Update rubies: 2017-09
Update to nokogiri 1.8.1
Makes the Agent easier to use and to debug. It now verifies the API token and auto completes the `chat_id`. Log entries are only created on failure to avoid cluttering the Agent log. #2135
Make TelegramAgent FormConfigurable, DryRunable and add logging
There's no use to retry when those errors occur, so just log an error message and let it go.
…error Do not treat already retweeted/favorited error as failure
docker/single-process: add DOCKER_CMD environment variable to trigger
worker task (e.g., -e DOCKER_CMD='bin/threaded')
bin/docker_wrapper: a wrapper to chmod -R g=u
Fixes restart issue of the single-process image because the pid file was already written in the previous run. Since we only start one server we don't need to track it's pid.
Setting $HOME to a writable directory fixes:
`/` is not writable.
Bundler will use `/tmp/bundler/home/unknown' as your home directory
temporarily.
Unsetting `no_proxy` removes faraday warnings about `no_proxy` not
being supported.
Updated spring to allow running the specs with guard and spring again.
Fix running specs with guard and spring
Make Docker image runnable as non-root user
A bit of a counterintuitive solution as I'd logically expect SMTP_AUTHENTICATION to be set to 'none' vs SMTP_USER_NAME but regardless clarifying for local Postfix configs like mine that don't require auth from localhost.
Clarify using SMTP without authentication
Add a workaround for broken AlreadyRetweeted error detection
By using the `interpolated` helper method our custom tags like `credential` can be used in the LiquidOutputAgent. Fixes #2042
Allow usage of custom Liquid tags in LiquidOutputAgent
add proxy support for WebRequestConcern
Upgrade Dropbox Agents to new v2 API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.