Skip to content
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

"NO xml in atomInfo.xml" when running segment validation tests #612

Closed
nicholas-fr opened this issue Nov 9, 2022 · 3 comments
Closed

"NO xml in atomInfo.xml" when running segment validation tests #612

nicholas-fr opened this issue Nov 9, 2022 · 3 comments
Assignees
Milestone

Comments

@nicholas-fr
Copy link

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.

root@80d4d1513f39:/var/www/html/Utils/sessions/1667985563/Period0/Adaptation0/Representation0# cat atomInfo.xml
<atomlist>
  <ftyp majorbrand="iso6" version="0x1" compatible_brands='[
     "cfhd"
     "cmf2"
     "iso6"
     "dash"
    ]'>
  </ftyp>
[...]
</atomlist>
@dsilhavy dsilhavy added this to the v2.1.0 milestone Nov 9, 2022
@dsilhavy
Copy link
Contributor

dsilhavy commented Nov 9, 2022

@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.

@Phencys
Copy link
Collaborator

Phencys commented Nov 18, 2022

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.

dsilhavy pushed a commit that referenced this issue Nov 30, 2022
* 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
@dsilhavy
Copy link
Contributor

dsilhavy commented Dec 6, 2022

Fixed in #616, please comment if you still encounter this, closing for now.

@dsilhavy dsilhavy closed this as completed Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants