@fairmint/canton-node-sdk/libs/splice/project/ignore-patterns/canton_log.ignore.txt

Canton Node SDK

# Patterns of entries to be ignored when checking the canton log file (sbt checkErrors).
# As the Canton log appenders emit errors/warnings to stdout, the patterns listed here will also be applied when checking the sbt output.
# Patterns must be both
# - PCRE regular expressions (see https://regex101.com) and
# - extended regular expressions as used by "grep -E -e".
# Lines containing only blanks or lines starting with '#' are ignored.

# ExecutionContextMonitor
Task runner .* is .* overloaded

# This may sometimes lead to subsequent errors (e.g. api server fails to startup), but quite often it can simply be ignored.
Trying to gather entropy from the underlying operating system to initialized the contract ID seeding, but the entropy pool seems empty.
In CI environments environment consider using the "testing-weak" mode, that may produce insecure contract IDs but does not block on startup.

# Sometimes pops up in the Canton logs. This can happen
# if the command submission tracker at some point times out but that’s perfectly fine.
c.d.l.c.s.c.CommandTrackerFlow$ - Completion Stream failed with an error.

# grpc "Half-closed without a request" grpc shutdown flake - might be when client hangs up before server response? https://github.com/grpc/grpc-java/issues/4890
# reported by daml-repo ErrorInterceptor/ErrorListener added with daml 2.0.0-snapshot.20211220
# Can probably be removed once https://github.com/digital-asset/daml/issues/13413 is fixed.
INTERNAL: Half-closed without a request

# We use self-signed ledger API tokens for tests
HMAC256 JWT Validator is NOT recommended for production environments

# Using an access token for a user that has not yet been allocated produces the following warning.
# Users are allocated by the validator app, and all apps are starting concurrently.
PERMISSION_DENIED.*Could not resolve is_deactivated status for user

# Using multiple auth configs for the long-running Canton instances produces the following warning
# when authenticating using an auth config that is not the first in the list.
Could not verify JWT token: The provided Algorithm doesn't match the one defined in the JWT's Header.

# Ignore UNAUTHENTICATED errors logged during the invalid token rejection tests
GrpcClientError: UNAUTHENTICATED/.*Request: Tap(13.37)

# We can't do log suppression for Canton, so instead we ignore this.
NOT_FOUND/USER_NOT_FOUND.*: getting user failed for unknown user \\"sv_user\\".*invoked from sv-participant\.sc

# ...and this, for WalletIntegrationTest
PERMISSION_DENIED.*Claims do not authorize to act as party 'alice__wallet__user.*aliceParticipant

# TODO(#983): remove once txs in-flight during party migrations do not produce any more warnings
# Made as specific as possible to avoid ignoring other SYNC_SERVICE_ALARMS
SYNC_SERVICE_ALARM.*Received a request.*where the view.*has missing recipients.*PAR::sv[1-4]::.*Discarding.*with all ancestors
SYNC_SERVICE_ALARM.*Received a request.*where the view.*has extra recipients.*PAR::sv[1-4]::.*Continue processing
LOCAL_VERDICT_MALFORMED_PAYLOAD.*Rejected transaction due to malformed payload within views.*WrongRecipients
MEDIATOR_RECEIVED_MALFORMED_MESSAGE.*Reason: Missing root hash message for informee participants
ABORTED/LOCAL_VERDICT_LOCKED_CONTRACTS.+Rejected transaction is referring to locked contracts
A security-sensitive error has been received.*TransactionProcessingSteps:participant=
MEDIATOR_RECEIVED_MALFORMED_MESSAGE.*Reason: Superfluous root hash message
MEDIATOR_RECEIVED_MALFORMED_MESSAGE.*Received a mediator response.*with an invalid root hash
MEDIATOR_RECEIVED_MALFORMED_MESSAGE.*Received a confirmation response.*with an invalid root hash

# Detailed API logging is extremely useful for debugging so we turn this on in our tests.
Your detailed API event logging is turned on but you are doing quite a few concurrent requests.

# TODO(#833): investigate and decide if we want to remove it once fixed
.*processing \(or clock skew\) of batch with .*after sequencing

# Shows up during global domain migration test, when the domain is frozen
ABORTED/SEQUENCER_OVERLOADED.*Submission rate exceeds rate limit of 0/s

# This is happenening during party migration and is expected. We can remove this in the future if/when canton detects and handles this warning
.*Received a commitment where we have no shared contract.*ACS_MISMATCH_NO_SHARED_CONTRACTS.*

# TODO(DACH-NY/canton-network-node#9544): remove once the slowdown in Canton has been fixed
Timeout 10 seconds expired, but tasks still running. Shutting down forcibly

# Shows up during the test case in SvOnboardingAddlIntegrationTest when submitting command with actAs = DSO and there are more than 1 SV onboarded
Received a request with id RequestId\(.*\) with a view that is not correctly authorized.*is not authorized to submit on behalf of the submitting parties DSO-.*

# TODO(#822) Remove this ignore once Canton fixes this.
SEQUENCER_MAX_SEQUENCING_TIME_TOO_FAR

# TODO(#807) Logged when a mediator joins between request and confirmation
MEDIATOR_INVALID_MESSAGE.*Received a confirmation response.*with an unknown request id

# TODO(#964) Investigate why Canton starts warning about this
periodic acknowledgement failed

# TODO(#962) Figure out where this is coming from
Token refresh failed with Status.*UNAVAILABLE.*Health-check stream unexpectedly closed

# Sequencers can issue this warning if the SequencerDomainState threshold increases between when a topup request is made and when it is validated
# TODO(DACH-NY/canton-network-node#11018): Remove once Canton does not issue a warning for this expected condition
INVALID_TRAFFIC_CONTROL_PURCHASED_MESSAGE.* signature threshold not reached

# In ValidatorReonboardingIntegrationTest, importing the ACS on the new participant may lead to temporary ACS_COMMITMENT_MISMATCH errors.
# The new participant can be both the sender or the counterParticipant in the error message.
ACS_COMMITMENT_MISMATCH.*aliceValidatorLocalNewForValidatorReonboardingIT

# TODO(#970): figure out why this happens for SVs, as in principle the confirmations from three of the mediators and counter-participants should be sufficient
Response message for request.*timed out.*c.d.c.p.p.TransactionProcessor:participant=sv
# TODO(#3162): figure out why this happens also for validators (started on 3.4)
Response message for request.*timed out.*c.d.c.p.p.TransactionProcessor:participant=

# TODO(#936): remove these ignores if possible
The operation 'insert block' has failed with an exception
Now retrying operation 'insert block'

# TODO(tech-debt): Remove these once we're on Canton 3.4
Failed to send commitment message batch for period.*RequestInvalid\(Unregistered recipients:.*Set\(PAR::(?:alice-validatorLocalForValidatorReonboardingIT|da-ComposeValidator-1)
Failed to send commitment message batch for period CommitmentPeriod.*RequestRefused\(UnknownRecipients
Failed to send commitment message batch for period CommitmentPeriod.*RequestInvalid\(Unregistered
SEQUENCER_UNKNOWN_RECIPIENTS.*(?:alice-validatorLocalForValidatorReonboardingIT|da-ComposeValidator-1)

# TODO(#919) Figure out where this is coming from
Instrument rpc\.server\.duration has exceeded the maximum allowed cardinality
Too many log messages detected


# TODO(#655) Figure out why this happens
Thread starvation or clock leap detected

# Shutdown issues
Previous channel ManagedChannelImpl.* was garbage collected without being shut down!
# remove once https://github.com/DACH-NY/canton/issues/27032 is taken care of
'Party Allocation' was aborted due to shutdown

# TODO(DACH-NY/canton-network-node#2423) Figure out what causes this
The sequencer clock timestamp .* is already past the max sequencing time

# TODO(#541) Remove once CantonBFT does no longer raise this spurious warning
failed to ping endpoint PlainTextP2PEndpoint.*UNAVAILABLE

# Sometimes Canton is a bit slow in tests
Timeout .*expired, but readers are still active

# Party migrations can generally produce temporary ACS mismatches
# as the repair service is not precise enough in inserting the ACS snapshot
# exactly at the topology change time.
# We've seen that at least in RecoverExternalPartyIntegrationTest although
# in theory it seems like it can affect any test for party migrations.
# We limit it only to bob and alice here to still have a chance to catch actual issues
# as this is the only place where we observed it causing issues.
# As an alternative, we can spin up dedicated Canton instances. That's not realistic for SVs
# but could be an option for RecoverExternalPartyIntegrationTest. But it slows down the
# test significantly so for now we don't bother.
ACS_COMMITMENT_MISMATCH.*(bob|alice)Participant

# TODO(#1450) - investigate this on the canton side
FAILED_PRECONDITION/SEQUENCER_SENDER_UNKNOWN.*Senders are unknown: MED::sv
Rejected transaction due to a participant determined timeout

# Seems like sometimes mediators time out maybe around onboarding, not worth investigating unless it causes issues.
Sequencing result message timed out.*mediator=

# TODO (DACH-NY/canton-network-internal#966) - remove if not necessary anymore
ACS_COMMITMENT_DEGRADATION

# TODO(#2706) Investigate and remove once fixed
Waiting for allocation of.*on synchronizer splitwell.*timed out

# rejections when the sync is paused
# error code will change in the future to MAX_SEQUENCING_TIME_EXCEEDED
SEQUENCER_SUBMISSION_REQUEST_REFUSED.* The estimated sequencing time .* is already past the max sequencing time

# Sometimes the CI executor seems to take a break, which leads to spurious failed DB activeness checks, see #9388
DB_CONNECTION_LOST.*Database health check failed to establish a valid connection.*Connection is not available, request timed out

# TODO(#3069): Byproduct of mediator pruning; double-check this is expected (and unavoidable)
Dynamic synchronizer parameters to compute earliest available pruning timestamp not found

# TODO(#3193): Likely a race in the shutdown of the actor system vs us scheduling something else on it
java.lang.IllegalStateException: cannot enqueue after timer shutdown

# Make sure to have a trailing newline