You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It reproduces on Ruby 3.2.2 only, but that bug of Ruby exists from at least Ruby 2 series
I don't understand why it reproduces on Ruby 3.2.2 only (fluent-package v5.0.0 ~ v5.0.2)
Details
I feel like 100 characters would be easy to reproduce.
(I am not sure if the number of characters really has anything to do with the ease of reproduction.)
We confirmed that it's completely harmless because:
* However, it does not impact the Fluentd's behavior since [Ruby chops the character regardless of the content](https://github.com/ruby/ruby/blob/v3_2_2/ext/win32/lib/win32/registry.rb#L652)
We suspected it might be the cause of #618, but we've confirmed that it's not applicable too.
So we no longer need to track this issue.
Abst
fluentdopt
registry valueDetails
I feel like 100 characters would be easy to reproduce.
(I am not sure if the number of characters really has anything to do with the ease of reproduction.)
> fluentd --reg-winsvc-fluentdopt aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Confirm the value:
A:"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
B:"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaꘀ"
C:[97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 97, 234, 152, 128]
The garbage character can be different.
The text was updated successfully, but these errors were encountered: