Skip to content

bug: Failed assertion in public fn leads to "Note encrypted logs hash mismatch" #6651

Closed
@spalladino

Description

@spalladino

Test e2e_fees dapp_subscription › should reject after the sub runs out is failing with the following error:

"Note encrypted logs hash mismatch. Expected 0x0000000000000000000000000000000000000000000000000000000000000000, got 0x00d1b0898e6708686591b351231001662892c6ac3982c647a12cda9e31f33f75.
                 Processed: {\"functionLogs\":[]}"

However, it's expected for it to fail with a failed assertion:

Failed to solve brillig function '(context.block_number()) as u64 < expiry_block_number as u64

The mismatch is triggered because the logs being emitted by the kernel and by the public processor don't match. Given there was a revert, it seems that the kernel was smart enough to not emit the logs, but the public processor wasn't.

Metadata

Metadata

Assignees

No one assigned

    Labels

    T-bugType: Bug. Something is broken.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions