Fix invalid message polluting subsequent message

[kaorimatz]

A message that cannot be converted to msgpack currently pollutes a subsequent message. For example,

logger = Fluent::Logger::FluentLogger.new
logger.post_with_time('tag1', { foo: 1 << 64 }, Time.utc(2023, 12, 05)) # FluentLogger: Can't convert to msgpack: ["tag", 1701734400, {:foo=>18446744073709551616}]: bignum too big to convert into `unsigned long long'
logger.post_with_time('tag2', { bar: 'bar' }, Time.utc(2023, 12, 06))

sends the following message

2023-12-05T00:00:00+00:00       tag1     {"foo":["tag2",1701820800,{"bar":"bar"}]}

instead of the following.

2023-12-06T00:00:00+00:00       tag2     {"bar":"bar"}

[ashie]

Thanks!

[ashie]

We need to release a new version, but I don't have ownership of this gem on RubyGems.
https://rubygems.org/gems/fluent-logger

Could you add me as an onwer of this gem on RubyGems? @frsyuki @repeatedly

[ashie]

Could you add me as an onwer of this gem on RubyGems? @frsyuki @repeatedly

I've received your invitation. Thanks!

[ashie]

I've released v0.9.1.

[kaorimatz]

@ashie Awesome, thank you for reviewing the change and releasing a new version. (Thanks to @frsyuki for adding @ashie as a gem owner.)