Sébastien Ros
Sébastien Ros
Do you think you can provide a PR ? I assume the mitigation is to delete the custom pattern for this culture before you change the settings.
Not sure but worst case scenario you can always use custom SQL queries.
It allocates less, but it locks much more :/ ``` | application | baseline | intern | | | ----------------------------- | ------------- | ----------- | -------- | | CPU Usage...
Here is the file to change for the updated modes: https://github.com/aspnet/Benchmarks/blob/main/build/pgo-scenarios.yml I will remove the ARM64 option (PowerBI change). Do you need to get these running on Ampere (80), Linux|Windows?
@MichaelPetrinolis isn't it already supported?
Can you also check if the current tenant controller/views can be adapted to support any tenant instead of the default one only? This way the new feature could use them...
Mutations are already supported, it's just that none has been implemented in dev yet.
That could be part of the data stored on the field instead.
We have talked about tags already for standard media fields. I would be ok with that only as another property on the field. But that means changing the ui significantly....
If we separate the module from the features (new Orchard.ResourceManagement.Core project) then I don't think we need the new IResourceSettingsProvider concept. The module would link Orchard Core settings with the...