Mako Runtime Error

Post any problems / bugs / issues that are Mylar-related in here.
Post Reply
User avatar
DrSeussFreak
Posts: 122
Joined: Wed Jan 29, 2014 10:50 pm

Mako Runtime Error

Post by DrSeussFreak »

All of the sudden today some of the fixes you put in undid themselves (and I am caught up on commits).

1) Archived items are not staying archived, they are getting reverted back skipped.
2) If I have 21 issues in a 21 issue series, and all are marked archived, on the home page it shows 20/21, stating I am missing an issue.
3) Archived Annuals no longer stay archived.
4) When I try to open "All-New Invaders" I get the following
Error !

AttributeError: 'NoneType' object has no attribute 'startswith'

371 <a href="#" onclick="doAjaxCall('queueissue?ComicID=${issue['ComicID']}&IssueID=${issue['IssueID']}&ComicIssue=${issue['Issue_Number']}&mode=want', $(this),'table')" data-success="Retrying the same version of '${issue['ComicName']}' '${issue['Issue_Number']}'" title="Retry the same download again"><img src="interfaces/default/images/retry_icon.png" height="25" width="25" /></a>
372 <a href="#" title="Mark issue as Skipped" onclick="doAjaxCall('unqueueissue?IssueID=${issue['IssueID']}&ComicID=${issue['ComicID']}',$(this),'table')" data-success="'${issue['Issue_Number']}' has been marked as skipped"><img src="interfaces/default/images/skipped_icon.png" height="25" width="25" /></a>
373 %elif (issue['Status'] == 'Downloaded'):
374 <%
375 linky = os.path.join(comic['ComicLocation'],issue['Location'])
376 if not os.path.isfile(linky):
377 linky = None
378 %>
379 %if linky:
/usr/local/mylar/env/lib/python2.7/posixpath.py, line 75:
if b.startswith('/'):
/usr/local/mylar/share/mylar/data/interfaces/default/comicdetails.html, line 374:
<%
/usr/local/mylar/share/mylar/data/interfaces/default/base.html, line 78:
${next.body()}
/volume1/@appstore/mylar/share/mylar/mako/runtime.py, line 718:
callable_(context, *args, **kwargs)
/volume1/@appstore/mylar/share/mylar/mako/runtime.py, line 692:
_exec_template(inherit, lclcontext, args=args, kwargs=kwargs)
/volume1/@appstore/mylar/share/mylar/mako/runtime.py, line 660:
**_kwargs_for_callable(callable_, data))
/volume1/@appstore/mylar/share/mylar/mako/template.py, line 296:
return runtime._render(self, self.callable_, args, data)
/volume1/@appstore/mylar/share/mylar/mylar/webserve.py, line 52:
return template.render(**kwargs)
"Adults are nothing but obsolete children, and the hell to them" - Theodor Seuss Geisel
User avatar
evilhero
Site Admin
Posts: 2887
Joined: Sat Apr 20, 2013 3:43 pm
Contact:

Re: Mako Runtime Error

Post by evilhero »

Based on that log, I would say the culprit behind all your problems is the mako error, which relates to a series not having a proper location set for a given issue. This could be caused by any number of things, sometimes a refresh of the series brings in new issue data that Mylar doesn't understand or it bombs out elsewhere due to another problem.


What I would try doing first is the following :

-Try shutting down / restarting Mylar.

-Go to the Manage tab, Manage comics and delete the series that's giving you problems.

-Try to readd it again and it should come down ok.

Whenever you get an error /traceback or even Cherrypy error, you need to shutdown Mylar and restart it as it needs to clear out the variables that are causing the problems.

Let me know if you're still having problems after that and we can troubleshoot further if required.
User avatar
DrSeussFreak
Posts: 122
Joined: Wed Jan 29, 2014 10:50 pm

Re: Mako Runtime Error

Post by DrSeussFreak »

already had performed a restart. Removed and re-added the comic and now as soon as I mark them as archived I get an error

I cannot get the logs to switch from info to debug, so no idea what the error is
"Adults are nothing but obsolete children, and the hell to them" - Theodor Seuss Geisel
User avatar
evilhero
Site Admin
Posts: 2887
Joined: Sat Apr 20, 2013 3:43 pm
Contact:

Re: Mako Runtime Error

Post by evilhero »

Check the mylar.log file for debugging info, the drop down in the gui doesn't work (yet!)

You can try running Mylar as a non daemon and seeing if there's a traceback error in the python console as well.
User avatar
DrSeussFreak
Posts: 122
Joined: Wed Jan 29, 2014 10:50 pm

Re: Mako Runtime Error

Post by DrSeussFreak »

27-Apr-2014 21:09:44 - INFO :: CP Server Thread-4 : Marking All-New Invaders 4 as Archived
27-Apr-2014 21:09:44 - DEBUG :: CP Server Thread-4 : updated...to Archived
27-Apr-2014 21:09:44 - INFO :: CP Server Thread-4 : Marking All-New Invaders 2 as Archived
27-Apr-2014 21:09:44 - DEBUG :: CP Server Thread-4 : updated...to Archived
27-Apr-2014 21:09:44 - INFO :: CP Server Thread-4 : Marking All-New Invaders 1 as Archived
27-Apr-2014 21:09:44 - DEBUG :: CP Server Thread-4 : updated...to Archived
27-Apr-2014 21:09:44 - INFO :: CP Server Thread-4 : Marking All-New Invaders 3 as Archived
27-Apr-2014 21:09:44 - DEBUG :: CP Server Thread-4 : updated...to Archived
27-Apr-2014 21:09:44 - INFO :: CP Server Thread-4 : Now checking files for All-New Invaders (2014) in /volume1/Comics/Marvel/All-New Invaders [2014]
27-Apr-2014 21:09:44 - DEBUG :: CP Server Thread-4 : [FILECHECKER] comic: All-New Invaders
27-Apr-2014 21:09:44 - DEBUG :: CP Server Thread-4 : [FILECHECKER] Looking in: /volume1/Comics/Marvel/All-New Invaders [2014]
27-Apr-2014 21:09:44 - DEBUG :: CP Server Thread-4 : there are 12 files.
27-Apr-2014 21:09:44 - DEBUG :: CP Server Thread-4 : [FILECHECKER] numberinseries: False
27-Apr-2014 21:09:44 - DEBUG :: CP Server Thread-4 : [FILECHECKER] decimalinseries: False
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : [FILECHECKER] subnm len : 1
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : [FILECHECKER] 1: detected invalid filename - attempting to detect year to continue
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : decimal issue detected, not removing decimals
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : [FILECHECKER] subname no brackets: All-New Invaders -
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : [FILECHECKER] - appears in series title.
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : [FILECHECKER] up to - :All
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : [FILECHECKER] after - :New Invaders -
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : [FILECHECKER] new subname is : AllNew Invaders -
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : [FILECHECKER] watchcomic:AllNew Invaders ..comparing to found file: AllNew Invaders -
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : [FILECHECKER] AllNew Invaders - watchlist match on : /volume1/Comics/Marvel/All-New Invaders [2014]/All-New Invaders - 2014 - 001.cbr
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : [FILECHECKER] we should remove 0 characters
27-Apr-2014 21:09:45 - DEBUG :: CP Server Thread-4 : [FILECHECKER] detected 1 special characters
"Adults are nothing but obsolete children, and the hell to them" - Theodor Seuss Geisel
User avatar
evilhero
Site Admin
Posts: 2887
Joined: Sat Apr 20, 2013 3:43 pm
Contact:

Re: Mako Runtime Error

Post by evilhero »

With the filename as 'All-New Invaders (2014) 001.cbz' or 'All-New Invaders 001 (2014).cbz', it scans in fine and the Archiving tag sticks as well.

With the filename as 'All-New Invaders - 2014 - 001.cbz', it throws a traceback error in the python console window:

Code: Select all

  File "/home/mylar/mylar/filechecker.py", line 226, in listFiles
    subname = str(subnm[0]).lstrip() + str(subnm[2]).lstrip() + ' (' + str(subnm[1]).strip() + ') '
IndexError: list index out of range
So obviously having the year within the filename as "- 2014 -" is throwing off the filename parser. I'm not sure how I can include that without it throwing something else off as it stands (the '-' also denotes an issue title, along with negative isssue numbering, etc). I'll have to look into this abit further, possibly try to base it off of what your default settings are for file renaming. I'm going to assume that you have the renaming set up as "$Series - $Year - $Issue" ?

As an aside, the traceback errors (such as above and are normally only available when Mylar is run in interactive mode so the console window is open) will be logged within the log file in a future commit (I've been testing out some of the logic I recently borrowed from a recent Headphones push where it was being used so I thought it benefical to see if it would work with Mylar since alot of users seems to miss these types of errors when run as a daemon)
User avatar
DrSeussFreak
Posts: 122
Joined: Wed Jan 29, 2014 10:50 pm

Re: Mako Runtime Error

Post by DrSeussFreak »

so my confusion then is based on the fact that this is how my naming convention has been since I first installed Mylar.

Image
"Adults are nothing but obsolete children, and the hell to them" - Theodor Seuss Geisel
User avatar
evilhero
Site Admin
Posts: 2887
Joined: Sat Apr 20, 2013 3:43 pm
Contact:

Re: Mako Runtime Error

Post by evilhero »

Ok, if that's the case then it's a recent change to the filechecker that is causing the issue and I know what it would be.. I'll look into this later tonight as I can't get back to a machine until then.
User avatar
DrSeussFreak
Posts: 122
Joined: Wed Jan 29, 2014 10:50 pm

Re: Mako Runtime Error

Post by DrSeussFreak »

I am happy to test anything, just let me know if you need me to.
"Adults are nothing but obsolete children, and the hell to them" - Theodor Seuss Geisel
Post Reply