starred/log.io-NarrativeScience-old

Fork 0

mirror of https://github.com/NarrativeScience-old/log.io.git synced 2026-04-26 01:25:55 +03:00

[GH-ISSUE #66] First character of log string showed as single line (sometimes multiple) #49

New issue

Closed

opened 2026-02-26 05:31:10 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 05:31:10 +03:00

Owner

Originally created by @jochenonline on GitHub (Apr 11, 2013).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/66

Sometimes before a log line is displayed the first character of the line is presented as a single line. This looks like this then:

release linux [
release linux [
release linux [4] 2013-04-11 13:54:17 [INFO] 6960 0 6960
release linux [4] 2013-04-11 13:54:54 [INFO] [2013-04-11 13:54:54] [192.168.0.10]

release and linux are stream and node. The log string begins with [.

Originally created by @jochenonline on GitHub (Apr 11, 2013). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/66 Sometimes before a log line is displayed the first character of the line is presented as a single line. This looks like this then: ``` release linux [ release linux [ release linux [4] 2013-04-11 13:54:17 [INFO] 6960 0 6960 release linux [4] 2013-04-11 13:54:54 [INFO] [2013-04-11 13:54:54] [192.168.0.10] ``` `release` and `linux` are stream and node. The log string begins with `[`.

kerem closed this issue

2026-02-26 05:31:10 +03:00

kerem commented

2026-02-26 05:31:10 +03:00

Author

Owner

@chge commented on GitHub (Apr 25, 2013):

The same thing after clean install on Debian 2.6.32-5-amd64 with log.io 0.3.3.

@chge commented on GitHub (Apr 25, 2013): The same thing after clean install on Debian 2.6.32-5-amd64 with log.io 0.3.3.

kerem commented

2026-02-26 05:31:10 +03:00

Author

Owner

@vinsidious commented on GitHub (May 11, 2013):

I had the same problem, it was fixed when I created a new log file from scratch and made sure to save it with UTF-8 encoding.

@vinsidious commented on GitHub (May 11, 2013): I had the same problem, it was fixed when I created a new log file from scratch and made sure to save it with UTF-8 encoding.

kerem commented

2026-02-26 05:31:11 +03:00

Author

Owner

@jochenonline commented on GitHub (Jun 5, 2013):

Updated to the last version and no change till now. These are the last 10 lines of my mongodb logging:

mongodb server W
mongodb server Wed Jun 5 13:35:49.708 [conn1221615] end connection 127.0.0.1:40809 (364 connections now open)
mongodb server Wed Jun 5 13:35:49.708 [conn1221616] end connection 127.0.0.1:40810 (363 connections now open)
mongodb server W
mongodb server Wed Jun 5 13:35:49.709 [conn1221617] end connection 127.0.0.1:40811 (362 connections now open)
mongodb server W
mongodb server W
mongodb server Wed Jun 5 13:35:49.709 [conn1221619] end connection 127.0.0.1:40813 (361 connections now open)
mongodb server W
mongodb server Wed Jun 5 13:35:49.709 [conn1221618] end connection 127.0.0.1:40812 (360 connections now open)

@jochenonline commented on GitHub (Jun 5, 2013): Updated to the last version and no change till now. These are the last 10 lines of my mongodb logging: ``` mongodb server W mongodb server Wed Jun 5 13:35:49.708 [conn1221615] end connection 127.0.0.1:40809 (364 connections now open) mongodb server Wed Jun 5 13:35:49.708 [conn1221616] end connection 127.0.0.1:40810 (363 connections now open) mongodb server W mongodb server Wed Jun 5 13:35:49.709 [conn1221617] end connection 127.0.0.1:40811 (362 connections now open) mongodb server W mongodb server W mongodb server Wed Jun 5 13:35:49.709 [conn1221619] end connection 127.0.0.1:40813 (361 connections now open) mongodb server W mongodb server Wed Jun 5 13:35:49.709 [conn1221618] end connection 127.0.0.1:40812 (360 connections now open) ```

kerem commented

2026-02-26 05:31:11 +03:00

Author

Owner

@jpontius commented on GitHub (Nov 7, 2014):

I am seeing this issue as well. I'm watching simple text files of my own creation, text/plain; charset=us-ascii

500 Bruker 11-06-2014 15:25 (00:08) rliu3 2016593503020000 1H Chloroform-d VT=No None
500 Bruker 1
500 Bruker 11-06-2014 15:40 (00:10) jmeloche 2018953503020000 1H Chloroform-d VT=No None
500 Bruker 11-06-2014 15:55 (00:11) yshi3 3415213503010001 1H Chloroform-d VT=No None
500 Bruker 11-06-2014 16:14 (00:17) bbarret8 3414043503010001 1H|13C|31P|19F Benzene-d6 VT=No None
500 Bruker 1
500 Bruker 11-06-2014 16:26 (00:11) svilanov 3414043503010001 1H|31P Benzene-d6 VT=No None

@jpontius commented on GitHub (Nov 7, 2014): I am seeing this issue as well. I'm watching simple text files of my own creation, text/plain; charset=us-ascii ``` 500 Bruker 11-06-2014 15:25 (00:08) rliu3 2016593503020000 1H Chloroform-d VT=No None 500 Bruker 1 500 Bruker 11-06-2014 15:40 (00:10) jmeloche 2018953503020000 1H Chloroform-d VT=No None 500 Bruker 11-06-2014 15:55 (00:11) yshi3 3415213503010001 1H Chloroform-d VT=No None 500 Bruker 11-06-2014 16:14 (00:17) bbarret8 3414043503010001 1H|13C|31P|19F Benzene-d6 VT=No None 500 Bruker 1 500 Bruker 11-06-2014 16:26 (00:11) svilanov 3414043503010001 1H|31P Benzene-d6 VT=No None ```

kerem commented

2026-02-26 05:31:11 +03:00

Author

Owner

@wilpey commented on GitHub (Dec 22, 2015):

I have the same issue. Anyone managed to solve this?

@wilpey commented on GitHub (Dec 22, 2015): I have the same issue. Anyone managed to solve this?

kerem commented

2026-02-26 05:31:11 +03:00

Author

Owner

@msmathers commented on GitHub (Feb 18, 2020):

log.io v0.4.x has been completely rewritten and has new message parsing logic that should address this... please open a new ticket if this behavior continues, thanks!

@msmathers commented on GitHub (Feb 18, 2020): log.io v0.4.x has been completely rewritten and has new message parsing logic that should address this... please open a new ticket if this behavior continues, thanks!