7.5.0 login freeze and CPU go to 100%, but 6.9.0 works fine

[linchen2chris]

Priority

(Medium) I'm annoyed but I'll live

Description

hi team, when I run m365 login --authType password --userName chen.lin@xxxx.com --password xxxxxx --debug then it freeze, but then I switch to m365 6.9.0, everything works.

Steps to reproduce

1. install m365 7.5.0
2. run m365 login --authType password -u xxxx -p xxxx --debug

Expected results

it should login success

Actual results

it freeze

Diagnostics

No response

CLI for Microsoft 365 version

3.7.0

nodejs version

18.19.0

Operating system (environment)

Linux

Shell

bash

cli doctor

can't provider doctor, because it need login first

Additional Info

No response

[waldekmastykarz]

Thanks for reaching out @linchen2chris and sorry to hear CLI is not working as expected. Could you please try to run v7.0 and see if you still see the error? It would help us a lot to debug the issue, if we could find the first CLI version that shows this behavior. We appreciate your help

[martinlingstuyl]

Just tried 7.5 on Ubuntu 20.04.

• I can't reproduce the freezing.
• The cli doctor command throws the same error on my end

[martinlingstuyl]

I'm curious to hear your results when installing 7.0 or 7.4 @linchen2chris

[waldekmastykarz]

• The cli doctor command throws the same error on my end

cli doctor is not an anonymous command which is why you need to sign in first. That's by design.

[linchen2chris]

I'm curious to hear your results when installing 7.0 or 7.4 @linchen2chris

hi @martinlingstuyl 7.0.0 works

but 7.4.0 freeze, same with 7.5.0

[linchen2chris]

@martinlingstuyl I also tried 7.3.0 and 7.2.0: 7.2.0 works

but 7.3.0 freeze, maybe 7.3.0 is the first version breaks. hope that helps

[martinlingstuyl]

So what kind of Linux environment are you running @linchen2chris ?

[linchen2chris]

So what kind of Linux environment are you running @linchen2chris ?

centos in docker

[martinlingstuyl]

Would you mind sharing your dockerfile. So we can try to reproduce it?

[linchen2chris]

FROM centos

RUN cd /etc/yum.repos.d/ RUN sed -i 's/mirrorlist/#mirrorlist/g' /etc/yum.repos.d/CentOS- RUN sed -i 's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' /etc/yum.repos.d/CentOS- WORKDIR /autotest/ RUN curl -O https://nodejs.org/download/release/v18.19.1/node-v18.19.1-linux-x64.tar.gz \ && tar -xf node-v18.19.1-linux-x64.tar.gz \ && rm node-v18.19.1-linux-x64.tar.gz ENV PATH="/autotest/node-v18.19.1-linux-x64/bin:${PATH}" RUN npm install -g @pnp/cli-microsoft365@6.9.0

[waldekmastykarz]

Hey @martinlingstuyl, did you have a chance to look into this?

[martinlingstuyl]

No unfortunately not, @waldekmastykarz...

[martinlingstuyl]

...but is 7.3 the same version where we updated Ora? We may just have found an additional side effect of the spinner.

[martinlingstuyl]

@Adam-it...

[Adam-it]

...but is 7.3 the same version where we updated Ora? We may just have found an additional side effect of the spinner.

Yes it is. In 7.2 it was 5.4.1 and in 7.3 we updated it to higher version which introduce some problems.

[martinlingstuyl]

@linchen2chris, we'll be removing a faulty package from the CLI in the next beta. We're expecting it may be the reason for your issues. We'll get you up to speed as soon as we've done that so you can try out the new beta. Sorry for the long hold up.