Tenderly crashes my computer

[danielaeichner]

I installed tenderly with:
$brew tap tenderly/tenderly && brew install tenderly

And then tried to do $tenderly login
I put in my access token. After waiting for a while, it comes back with some error message that it couldn't authenticate.
I can't exit the terminal with anything after that. My laptop gets really slow and then eventually crashes.
I'm running macOS Monterey 12.3.1 on a MacBook Pro 32GB

I tried this about 4 times.
Homebrew 3.6.16

I just found out that running tenderly with any command crashes my computer, even $tenderly --version

[beruda]

Hey @DanielaKirsch — could you try running brew reinstall tenderly and trying to login again?

[danielaeichner]

Same thing.

$ brew reinstall tenderly
==> Fetching tenderly/tenderly/tenderly
==> Downloading https://github.com/Tenderly/tenderly-cli/releases/download/v1.4.
Already downloaded: /Users/danielaeichner/Library/Caches/Homebrew/downloads/1b7cf37f63e81d8caf5020a5bcd1408d6653ab8afbbbddf4300f79b055c9137c--tenderly_1.4.10_Darwin_arm64.tar.gz
==> Reinstalling tenderly/tenderly/tenderly
🍺 /opt/homebrew/Cellar/tenderly/1.4.10: 5 files, 17.8MB, built in 1 second
==> Running brew cleanup tenderly...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see man brew).

% tenderly login
Use the arrow keys to navigate: ↓ ↑ → ←
✔ Access key can be generated at https://dashboard.tenderly.co/account/authorization
✔ Access key: *********************
Failed making request. Please try again.

And then, after "Failed making request. Please try again." my computer stops working and I have to restart. I can't even force quit anything.

[beruda]

Could you try upgrading to macOS Ventura?

[danielaeichner]

Is Tenderly not compatible with macOS Monterey? Why would it not be? Monterey is only a year old.

[beruda]

It really shouldn't be incompatible, but there's simply no precedent for this issue — you're the first person we've had report this problem. The CLI really doesn't do anything weird, so this shouldn't happen.

We can only conclude that this has something to do with your computer. However, without access to your machine, we have no real way of reproducing or debugging it, unfortunately.

I can recommend trying these approaches:

• installing a previous version of the CLI
• creating a fresh account on your machine & installing the CLI
• (the most drastic step) factory resetting your OS & reinstalling the CLI