Skip to content
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

Y25-009 - [BUG] Requests not being passed automatically (GEMs input) #2146

Closed
KatyTaylor opened this issue Jan 9, 2025 · 0 comments · Fixed by #2162
Closed

Y25-009 - [BUG] Requests not being passed automatically (GEMs input) #2146

KatyTaylor opened this issue Jan 9, 2025 · 0 comments · Fixed by #2162
Assignees

Comments

@KatyTaylor
Copy link
Contributor

KatyTaylor commented Jan 9, 2025

Describe the bug
In the scRNA Core pipeline (entrypoint starting with GEMs plate), the library prep (GEMS input) requests are not being successfully passed. This then causes a problem on the first step of the aggregation pipeline, as in FreshService ticket https://sanger.freshservice.com/a/tickets/18528?current_tab=details This is likely because the purpose config refers to old request type name - it was not updated during #2027.

See config > purposes > scrna_core_cdna_prep.yml, purpose LRC GEM-X 5p cDNA PCR XP, work_completion_request_type - limber_scrna_core_cdna_prep_gem_x_5p_pbmc_pools_input is out of date, should be limber_scrna_core_cdna_prep_gem_x_5p_gems_input.

RT Ticket Number
If applicable

Tasks:

  • Update the purpose config to have the correct request type name
  • Modify the integration suite test for this entrypoint to add the aggregation pipeline onto the end (currently it just does the library prep part). (Could do this first for test-driven development)
@psd-issuer psd-issuer bot changed the title [BUG] Requests not being passed automatically (GEMs input) Y25-009 - [BUG] Requests not being passed automatically (GEMs input) Jan 9, 2025
@KatyTaylor KatyTaylor added the Bug Bug in code label Jan 9, 2025
@seenanair seenanair self-assigned this Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants