✅ Deploy Preview for nextflow-docs-staging ready!

Name	Link
🔨 Latest commit	e28ef7f
🔍 Latest deploy log	https://app.netlify.com/projects/nextflow-docs-staging/deploys/69af2e622c5a1e00087c29ea
😎 Deploy Preview	https://deploy-preview-6679--nextflow-docs-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

This PR does not make any changes to operators, so you need some extra logic in some cases to pass records through an operator.

For example, given two record channels that you want to join:

samples_ch = fastqc_ch.join(quant_ch, by: 'id')

The above syntax is what we'd like to do, but join doesn't work with records yet, so you have to wrap the records as tuples before the join and unwrap after the join:

samples_ch = fastqc_ch.map { r -> tuple(r.id, r) }
    .join( quant_ch.map { r -> tuple(r.id, r) } )
    .map { id, r1, r2 -> r1 + r2 }

Does this change the hashing irrespective the use of record types? if so could be confined only when the feature is enabled?

The hashing change was to hash maps by their keys and values instead of only their values

It made more sense to apply this change for all records and maps because it fixes a bug (#4916) where e.g. a meta-map key would be renamed but the task wouldn't re-execute

Considering the impact breaking the cache in production deployment it may be worth considering making this configurable. Default should use the new version, however it could be possible to back to the previous caching. it should be fairly simple to have a caching strategy as a singleton in the session or process level.

I'm not sure that anyone is asking for that, but if we were to do anything about it, I would do something like #6353 where we add an environment variable to the STABLE/26.04.x branch after it is released, so that it doesn't clutter the codebase going forward