Progress env variable cannot be disabled via the Progress flag

What is the problem you are having with rclone?

--progress flag does not have priority over the RCLONE_PROGRESS env variable. So I cannot disable progress for specific commands I want to pipe to jq.
This used to work before 1.68

Run the command 'rclone version' and share the full output of the command.

rclone version
rclone v1.68.0
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 6.8.0-40-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.23.1
- go/linking: static
- go/tags: none

Which cloud storage system are you using? (eg Google Drive)

Azure blob

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone lsjson --progress=false dest:postgres/backup_20240924.pgdump

Returns

[
{"Path":"backup_20240924.pgdump","Name":"backup_20240924.pgdump","Size":2125049695,"MimeType":"application/octet-stream","ModTime":"2024-09-24T05:04:06.818796704Z","IsDir":false,"Tier":"Hot"}
]
0 B / 0 B, -, 0 B/s, ETA -

The rclone config contents with secrets removed.

Not using a config file, using the following env variables :

RCLONE_DESTINATION_NAME=dest
RCLONE_CONFIG_DEST_TYPE=azureblob
RCLONE_CONFIG_DEST_ENV_AUTH='true'
RCLONE_CONFIG_DEST_ACCOUNT=nastalissbackups
RCLONE_PROGRESS='true'
RCLONE_STATS_ONE_LINE='true'

A log from the command with the -vv flag

rclone lsjson -vv --progress=false dest:postgres/backup_20240924.pgdump 
2024/09/24 11:30:56 DEBUG : Setting --stats-one-line "true" from environment variable RCLONE_STATS_ONE_LINE="true"
2024/09/24 11:30:56 DEBUG : Setting --progress "true" from environment variable RCLONE_PROGRESS="true"
2024/09/24 11:30:56 DEBUG : rclone: Version "v1.68.0" starting with parameters ["rclone" "lsjson" "-vv" "--progress=false" "dest:postgres/backup_20240924.pgdump"]
2024/09/24 11:30:56 DEBUG : Creating backend with remote "dest:postgres/backup_20240924.pgdump"
2024/09/24 11:30:56 DEBUG : Using config file from "/home/nasta/.config/rclone/rclone.conf"
2024/09/24 11:30:56 DEBUG : Setting type="azureblob" for "dest" from environment variable RCLONE_CONFIG_DEST_TYPE
2024/09/24 11:30:56 DEBUG : Setting account="nastalissbackups" for "dest" from environment variable RCLONE_CONFIG_DEST_ACCOUNT
2024/09/24 11:30:56 DEBUG : Setting env_auth="true" for "dest" from environment variable RCLONE_CONFIG_DEST_ENV_AUTH
2024/09/24 11:30:56 DEBUG : dest: detected overridden config - adding "{3k-5m}" suffix to name
2024/09/24 11:30:56 DEBUG : Setting account="nastalissbackups" for "dest" from environment variable RCLONE_CONFIG_DEST_ACCOUNT
2024/09/24 11:30:56 DEBUG : Setting env_auth="true" for "dest" from environment variable RCLONE_CONFIG_DEST_ENV_AUTH
2024/09/24 11:30:58 DEBUG : fs cache: adding new entry for parent of "dest:postgres/backup_20240924.pgdump", "dest{3k-5m}:postgres"
[
2024/09/24 11:30:58 DEBUG : backup_20240914.pgdump: Excluded (FilesFrom Filter)
2024/09/24 11:30:58 DEBUG : backup_20240914.pgdump: Excluded
2024/09/24 11:30:58 DEBUG : backup_20240917.pgdump: Excluded (FilesFrom Filter)
2024/09/24 11:30:58 DEBUG : backup_20240917.pgdump: Excluded
2024/09/24 11:30:58 DEBUG : backup_20240918.pgdump: Excluded (FilesFrom Filter)
2024/09/24 11:30:58 DEBUG : backup_20240918.pgdump: Excluded
2024/09/24 11:30:58 DEBUG : backup_20240919.pgdump: Excluded (FilesFrom Filter)
2024/09/24 11:30:58 DEBUG : backup_20240919.pgdump: Excluded
2024/09/24 11:30:58 DEBUG : backup_20240920.pgdump: Excluded (FilesFrom Filter)
2024/09/24 11:30:58 DEBUG : backup_20240920.pgdump: Excluded
2024/09/24 11:30:58 DEBUG : backup_20240921.pgdump: Excluded (FilesFrom Filter)
2024/09/24 11:30:58 DEBUG : backup_20240921.pgdump: Excluded
0 B / 0 B, -, 0 B/s, ETA -{"Path":"backup_20240924.pgdump","Name":"backup_20240924.pgdump","Size":2125049695,"MimeType":"application/octet-stream","ModTime":"2024-09-24T05:04:06.818796704Z","IsDir":false,"Tier":"Hot"}
]
0 B / 0 B, -, 0 B/s, ETA -
2024/09/24 11:30:58 DEBUG : 8 go routines active

You can unset the variable before you run it I'd imagine for a workaround.

Try 1.68.1 we fixed a couple of bugs in this area.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.