sequencescape
sequencescape copied to clipboard
Web based LIMS
**Describe the Housekeeping** The API V2 well and receptacle resources both lack links back to the labware/plate. This is a little bizzare, and results in us jumping through hoops in...
I get the following after successfully installing and logging in: ViteRuby::MissingExecutableError in Homes#showShowing /code/app/views/layouts/application.html.erb where line #25 raised:❌ The vite binary is not available. Have you installed the npm packages?...
This is your daily update of **all** Bundler dependencies. Please take a good look at what changed and the test results before merging this pull request. ### What changed? ✳️...
**Describe the bug** If two requests in a batch come from the same source well, you are unable to start the batch. Instead you get a 500: > An AASM::InvalidTransition...
**User story** As NPG, in cases where the same multiplexed library tube is loaded onto all 4 lanes, I would like the compound sample names to be consistent across the...
**Describe the bug** When processing a stock_resource message with UWH consumers: ```{"stock_resource":{"stock_resource_uuid":``` getting the following error: ``` Dead-letter Exception: Contains two elements with the same composite identifier: combination of id_stock_resource_lims,...
**Describe the Housekeeping** While migrating to vite, I noted a fail chunk of legacy inline javascript. We should probably move this into proper js files, and pass in properties via...
Add new Squix printers to required LIMS (SS< Limber etc) Printer 1 - Hostname: aa209bc1 - IP Address: 172.30.1.108 - MAC Address: 00:02:E7:08:64:97 - Label Type: Tube Labels Printer 2...
**Describe the bug** With Pacbio run messages: ```{"pac_bio_run":{"pac_bio_run_id":``` getting the following exception in UWH consumers: ``` Mar 25 14:46:15 ware-prod unified_warehouse[28402]: (thread-7160) [WIP:production] ERROR -- : 🦊 production_MultiLimsWarehouseConsumer_28402: Dead-letter Exception:...
**Describe the Housekeeping** We used to connect to MySQL in strict mode in development, which places certain constraints on queries, especially GROUP BY. (The ONLY_FULL_GROUP_BY mode is especially important here)...