what does this eror means?

[aniel300]

[2024-12-25T11:00:07Z DEBUG m3u_filter::utils::request_utils] Request took:0 secs, Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("xxx.live")), port: Some(8443), path: "/player_api.php", query: Some("username=xxx&password=xxx&action=get_series_categories"), fragment: None }

[euzu]

Only debug message.

[aniel300]

i also get this as well
[2024-12-25T11:05:59Z DEBUG m3u_filter::utils::request_utils] Request took:0 secs, Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("xxx.org")), port: Some(8080), path: "/player_api.php", query: Some("username=xxx&password=xxx&action=get_vod_categories"), fragment: None }

[euzu]

Wait this are not error messages, it is debug.
It says the request to this url took 0 seconds (was fast, without delay)

[euzu]

If it is Xtream-Codes you need user password.

This has nothing to do with me, it is the xc api.

[aniel300]

yes that i know am asking if '' would be needed around it since visual code is marking it in a strange way. also is there a way to include the update process within the info debug and not the debug debug envl, or a way to make it easier to know when it finished updating?

[euzu]

If this is a config file for m3u-filter, it uses yaml file format.
In yaml you can define a string like this:

password: 'my very secret password'

[aniel300]

also is there a way to include the update process within the info debug and not the debug debug env, or a way to make it easier to know when it finished updating?

[aniel300]

also is there a way to include the update process within the info debug and not the debug debug env, or a way to make it easier to know when it finished updating?

can u implement this? btw merry Christmas and I hope u feeling better

[euzu]

In the logs you can see a info output

2024-12-25T11:44:23Z INFO  m3u_filter::processing::playlist_processor] {"stats": {"name":"xtream","type":"xtream","errors":0,"raw":{"groups":23,"channels":1617},"processed":{"groups":3,"channels":4},"took":"1 secs"}}

This means the update process is finished

[euzu]

Yes

[aniel300]

ahh ok, thank u.

[euzu]

I have added a new output log (INFO level)
Update process finished!
which will be in the next release.

[aniel300]

sweet. perfect bud.

[aniel300]

I have added a new output log (INFO level) Update process finished! which will be in the next release.

can u add a way to know which m3u or xc are dead, fail, etc similar to how it is shown in the debug level upon the completion of sync on the info level one? trying to find that info when using the debug level while using redirect and heavy traffic/ request is a little hard if am not mistaken. i mainly trying to find out which m3u/xc are dead/bad to take them out.

[euzu]

yes i added a log at info level, will be in the next beta image.

[aniel300]

lets go

[aniel300]

was this added to Release v2.1.1 or should i wait for the next beta?