Mark Ormesher

Was this meant to be closed? I've not had time to look at your suggestions yet but I would still like to work on this

Hey @timothymiller - sorry for the delay here, finally getting time to sit down and properly read through your comments. 100% with you on not breaking any backwards compatibility. The...

Hey @sronbheannach, thanks for the feedback. I don't have a ton of time to give to this project at the moment, but if you want to PR that improvement I'd...

Hi @KunduzNbkva, unfortunately that's not supported at the moment. It's not something I'm likely to have time to add any time soon, but if you're interested in contribution I'd be...

Hey @rolenin. Scrolling the speed-dial menu isn't currently possible in the library, but I suppose it could be added. Can I ask how many items you're trying to show? According...

Seems like a pretty good use case for a scrollable menu to me 🙂 I'll see if I can get to it next week, but I can't promise anything. Feel...

Hey @antranvn. If the menu options are much closer to each other than the ones in image in the readme it might be a bug - if so, could you...

@GeorgeTaveras1231 have you considered publishing your resolver plugin as a tiny NPM package that could be plugged into TSM? Alternatively @skovy would you consider `enhanced-resolve` as well-established enough to accept...

It shouldn't break any existing use cases, but we'd obviously want to test that. We could _expose_ an extra optional config to let people control `enhanced-resolve`'s behaviour, but the default...

I think I am also seeing this issue, running NFS-Ganesha V4.0.12 on Debian Bullseye, with one GlusterFS (v9.2) share configured. I see the same pattern of steadily increasing memory usage:...