Feature #10592
closed
Try to get rid of ZIP error workaround
Added by Evgeny Novikov almost 4 years ago.
Updated over 3 years ago.
Description
We made this workaround to handle so called ZIP errors, i.e. when Bridge should receive archives within requests from Core, but it finds out that they are broken. In this case Core infinitely resends such request and I guess that after a second attempt everything is okay (but I did not evaluate that ever).
Maybe after #10579 we will not need this workaround, but we need to estimate this before.
Related issues
1 (1 open — 0 closed)
I've added logging of ZIP errors in Bridge in the branch "feature_10592" (file "logs/ZIP.log").
I merged the branch to master. Let's see on logs...
- Priority changed from Urgent to High
- Target version deleted (
3.0)
I do not see any errors related to broken ZIP archives in Bridge logs after several days of extensive operation. So, let's hope that we identified this ugly issue at last. But let's get rid of the workaround after 3.0 to avoid any unpleasant surprises.
- Related to Feature #6587: Extract class Session to common libraries added
- Target version set to 3.1
It seems that it's time to get rid of this workaround at last.
- Category set to Bridge
- Assignee changed from Evgeny Novikov to Vladimir Gratinskiy
I got rid of this workaround in Core and Scheduler in branch get-rid-of-zip-error-workaround. Indeed, most work for this issue is in Bridge
- Due date set to 03/01/2021
- Category deleted (
Bridge)
- Status changed from New to Resolved
- Assignee changed from Vladimir Gratinskiy to Evgeny Novikov
- % Done changed from 0 to 100
Implemented in bridge-10592.
- Category set to Bridge
- Assignee changed from Evgeny Novikov to Vladimir Gratinskiy
- Status changed from Resolved to Closed
The branch passed tests, so, there is no more ZIP error workaround! Let's hope that nobody will need it anymore.
Also available in: Atom
PDF