Error while running for azure devops

[psipher]

Error when pushing code:
error: src refspec dev_remote_ea5Eu does not match any
error: failed to push some refs to
'https://dev.azure.com/*****/1b31f8ce-52b2-4921-a7db-1afe457da95c/_git/Tes
tDev_ea5Eu'

[hugo-syn]

Are you allowed to push code on this project ? What are the permissions bounded to your token ?

[dracorp]

Another error on ADO:

I always get [-] Error during pipeline run: string index out of range.

For -d option:

[D] Running pipeline: 1514
[*] Getting pipeline output
[!] Pipeline still running, sleeping for 15s
[!] Pipeline still running, sleeping for 15s
[+] Pipeline has successfully terminated.
[D] Log ID of the extraction task: 7
[+] Output:
[-] Error during pipeline run: string index out of range
[-]  string index out of range
...
IndexError: string index out of range

Run on MacOS 14.2, Python 3.11

[hugo-syn]

Hi, do you have the exact location of the index out of range error in the stack trace please ? If you can provide the full stack trace (without any credential) that would be nice :)

[dracorp]

Here you go:
log.txt

[hugo-syn]

Thank you @dracorp, I found the bug but it's really weird. It seems that everything went well but that there is no data in the output of the pipeline. Can you tell me if you have data in the output of the different pipelines or if the files are empty or not present at all ? It should be located here:

nord-stream-logs/azure_devops/<org>/<projectid>/pipeline_<date>.log

[dracorp]

Yes, I have:

2023-12-27T11:45:54.1765613Z ##[section]Starting: Task fWQf8
2023-12-27T11:45:54.1770065Z ==============================================================================
2023-12-27T11:45:54.1770179Z Task         : Bash
2023-12-27T11:45:54.1770230Z Description  : Run a Bash script on macOS, Linux, or Windows
2023-12-27T11:45:54.1770451Z Version      : 3.231.5
2023-12-27T11:45:54.1770505Z Author       : Microsoft Corporation
2023-12-27T11:45:54.1770577Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash
2023-12-27T11:45:54.1770664Z ==============================================================================
2023-12-27T11:45:54.4893137Z Generating script.
2023-12-27T11:45:54.4901729Z Script contents:
2023-12-27T11:45:54.4902335Z env -0 | awk -v RS='\0' '/^secret_/ {print $0}' | base64 -w0 | base64 -w0 ; echo
2023-12-27T11:45:54.4907065Z ========================== Starting Command Output ===========================
2023-12-27T11:45:54.4916481Z [command]/usr/bin/bash /home/vsts/work/_temp/da992292-af81-4829-89a3-c8e6f9223093.sh
2023-12-27T11:45:54.5022054Z encoded_secrets
2023-12-27T11:45:54.5022504Z
2023-12-27T11:45:54.5100673Z ##[section]Finishing: Task fWQf8

The pipeline returns encoded_secrets which I've checked with base64 -d | base64 -d and they are correct.

[hugo-syn]

Thanks, that is really weird, I didn't manage to reproduce the bug, but I pushed a fix, tell me if it's better and if the display is correct.