Open zhaow-de opened 8 months ago
Confirmed that the issue exists for the following env.
OS: Amazon Linux 2023 arm
fluent bit: [fluent bit] version=3.0.3
BTW, if I change the os arch to x86, the issue disappeared...
Build with -fsigned-char
on arm
resolves this issue.
@RamaMalladiAWS sorry, that's a cmake flag right? I think we need to add this to AWS for Fluent Bit distro. Would you like to submit the github commit for the diff of the change?
@RamaMalladiAWS sorry, that's a cmake flag right? I think we need to add this to AWS for Fluent Bit distro. Would you like to submit the github commit for the diff of the change?
Yes, I can do.
I submitted PR: https://github.com/fluent/fluent-bit/pull/8851.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale
label.
We are waiting on merge of PR: https://github.com/fluent/fluent-bit/pull/8851.
Bug Report
Describe the bug
We have emojis in the log message. The emojis are carried forward in the pipeline at fluent-bit appropriately. However, in the last step, if the output is
s3
orfile
, the emojis got UNICODE-escaped in the produced file.To Reproduce
Create a simple test input file
input.log
, which contains only one line:Run
fluent-bit
with Docker usingfile
output:In the
output.log
file, the emoji is UNICODE-escaped:Expected behavior
The output should be:
Your Environment
Docker version:
Additional context
Still taking the
input.log
example, I succeeded with some other scenarios:Case 1: run fluent-bit with Docker using
stdout
as output. --Work as expectedCommand:
Output (from the log):
Case 2: run fluent-bit without Docker using
file
as output. --Work as expectedCommand:
Output (from
output.log
file):I also tried to build the image by taking
debian:bullseye-slim
as the base image. Installedlocales
:and set the environment variables accordingly in the
Dockerfile
:It did not change the result.