Bug 2103093
Summary: | upload of 2.8 GiB SRPM over slow network dies with division by zero | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kamil Dudka <kdudka> |
Component: | python-progress | Assignee: | Pavel Raiskup <praiskup> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 35 | CC: | clime7, copr-team, imvalgo, jkadlcik, kdudka, msuchy, praiskup, python-sig, slavek.kabrda, turecek.dominik |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-progress-1.6-4.fc37 python-progress-1.6-4.el9 python-progress-1.6-4.fc36 python-progress-1.6-4.fc35 python-progress-1.6-4.el8 python-progress-1.6-4.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-07-05 15:35:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kamil Dudka
2022-07-01 12:30:32 UTC
I ended up with the following hotfix in progress/__init__.py: @property def avg(self): x = self.last - self.deque[0][0] if x <= 0.0 and x >= 0.0: return float('inf') else: return self.counter / x Thank you for the report and patch. The situation is very weird. Unless (a) the connection is _very_ unstable, and the box is _very_ fast, OR (b) the time() on the box goes backward, I'm clueless. This is the proposed fix for both a) and b) situations: https://src.fedoraproject.org/rpms/python-progress/pull-request/5 Thank you for the quick fix! I will retest it when I am back on my home network. I wanted to verify the fix. Unfortunately, I am not able to trigger the traceback captured in comment #0 right now any more. FEDORA-2022-55f18fa50e has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-55f18fa50e FEDORA-2022-3f942d3b4f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3f942d3b4f FEDORA-EPEL-2022-6f72c19cfc has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6f72c19cfc FEDORA-EPEL-2022-cb1d0a0321 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-cb1d0a0321 FEDORA-EPEL-2022-1b7daed183 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-1b7daed183 FEDORA-2022-210571b2ac has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-210571b2ac > I wanted to verify the fix. Unfortunately, I am not able to trigger the
> traceback captured in comment #0 right now any more.
No problem, the issue you faced before was weird, and unlikely. Thank you
for the attempt at least! The PR is correct anyway, I believe. So I
merged and built. Please reopen if you face the same issue again.
FEDORA-2022-55f18fa50e has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-3f942d3b4f has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-3f942d3b4f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3f942d3b4f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-210571b2ac has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-210571b2ac` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-210571b2ac See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-1b7daed183 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-1b7daed183 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-cb1d0a0321 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-cb1d0a0321 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-6f72c19cfc has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6f72c19cfc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-1b7daed183 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-210571b2ac has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-3f942d3b4f has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2022-cb1d0a0321 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2022-6f72c19cfc has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. |