Samuel Colvin

We also want: * the path of the error, e.g. `['foo', 'bar', 0]` - this should be opt in with (another) generic option, hopefully the last * the exact position...

I'm happy to add this via full support for the annotated-types type. @bram-tv by the way, you can use custom errors to make the errors nicer.

Sorry for the delay, here we go: ### `logical_plan` ``` Projection: records_store.span_name Limit: skip=0, fetch=20 Sort: bit_length(records_store.attributes) DESC NULLS FIRST, fetch=20 TableScan: records_store projection=[span_name, attributes] ``` ### `physical_plan` ``` ProjectionExec:...

Closing, can always create a new issue if someone reproduces.

Thank you so much for working on this.

I think #10511 is related to this, except it's using `ExternalSorterMerge` which from the name has no "top K" behaviour, hence the very high memory footprint?

This is great, thank you.

Does the file being watched exist?

thanks, I assume v0.23 has the same issue?

Thanks so much for the feedback, please could you try with `force_polling` and see if the error still occurs?