| Age | Commit message (Collapse) | Author |
|---|
|
There was common situations where two provider instances where running
in parallel. And was creating weird errors (like getting wrong api_uri)
because the bootstrap deferreds were global but the Provider objects
not.
I don't like much singletons, but I think now is simpler than before.
- Resolves: #9073
|
|
here we port the if-modified-since conditional mechanism, so that we
only write the config if it is newer than whan we have.
we also add a line with the status code to the logs, so that it's easier
to debug.
note that the 'configs.json' file is never returning 304.
- Resolves: #8773
|
|
The workaround is no needed anymore, if we do 'GET' instead of 'POST' to
fetch all the provider configuration jsons it works smoothly.
- Resolves: #9056
|
|
|
|
Old versions of the webapp let agent download an invalid.json, instead
of returning a 404. We try to parse the json, and if no valid json is
found, we use the workaround for manually downloading the service files.
- Resolves: #9004
|
|
if there is no ca_cert passed and the provider is configured, use the
pinned ca cert when the autoconf parameter is true.
|
|
leap.common is going to handle this
|
|
- Resolves: #8881
|
|
|
|
- Resolves: #8884
|
|
This fixes two bugs with handling the autoconf parameter:
- It looks for "True" instead of "true" in the dispatching code to
account for json.dumps() converting true into a boolean and str()
returning the python-style capitalized version "True".
- It moves the initial definitions of offirst_bootstrap,
ongoing_bootstrap, and stuck_bootstrap into the class instantiation
method so they don't get shared between instances of the
class. Previously, this caused one instance being bootstrapped to
causes other instances to think they were also actively being
bootstrapped.
Resolves #8843
|
|
I changed most of the logger statements to use a class attribute, in
this way it's easier to identify which class it's logging them.
in some cases I leave a module-level logger, when we're either using
functions or when the module it's too small.
at the same time I did a general review and cleanup of the logging
statements.
|
|
Instead of hardcoding them in the code.
|
|
|
|
|
|
|
|
|
|
- Resolves: #8498
|
|
- Resolves: #8400
|
|
|
|
|
