Skip to content
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.

CLI hangs after any command that requires connection to the network #941

Open
mayzyo opened this issue Feb 21, 2022 · 0 comments
Open

CLI hangs after any command that requires connection to the network #941

mayzyo opened this issue Feb 21, 2022 · 0 comments
Labels
bug Something isn't working T-dev-tools

Comments

@mayzyo
Copy link

mayzyo commented Feb 21, 2022

Describe the bug
my near-cli stopped working yesterday after updating it to the latest (but not immediately aftewards I think). I tried reboot, reinstall, clean install in a fresh environment, even a simple 'near state' command just hangs. No error message even with the verbose flag, it just calls the function and gets stuck until I ctrl+c.

I am working inside WSL2 over a VPN. It's been working great for the past few weeks.

To Reproduce
Steps to reproduce the behavior:
1. near state mayzyo.testnet
2. See no error and just hangs

Expected behavior
It should return the current state of the account from testnet or show an error.

Screenshots
![image](https://user-images.githubusercontent.com/25147960/154877519-6b79bb0f-f2f8-4654-91ad-e71d1a57505e.png)

Desktop (please complete the following information):

  • OS: Windows (WSL2 Debian)
  • Version 11 Pro 21H2 (Bullseye)
@mayzyo mayzyo added the bug Something isn't working label Feb 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working T-dev-tools
Projects
None yet
Development

No branches or pull requests

1 participant