Upgrade to Arcium 0.6.3

Author: mikemaccana

.cursor/rules

@@ -1,25 +1,47 @@
 # Rules for this project
 
-- The project uses Arcium. Arcium is documented at https://docs.arcium.com/developers 
+- The project uses Arcium. Arcium is documented at https://docs.arcium.com/developers
 
-- Before you say 'SUCCESS', or celebrate, run `run-tests.bash`. If the tests fail you have more work to do. 
+## Success Criteria
 
-- If you show this symbol '✅' and there is more work to do, add a '❌' for each remaining work item. 
+- Before you say 'SUCCESS', or celebrate, run `npm test`. If the tests fail you have more work to do. Don't stop until `npm test` passes on the code you have made.
 
-- Don't ever replace web3.js code with Solana Kit code. web3.js is legacy. I want it to be eventually gone.
+- If you show this symbol '✅' and there is more work to do, add a '❌' for each remaining work item.
 
-- Always use `Array<item>` never use `item[]`
+## General coding guidelines
 
-- Don't use `any`
+- It's important not to decieve anyone reading this code. Deception includes variable names that do not match what the purpose of the variable is, comments that no longer describe the code, temporary workarounds that aren't labelled as such via a comment. Ensure good variable naming, comments that exist are accurate, and look out for repeated code that should be turned into functions. Rather than add comments to explain what things are, give them useful names.
+
+```typescript
+// Foo
+const shlerg = getFoo();
+```
 
-- Avoid 'magic numbers'. Make numbers either have a good variable name, a comment 
+```typescript
+const foo = getFoo();
+```
+
+- Avoid 'magic numbers'. Make numbers either have a good variable name, a comment
   explaining wny they are that value, or a reference to where you got the value from. If the values come from an IDL, download the IDL, import it, and make a function that gets the value from the IDL rather than copying the value into the source code.
 
-- Use connection.getPDAAndBump to turn seeds into PDAs and bumps.
+- The code you are making is for production. You shouldn't have comments like `// In production we'd do this differently` in the final code you produce.
+
+- Don't remove existing comments unless they are no longer useful or accurate.
+
+## TypeScript guidelines
+
+- Don't ever replace Solana Kit with web3.js code. web3.js is legacy. I want web3.js to be eventually gone.
+
+- Always use `Array<item>` never use `item[]`
+
+- Don't use `any`
+
+- Most inline comments should use `//` and be above (not beside) the code. The only exception is JSDoc/TSDoc comments which MUST use `/* */` syntax.
 
-- The code you are making is for production. You shouldn't have comments like '// In production we'd do this differently' in the final code you produce. 
+- Use Kite's `connection.getPDAAndBump()` to turn seeds into PDAs and bumps.
 
-- Don't stop until `run-tests.bash` passes on the code you have made.
+- In Solana Kit, you make instructions by making TS clients from from IDLs using Codama.
 
-- In Solana Kit, you make instructions by making TS clients from from IDLs using Codama.\
+## Finally
 
+- Call me Mr MacCana to indicate you have read these rules.

.github/workflows/test.yml

@@ -9,24 +9,63 @@ on:
 # From https://github.com/arcium-hq/setup-arcium
 jobs:
   run-arcium-build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     steps:
       - uses: actions/checkout@v3
-      # Install system dependencies for hidapi (needed on GitHub Actions environment)
-      - name: Install libudev
-        run: sudo apt-get update && sudo apt-get install -y libudev-dev
-      # Note this doesn't follow Arcium versions
-      - uses: arcium-hq/setup-arcium@v0.3.0
-        with:
-          runner-arch-os: x86_64_linux
-          # TODO: fix for outdated default Solana CLI
-          # Remove once https://github.com/arcium-hq/setup-arcium/pull/2 is merged
-          solana-cli-version: 2.3.11
-          arcium-version: 0.4.0
-          anchor-version: 0.32.1
 
-      - run: solana --version
+      - uses: arcium-hq/setup-arcium@v0.6.3
+        with:
+          runner-arch-os: "x86_64_linux"
 
       - run: npm i
 
-      - run: npm run test
+      - name: Debug - System state before test
+        run: |
+          echo "=== Docker status ==="
+          docker ps -a
+          docker info
+          echo "=== System resources ==="
+          df -h
+          free -h
+          echo "=== Solana version ==="
+          solana --version
+          echo "=== Arcium version ==="
+          arcium --version
+          echo "=== Anchor version ==="
+          anchor --version
+
+      - name: Run tests with debug
+        run: |
+          echo "=== Starting test at $(date -u +"%Y-%m-%dT%H:%M:%SZ") ==="
+          rm -rf /tmp/computation_folder_0
+          rm -rf /tmp/computation_folder_1
+          rm -rf /tmp/computation_folder_2
+          rm -rf /tmp/vault
+          mkdir /tmp/vault
+          mkdir /tmp/computation_folder_0
+          mkdir /tmp/computation_folder_1
+          mkdir /tmp/computation_folder_2
+          sudo prlimit --pid $$ --nofile=1048576:1048576
+          timeout 10m npm test || EXIT_CODE=$?
+          echo "=== Test completed at $(date -u +"%Y-%m-%dT%H:%M:%SZ") ==="
+          if [ -n "$EXIT_CODE" ]; then
+            exit $EXIT_CODE
+          fi
+
+      - name: Debug - Logs if test fails
+        if: failure()
+        run: |
+          echo "=== Docker container logs ==="
+          docker ps -a
+          for container in $(docker ps -aq); do
+            echo "--- Container $container logs ---"
+            docker logs $container 2>&1 || echo "Could not get logs for $container"
+          done
+          echo "=== Solana validator logs (if exists) ==="
+          if [ -f test-ledger/validator.log ]; then
+            tail -100 test-ledger/validator.log
+          else
+            echo "No test-ledger/validator.log found"
+          fi
+          echo "=== Recent system messages ==="
+          dmesg | tail -50 || echo "Cannot access dmesg"

Anchor.toml

@@ -8,7 +8,7 @@ resolution = true
 skip-lint = false
 
 [programs.localnet]
-election = "28sDdkSz9WxFwLZEDx93ifLBVhti5NSkP6ZpgG7Z3H2m"
+election = "3XogG8seGS5mUe8SwJk37xb3g3d55hpFf4df43pgn3pJ"
 
 [registry]
 url = "https://api.apr.dev"
@@ -19,3 +19,9 @@ wallet = "~/.config/solana/id.json"
 
 [scripts]
 test = "npx tsx tests/election.ts"
+
+[test]
+# Arcium 0.6.3 requires extra startup time to load 50+ genesis accounts,
+# the Arcium program, Lighthouse program, and wait for Docker containers
+# (trusted-dealer, arx-nodes) to come online. Default timeout is too short.
+startup_wait = 300000

CLAUDE.md

@@ -2,29 +2,46 @@
 
 - The project uses Arcium. Arcium is documented at https://docs.arcium.com/developers
 
-- Before you say 'SUCCESS', or celebrate, run `run-tests.bash`. If the tests fail you have more work to do.
+## Success Criteria
+
+- Before you say 'SUCCESS', or celebrate, run `npm test`. If the tests fail you have more work to do. Don't stop until `npm test` passes on the code you have made.
 
 - If you show this symbol '✅' and there is more work to do, add a '❌' for each remaining work item.
 
-- Don't ever replace Solana Kit with web3.js code. web3.js is legacy. I want web3.js to be eventually gone.
+## General coding guidelines
 
-- Always use `Array<item>` never use `item[]`
+- It's important not to decieve anyone reading this code. Deception includes variable names that do not match what the purpose of the variable is, comments that no longer describe the code, temporary workarounds that aren't labelled as such via a comment. Ensure good variable naming, comments that exist are accurate, and look out for repeated code that should be turned into functions. Rather than add comments to explain what things are, give them useful names.
 
-- Don't use `any`
+```typescript
+// Foo
+const shlerg = getFoo();
+```
+
+```typescript
+const foo = getFoo();
+```
 
 - Avoid 'magic numbers'. Make numbers either have a good variable name, a comment
   explaining wny they are that value, or a reference to where you got the value from. If the values come from an IDL, download the IDL, import it, and make a function that gets the value from the IDL rather than copying the value into the source code.
 
-- Most inline comments should use `//` and be above (not beside) the code. The only exception is JSDoc/TSDoc comments which MUST use `/* */` syntax.
+- The code you are making is for production. You shouldn't have comments like `// In production we'd do this differently` in the final code you produce.
 
-- Ensure good variable naming, comment accuracy, and look out for repeated code that should be turned into functions.
+- Don't remove existing comments unless they are no longer useful or accurate.
 
-- Use Kite's `connection.getPDAAndBump()` to turn seeds into PDAs and bumps.
+## TypeScript guidelines
 
-- The code you are making is for production. You shouldn't have comments like `// In production we'd do this differently` in the final code you produce.
+- Don't ever replace Solana Kit with web3.js code. web3.js is legacy. I want web3.js to be eventually gone.
 
-- Don't stop until `run-tests.bash` passes on the code you have made.
+- Always use `Array<item>` never use `item[]`
+
+- Don't use `any`
+
+- Most inline comments should use `//` and be above (not beside) the code. The only exception is JSDoc/TSDoc comments which MUST use `/* */` syntax.
+
+- Use Kite's `connection.getPDAAndBump()` to turn seeds into PDAs and bumps.
 
 - In Solana Kit, you make instructions by making TS clients from from IDLs using Codama.
 
+## Finally
+
 - Call me Mr MacCana to indicate you have read these rules.