Closed MartinThoma closed 3 years ago
See https://status.python.org/incidents/grk0k7sz6zkp for context.
PyPI has had significant uptick in automated hits to the XMLRPC API, which has resulted in needing to take that offline, as it hampers the rest of the application's ability to function.
This happen to me too how to fix ?
Happen to me too Have you found any way to fix it?
@wkt @Syize "Me too" is not helpful. You can leave a "thumbs up" on the question. That already indicates you're interested in it. The developers are aware of the problem and are blocked by https://status.python.org/incidents/grk0k7sz6zkp . Those comments stop them from working on issues.
If only there was a way to blacklist ips....
For everyone landing here wondering what to do, note that this only affects pip search
. That command is currently broken by this, but you can still search the same database in your browser at https://pypi.org. Once you find a package there, pip install <package-name>
etc. still work.
Here is a quickfix to workaround the fact that pip search is broken:
Usage:
curl "https://search.hyper.dev/?q=jdango+saerch"
55 django-oscar-docdata https://pypi.org/project/django-oscar-docdata/
55 django-redirects https://pypi.org/project/django-redirects/
55 django-oscar-dsd https://pypi.org/project/django-oscar-dsd/
56 django-search-statistic https://pypi.org/project/django-search-statistic/
56 django-trace https://pypi.org/project/django-trace/
56 django-rated https://pypi.org/project/django-rated/
56 django-react https://pypi.org/project/django-react/
57 django-screener https://pypi.org/project/django-screener/
57 django-sections https://pypi.org/project/django-sections/
57 django-sitecats https://pypi.org/project/django-sitecats/
57 django-retracer https://pypi.org/project/django-retracer/
57 django-sendgrid https://pypi.org/project/django-sendgrid/
57 django-redirect https://pypi.org/project/django-redirect/
58 onionsearch https://pypi.org/project/onionsearch/
58 django-staticshard https://pypi.org/project/django-staticshard/
58 django-sebs https://pypi.org/project/django-sebs/
58 django-scss https://pypi.org/project/django-scss/
58 jina-search https://pypi.org/project/jina-search/
59 django-sharded https://pypi.org/project/django-sharded/
59 django-static-echarts https://pypi.org/project/django-static-echarts/
59 django-oscar-datacash https://pypi.org/project/django-oscar-datacash/
59 django-ratchet https://pypi.org/project/django-ratchet/
60 django_rediscache https://pypi.org/project/django_rediscache/
61 job-search https://pypi.org/project/job-search/
62 django-shared https://pypi.org/project/django-shared/
62 django-tracer https://pypi.org/project/django-tracer/
62 django-trench https://pypi.org/project/django-trench/
62 django-scanredirect https://pypi.org/project/django-scanredirect/
64 django-oscar https://pypi.org/project/django-oscar/
69 djangorestsearch https://pypi.org/project/djangorestsearch/
69 django-searchbar https://pypi.org/project/django-searchbar/
69 django-oscar-cch https://pypi.org/project/django-oscar-cch/
77 django-search https://pypi.org/project/django-search/
Related issue: https://github.com/pypa/warehouse/issues/8002
The issue linked above is about replacing the functionality of the search box you see on pypi.org, not pip search
(the issue of which is a standard API that not only applies to PyPI but also custom indexes).
My understanding is if MeiliSearch is good enough it can sustain the load for pip search too.
This is mainly speculation since I am not familiar with how Warehouse is implementing search, but my understanding is that the current load issue is caused by the XML-RPC API, not the actual search itself. So the solution must be a replacement of XML-RPC, and what is providing the actual search results internally does not really matter.
This is mainly speculation since I am not familiar with how Warehouse is implementing search, but my understanding is that the current load issue is caused by the XML-RPC API, not the actual search itself. So the solution must be a replacement of XML-RPC, and what is providing the actual search results internally does not really matter.
This is accurate.
Closing since #5216 is a superset of this issue and whatever the resolution is there, that'll be the answer to this issue as well. :)
Environment
Description
I just got this:
Expected behavior
No error message (or at least no traceback)
How to Reproduce
pip search something
Output
See above