This repository was archived by the owner on Oct 12, 2022. It is now read-only.
lazily initalize TLS block on first access#458
Merged
alexrp merged 1 commit intodlang:masterfrom Mar 21, 2013
Merged
Conversation
Contributor
|
Is the auto tester not testing this or something? |
Member
Author
|
Not sure what is going on here, but here are the tests. |
alexrp
added a commit
that referenced
this pull request
Mar 21, 2013
lazily initalize TLS block on first access
Contributor
|
@braddr did the results get lost en route to github or something? |
Member
|
Occasionally github rejects status api calls leading to gaps in the reporting. 4xx errors aren't retried. I just noticed that libcurl is failing to include http auth headers sometimes. I've disabled connection reuse to see if that helps. Unfortunately the errors are rather few and far between, so no telling if/when it'll recur. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This will allow to redo #456 correctly.