📜 Description

Spurious failed to stitch errors as below. An entry already exists in the final_entities table for the entity ref and has a stitching ticket.

[1] 2024-12-09T19:20:54.758Z catalog error Failed to stitch component:default/<some unique name>, error: insert into "final_entities" ("entity_id", "entity_ref", "hash", "stitch_ticket") values ($1, $2, $3, $4) on conflict ("entity_id") do update set "stitch_ticket" = excluded."stitch_ticket" - duplicate key value violates unique constraint "final_entities_entity_ref_uniq" 

👍 Expected behavior

We should not see the errors, this is new behavior upgrading from 1.32.2 to 1.33.4

👎 Actual Behavior with Screenshots

Even though we see these errors, it appears the entity is stitched properly ultimately.

👟 Reproduction steps

This will be difficult to describe how to reproduce since our environment has custom providers that emit systems/components as well as several GitHub repositories with catalog-info.yaml files that source domains, users, groups, etc.

I started from a clean database. I'd note that I've tried running several times from a fresh database and I see errors from all sources (custom provider, GitHub yamls).

📃 Provide the context for the Bug.

No response

🖥️ Your Environment

1.33.4 upgrading from 1.32.2

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Are you willing to submit PR?

Yes I am willing to submit a PR!