Missing project(s) from dropdown [#3314942]

Problem/Motivation

Noticed that smart_date is not available as an additional project on https://simplytest.me/. I looked through the issue queue and didn't see a similar issue.

The module is not experimental and has several full releases.

Maintainer, mandclu mentioned that, "for a long time one of the dependencies for the smart_date_starter_kit wasn't recognized by simplytest.me, so you could install Smart Date but not the starter kit or calendar kit. Now we sort of have the reverse problem"

Steps to reproduce

Go to simplytest.me and start typing smart_date. There is no autocomplete result and it errors if you try to launch project without a match.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comment	File	Size	Author
#14	eca_simplytest.png	1.21 MB	mxr576
#12	after_simplytest.png	199.09 KB	atul_ghate
#12	before_simplytest.png	421.18 KB	atul_ghate
#9	simplytest.png	229.21 KB	akhil babu
	Screen Shot 2022-10-12 at 9.47.34 AM.png	2.54 MB	joewhitsitt

Issue fork simplytest-3314942

Show commands

Start within a Git clone of the project using the version control instructions.

Add & fetch this issue fork’s repository

Or, if you do not have SSH keys set up on git.drupalcode.org:

Add & fetch this issue fork’s repository

3314942-missing-projects-from changes, plain diff MR !142
Check out this branch for the first time

Check out existing branch, if you already have it locally

About issue forks

Comments

Comment #1

12 October 2022 at 14:52

joewhitsitt created an issue. See original summary.

Comment #2

joewhitsitt

Iowa

commented 12 October 2022 at 14:55

mglaman mentioned, "this is something which could be “checked” locally w/o needing tugboat to qa the import failure"

Comment #3

mahtab_alam commented 13 October 2022 at 12:47

We may need to import the projects again via navigating to /admin/config/simplytest/import as for this project 'smart_date' the Simplytest Project entities not exists.
Manually adding the smart_date project on Simplytest Project entities is showing this project list on dropdown element.

Comment #4

nerdstein

he/him

English

United States

commented 13 October 2022 at 13:58

It is good to know it can be imported. But, I wonder why the importer is not picking it up. It has to process a lot of information but should be gradually getting through that with CRON. We should try to understand why the importer is not automatically getting it or if we didnt set up cron properly

Comment #5

andrew.wang commented 17 October 2022 at 20:08

Same issue for svg_image - this module has stable releases but is not shown in the simplytest.me drop down.

Comment #6

2pha

English

commented 18 November 2022 at 06:36

I wanted to run a quick test of the Profile module but it would not show up

Comment #7

26 December 2022 at 11:37

Akhil Babu made their first commit to this issue’s fork.

Comment #8

26 December 2022 at 11:45

Akhil Babu opened merge request !142

Comment #9

akhil babu

he/him

commented 26 December 2022 at 12:27

Status:

Active

» Needs review

Status	File	Size
new	simplytest.png	229.21 KB

When user searches for a project, simplytest first checks its database to see whether the project details are already present or not. If data is already presnet in database, that will be showed as "suggestion". Else, project details will be fetched from the API -> Stored in database -> Retured to user. So, data is fetched from API only if a "match" is not present in database and this behavior seems to have caused this issue.

When 'smart_date' is searched, Simplytest checks the database. Data for the module smart dates (smart date and smart dates are two different modules) is already present in db. Since a match is found, this data is returned instead of fetching the data from API.

Similarly, when "svg_image" is searched, already stored data of "svg_image_field" is retured. For "profile" module, "profile2", "profile_switcher" etc are retured as these are matches existing in database for the keyword "profile".

I have updated this logic to check whether the exact match is present in the suggestions retrieved from db. If not, API will be triggered and data will be retrieved and stored. Moving this issue to review state for feedbacks and corrections.