I was also getting this same error on update hook 8037 just using dxpr_builder. I just edited the .install file and changed that line manually from config/install to config/optional and the update ran fine after that.
Setting back to needs review.
Thanks everyone for the quick response and I apologize for my delayed response.
@avpaderno I wasn't aware there was a 10 day waiting period. I appreciate the info and I'm definitely ok with that.
@ vishal.kadam thank you for pointing out those issue. I have corrected the core version requirements in the .info and just removed it from composer since it didn't need to be there. I also updated the comment to be more specific in the .module file. All changes are current in the 1.x branch.
I did work this evening to get all the CI passing as well. Ran into some issues with that but got them all straightened out. Please let me know if there is anything else I need to do.
jason.ullstam → created an issue.
Patch from #132 🐛 FinishResponseSubscriber: Need warning/error when headers exceed 16k Needs work worked for me on a site that was getting 500s. Core 10.4.6.
I attempted the patch from #5 and it failed. I also tested just making the change manually and I was still seeing the issue. Tried the patch from #9 and it ran successfully however did not resolve the issue for me. Running on core 10.4.2 with webform 6.2.9. I created a MR with a possible resolution. It did work on my instances. Also uploading a patch file for testing.
jason.ullstam → made their first commit to this issue’s fork.
I have also tested the patch from #11 🐛 MissingValueContextException: Required contexts without a value: node Active and it is working for us. Any idea when this might get added to a release. I have hundreds of sites using this module and would prefer to not patch if possible.
Same issue for me on existing sites and new site installs. Patch from #9 resolves the issue. Let's get this pushed!
I have tested the patch from #2 from @jsutta and this does work better in my opinion and also resolves an issue I was having where the cog was getting covered up by a field group drop down. I think this patch should be merged into the next release.
I have also verified that the patch from #2 resolves the fatal error on many of my production sites. Would be great if this MR could be approved and tagged.
I have tested this patch as well and it does resolve the issue for me on all of my sites. @ahebrank can this be merged?
I think this would be a "nice to have" feature. I'm currently self hosting Sentry so not sure I would use it fully until I saw how much increase in storage that would be. But definitely would like the option in Raven if it's possible.
Sounds great Mark! Much appreciated...
Verified patch from #135 📌 CKEditor 5 readiness Fixed is working on Drupal 9.5.3 with linkit dev-6.0.x. I would also ask the same as @rafaticarte about when this can be added to the next beta release. I have upgraded all my 120+ instances to CKeditor5 already and would prefer not to use the dev version of the linkit module with a patch.