Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Plate list page allows users to send unquantified compressed gdna plates to normalization page, which leads to error

Open
#485 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend, web-dev

Research direction

Start with plate_list.html, normalization.html, and parse_quantification.html, tracing how selected plates are passed through the query string. Reproduce the unquantified compressed gDNA flow and inspect the normalization submission path. Done means the route rejects or clearly handles unquantified plates before the backend raises a Python error.

Written by the indexing model from the issue text.

Description

bug priority:low

Reproduction GIF below. On plate_list.html, user can pick any compressed gDNA plates and send them to the normalization.html page--but normalization can only be performed on compressed gDNA plates that have been quantified (via the parse_quantification.html page) . The normalization page prevents users from adding unquantified plates on it directly but does not catch the case where an unquantified plate is sent in via the querystring from plate_list.html. This means the user can go ahead and submit their normalization request to the back end and get a nasty python error.

unquantified

I class this as a relatively low priority because I don't think the lab actually uses the "checkboxes from plate list" route very often. It is actually a big pain to manage and I would like to suggest we at least consider the possibility of axing it ...

Dominant language
Python
Stars
2
Forks
15
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from biocore/LabControl

All issues in biocore/LabControl

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.