Difference between revisions of "Help:Bug Tracking"
(Created page with "The iGEM Parts Registry has gone through a server migration to AWS and also an update to its user and groups system. iGEM Teams can add, edit, search, and view parts but user...") |
m |
||
| Line 20: | Line 20: | ||
==Known Issues/Bugs== | ==Known Issues/Bugs== | ||
| + | Some issues below, may be unrelated to the server migration and new user and groups system. | ||
| + | |||
* DNA BLAST is down. Teams will not be able to blast a sequence against the Registry. This also affects sequence analysis tools. | * DNA BLAST is down. Teams will not be able to blast a sequence against the Registry. This also affects sequence analysis tools. | ||
** If you are trying to determine if a part exists already in the Registry, the easiest way is to create a temporary part, and add your sequence in. | ** If you are trying to determine if a part exists already in the Registry, the easiest way is to create a temporary part, and add your sequence in. | ||
| − | * pgroup (part group) / groupparts tables are down. These tables let users see all the parts created by a specific group. | + | * pgroup (part group) / [[Help:Group_Parts_Table|groupparts tables]] are down. These tables let users see all the parts created by a specific group. |
| − | * part status needs updating. Part/sample status is not currently updated. It should be ignored for now. | + | * [[Help:Part_Status_Box|part status box]] needs updating. Part/sample status is not currently updated. It should be ignored for now. |
Revision as of 12:43, 23 July 2024
The iGEM Parts Registry has gone through a server migration to AWS and also an update to its user and groups system.
iGEM Teams can add, edit, search, and view parts but users may encounter issues and bugs along the way.
If you encounter unexpected behavior from the Registry, please first check to see if it is reported on the list below.
If it is not on the list below, please send an email to registry (at) igem (dot) org, with the following information:
- In the subject,
- include "ERROR/BUG:" followed by a brief description of the error
- In the body of the email, include:
- Your team name
- A more detailed description on how you encountered the error. This may include the specific links, actions you were taking, and any other details that be helpful in recreating the unexpected behavior.
- Screenshot of the error or error message
- Date/time error occured (estimate is OK)
- Browser used
Known Issues/Bugs
Some issues below, may be unrelated to the server migration and new user and groups system.
- DNA BLAST is down. Teams will not be able to blast a sequence against the Registry. This also affects sequence analysis tools.
- If you are trying to determine if a part exists already in the Registry, the easiest way is to create a temporary part, and add your sequence in.
- pgroup (part group) / groupparts tables are down. These tables let users see all the parts created by a specific group.
- part status box needs updating. Part/sample status is not currently updated. It should be ignored for now.