Bug 60506
Summary: | up2date traceback with today's php errata | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | James Manning <jmm> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED ERRATA | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | gafton, mihai.ibanescu, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-02-28 19:47:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James Manning
2002-02-28 19:07:55 UTC
this... [02:11] <adrian> that will go away when we turn the servers back on ...notwithstanding, I still think either 1) error message should be much better or 2) retries would be nice, ncftp style with sleeps perhaps? yeah yeah, a nicer error would be better. In the next version. All network calls get 5 retries at 1 or 5 second intervals (newer versions are 5). wow, what a weird code path to get a network error in. Thats like the last call you make after a dozen or more network calls on average. Bad timing for a server error ;-> I'll catch exceptions for these cases too, I missed them in most recent "catch all exceptions" extravaganza. fixed in cvs, should be in next errata reflecting today's errata push |