Some weird bug probably
Closed this issue · 10 comments
Try to click on the library prep for this project:
It looks like there are 4 flowcells with the same ID in the DB ...
Someone added 140815_SN1025_0223_BC4HAPACXX to the DB three times too many.
First : 12:10:44
Second : 14:53:16
Third : 15:21:46
Fourth : 15:21:46
I'll try to get the logs for that.
Logs :
INFO [2014-09-22 15:07:54,616] 200 GET /project/P1272 (130.237.207.18) 110.90ms
INFO [2014-09-22 16:23:25,874] 200 GET / (130.237.207.18) 87.33ms
Either we didn't log anything, or someone added data without going throught the API
Operator on the doc updated at 15:21:46 :
francesco.vezzi@scilifelab.se
So, as far as I can tell, someone with francesco's identification cookie added the same flowcell multiple times.
For a reason obscure to me everyone is using my authentication .... no idea why...
Probably this has been Pär trying to update a project from the file system.
FV
On 23 Sep 2014, at 09:59, Denis Moreno notifications@github.com wrote:
Operator on the doc updated at 15:21:46 :
francesco.vezzi@scilifelab.se
So, as far as I can tell, someone with francesco's identification cookie added the same flowcell multiple times.—
Reply to this email directly or view it on GitHub.
Well, I asked Pär and he says it's not him. I'll bet on Mario then. Damn
americans !
On Tue, Sep 23, 2014 at 10:44 AM, Francesco notifications@github.com
wrote:
For a reason obscure to me everyone is using my authentication .... no
idea why...Probably this has been Pär trying to update a project from the file
system.FV
On 23 Sep 2014, at 09:59, Denis Moreno notifications@github.com wrote:
Operator on the doc updated at 15:21:46 :
francesco.vezzi@scilifelab.se
So, as far as I can tell, someone with francesco's identification cookie
added the same flowcell multiple times.—
Reply to this email directly or view it on GitHub.—
Reply to this email directly or view it on GitHub
#53 (comment)
.
Okay, now it's all fixed.
I removed the duplicates from the DB and I updated the code to make sure that does not happen again.
Wait but do you mean that four seqruns with this ID were created within the same project/sample/libprep? Because multiple samples can have the same seqrun of course, as a single sequencing run can contain multiple samples. If you mean the first thing I said then that is good that it is fixed of course.
On Sep 23, 2014, at 9:49, Denis Moreno notifications@github.com wrote:
Someone added 140815_SN1025_0223_BC4HAPACXX to the DB three times too many.
First : 12:10:44
Second : 14:53:16
Third : 15:21:46
Fourth : 15:21:46
I'll try to get the logs for that.—
Reply to this email directly or view it on GitHub.
yes, multiple sample can, but what happened was that I ended up with 4 entries where they key (project id, sample id, libprep id, run id) were identical. That is not something possible is it ?
That is not something possible! Correct. Okay good then. Now if you’ll all excuse me I need to get back to using Francesco’s Charon token.
On Sep 23, 2014, at 17:15, Denis Moreno notifications@github.com wrote:
yes, multiple sample can, but what happened was that I ended up with 4 entries where they key (project id, sample id, libprep id, run id) were identical. That is not something possible is it ?
—
Reply to this email directly or view it on GitHub.