Sebb created WHIMSY-124:
---------------------------
Summary: podlings.rb/namesearch does not handle HTTP errors well
Key: WHIMSY-124
URL: https://issues.apache.org/jira/browse/WHIMSY-124
Project: Whimsy
Issue Type: Bug
Components: Core
Reporter: Sebb
Assignee: Sam Ruby
Priority: Minor
Seeing some errors like this:
Problem (danger) detected in podlings job
...
{noformat}
/usr/local/rvm/gems/ruby-2.4.1/gems/json-2.1.0/lib/json/common.rb:156:in
`parse': 765: unexpected token at '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML
2.0//EN"> (JSON::ParserError)
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator at
webmas...@apache.org to inform them of the time this error occurred,
and the actions you performed just before this error.</p>
<p>More information about this error may be available
in the server error log.</p>
</body></html>
'
from
/usr/local/rvm/gems/ruby-2.4.1/gems/json-2.1.0/lib/json/common.rb:156:in `parse'
from /x1/srv/whimsy/lib/whimsy/asf/podling.rb:361:in `namesearch'
from /x1/srv/whimsy/lib/whimsy/asf/podling.rb:386:in `namesearch'
from /x1/srv/whimsy/lib/whimsy/asf/podling.rb:321:in `as_hash'
from roster/public_podlings.rb:88:in `block in <main>'
from roster/public_podlings.rb:88:in `map'
from roster/public_podlings.rb:88:in `<main>'
{noformat}
This appears to be due to an HTTP error contacting JIRA.
Unfortunately such errors are quite common so I think it would be worth trying
to work round the error. Or at least provide a more meaningful error message.
A retry would be possible, but would that slow things down too much?
If the cache is present but not (too) stale it could perhaps be re-used?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
