Sanity-check - I’m pretty sure I’ve ~recently (last 6 months) managed to get rose file install checksums being exercised and behaving as I expect when I do a rose file install using them (i.e. convinced myself that if I specify checksum to be non-empty, then the file install fails if the checksum value is invalid - and only passes if the checksum value is correct).
But I:
- can’t get this to work now (it’s not catching a changed file hash in my target workflow)
- can’t spot what I’m (likely!) doing wrong in a minimum working example to reproduce issue below
- don’t have any clear evidence in my version control of this successfully exercising - only that I updated values. Relevant cylc logs long gone
- spot any likely contenders which might have changed things here in timeframe since I ~recall having this working in rose/CHANGES.md at master · metomi/rose · GitHub
Can I check if the MWE below is:
- using the rose file install checksum as expected?
- missing anything it needs to get this to work (i.e. catch stale checksum values)?
Thanks!
MWE
Unexpected behaviour
- I’m almost sure that in recent past (last 6 months), specifying the checksums like I have in most of the file installs would result in the behaviour in bullet below (and comments in rose-app.conf)
- But now the checksum value seems to be being completely ignored:
- an empty checksum value doesn’t lead to checksum being reported
- a correct checksum value doesn’t lead to output indicating the checksum value check has correctly passed
- a bad checksum value doesn’t result in loud failure
- i.e. same behaviour as if I’d not provided a checksum value at all
- Am I doing something wrong?
- Or is this no longer performing as expected?
Setup
Versions:
$ cylc --version
8.7.0
$ rose --version
rose 2.8.1
```
Workflow:
```console
$ tree -Fa --noreport .
.
├── app/
│ └── check_executable/
│ └── rose-app.conf
├── bin/
│ └── fake_executable
└── flow.cylc
```
flow.cylc:
```console
$ cat flow.cylc
[scheduling]
[[graph]]
R1 = check_executable
[runtime]
[[root]]
platform = localhost
script = rose task-run --verbose
[[check_executable]]
[[[meta]]]
title = Check checksum behaviour
description = Is file install checksum no longer getting checked?!
url = https://metomi.github.io/rose/doc/html/api/configuration/file-creation.html#rose:conf:*[file:TARGET]checksum
```
app:
```console
$ cat app/check_executable/rose-app.conf
[command]
default=echo "Checking file install checksum behaviour?"
[env]
exe_no_checksum=${CYLC_TASK_SHARE_CYCLE_DIR}/exe_no_checksum
exe_empty_checksum=${CYLC_TASK_SHARE_CYCLE_DIR}/exe_empty_checksum
exe_actual_checksum=${CYLC_TASK_SHARE_CYCLE_DIR}/exe_actual_checksum
exe_bad_checksum=${CYLC_TASK_SHARE_CYCLE_DIR}/exe_bad_checksum
src=${CYLC_WORKFLOW_RUN_DIR}/bin/fake_executable
[file:${exe_no_checksum}]
# No checksum provided: don't expect checksum to be reported / checked
source=${src}
[file:${exe_empty_checksum}]
# Empty checksum: as rose task-run is verbose, expect actual checksum value to be reported, but not checked
checksum=
source=${src}
[file:${exe_actual_checksum}]
# Correct checksum: expect checksum value to be checked, reported, file install to succeed
checksum=eb9c2bf0eb63f3a7bc0ea37ef18aeba5
source=${src}
[file:${exe_bad_checksum}]
# Bad checksum: expect the file install to fail noisily, with error message fingering checksum
checksum=whoops_bad_checksum_maybe_stale
source=${src}
```
```console
$ cat bin/fake_executable
some content
$ md5sum bin/fake_executable
eb9c2bf0eb63f3a7bc0ea37ef18aeba5 bin/fake_executable
```
### Output
Workflow validates, installs, and plays happily to completion - would have expected the final file install to have caused a failure due to incorrect checksum
```console
$ workflow_dir=$(pwd)
$ workflow_name=$(basename $workflow_dir)
$ cylc vip ${workflow_dir:-NO_wd} --workflow-name=${workflow_name:-NO_wn} # snip
$ cat ~/cylc-run/${workflow_name:-NO_wn}/runN/log/scheduler/01-start-01.log
2026-10-27T10:47:57Z INFO - Workflow: rose_file_checksum/run1
2026-10-27T10:47:57Z INFO - Scheduler: url=redacted
2026-10-27T10:47:57Z INFO - Workflow publisher: url=redacted
2026-10-27T10:47:57Z INFO - Run: (re)start number=1, log rollover=1
2026-10-27T10:47:57Z INFO - Cylc version: 8.7.0
2026-10-27T10:47:57Z INFO - Run mode: live
2026-10-27T10:47:57Z INFO - Initial point: 1
2026-10-27T10:47:57Z INFO - Final point: 1
2026-10-27T10:47:57Z INFO - Cold start from 1
2026-10-27T10:47:57Z INFO - New flow: 1 (original flow from 1) 2026-10-27T10:47:57
2026-10-27T10:47:57Z INFO - [1/check_executable:waiting(runahead)] => waiting
2026-10-27T10:47:57Z INFO - [1/check_executable:waiting] => waiting(queued)
2026-10-27T10:47:57Z INFO - [1/check_executable:waiting(queued)] => waiting
2026-10-27T10:47:57Z INFO - [1/check_executable:waiting] => preparing
2026-10-27T10:47:59Z INFO - [1/check_executable/01:preparing] submitted to localhost:redacted
2026-10-27T10:47:59Z INFO - [1/check_executable/01:preparing] => submitted
2026-10-27T10:48:02Z INFO - [1/check_executable/01:submitted] => running
2026-10-27T10:48:03Z INFO - [1/check_executable/01:running] => succeeded
2026-10-27T10:48:04Z INFO - Workflow shutting down - AUTOMATIC
2026-10-27T10:48:04Z INFO - DONE
```
App doesn't give any indication of checksums being considered either - from memory, equivalent (?) usage elsewhere would have given checksum fingerprints around `[INFO] install` for the `exe_empty_checksum` and `exe_actual_checksum` install targets - and a loudly explicit failure message for `exe_bad_checksum` target.
```console
$ cat ~/cylc-run/${workflow_name:-NO_wn}/runN/log/job/1/check_executable/NN/job.out
Workflow : rose_file_checksum/run1
Job : 1/check_executable/01 (try 1)
User@Host: edmund@cylc_server_A
2026-10-27T10:48:01Z INFO - started
[INFO] create: ~/cylc-run/rose_file_checksum/run1/share/data
[INFO] export ROSE_CYCLING_MODE=integer
[INFO] export ROSE_DATA=~/cylc-run/rose_file_checksum/run1/share/data
[INFO] export ROSE_DATAC=~/cylc-run/rose_file_checksum/run1/share/cycle/1
[INFO] export ROSE_SUITE_DIR=~/cylc-run/rose_file_checksum/run1
[INFO] export ROSE_SUITE_DIR_REL=cylc-run/rose_file_checksum/run1
[INFO] export ROSE_SUITE_NAME=rose_file_checksum/run1
[INFO] export ROSE_TASK_CYCLE_TIME=1
[INFO] export ROSE_TASK_ID=1/check_executable
[INFO] export ROSE_TASK_IS_COLD_START=true
[INFO] export ROSE_TASK_LOG_DIR=~/cylc-run/rose_file_checksum/run1/log/job/1/check_executable/01
[INFO] export ROSE_TASK_LOG_ROOT=~/cylc-run/rose_file_checksum/run1/log/job/1/check_executable/01/job
[INFO] export ROSE_TASK_NAME=check_executable
[INFO] export ROSE_TASK_PREFIX=check
[INFO] export ROSE_TASK_SUFFIX=executable
[INFO] Configuration: ~/cylc-run/rose_file_checksum/run1/app/check_executable/
[INFO] file: rose-app.conf
[INFO] export PATH=~/cylc-run/rose_file_checksum/run1/share/bin:~/cylc-run/rose_file_checksum/run1/bin:...
[INFO] export exe_actual_checksum=~/cylc-run/rose_file_checksum/run1/share/cycle/1/exe_actual_checksum
[INFO] export exe_bad_checksum=~/cylc-run/rose_file_checksum/run1/share/cycle/1/exe_bad_checksum
[INFO] export exe_empty_checksum=~/cylc-run/rose_file_checksum/run1/share/cycle/1/exe_empty_checksum
[INFO] export exe_no_checksum=~/cylc-run/rose_file_checksum/run1/share/cycle/1/exe_no_checksum
[INFO] export src=~/cylc-run/rose_file_checksum/run1/bin/fake_executable
[INFO] source: ~/cylc-run/rose_file_checksum/run1/bin/fake_executable
[INFO] install: ~/cylc-run/rose_file_checksum/run1/share/cycle/1/exe_bad_checksum
[INFO] source: ~/cylc-run/rose_file_checksum/run1/bin/fake_executable
[INFO] install: ~/cylc-run/rose_file_checksum/run1/share/cycle/1/exe_empty_checksum
[INFO] source: ~/cylc-run/rose_file_checksum/run1/bin/fake_executable
[INFO] install: ~/cylc-run/rose_file_checksum/run1/share/cycle/1/exe_actual_checksum
[INFO] source: ~/cylc-run/rose_file_checksum/run1/bin/fake_executable
[INFO] install: ~/cylc-run/rose_file_checksum/run1/share/cycle/1/exe_no_checksum
[INFO] source: ~/cylc-run/rose_file_checksum/run1/bin/fake_executable
[INFO] command: echo "Checking file install checksum behaviour?"
Checking file install checksum behaviour?
2026-10-27T10:48:02Z INFO - succeeded
```