fix: nargo fmt

[LHerskind]

Ran nargo fmt.

[LHerskind]

• feat: add ciphertext computation for log header #6175
• fix: nargo fmt #6169 👈
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @LHerskind and the rest of your teammates on Graphite

[TomAFrench]

btw, we have nargo fmt --check which works as a CI check for this. You could add an earthly target for this to enforce this going forwards.

[LHerskind]

btw, we have nargo fmt --check which works as a CI check for this. You could add an earthly target for this to enforce this going forwards.

While we got you here @TomAFrench.
Running nargo fmt can cause a failure in tests where we are expecting certain error messages as it changes due to the formatting. Example:

[TomAFrench]

This looks like more of an artifact of aztec's own simulator's error logic to me.

aztec-packages/yarn-project/circuit-types/src/simulation_error.ts

Lines 104 to 109 in fbd78fd

	getMessage() {
	if (this.noirErrorStack && !isNoirCallStackUnresolved(this.noirErrorStack) && this.noirErrorStack.length) {
	return `${this.originalMessage} '${this.noirErrorStack[this.noirErrorStack.length - 1].locationText}'`;
	}
	return this.originalMessage;
	}

[benesjan]

Closed in favor of #6184 as @LHerskind absolutely refuses to let this one in 😆