rany2
rany2
> AES-GCM workloads (e.g. TLS, IPsec, WireGuard) Does this really improve performance for WireGuard? WireGuard doesn't use AES-GCM.
Can we instead just have the chromium versions for the different platforms stored in text files? So chromium_version_linux.txt, chromium_version_mac.txt, etc? This way I can pull that easily. I really don't...
Mhmm, I don't mean that the downloader would use that information but I guess it would be confusing to have these text files in the main repository. Maybe we can...
@PF4Public it does help but FEDC automatically creates the pull requests for me and that's generally helpful when it's a minor version bump. I know it's kind of lazy on...
I think that might work. I'll give it a try and report back. I'm just not sure if their regex engine supports backreferences.
It didn't work because I am forced to only have one capture group and the backreference ends up getting captured. I thought I could try to use jq to get...
Well, the issue is that it should be obvious for all Flatpak users. Unfortunately most Flatpak users are new to Linux so it actually won't be obvious to them.
> So my build with `symbol_level=2` and `blink_symbol_level=2` set still didn't give further info I think you need to have a debug build and set `v8_optimized_debug` to false as well.
I think the detection is a false positive. At least I can't find any blocking code for edge-tts that can cause this. The reason the sync varient doesn't trigger it...
@XHyperDEVX That error is unrelated to edge-tts. Different component.