Patrik Oldsberg

Results 400 comments of Patrik Oldsberg
trafficstars

Alright, ready for another round @freben 🚧 The subscription read query turned out to be a bit of a bottleneck, taking ~30ms in [this basic performance test](https://github.com/backstage/backstage/blob/3bd926905efb514cb3434ff63ffefdd827bd8724/plugins/events-backend/src/service/hub/DatabaseEventBusStore.test.ts#L198-L236). This is what...

Bit more investigation and I of course find some cases where the new query format performs worse 😁. Not a massive difference, but when testing with more densely populated events...

Hi! Sorry, but we'll need to stick to our documented requirements for becoming an org member that's outlined in our [goverenance](https://github.com/backstage/community/blob/main/GOVERNANCE.md#organization-member). You can still contribute and participate in the community...

To double-check, would it make sense to add you to https://github.com/backstage/backstage/blob/master/OWNERS.md#community-plugins instead? That'd include org membership

Yep closing this as @nickboldt was added as a community plugins project area maintainer instead

Yep this is indeed missing. Open to suggestions what the best way to make this available in the new backend system is. Ideally we'd avoid re-exporting the existing built-in processors....

Poking around at this a bit I realized we already have a bit of logic in place to allow for replacement: https://github.com/backstage/backstage/blob/b4c90d9f1b02017f1186c08c2a899e84c854d82a/plugins/catalog-backend/src/service/CatalogBuilder.ts#L723-L734 Given that that piece of code already exists...

Yep that's an interesting point, I think coming back to https://github.com/backstage/backstage/issues/27004#issuecomment-2579805017 it might be best to have that logic replace the processor in-place rather than pushing it to the end...

Had a discussion around this in the framework SIG and settled that the best way forward for now is to export the built-in processors and make it possible to replace...

@tylerd-canva just needs a rebase to bring in the node 22 workflows and resolve the conflict