Skip to content

Conversation

@OPhamster
Copy link

@OPhamster OPhamster commented Jun 16, 2024

  • In the event that the snapd service is not running, the snap client can spend a large amount of time trying to connect to it and ultimately failing. The expectation is that since snap comes already installed in several linux distros that the socket is placed in the same place.
 $ # with the check
 $ time ./screenfetch-dev
  real    0m0.680s
  user    0m0.389s
  sys     0m0.260s

 $ # without the check
 $ time screenfetch
  real    2m0.908s
  user    0m0.632s
  sys     0m0.501s

An alternative fix to #740

* In the event that the snapd service is not running, the snap client can spend
  a large amount of time trying to connect to it and ultimately failing. The
  expectation is that since snap comes already installed in several linux
  distros that the socket is placed in the same place.

```bash
 $ # with the check
 $ time ./screenfetch-dev
  real    0m0.680s
  user    0m0.389s
  sys     0m0.260s

 $ # without the check
 $ time screenfetch
  real    2m0.908s
  user    0m0.632s
  sys     0m0.501s
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant