New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config: Failed to parse config ending with newline. #2228
Comments
It seems a bug. |
It's bug for config to parsing the config directive, should be error when ends with '\n' without ';' Postpone to 5.0 |
winlinvip
changed the title
Documentation for realtime config has an error
Config: Failed to parse config ending with newline.
Apr 23, 2024
Each config directive should end with
|
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Apr 24, 2024
make sure one directive token don't span more than two lines.
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Apr 24, 2024
make sure one directive token don't span more than two lines.
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Apr 24, 2024
make sure one directive token don't span more than two lines.
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Apr 24, 2024
make sure one directive token don't span more than two lines.
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Apr 24, 2024
make sure one directive token don't span more than two lines.
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Apr 24, 2024
make sure one directive token don't span more than two lines.
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Apr 24, 2024
make sure one directive token don't span more than two lines.
suzp1984
added a commit
to suzp1984/srs
that referenced
this issue
Apr 24, 2024
make sure one directive token don't span more than two lines.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description'
Please ensure that the markdown structure is maintained.
3.0.153
Please ensure that the markdown structure is maintained.
Please ensure that the markdown structure is maintained.
Replay
Please ensure that the markdown structure is maintained.
Expect
Please ensure that the markdown structure is maintained.
If I add the missing semi-colon to the config after
tcp_nodelay on
then the min_latency setting is applied correctly. The sample configuration is incorrect in bothconf/realtime.conf
and the wiki in both languages.TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: