This issue became problematic for us during the cleanup phase of our PHPUnit tests.
When the cleanup phase attempted to delete a locked node, it encountered the problematic exit(0). This caused the entire test suite to exit early in a way that GitLab didn't recognize as a failure.
Interestingly, the issue only arose after this commit:
https://git.drupalcode.org/project/content_lock/-/commit/7f8a2d3652e6f40...
Patch #13 solved the problem initially but I'm seeing the problem re-occurring after a while and requiring a cache clear to bring back the 'more' link.
genebobmiller → created an issue.
Thanks for investigating Alex, I'll dig deeper and see why our instance is behaving differently.
genebobmiller → created an issue.
I am still seeing the message:
```
Warning: SQLSTATE: IMSSP
Error Code: -33
Error Message: An invalid attribute was designated on the PDO object.
in Drupal\sqlsrv\Driver\Database\sqlsrv\Connection->__construct()
(line 209
```
Is that expected?
sqlsrv:4.3.4
In a recent 10.1.2 install I am seeing the field widget row settings respected on the Body field but not the Summary field.
Is that expected?
Recently hit this issue.
The cause in my case was the second level dependency league/uri-interfaces which was being installed at version 7.0.0-beta.2.
uri-interfaces should contain the UriString class but in the beta.2 version it does not.
We would like to use league/uri-interfaces:7.0.0 but this requires psr/http-message ^1.1 || ^2.0 which is incompatible with drupal/core-recommended:9.5.8.
```
drupal/core-recommended 9.5.8 requires psr/http-message (~1.0.1)
```
For now I'm solving the problem by explicitly locking league/uri to 6.7.0 in my composer.json
```
composer require league/uri:6.7.0
```
Amazing, thanks everyone!
genebobmiller → created an issue.
Thanks @shailja179,
I gave this a test, but unfortunately this patch doesn't solve the issue.
- It's still possible to enter and save an invalid date in the scheduled transition form.
- The invalid transition date is still recorded in the `node__scheduled_transition_date` table.
- Running drupal cron with an invalid date in `node__scheduled_transition_date` table still causes an error that blocks the entire cron run:
`Error: Call to a member function getTimestamp() on null in Drupal\lightning_scheduler\TransitionSet->toArray() (line 60...`
genebobmiller → created an issue.