in reply to cpan warning for XML::DoubleEncodedEntities
You didn't say which version of cpan you have, super search is your friend -> Re^4: pod2html: link (L<...>) formatting code (timeloop)
"...and that this interface will be stopped on December 31 2018"
This has nothing to do with the problem reported.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: cpan warning for XML::DoubleEncodedEntities
by Aldebaran (Curate) on Jan 02, 2023 at 05:54 UTC | |
Thx, marto. I know that's not gonna quote well, but your link led to correction: choroba's response in Re^5: pod2html: link (L<...>) formatting code (timeloop). Essentially, the fix is: rm /home/ken/.cpan/sources/authors/id/?/??/*/CHECKSUMSRegarding Super Search, I haven't been able to make useful queries with it lately. Is that just me being Super Rusty? Continuing:
Those are certainly the usual suspects, and when I have a problem implementing software with such names on it, I strongly suspect that the problem is local, either on my machine or between my ears. Proceeding:
Alles klar...und...
I went over this install very closely, reading many of the sources:
And then, and then, and gentleman and then:
Q1) How can I repeat the tests in a comprehensive fashion? I stepped through one of the tests in the debugger:
I lengthened Tom's one-liner to a lexical script:
Output with various choices of ARGV, and a few (edited) runs dumping @q: Read more... (3 kB)
Finally, while I am writing up this simbad install project with what I'm calling success, the site and the client that gets it seem to be going just fine SOAP or no SOAP. (I still don't know what that is.) marto was completely correct that the interface had nothing to do with the problem reported. This is how you get this info with your browser:
or betelgeuse. Thanks all for comments, | [reply] [d/l] [select] |
by kcott (Archbishop) on Jan 02, 2023 at 07:11 UTC | |
[Minor attribution issue: s/link led to Corion's response/link led to choroba's response/ (2nd paragraph)] After successful "rm sources/authors/id/?/??/*/CHECKSUMS", I'd suggest the first thing to do would be to upgrade CPAN. As I indicated in "Re: cpan warning for XML::DoubleEncodedEntities", the vulnerability exists in v2.28; it's fixed in v2.29 (I left some notes about that in "Re^8: pod2html: link (L<...>) formatting code (timeloop)"); the current version is v2.34. "Q1) How can I repeat the tests in a comprehensive fashion?" For this, I'd generally use the prove utility. On the Astro::SIMBAD::Client page, there's a direct link to the tarball, there's also a link to the GitHub repository if you prefer that. Unpack the tarball and run the usual "perl Makefile.PL" followed by "make". At this point, the next step would normally be "make test"; instead of that, run prove here. There are a host of options. Some suggestions:
You can run those tests as many times as you want. I can't see a "Q2) ...?". :-) — Ken | [reply] [d/l] [select] |
by Aldebaran (Curate) on Jan 13, 2023 at 23:46 UTC | |
looking at testsThanks for your reply, kcott. As the world turns, you or Athanasius are the monks who take a first gander with what I am posting in SoPW. I want you to know that I respect you, and I try to adopt your perl style when you offer it. I traffic in a lot of exotic wide characters that I barely understand unless I can relate them to what I know, and when I'm knocking on the monastery door, my encodings are usually less than successful, and anything but well-ordered. I don't think the game is always winnable with some data sets, and I get them too. I'm working on better ways to represent translated data on the command line, but that's still in the works. I'd like to take 2 hot seconds to thank the author(s) of Astro::SIMBAD::Client. If there is anything here that reads as criticism, it is that I'm trying to make good software better. I'm delighted that the utility exists. For this, I'd generally use the prove utility. On the Astro::SIMBAD::Client page, there's a direct link to the tarball, there's also a link to the GitHub repository if you prefer that. Unpack the tarball and run the usual "perl Makefile.PL" ...Q1) How do I make a merge request on this project to change the documentation? I've been around the track a couple times with this software, and I'm starting to get the sense of it. I've learned that SOAP is a relative of SMTP. If half the things I know about SMTP apply to SOAP, then I would say that it is an issue that is superceded by the current script. So where does the text come from that hits STDOUT during:
Specifically, adiosing the lines:
Q1) (^^^specifically) How do I make a merge request on this project to change the documentation? I get a really good look at basic.t in the debugger at the precipice before it succeeds:
This is using the following save/source file:
Q2) p $smb{server} wasn't the right syntax to print that value. What is? (I'm rusty) Moving on to proving.
We've got a couple issues here. Does the # commented line represent a test? As we look deeper, the answer is: yes and no. I might call it a "test on the sly:"
So, when I fired up that prove command, I populated the southern end of this routine with values. Yes, the error was successfully reported, and I don't know that I would want to write software that gets blamed for failing when the internet is off, so it represents a bit of a quandary for me. As it is, I kick my network manager in the rear, and then repeat:
Q3) How would we lend this routine official test status? Q4) How would we write code to trap this error and then do something useful about it (that is, bouncing the network, waiting 15 seconds and trying again)? Q5) How do you get privileges for a script that didn't start with them? I'm not sure what the answer is to Q5, but I won't call it a proper answer if it involves me tapping around the keyboard to enter a password. It occurs to me that there might need to be a place where scripts can read the word that makes them sudoed, for example:
Q6) Are there more subtle ways to do this? I can't see a "Q2) ...?". :-)I've always got more questions. I'm trying to pick the right battles. :-) Cheers | [reply] [d/l] [select] |
by hippo (Archbishop) on Jan 14, 2023 at 11:09 UTC | |
by Aldebaran (Curate) on Jan 14, 2023 at 22:42 UTC | |
by kcott (Archbishop) on Jan 14, 2023 at 01:55 UTC | |
by Anonymous Monk on Jan 02, 2023 at 18:15 UTC | |
Tom didn't do that, it was just another perl hacker :) Also, your "Output with various choices" wrt "Mintaka" suggests it didn't work, but it does. I guess a few extra lines got pasted cause there's two "$VAR1". | [reply] |