CSV exporter might fail if the CID used by the temporary storage surpasses the max DB length for the name

[DiegoPino]

What?

Unheard of before. But I should have known better bc I saw something (and fixed) similar while building the LoD reconciliation service.

During an CSV export, to keep the order of children/parents in place we generate a Batch that uses temporary storage. Temporary storage requires a unique ID per item, and that one (to avoid overlaps while multiple users export at the same time or a single user does the same) is generated using a combination of the Views, the Display ID, etc

See:

ami/src/Plugin/Action/AmiStrawberryfieldCSVexport.php

Lines 553 to 555 in 9283bf0

	$this->context['sandbox']['cid_prefix'] = $this->context['view_id'] . ':'
	. $this->context['display_id'] . ':' . $this->context['action_id'] . ':'
	. md5(serialize(array_keys($this->context['list']))) . ':';

This name, when the Views Machine name + the Display name are very long (happened to me, I promise) will fail badly at the DB level!
(gosh drupal) giving you a truly scary exception 👻

Solution is to reduce the whole thing to an md5() and done.

[DiegoPino]

Solved via cdf77a6 but I will have to go the long and pailful road of making an issue/pull at drupal for this one
https://git.drupalcode.org/project/views_bulk_operations/-/blob/4.2.x/src/ViewsBulkOperationsBatch.php#L76