Hrm, I'll be interested to see what's causing that to happen.
On Sun, Aug 16, 2020 at 9:16 PM bareheiny <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
Sorry - had and then lost a log last night.
Have a new one, but can redo it once the change is the other.
Interestingly, I’m seeing an “out of memory” error in the cmd window - but
that doesn’t stop CX from working as previous oom errors have.
On 17/08/2020, at 12:22, Darryl L. Pierce <mcpierce@xxxxxxxxx> wrote:
Wait until the changes I pushed into a PR yesterday get through review. I
added code to save the stack trace when a task throws an exception.
Hopefully that’ll help us diagnosis the problem.
On Sat, Aug 15, 2020 at 8:08 PM bareheiny <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
No logs unfortunately- but I can redo the import and capture the log.Sent from Gmail Mobile
On 16/08/2020, at 00:29, Darryl L. Pierce <mcpierce@xxxxxxxxx> wrote:
Hrm. Okay, so one improvement that comes to mind for finding the cause is
to change the task manager so that it doesn't delete the task in the
database until after it's completed processing. Instead we would have it
mark the task as claimed and only delete it when the task completes.
Next, I'm guessing there's some exception that's being thrown that should
have been caught and output to the log to cause the processing task to
fail. Unless that exception is killing the worker thread but even that
should show up in the logs. Did you capture logs of the processing for this
run?
On Sat, Aug 15, 2020 at 4:06 AM Guy Incognito <
dmarc-noreply@xxxxxxxxxxxxx> wrote:
With a fresh DB, I’ve imported 5 trades – import started a little before
843am. At 843am, 1 archive was fully imported – the remaining 4 are still
processing.
755pm, 2 archives fully imported – and 3 still processing. CMD window
shows no sign of processing – just the waiting for task notifications.
Basic archive information:
Archive 1 (351 pages, 265MB) – not imported
Archive 2 (146 pages, 81MB) – fully imported
Archive 3 (489 pages, 378MB) – not imported
Archive 4 (507 pages, 376MB) – fully imported
Archive 5 (420 pages 389MB) – not imported
*From: *Darryl L. Pierce <mcpierce@xxxxxxxxx>
*Sent: *Saturday, 15 August 2020 7:00 AM
*To: *comixed-dev@xxxxxxxxxxxxx
*Subject: *[comixed-dev] Re: Stuck in processing...again.
If that's happening with 0.7 then there may be some issues to contend
with in how we're refactored processing comics during import. How long did
you let it run before killing the process? And how many pages are in the
trades?
I may need to grab the files from you at some point to import locally to
reproduce the problem.
On Thu, Aug 13, 2020 at 10:04 PM Guy Incognito <
dmarc-noreply@xxxxxxxxxxxxx> wrote:
This seems to occur when I attempt to import multiple trades into CX.
For example I recently attempted to import around 14 files, that
included 7 trades – the trades were stuck in processing, until I deleted
them manually via the backend.
The CMD window didn’t show any sign of import activity - and the only
indication the comics were stuck is the spinning wheel overlay on the cover
images.
In order to get them imported, I need to do it one at a time.
Can get likely get more information if required – just need to know what
you want.
Seems to be restricted to 0.7, as I just imported the problem comics in
0.6 without any issue.
--
Darryl L. Pierce <mcpierce@xxxxxxxxx>
"Le centre du monde est partout." - Blaise Pascal
"Let's try and find some point of transcendence and leap together." -
Gord Downie
--
Darryl L. Pierce <mcpierce@xxxxxxxxx>
"Le centre du monde est partout." - Blaise Pascal
"Let's try and find some point of transcendence and leap together." -
Gord Downie
--
