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
The parser currently goes back to ID state after CUETEXT when it should go back to HEADER so that a X-TIMESTAMP-MAP that may appear can be parsed. I tried updating the code and adding tests for this case, but I can't get it to run (I jumped back node:10 in a docker image with a Debian Buster base but it wouldn't run (appears that PhantomJS is hanging or something).
So is there a recommend way to run the tests with a current setup so I can make and test a fix for this?
The text was updated successfully, but these errors were encountered:
The parser currently goes back to
ID
state afterCUETEXT
when it should go back toHEADER
so that aX-TIMESTAMP-MAP
that may appear can be parsed. I tried updating the code and adding tests for this case, but I can't get it to run (I jumped backnode:10
in a docker image with a Debian Buster base but it wouldn't run (appears that PhantomJS is hanging or something).So is there a recommend way to run the tests with a current setup so I can make and test a fix for this?
The text was updated successfully, but these errors were encountered: