mirror of
https://github.com/facebook/sapling.git
synced 2024-10-07 15:27:13 +03:00
4e3c6d9b7a
If code inside a context manager returns a generator, the context manager exits before the generator is iterated. hgweb was using a context manager to control thread safe access to a localrepository instance. But it was returning a generator, so there was a race condition between a previous request streaming a response to the client and a new request obtaining the released but in use repository. By iterating the generator inside the context manager, we ensure we don't release the repo instance until after the response has finished. With this change, hgweb finally appears to have full localrepository isolation between threads. I can no longer reproduce the 2 exceptions reported in issue4756. test-hgweb-non-interactive.t has been modified to consume the output of calling into a WSGI application. Without this, execution of the WSGI application stalls because of the added yield statement. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| common.py | ||
| hgweb_mod.py | ||
| hgwebdir_mod.py | ||
| protocol.py | ||
| request.py | ||
| server.py | ||
| webcommands.py | ||
| webutil.py | ||
| wsgicgi.py | ||