learningequality / learningequality/studio
Unstable - It's possible to submit the 'Submit to Community Library' form while the submission is in progress
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
Observed behavior
Observed while testing https://github.com/learningequality/studio/pull/5750:
If immediately after submitting a channel for the community library I click again the Submit to community library option then I can fill in again the Submit to Community Library form, while the submission is still in progress. This results in an error message followed by a Page not found error message for the channel editor:
https://github.com/user-attachments/assets/a6645ea4-9106-4c1c-8e27-a4eafa875357
Expected behavior
It should not be possible to submit the channel for review at this point.
Steps to reproduce the issue
- Sign in to Studio at Unstable
- Create a new channel, import content and publish it.
- Click the Share button, select the Submit to community library option and submit the form.
- Repeat the same while the submission is still in progress.
Usage Details
- Studio Unstable
- OS: Windows 11
- Browser: Chrome, Firefox
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the flow from the Share button through “Submit to community library” while the first submission is in progress. Trace the entry point that opens the submission form and verify that a second submission is unavailable and does not produce the reported error or Page not found response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100