Backend not ready for catalog mfe in latest version (ulmo.1)

Site Operators Tutor Help
, , , ,
1

Hi,

I installed the latest version of openedx (ulmo.1) in my local for testing using tutor (v21.0.0).
Then I tried to use the catalog mfe (release/ulmo.1).

And I think that backend changes may not be ready for it yet.

I saw that the edx-platform (release/ulmo.1) is using the edx-search version 4.3.0 see here.

In edx-search (4.3.0), we do not have the /search/unstable/v0/course_list_search/ endpoint yet, which catalog mfe is using.

I have also created an issue : here

Is it work in-progress or is there something that I am missing in configs?

How can someone who is using ulmo.1 can use the catalog mfe?

Thanks.

2

unfortunately I neglected to record logs from my first attempt at installing Catalog yesterday, but I also had some issues where it broke Meilisearch and gave some weird problems when rebuilding images or doing the launch/init commands. I’ve since reverted all my changes and got it back up and running however meilisearch remains broken so I’m unable to search anything in my server… Sorry no answers for you just yet, just letting you know you aren’t alone with Catalog issues, I’ll have to try again and pay better attention to the logs :sweat_smile:

1 Like
3

Thanks for your reply.
Good to know that the error is not my environment specific :sweat_smile:

4

@brian.smith could you take a look here?

5

we’re discussing this in Slack here: Slack and will have some updates in the next day/two. Short: We know the issue and will make a resolution!

6

Okay @sarina thanks for the update. :smiley:

7

Oh, and I opened a Github issue Error when loading new catalog microfrontend · Issue #99 · openedx/frontend-app-catalog · GitHub

8

Thank you so much for reporting this. A new version of edx-search that includes the needed change (4.4.0) has been published to PyPI.

I’ve made PRs to edx-platform updating the dependency (master, ulmo backport), so this will be resolved for ulmo.2 and future Open edX releases.

I also made a PR to frontend-app-catalog updating the README to include a workaround Tutor plugin for ulmo.1.

The workaround plugin is:

from tutor import hooks

INSTALL_SEARCH_440 = r"""
RUN --mount=type=cache,target=/openedx/.cache/pip,sharing=shared \
    pip install "edx-search==4.4.0"
"""

hooks.Filters.ENV_PATCHES.add_items([
    ("openedx-dockerfile-post-python-requirements", INSTALL_SEARCH_440),
    ("openedx-dev-dockerfile-post-python-requirements", INSTALL_SEARCH_440),
])
4 Likes
9

Just to add. After adding this hook, you must rebuild the `openedx` container (`tutor images build openedx`), and reboot your platform.

10

Thank you very much @brian.smith

11

I had a similar issue when testing new platform versions because backend changes and frontend updates are not always synced at the same time. During my research phase, I even used write my economics dissertation support when dealing with complex system documentation, since managing technical details alongside academic work became hard. It looks like the missing endpoint and edx-search version mismatch caused the problem here, so updating dependencies or using the workaround plugin makes sense. These early release gaps are frustrating but normal during active development cycles.