Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
TLMSP curl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CYBER - Cyber Security
TS 103 523 MSP
TLMSP
TLMSP curl
Commits
f97d1949
Commit
f97d1949
authored
20 years ago
by
Daniel Stenberg
Browse files
Options
Downloads
Patches
Plain Diff
adding issue 36 to be fixed before release
parent
4661cc74
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
TODO-RELEASE
+14
-0
14 additions, 0 deletions
TODO-RELEASE
with
14 additions
and
0 deletions
TODO-RELEASE
+
14
−
0
View file @
f97d1949
...
...
@@ -6,6 +6,20 @@ Issues not sorted in any particular order.
To get fixed in 7.11.2 (planned release late April/early May 2004)
======================
36. autobuild test failures on Tru64/IRIX (test case 88 for example)
The problem is once again (this is the same scenario we had before in the
notorious test case 91 failure bug hunt) that when doing a second request,
the client hasn't yet found out that the previous connection is on its way
to get closed. It then re-uses the connection only to find it closed right
away.
We have code starting at lib/transfer.c:1949 that is supposed to detect
this situation and enforce a retry. This retry never happens on these
failures, indicating that the check is bad or that some code has ruined the
values used in the check.
To get fixed in 7.12.0 (no date)
======================
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment