Skip to content

chore(release): sync upstream release/ulmo.1 into release-ulmo#84

Open
viv-helix wants to merge 2 commits intorelease-ulmofrom
test/upstream-ulmo.1
Open

chore(release): sync upstream release/ulmo.1 into release-ulmo#84
viv-helix wants to merge 2 commits intorelease-ulmofrom
test/upstream-ulmo.1

Conversation

@viv-helix
Copy link

@viv-helix viv-helix commented Mar 18, 2026

Description:

  • Created a new branch from release-ulmo
  • Cherry-picked recent commits from upstream release/ulmo.1
  • Opened PR to merge updates into release-ulmo

Ensures release-ulmo stays aligned with upstream fixes and improvements.

Jira:

ormsbee and others added 2 commits March 9, 2026 13:14
When uploading a library archive file during the creation of a new
library, the code prior to this commit did not properly handle the "In
Progress" state, which is when the celery task doing the archive
processing is actively running. Note that this is distinct from the
"Pending" state, which is when the task is waiting in the queue to be
run (which in practice should almost never happen unless there is an
operational issue).

Since celery tasks run in-process during local development, the task
was always finished by the time that the browser made a call to check
on the status. The problem only happened on slower sandboxes, where
processing truly runs asynchronously and might take a few seconds.
Because this case wasn't handled, the frontend would never poll for
updates either, so the upload was basically lost as far as the user
was concerned.
…es (openedx#2734) (openedx#2766)

- add temporary message alert in sections settings tab in libraries
- increase sidebar width to remove `More` option and display all tabs
together

(cherry picked from commit 3eeca24)
@viv-helix viv-helix changed the title Test/upstream ulmo.1 chore(release): sync upstream release/ulmo.1 into release-ulmo Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants