You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the tool via a Docker image build with the latest development branch (626fe38), on the CTA WAVE test vectors, with segment validation enabled, the following unexpected message appears: NO xml in /var/www/html/Utils/sessions/[...]/Period0/Adaptation0/Representation0/atomInfo.xml
Example:
php Process_cli.php --cmaf --ctawave --segments https://dash.akamaized.net/WAVE/vectors/cfhd_sets/12.5_25_50/t34/2022-10-17/stream.mpd
Going to run segment validator with config file /var/www/html/Utils/sessions/1667985563/Period0/Adaptation0/Representation0/segmentValidatorConfig.txt
NO xml in /var/www/html/Utils/sessions/1667985563/Period0/Adaptation0/Representation0/atomInfo.xml
The "NO xml" message might be caused by the lack of a root xml element in atomInfo.xml, unless it is another known issue.
@Phencys analyzed that and found the root cause. It seems to be caused by an invalid XML tag. The fix will be part of the internal refactor phase 2 and milestone 2.1.0.
I have created a pull request that should both clarify the actual meaning of this message if it occurs, and prevent if from occuring at this point in the first place.
* Add timeouts and some basic "HEALTH" checks on segment validator.
* Improvement for issue #614
* Less ambiguous message for issue #612
* Fix typo in validation test script for CTA WAVE
* Removed MPD handler as it is not part of this bugfix release
* Use global logger where needed
When running the tool via a Docker image build with the latest development branch (626fe38), on the CTA WAVE test vectors, with segment validation enabled, the following unexpected message appears:
NO xml in /var/www/html/Utils/sessions/[...]/Period0/Adaptation0/Representation0/atomInfo.xml
Example:
The "NO xml" message might be caused by the lack of a root xml element in atomInfo.xml, unless it is another known issue.
The text was updated successfully, but these errors were encountered: