more creatures gret and small question
hello More Creatures Great and Small Episode 9 in in the tv.cache 4648|tv|More Creatures Great and Small|b0400tyf|2018-03-02T16:20:00+00:00|1522599600|Episode 9||9|default|1800|Vet Megan is on a mission in Fife to help rehome 80 commercial caged hens.|BBC Two|||1519047272||http://www.bbc.co.uk/programmes/b0400tyf| when attempting to fetch this episode I received the below error: INFO: Search args: '' INFO: Loaded history for first check. INFO: Loading recordings history INFO: Programme not in history INFO: Got 8814 file cache entries for tv INFO: Got 18545 file cache entries for radio INFO: Cleaning PID - old: 'b0400tyf' new: 'b0400tyf' INFO: Getting URL: http://www.bbc.co.uk/programmes/b0400tyf.json INFO: tv episode PID detected (b0400tyf) Matches: 4648: More Creatures Great and Small - Episode 9, BBC Two, b0400tyf INFO: 1 matching programmes INFO: Programme not in history INFO: Getting URL: http://www.bbc.co.uk/programmes/b0400tyf.json INFO: Getting URL: http://open.live.bbc.co.uk/mediaselector/5/select/version/2.0/mediaset/iptv-all/vpid/b0400tyc/transferformat/dash?cb=32849 ERROR: Response: 404 Not Found INFO: Getting URL: http://open.live.bbc.co.uk/mediaselector/5/select/version/2.0/mediaset/pc/vpid/b0400tyc/transferformat/dash?cb=57114 ERROR: Response: 404 Not Found INFO: Getting URL: http://open.live.bbc.co.uk/mediaselector/5/select/version/2.0/mediaset/iptv-all/vpid/b0400tyc/transferformat/hls?cb=09524 ERROR: Response: 404 Not Found INFO: Getting URL: http://open.live.bbc.co.uk/mediaselector/5/select/version/2.0/mediaset/apple-ipad-hls/vpid/b0400tyc/transferformat/hls?cb=40092 ERROR: Response: 404 Not Found INFO: No streams available for 'original' version (b0400tyc) - skipping INFO: No streams found for 'original' version (b0400tyc) - deleting WARNING: No media streams found for requested programme versions and recording modes. ERROR: Could not get programme metadata It appears that the episode was scheduled to be aired and for whatever reason was skipped. This also happened with Episode 1 Never figured that one out. thoughts, comments, hints welcomed. -- terry l. ridder ><> ___ get_iplayer mailing list get_iplayer@lists.infradead.org http://lists.infradead.org/mailman/listinfo/get_iplayer
Re: Format of options file
I don't know the history of this thread, but a Windows perl will use the
`:crlf` layer which is fine for both Windows (CR LF) and Linux (LF) line
terminations. The CR will be removed, and every line read will end with LF
("\n")
The most common problem arises when a Linux perl attempts to read a Windows
text file. The default PerlIO stack on Linux is an empty one, so the CR LF
characters appear intact in every line read
There are a few solutions:
1/ Change the default PerlIO layers
use open qw/ :std :crlf /
will cause every file to be opened with the Windows `:crlf` layer, which
removes any CR if it is there. It doesn't affect Linux files at all
2/ If you *always* `chomp` every line, then use
s/\R\z//
instead, which will remove any line termination character or character pair
3/ If you *always* `split` every line using the default of `split ' ', $_` then
there is nothing to do: CR is considered to be a whitespace character and will
be removed from the fields
There are clearly variations on this idea, but it shouldn't be hard to resolve
from here
Can someone please tell me whether I have answered the original question, or if
I'm miles off?
Rob Dixon
Norfolk
England
-Original Message-
From: Ralph Corderoy
To: get_iplayer@lists.infradead.org
Sent: Tue, 06 Mar 2018 13:30
Subject: Re: Format of options file
Hi David,
> binmode does still work AFAIK, but a more modern and flexible method
> is to use the crlf I/O layer, which is documented here:
> https://perldoc.perl.org/PerlIO.html
>
> Note however that an awful lot of perl code just doesn't bother.
Windows stacks the `:crlf' layer by default. I *think* Richard's trying
to avoid that because he wants his get_iplayer to use POSIX text files
on Linux, as normal, and Windows.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
___
get_iplayer mailing list
get_iplayer@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/get_iplayer
___
get_iplayer mailing list
get_iplayer@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/get_iplayer
Re: Format of options file
> > binmode does still work AFAIK, but a more modern and flexible method > > is to use the crlf I/O layer, which is documented here: > > https://perldoc.perl.org/PerlIO.html > > > > Note however that an awful lot of perl code just doesn't bother. > > Windows stacks the `:crlf' layer by default. I *think* Richard's trying > to avoid that because he wants his get_iplayer to use POSIX text files > on Linux, as normal, and Windows. PerlIO enables you to go either way, and no code changes are necessary. The simplest solution is to run the equivalent of 'PERLIO=crlf get_iplayer [...]' on Linux, perhaps via an alias in your shell. Probably best not to set PERLIO=crlf permanently if you run other Perl programs. You may not like having files with CRLF line endings, but they will still work on both platforms if you screw up editing and get mixed line endings. If you really can't abide CRLF, use PERLIO=perlio on Windows instead to produce LF line endings. Probably simplest to set it locally in the get_iplayer batch file. You just have to be careful not to inject CRLF line endings if you edit any files directly, though I would expect any decent text editor on both platforms can avoid that. ___ get_iplayer mailing list get_iplayer@lists.infradead.org http://lists.infradead.org/mailman/listinfo/get_iplayer
Re: Format of options file
Hi David, > binmode does still work AFAIK, but a more modern and flexible method > is to use the crlf I/O layer, which is documented here: > https://perldoc.perl.org/PerlIO.html > > Note however that an awful lot of perl code just doesn't bother. Windows stacks the `:crlf' layer by default. I *think* Richard's trying to avoid that because he wants his get_iplayer to use POSIX text files on Linux, as normal, and Windows. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___ get_iplayer mailing list get_iplayer@lists.infradead.org http://lists.infradead.org/mailman/listinfo/get_iplayer
Re: Format of options file
On Mon, Mar 05, 2018 at 08:04:09PM +, RS wrote: > It's worse than I thought. I had got the impression from the perlport > perldoc that if replaced \n with \012 in a print statement I would get a > LF on its own in Windows. I don't. If I insert \015 I can have a CR on > its own, but \012 is still replaced with CR LF. > > This article > http://www.perlmonks.org/?node=binmode > says I can use binmode, so that may be an answer. It's quite old, so it > may no longer apply. binmode does still work AFAIK, but a more modern and flexible method is to use the crlf I/O layer, which is documented here: https://perldoc.perl.org/PerlIO.html Note however that an awful lot of perl code just doesn't bother. Windows is very much a second-class citizen in the perl world. -- David Cantrell | Nth greatest programmer in the world If you can read this, thank a teacher. If you're reading it in English, thank Chaucer. ___ get_iplayer mailing list get_iplayer@lists.infradead.org http://lists.infradead.org/mailman/listinfo/get_iplayer
Re: Message with suspicious header
On Sat, 2018-03-03 at 13:00 +, Dave Widgery wrote: > I have yet again had a message held due to a suspicious header, all I > did was press reply? For messages which are in response to a thread, the system is checking that they start with either 'Re:' or 'Aw:', or some other things. For some reason your latest one started 'Re[2]:' instead. I'll look at fixing the checks to tolerate that too, bizarre though it is. Apologies for the inconvenience, but across the full set of mailing lists this is a useful tool to... "encourage" people to behave correctly and not do bad things which detract from the communication. smime.p7s Description: S/MIME cryptographic signature ___ get_iplayer mailing list get_iplayer@lists.infradead.org http://lists.infradead.org/mailman/listinfo/get_iplayer
