Back to CLN v23.11.2 but enable anchor, batching tests fix

cyphernodeconf_docker/templates/lightning/c-lightning/config

@@ -56,3 +56,5 @@ announce-addr=<%= locals.lightning_external_ip %>:9735
 <% } %>
 <% } %>
 <% } %>
+
+experimental-anchors

dist/setup.sh

@@ -928,7 +928,7 @@ OTSCLIENT_VERSION="v0.9.0-rc.3"
 PYCOIN_VERSION="v0.9.0-rc.3"
 CYPHERAPPS_VERSION="releases/v0.9.0"
 BITCOIN_VERSION="v24.0.1-mosquitto-debian"
-LIGHTNING_VERSION="v24.02.2"
+LIGHTNING_VERSION="v23.11.2"
 TRAEFIK_VERSION="v2.6.3"
 MOSQUITTO_VERSION="1.6-openssl"
 POSTGRES_VERSION="14.0-bullseye"

proxy_docker/app/tests/test-batching.sh

@@ -196,6 +196,12 @@ testbatching() {
   fi
   trace 2 "\n\n[testbatching] ${BCyan}Tested batchspend.${Color_Off}\n"
 
+  # The batchspend should have triggered the safety net mechanism of flagging the recipient's txid as DEFECT-
+  # When this happens, a manual intervention is needed to make sure the payment has not been broadcast to avoid double-payments.
+  # In this case, an output amount was too large so we know the payment has not been done.  Let's just remove the DEFECT- flag.
+  trace 2 "\n\n[testbatching] ${BCyan}Cleaning up the failed batchspend...${Color_Off}\n"
+  docker exec -it $(docker ps -q -f "name=proxy\.") psql -U cyphernode -h postgres -c "UPDATE recipient SET tx_id = NULL WHERE id IN (${id}, ${id2}); DELETE FROM tx WHERE id = (SELECT tx_id FROM recipient WHERE id = ${id});"
+
   # getbatchdetails the default batcher
   trace 2 "\n\n[testbatching] ${BCyan}Testing getbatchdetails...${Color_Off}\n"
   response=$(exec_in_test_container curl -sd '{}' proxy:8888/getbatchdetails)