-
Notifications
You must be signed in to change notification settings - Fork 36
"No match was found" is shown when searching items and properties using default settings #381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Just in case this matters, in previous attempts of getting Wikibase running, I tried installing it without using Docker, and I recall that in the README file of the extension CirrusSearch, it was recommended to execute some commands. I've copy-pasted the relevant part from the README file in the code block below.
In the Wikibase instance that I used for documenting this issue, I didn't follow the steps (shown in the code block above) after performing all the steps mentioned in the README file of this repository, because I thought that when the Docker containers are created, all the necessary commands are executed. |
Another connected issue Rodrigo: #296 Perhaps sharing your .env file or other config details will help? |
@ross-spencer Sure, this is my
|
Hey hey, thanks for the report I can confirm today that search with elastic search works with the wmde.9 release, but I did have some issues with the current docker-compose example. Can you check the logs of the job runner and paste them here?
Also what is the directory listing in your current job runner?
And just to double check, what is the current entry point?
I believe that #359 may resolve your issues which changes the way settings are shared between the main wikibase container and the job runner container. If you provide the information above I may be able to help further
|
@addshore Thanks for the response. Here's the information that you asked and some other information that I considered relevant. Requested informationCan you check the logs of the job runner and paste them here? I ran the command and the following message was printed 2013 times.
I used
I used
Also what is the directory listing in your current job runner?
Also what is the directory listing in your current job runner?
Additional informationThese are the files that are in the directory where I ran
Here's the information that shows
I searched the string wikibase-release-pipeline/example/docker-compose.yml Lines 44 to 62 in 6ab3c2a
wikibase-release-pipeline/example/docker-compose.extra.yml Lines 18 to 20 in 6ab3c2a
wikibase-release-pipeline/example/template.env Lines 26 to 27 in 6ab3c2a
Personal thoughtsI think the problem has to do with |
These should be files not directories. If you still have a mostly empty set ups it'll be easiest to just run |
@addshore Thanks for the help. I downloaded the files
Below I wrote some additional notes that are related to this issue. Note 1I'm a beginner Docker user and that was my first time running a Wikibase instance, so I'm not very familiar with the dependencies by Docker. When I read wikibase-release-pipeline/example/README.md Lines 1 to 24 in 2f4394c
Would it be possible to be clear about the importance of those files? For example, something along these lines.
Note 2I decided to use the tag wmde.9 instead of the commit that I referenced before to ensure that things are more stable. However, I noticed that the wikibase-release-pipeline/example/template.env Lines 4 to 12 in e8744b2
For this reason, I decided to use the latest commit as of the time of this writing and everything seems to be working fine. I'm not sure if it is possible to edit the files of a published tag in Git since I've never tried it before. If it were possible, I think it would be appropriate to edit that file since it could be confusing (e.g. a user creates an issue with regards to Note 3Here's a summary of what happened for users that might find a similar issue: the mistake I made that caused this issue was that I didn't download the files |
TL; DR
I'm using default settings, I haven't modified neither
docker-compose.yml
,docker-compose.extra.yml
nortemplate.env
. The issue is that "No match was found" is shown when searching properties and items when adding statements even though items and properties do exist. Apart from that, the error "An error has occurred while searching: We could not complete your search due to a temporary problem. Please try again later. " is shown when searching anything in Special:Search.Fresh installation
This sections describes the steps that I followed to delete the files from previous attempts of running Wikibase in Docker and the installation process.
Remove files from previous installation
When I found this issue, this was the state of the containers.
I stopped all containers using the following command.
I removed all containers using the following command.
I stopped and removed containers and networks using the following command.
I deleted all volumes using the following command.
I removed the configuration files for Docker using the following command.
Installation process
I downloaded the following files (see code block below) in that commit with hash
6ab3c2aac2bb5dc95c72ebbe8b2231799acbef35
, because that was the hyperlink for the text "example directory" in https://www.mediawiki.org/wiki/Wikibase/Docker#Preparing_your_environment (revision). Here's the link to the files in that commit in the Github repository: docker-compose.yml, docker-compose.extra.yml and template.env.I started Docker using the following command.
I used the following command to show the status of the containers.
At this point, I could
The problem
Matches weren't shown when searching properties when adding statements (see first image below). A match was found when using the identifier of the property (see second image below).
Similarly, matches weren't shown when searching items when adding statements (see first image below). A match was found when using the identifier of the item (see second image below).
The following error was shown when using the search bar (see image below).
Similar issues
I found these issues that were related to this issue.
.env
file..env
file.The text was updated successfully, but these errors were encountered: