HelloZeroNet / HelloZeroNet/ZeroNet
Can not abort "python zeronet.py siteDownload" command
- Langage dominant
- JavaScript
- Étoiles
- 18.8k
- Forks
- 2.3k
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
### Step 1: Please describe your environment
Version: 0.6.1 r3221, Python 2.7.5 (default, Aug 4 2017, 00:39:18)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-16)], Gevent: 1.0
OS: Linux 64 bit
### Step 2: Describe the problem:
If site does not have any peers, the "python zeronet.py siteDownload" command gets stuck and i can not abort it:
> [user@localhost ZeroNet]# python zeronet.py siteDownload addresshere
> - Starting ZeroNet...
> - OpenSSL loaded, version: 01000207F
> - Version: 0.6.1 r3221, Python 2.7.5 (default, Aug 4 2017, 00:39:18)
> [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)], Gevent: 1.0
> - Opening a simple connection server
> TorManager Connecting to Tor Controller 127.0.0.1:9051
> TorManager Tor controller connect error: error: [Errno 111] Connection refused in TorManager.py line 170 > socket.py line 342
> TorManager Starting self-bundled Tor, due to Tor proxy port 127.0.0.1:9050 check error: No connection
> Site:1KR7WW..hMPK Content.json not exist: data/addresshere/content.json
> Announcing...
> Downloading...
> ConnServer Internet offline
> ^CShutting down...
> - Unhandled exception
> None
> KeyboardInterrupt
> ^CShutting down...
> - Unhandled exception
> None
> KeyboardInterrupt
> exit
> ^Ad^CShutting down...
> - Unhandled exception
> None
> KeyboardInterrupt
Keyboard interrupt means i did abort command Ctrl+C in my console (Putty SSH client)
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Start at the `python zeronet.py siteDownload` entry point and reproduce the command with a site that has no peers. Trace the shutdown path after Ctrl+C and verify that the process exits cleanly without repeated KeyboardInterrupt or unhandled-exception output.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- python
- Domaine
- cli, networking
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100