{"issue":{"state":"open","created_at":"2011-12-15T07:12:44Z","updated_at":"2011-12-15T07:12:44Z","user":{"gravatar_id":"e53c81431e32f1d8432bb81da39cbeb6","id":31044,"url":"https://api.github.com/users/thaljef","avatar_url":"https://secure.gravatar.com/avatar/e53c81431e32f1d8432bb81da39cbeb6?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"thaljef"},"comments":0,"body":"I have one more request, but I don't yet have time to implement myself...\r\n\r\nThe Pod::Weaver::Section::Support plugin throws a fatal error if it does not find the right metadata.  Usually, I have D::Z::Plugin::GitHub::Meta provide that metadata.  But if I'm offline, then Github::Meta doesn't provide any metadata and DZ blows up.  It usually looks something like this:\r\n\r\n[DZ] beginning to build Dist-Zilla-Chef\r\n[DZ] dist's main_module is lib/Dist/Zilla/Chef.pm\r\n[DZ] extracting distribution abstract from lib/Dist/Zilla/Chef.pm\r\n[GitHub::Meta] Getting GitHub repository info\r\n[GitHub::Meta] Err: Can't connect to GitHub.com\r\n[DZ] No bugtracker in metadata!\r\n\r\nSo this basically means I can't build my dist when I'm offline (unless I tweak my dist.ini).  Obviously, that is a major hassle.  So I propose that Github::Meta should provide some dummy values for the metadata, if it can't get a response from GitHub.  You might also throw in a prompt to ask whether to use the dummy values or abort the build.","assignee":null,"id":2563784,"labels":[],"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"number":8,"title":"Feature Request: Use dummy values when offline","html_url":"https://github.com/AlexBio/Dist-Zilla-Plugin-GitHub/issues/8","closed_at":null,"milestone":null,"url":"https://api.github.com/repos/AlexBio/Dist-Zilla-Plugin-GitHub/issues/8"},"action":"opened"}