Incompatibility with antibot module

Hello Orkut, I followed given reproduced step. after that submit form but I haven't got any error.

my configuation- drupal-9.5.10
Php -8.1.2

My Drupal version is 10.1.3 and I've tried it both with php8.1 and php8.2.

Hello Orkut Murat Yılmaz, I have followed given reproduce step in drupal 10 but not got any error.
Attached configuration screenshot as well.

Sorry @shiv_yadav, but I haven't mentioned that I've applied the patch on this issue 🐛 PHP Fatal Error after drush cex RTBC too. Can you try with it as well?

The error message shows involved JS file to be handle via boost. This doesn't make sense. So we currently have a deeper problem which s just triggered by antibot in this case.

I'm still very busy in some customer projects. But soon I can invest some time to get this module stable.

Because I currently have to solve customer problem with css/js aggregation I took a deeper look inside the new strategy of the core with the routes 'system.css_asset' and system.js_asset ("core/modules/system/src/Routing/AssetRoutes.php"). The core is now acting a little bit like the boost module is doing. It first tries to deliver existing files, generates if needed and finally dumps them to file system. On a first step we should just exclude this routes from caching because the core already creates static files. Maybe it makes sense to include them with some configurable logic in future.

Beside my thoughts above about CSS/JS aggregation there is alos an impact of webserver configuration and core version.
@Orkut Murat Yılmaz Can you please add some information about core version and webserver configuration which helps to reproduce this specific situation.

I've re-installed the boost module with applying the patch on this issue 🐛 PHP Fatal Error after drush cex RTBC . This time it worked perfect.

My configuration is:

Drupal 10.2.0
Boost 8.x-1.x-dev (with the patch I've mentioned above)
Web Server: nginx/1.24.0
DB: PostgreSQL 15.5
PHP: 8.1.27

Thank you @C-Logemann, for reminding and for your efforts too. I guess that we can close this issue now.

@Orkut Murat Yılmaz Good that your system is working with the patch. But your error message showed me some potential problems we need to check and fix if needed. For this I created an new issue: 📌 Core 10.1 follow up: check and update event handler to avoid css/js Active