Heikki Hellgren

We enabled `--trace-warnings` in our instance and there could be some pointers to the `MaxListnersExceededWarning`s:  This probably should be investigated a bit more.

It seems to point to this: https://github.com/backstage/backstage/blob/961861292ee6f93c4948c6b5a16458fa8fa7b671/plugins/techdocs-backend/src/cache/cacheMiddleware.ts I wonder if the socket gets closed properly in case the underlying storage returns an error here. We will try now disabling the...

Small update: we disabled the TechDocs cache and for now it seems that it is not running out of memory anymore. Also, the `MaxListenersExceededWarning`s are gone. We will continue monitoring...

I actually encountered this same issue with Yarn1 -> Yarn4 migration. CI for some reason gets the compression level of zero while locally it's mixed. Forcing the compression level to...

Also this is somewhat related: https://github.com/backstage/backstage/issues/30184 -> Could we use also the `fields` in the `fullTextFilterFields`?

How about making the hook return `setFields` method - would it make it a bit more closer to the final solution with columns? I would really like to see the...

@vinzscam while I agree on your points, I see there's a desperate need for the dynamic `fullTextFilterFields` especially with the pagination. Without those, the search only works on the current...