[BUG] pyarmor obfuscation on CI flaky

[Justin-Regef]

We've encountered errors trying to obfuscate our code on CI machines. Here's a snippet of the logs:

Successfully installed pyarmor-8.2.9 pyarmor.cli.core-3.2.9
INFO     Python 3.11.11
INFO     Pyarmor 8.2.9 (trial), 000000, non-profits
INFO     Platform linux.x86_64
INFO     register "./pyarmor-regfile-5180.zip"
INFO     update license token
ERROR    request license token faild (3)
Error: Process completed with exit code 2.

And the Github action:

        -   name: Install Pyarmor, encode pyarmor rkey and save to output
            id: generate_pyarmor_key
            run: |
                pip install "pyarmor<8.3.0,>=8.2.9"
                mkdir -p ${GITHUB_WORKSPACE}/pyarmor_dir
                base64 -d <<< ${{ inputs.pyarmor_license }} > ./pyarmor-regfile-5180.zip
                pyarmor-8 -d register ./pyarmor-regfile-5180.zip
                pyarmor-8 gen key -O . -e $EXPIRATION_DATE --bind-data "{\"product\": \"${{ inputs.algo_name }}\", \"version\": \"${{ inputs.algo_version }}\", \"tls\": {\"enabled\": false}}" 

                PYARMOR_KEY_B64=$(cat ./pyarmor.rkey | base64 -w 0)
                echo "pyarmor_key_b64=$(echo $PYARMOR_KEY_B64)" >> $GITHUB_OUTPUT
                echo $PYARMOR_KEY_B64
            shell: bash

This used to work fine, but it suddenly became flaky, with this error occurring more often than not.
Thinking it was due to rate limits, we stopped builds for over 48 hours, but the problem persists nevertheless. I've independently tried the same licence on my local computer and it worked, it also still works on the CI machine once every few times (20%).
Are we being rate-limited? Or is there something else going on?

[jondy]

You're using CI license in wrong way. Please upgrade Pyarmor to 9.0+, and check the usage, refer to
https://eke.dashingsoft.com/pyarmor/ask/