Frost Ming

The problem here is that there are actually two backends for tasks: in-memory background task with sqlite result store and cloud-based ingress routing, only the former is built into the...

Make sure your index doesn't redirect non-existing package requests to PyPI. That is quite common in index implementations.

I can't reproduce it, could you track where the request is initiated from? btw did you enable `check_update`, that is always checking what `pypi.url` is configured to

I’m having trouble reproducing this issue. Can you reproduce it using the `numpy` package from pypi.org? We do have a check to clear existing hashes, but only when they lack...

We do not have control over which worker the data will go through: https://circus.readthedocs.io/en/latest/tutorial/step-by-step/#installation:~:text=Note%20The%20load%20balancing%20is%20operated%20by%20the%20operating%20system%20so%20you%E2%80%99re%20getting%20the%20same%20speed%20as%20any%20other%20pre%2Dfork%20web%20server%20like%20Apache%20or%20NGinx.%20Circus%20does%20not%20interfer%20with%20the%20data%20that%20goes%20through. How does it matter in your case?

> 2\. Run `python3 bento_request_en.py` in each pods. The balancing result is not correct since you are sending requests in sequence

> Do you mean that I should make the service API asynchronous and have the client send requests asynchronously as well? Just make the client send requests concurrently