ActivePython2.7 Windows10 64bits: Suddenly c:\>python "Rollbar error: empty token" message

Hello all,

This morning everything was doing well (PS C:\Users…> python fileXX.py was fine), when I tried again with a minor change in fileXX.py and since that time I keep having this error message:

"PS C:\Users…> python (or PS C:\Users…> python fileXX.py)
2021/07/19 14:57:38 Rollbar error: empty token
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x1266a1c]

goroutine 1 [running]:
github.com/ActiveState/cli/ …"

Nothing changed after powered on/off the computer.

More Error message

“PS C:> python
2021/07/19 17:01:48 Rollbar error: empty token
Error writing log message: Could not open log file for writing: state-13668.log
[ERROR Jul 19 17:01:48.528779100, defaults.go:149] Could not load configuration: Failed to load configuration.
…”

Hey there @EDDE — thanks for the error report — will pass this along to the team to investigate.

Thanks!

Hi @EDDE ,

Unfortunately you have ran into a known bug that will be fixed in an update landing soon. To work around it until then you can reset your internal config file. In effect this just means you’ll have to authenticate again, if you were already authenticated.

Please locate your config directory using the documentation here:

https://docs.activestate.com/platform/state/troubleshooting/

Then delete the config.yml file located in that directory.

Thanks Nathanr for your answer.

After deleting the config.yaml file, I call the program but I have still an alert message.

In the directory :

C:\Users\edouard.delevoy\AppData\Roaming\ActiveState\cli-release,

a new config.yaml file appears but empty.

Could you show me what you’re talking about? What message are you seeing?

This is normal. The old one was corrupted, so we deleted it. Which means a new one will be generated next time you invoke the state tool.

Hello Nathanr,

Here are what I get when I call the commands STATE and PYTHON.

The file config.yaml is empty.

image001.jpg