Nick Shulman responded: |
2017-10-16 03:28:58 |
Can you give us more information? What were you doing when you saw this error? Can you maybe attach a screenshot of this error?
For most errors, Skyline shows you the "Unexpected Error" dialog which includes the callstack, and gives you a "Report" button which would submit all of the information to our server.
There are some errors which cause Skyline to quit immediately. Usually in those cases, the next time that you start up Skyline, Skyline will show you the Unexpected Error dialog for the error that killed Skyline before.
It sounds like you are running into an error which is not being caught by our usual error handling stuff. Can you tell us more about how this error is being presented to you so that we can suggest places to look for more information? |
|
Tobias Kockmann responded: |
2017-10-16 03:41:46 |
The skyline installation runs in combination with the autoQC loader application. The unexpected error dialog is not showing up. |
|
Tobias Kockmann responded: |
2017-10-16 04:06:11 |
here is a screen shot. |
|
|
Vagisha Sharma responded: |
2017-10-17 09:32:47 |
Hi Tobi,
I suspect this happens when Skyline has to import a new raw file and remove an older one at the same time. See this support request ( https://panoramaweb.org/labkey/announcements/home/support/thread.view?rowId=1990).
I could try to confirm by looking at one of your AutoQC logs. You have several configurations running, so if you could send me the log for one that has been running long enough (longer than the "Results time window" setting) for some older results to start getting removed that would be great.
Are you using Skyline or Skyline-daily? This bug hasn't yet been fixed in Skyline-daily, but should be fixed soon.
Thanks,
Vagisha |
|
Tobias Kockmann responded: |
2017-10-23 06:53:02 |
I am using skyline, not daily. The problem is...I can not really tell you which config the error comes from (which log file to send). I attached one of the many. They were all started at the same time point. |
|
|
Tobias Kockmann responded: |
2017-10-29 04:41:20 |
Hi Vagisha,
this bug is super annoying. Is there any solution? Currently, our monitoring does not work at all, since skylines crashes at least once per day so there is no update of the our PanoramaWeb project.
Greetings,
Tobi |
|
Vagisha Sharma responded: |
2017-11-02 08:34:31 |
Hi Tobi,
I apologize for the delay in getting back to you. One thing you could do is to set the "Results time window" in your AutoQC Loader configurations to greater than 31 days (default). This setting determines how long imported results are retained in the Skyline document. This is a rolling window and every time a new raw file is imported into the document, older results with acquisition dates that no longer falls in this window are removed from the document. Since the problem you are seeing only happens when older results are removed, setting "Results time window" to a higher number will keep the older results for longer. So it will work for some time depending on the window size you choose. Your Skyline document will get bigger, of course. You could manually remove older results, if needed.
This bug will be fixed in the next Skyline-daily release that should come out in the next few days. I don't think we will have a patch release for Skyline, however. There aren't enough bug fixes for a patch release. Are you able to switch to Skyline-daily? Or will that be a problem?
Sorry for all the trouble this is causing in your QC workflow.
-Vagisha |
|
Tobias Kockmann responded: |
2017-11-10 23:30:00 |
Hi Vagisha,
is this the skyline-daily we need: Skyline-daily 3.7.1.11751 (released today)?
Brendan did not not list it. But he did list the bug fix for the missing values, great! THX!
Greetings,
Tobi |
|
Vagisha Sharma responded: |
2017-11-13 15:02:02 |
Hi Tobi,
I am sorry to say that the fix did not make it to the Skyline-daily released last Friday. But it will be in the next one. I will check with Brendan on when the next update will be and get back to you.
Thanks,
Vagisha |
|
Tobias Kockmann responded: |
2017-11-14 10:23:40 |
Hi Vagisha,
that is a bit disappointing...
Greetings,
Tobi |
|
christian trachsel responded: |
2017-12-08 01:30:23 |
Hi Vagisha,
I'm Christian the second QC supervisor here at FGCZ and I'm trying to keep the Skyline autoQC running. Is there any news from your side when a fix for this bug will be released? Currently, Tobi or I have to click away at least twice a day an error message to keep the system running. This is really frustrating and annoying and far away from a stable, automated QC system! We would really appreciate any progress on this issue.
Best,
Christian |
|
Vagisha Sharma responded: |
2017-12-08 08:40:32 |
Hi Christian,
Brendan is very close to a Skyline-daily release. It should be out by the end of next week if not earlier. I apologize for the delay in getting this bug-fix out.
-Vagisha |
|
Vagisha Sharma responded: |
2017-12-12 09:14:20 |
Hi Tobi and Christian,
Just wanted to check if the last Skyline-daily 4.0.9.11635 release fixed your problem.
Thank you,
Vagisha |
|
Tobias Kockmann responded: |
2017-12-14 04:53:42 |
Hi Vagisha,
Brendan did not list the bugfix in his release notes! It was included? What is the corresponding autoQC loader version? I assume we need to switch both?
Greetings,
Tobi |
|
Vagisha Sharma responded: |
2017-12-15 15:20:26 |
|
|
Tobias Kockmann responded: |
2018-01-09 08:31:16 |
Hi Vagisha,
I installed skyline-daily and autoQC loader-daily and so far the error did not appear again! :-) THX!
Greetings,
Tobi |
|