python / python/mypy

Stubgen fails with timeout for locust

Ouverte
#9,103 8 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

topic-stubgen
Langage dominant
Python
Étoiles
20.6k
Forks
3.3k
Métriques de merge des PR
Métriques de PR en attente

Description

Hi,
I'm trying to generate type stubs for Locust and stubgen fails with a timeout (see details below).
I was wondering if someone has any insight into what causes this or how to fix it.

Please provide more information to help us understand the issue:

  • Are you reporting a bug, or opening a feature request?
    Bug

  • Please insert below the code you are checking with mypy,
    or a mock-up repro if the source is private. We would appreciate
    if you try to simplify your case to a minimal repro.

    pip install mypy locust
    stubgen -p locust
    
  • What is the actual behavior/output?

    Traceback (most recent call last):
    File "./venv/bin/stubgen", line 10, in <module>
        sys.exit(main())
    File "mypy/stubgen.py", line 1564, in main
    File "mypy/stubgen.py", line 1422, in generate_stubs
    File "mypy/stubgen.py", line 1183, in collect_build_targets
    File "mypy/stubgen.py", line 1217, in find_module_paths_using_imports
    File "mypy/stubutil.py", line 62, in walk_packages
    File "mypy/moduleinspect.py", line 137, in get_package_properties
    File "mypy/moduleinspect.py", line 163, in _get_from_queue
    RuntimeError: Timeout waiting for subprocess
    
  • What is the behavior/output you expect?
    No console output and generated stubs in out/.

  • What are the versions of mypy and Python you are using?

    • Python v3.8.2
    • mypy 0.782
  • Do you see the same issue after installing mypy from Git master?
    Yes:

    Traceback (most recent call last):
    File "./venv/bin/stubgen", line 33, in <module>
        sys.exit(load_entry_point('mypy', 'console_scripts', 'stubgen')())
    File "/Users/simon/work/locust-test/mypy/mypy/stubgen.py", line 1564, in main
        generate_stubs(options)
    File "/Users/simon/work/locust-test/mypy/mypy/stubgen.py", line 1422, in generate_stubs
        py_modules, c_modules = collect_build_targets(options, mypy_opts)
    File "/Users/simon/work/locust-test/mypy/mypy/stubgen.py", line 1183, in collect_build_targets
        py_modules, c_modules = find_module_paths_using_imports(options.modules,
    File "/Users/simon/work/locust-test/mypy/mypy/stubgen.py", line 1217, in find_module_paths_using_imports
        found = list(walk_packages(inspect, packages, verbose))
    File "/Users/simon/work/locust-test/mypy/mypy/stubutil.py", line 62, in walk_packages
        prop = inspect.get_package_properties(package_name)
    File "/Users/simon/work/locust-test/mypy/mypy/moduleinspect.py", line 137, in get_package_properties
        res = self._get_from_queue()
    File "/Users/simon/work/locust-test/mypy/mypy/moduleinspect.py", line 163, in _get_from_queue
        raise RuntimeError('Timeout waiting for subprocess')
    RuntimeError: Timeout waiting for subprocess
    

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Reproduisez le problème avec stubgen -p locust après avoir installé mypy et locust. Commencez dans mypy/stubgen.py, au niveau de collect_build_targets et find_module_paths_using_imports, puis suivez les appels à travers mypy/stubutil.py et mypy/moduleinspect.py jusqu’au délai d’expiration du sous-processus. C’est terminé lorsque la commande s’exécute sans atteindre le délai d’expiration et génère des stubs dans out/.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
python
Domaine
tooling
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.