FIX Solr communication error #45
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
emteknetnz
force-pushed
the
pulls/1.6/broken-builds
branch
9 times, most recently
from
9c1fedc to
f81e97e
Compare
GuySartorelli
requested changes
Jul 19, 2022
src/Solr/CwpSolr.php
Outdated
Comment on lines
36
to
43
|
|
||
| if (!class_exists(Solr::class)) { | ||
| return; | ||
| } | ||
|
|
||
| // get options from configuration | ||
| $options = static::config()->get('options'); | ||
|
|
||
There was a problem hiding this comment.
I'm guessing these were accidental?
emteknetnz
force-pushed
the
pulls/1.6/broken-builds
branch
from
f81e97e to
deeec14
Compare
emteknetnz
force-pushed
the
pulls/1.6/broken-builds
branch
from
deeec14 to
4c24a4d
Compare
|
Fixed |
GuySartorelli
approved these changes
Jul 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue silverstripe/gha-ci#37
https://github.com/silverstripe/cwp-search/runs/7350149872?check_suite_focus=true#step:10:822
PHP Fatal error: Uncaught Apache_Solr_HttpTransportException: '0' Status: Communication Error in /home/runner/work/cwp-search/cwp-search/vendor/ptcinc/solr-php-client/Apache/Solr/Service.php:364Only happens on --prefer-lowest build
I'm not sure exactly what in fulltextsearch ^3.4 is required - it's something in here - ^3.3 will cause the build to fail
Auditor conflict is to fix a deprecated parameter order issue