node-launcher
node-launcher copied to clipboard
Wild Bug Appears :)
Wild bug appears! Please copy this text and open an issue on GitHub. Node Launcher version 6.0.6
Error information:
file could not be opened successfully File "run.py", line 22, in File "node_launcher/gui/application.py", line 15, in init File "node_launcher/node_set/node_set.py", line 41, in init File "node_launcher/node_set/lnd.py", line 90, in init File "node_launcher/services/lnd_software.py", line 15, in lnd File "node_launcher/services/node_software.py", line 73, in executable_path File "node_launcher/services/node_software.py", line 92, in extract File "tarfile.py", line 1578, in open
Please note, this bug occurred when launching 6.0.7
I had the same bug on MAC OS Node Launcher 6.0.6
Error information:
file could not be opened successfully File "run.py", line 22, in File "node_launcher/gui/application.py", line 15, in init File "node_launcher/node_set/node_set.py", line 41, in init File "node_launcher/node_set/lnd.py", line 90, in init File "node_launcher/services/lnd_software.py", line 15, in lnd File "node_launcher/services/node_software.py", line 73, in executable_path File "node_launcher/services/node_software.py", line 92, in extract File "tarfile.py", line 1578, in open
Running the EXE on Windows 10... very similar issue:
Wild bug appears! Please copy this text and open an issue on GitHub. Node Launcher version 6.0.6
Error information:
File is not a zip file File "run.py", line 22, in File "node_launcher\gui\application.py", line 15, in init File "node_launcher\node_set\node_set.py", line 41, in init File "node_launcher\node_set\lnd.py", line 90, in init File "node_launcher\services\lnd_software.py", line 15, in lnd File "node_launcher\services\node_software.py", line 73, in executable_path File "node_launcher\services\node_software.py", line 89, in extract File "zipfile.py", line 1225, in init File "zipfile.py", line 1292, in _RealGetContents
The same issue here, 6.0.7, also 6.0.6:
And another one here (on 6.0.7):
Does anyone knows how to fix this error in Mac?
same same
Same
lo mismo, que coño pasa?