Daijiro Fukuda

icon indicating a website link https://www.clear-code.com/ icon indicating an email [email protected]

icon company @clear-code icon location Tokyo, Japan icon location @clear-code A Fluentd maintainer. Supporting enterprise with Fluentd, nginx, milter, fcitx, GLFW, and so on.

Results 519 comments of Daijiro Fukuda

Fix line skipping issue in receive_lines method

@yugeeklab Sorry for the trouble. Could you please run the following command to recover your `origin/master` branch? (I wrongly pushed the current master to your `origin/master`. Sorry for the trouble.)...

Fix line skipping issue in receive_lines method

> Should I also reopen Pull Request? Of course! Thanks for reopening it! Sorry for the trouble.

out_file:Inconsistent path settings and symlink_path settings.

Thanks! There are 2 issues: 1. `path` setting validation issue. * It seems that validation for `tag` placeholder is not enough. 1. `symlink_path` setting validation issue. * We can completely...

'console' gem v1.25 causes LoadError

* Related to #4488

'console' gem v1.25 causes LoadError

There would be two options: * A: Fix the `require` path for `console` v1.25 * B: Stay using `console` v1.24

Backport(v1.16): Fix a failed test of ConsoleAdapter (#4477)

This fixes the CI failures for Ruby v3.0. (related to `console` gem v1.24) For Ruby v3.1, 3.2, and 3.3, we need to consider #4487. (related to `console` gem v1.25)

Backport(v1.16): Fix a failed test of ConsoleAdapter (#4477)

The following PR will solve this issue on v1.16, so we don't need this backport. * #4510

Warning: "Fiber#storage has borked keys and is being monkey-patched."

I have made an issue for `fiber-local`. * https://github.com/socketry/fiber-local/issues/4

Warning: "Fiber#storage has borked keys and is being monkey-patched."

> I have made an issue for `fiber-local`. > > * ['fiber-storage' outputs warning: Fiber#storage has borked keys and is being monkey-patched. socketry/fiber-local#4](https://github.com/socketry/fiber-local/issues/4) Fixed.

Output forward connections are in CLOSE_WAIT state

Looks like we need more information to investigate this. * Is the server side `out_forward` plugin? * Could you please share more logs? * Isn't there some detailed stacktraces? *...