Eric Wong

Just tested, no this does not work, same error. (The property is recognized though, file not found error will appear if I set a wrong path)

I tried https://certificatechain.io/ which can be used to regenerate the certificate chain, and the result shows that the certificate is root in itself. (For your knowledge, the base64 certificate above...

/remove-lifecycle stale

As I wrote this just now, the package.json says: ``` "apostrophe": "^2.47.0", "apostrophe-workflow": "^2.28.0" ``` , and in package lock, apostrophe is on 2.100.1, workflow is on 2.28.0

any updates :(

I dug into the core and applied this patch, apparently does the trick: ```patch diff --git a/node_modules/apostrophe-workflow/lib/implementation.js b/node_modules/apostrophe-workflow/lib/implementation.js index 22be6fc..1a6d573 100644 --- a/node_modules/apostrophe-workflow/lib/implementation.js +++ b/node_modules/apostrophe-workflow/lib/implementation.js @@ -348,6 +348,9 @@ module.exports...

This issue really hit me in the most unexpected way - As I was done configuring the zones, I went into /etc/firewalld/zones, made a "250610.backup" folder, and copied all XMLs...

Tested the same cases on v2.3.0. The failure behavior is basically the same as above. The only small difference is for the ☢️ scenario, `firewall-cmd --get-active-zones` will return empty in...

v2.3.0 appears to be affected as well. I tried to compile from source v2.3.0 on the same RHEL 9.6. Below is the output. ```sh [root@ip-10-0-1-23 src]# pwd /root/firewalld-2.3.0/src [root@ip-10-0-1-23 src]#...