Try fiddle 1.0.8 #14
Closed
Try fiddle 1.0.8 #14
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
If a file is mv-ed and a new file is created during calling `#refresh_watchers`s, and `#refresh_watchers` won't run `#start_watchers` and `#stop_watchers` for the path because `#target_paths_hash` always contains the path. Signed-off-by: Hiroshi Hatake <[email protected]>
…th-file in_tail: Handle to send rotated logs when mv is used for rotating
Signed-off-by: Or Sela <[email protected]> Signed-off-by: Takuro Ashie <[email protected]>
Suppress the following message while testing it: 2021-03-17T05:57:52.3545997Z /home/runner/work/fluentd/fluentd/lib/fluent/command/plugin_config_formatter.rb:165: warning: instance variable @table not initialized Follow up for fluent#3240. Signed-off-by: Takuro Ashie <[email protected]>
Fill an uninitialized instance variable of FluentPluginConfigFormatter
Fix MessagePackEventStream issue with Enumerable methods
…mpler way Signed-off-by: TAGOMORI Satoshi <[email protected]>
Signed-off-by: TAGOMORI Satoshi <[email protected]>
Signed-off-by: TAGOMORI Satoshi <[email protected]>
Signed-off-by: Takuro Ashie <[email protected]>
Signed-off-by: TAGOMORI Satoshi <[email protected]>
These plugins accept a parameter `plugin_type` but it hides the parent class's method `Fluent::Plugin::Parser#parser_type`, it causes unexpected behavior on a plugin which uses this method such as in_exec. Fix fluent#3296 Signed-off-by: Takuro Ashie <[email protected]>
In the previous version, <name> of prefix
is not mentioned.
Before:
Usage: fluent-plugin-generate [options] <type> <name>
Generate a project skeleton for creating a Fluentd plugin
Arguments:
type: input,output,filter,parser,formatter
name: Your plugin name
Options:
--[no-]license=NAME Specify license name (default: Apache-2.0)
After:
Usage: fluent-plugin-generate [options] <type> <name>
Generate a project skeleton for creating a Fluentd plugin
Arguments:
type: input,output,filter,parser,formatter
name: Your plugin name (fluent-plugin- prefix will be added to <name>)
Options:
--[no-]license=NAME Specify license name (default: Apache-2.0)
Signed-off-by: Kentaro Hayashi <[email protected]>
Signed-off-by: Hiroshi Hatake <[email protected]>
Signed-off-by: Hiroshi Hatake <[email protected]>
fluent-plugin-generate: add note about plugin name
Signed-off-by: Takuro Ashie <[email protected]>
In the previous versions, generated .gemspec doesn't follow depended gem version which is used in fluentd.gemspec at all. Instead, it is changed to retrieve depended gem version from Gemfile.lock to sync with it. Before: spec.add_development_dependency "bundler", "~> 1.14" spec.add_development_dependency "rake", "~> 12.0" spec.add_development_dependency "test-unit", "~> 3.0" It is required to update manually. After: spec.add_development_dependency "bundler", "~> 2.2.15" spec.add_development_dependency "rake", "~> 13.0" spec.add_development_dependency "test-unit", "~> 3.3" Above depended version is replaced by <%= %> in template. No need to update manually. Signed-off-by: Kentaro Hayashi <[email protected]>
Signed-off-by: Hiroshi Hatake <[email protected]>
Signed-off-by: Hiroshi Hatake <[email protected]>
Signed-off-by: Hiroshi Hatake <[email protected]>
Signed-off-by: Hiroshi Hatake <[email protected]>
kwargs Signed-off-by: Hiroshi Hatake <[email protected]>
Use rr 3.0 on unit tests for Ruby 3.0 kwargs changes
parser_csv, parser_syslog: Fix a naming conflict on parser_type
Follow depended gem version by fluent-plugin-generate
There are some failed unit test with Ruby 3.0 on windows, Instead of omitting those test cases, it may be better to mark "experimental" to clarify the issues. Signed-off-by: Kentaro Hayashi <[email protected]>
Signed-off-by: Kentaro Hayashi <[email protected]>
Signed-off-by: Ji-Ping Shen <[email protected]>
Signed-off-by: Takuro Ashie <[email protected]>
In recent CRuby, RubyVM::InstructionSequence is always defined. But other implementation such as truffleruby does not provide such class. Signed-off-by: Hiroshi Hatake <[email protected]>
Signed-off-by: Hiroshi Hatake <[email protected]>
On Windows, a win32 error `ERROR_SHARING_VIOLATION` is occured on `Fluent::FileWrapper.stat(path)` when a file is temporarily used by another process. Such files should be skipped safely until the file is released as same as ENOENT case. This patch rescues also other EACCES cases although they rarely occur. Signed-off-by: Takuro Ashie <[email protected]>
…if-only-available bin: fluentd: Specify trace_instruction as false if available
in_tail: Safely skip files used by another process on Windows
Otherwise it doesn't limit reading pace on reading many short lines. Signed-off-by: Takuro Ashie <[email protected]>
Use test driver's default one. Signed-off-by: Takuro Ashie <[email protected]>
in_tail: read_bytes_limit_per_second should precede read_lines_limit
ashie
force-pushed
the
try-fiddle-1.0.8
branch
9 times, most recently
from
8b90ebc to
6c72d25
Compare
Signed-off-by: Takuro Ashie <[email protected]>
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.
Which issue(s) this PR fixes:
Fixes #
What this PR does / why we need it:
Docs Changes:
Release Note: