0.9.3 - OperationalError
2 posters
Page 1 of 1
0.9.3 - OperationalError
I tried to tag Avengers #181 since the problem I had with it before was going to be fixed in this update, but ComicTagger's GUI can't find any search results for the issue. The search result box is just empty. Auto-Select brings up the search progress, but it just says "Searching for Avengers #181" and then nothing else happens.
I tried to put it into the CLI, and here's the result:
I tried to put it into the CLI, and here's the result:
Traceback (most recent call last):
File "<string>", line 484, in <module>
File "<string>", line 458, in main
File "<string>", line 162, in cli_mode
File "<string>", line 335, in process_file_cli
File "/Users/tony/Dropbox/tagger/comictagger/mac/build/pyi.darwin/ComicTagger/out00-PYZ.pyz/issueidentifier", line 262, in search
File "/Users/tony/Dropbox/tagger/comictagger/mac/build/pyi.darwin/ComicTagger/out00-PYZ.pyz/comicvinetalker", line 89, in searchForSeries
File "/Users/tony/Dropbox/tagger/comictagger/mac/build/pyi.darwin/ComicTagger/out00-PYZ.pyz/comicvinecacher", line 139, in get_search_results
sqlite3.OperationalError: no such table: VolumeSearchCache
DP812- Posts : 74
Join date : 2012-12-08
Re: 0.9.3 - OperationalError
Go to settings/preferences, and clear the cache. I think that might be what's going on.
Re: 0.9.3 - OperationalError
That's strange. I cleared the cache when I first opened the new version like the instructions said and the problem still happened. Tried clearing it again just now and now it works.ComicTagger wrote:Go to settings/preferences, and clear the cache. I think that might be what's going on.
DP812- Posts : 74
Join date : 2012-12-08
Re: 0.9.3 - OperationalError
What about this error?
Here's another one:
Traceback (most recent call last):
File "<string>", line 484, in <module>
File "<string>", line 458, in main
File "<string>", line 162, in cli_mode
File "<string>", line 335, in process_file_cli
File "/Users/tony/Dropbox/tagger/comictagger/mac/build/pyi.darwin/ComicTagger/out00-PYZ.pyz/issueidentifier", line 335, in search
File "/Users/tony/Dropbox/tagger/comictagger/mac/build/pyi.darwin/ComicTagger/out00-PYZ.pyz/issuestring", line 61, in asString
TypeError: bad operand type for abs(): 'NoneType'
Here's another one:
Traceback (most recent call last):
File "<string>", line 484, in <module>
File "<string>", line 458, in main
File "<string>", line 162, in cli_mode
File "<string>", line 335, in process_file_cli
File "/Users/tony/Dropbox/tagger/comictagger/mac/build/pyi.darwin/ComicTagger/out00-PYZ.pyz/issueidentifier", line 262, in search
File "/Users/tony/Dropbox/tagger/comictagger/mac/build/pyi.darwin/ComicTagger/out00-PYZ.pyz/comicvinetalker", line 89, in searchForSeries
File "/Users/tony/Dropbox/tagger/comictagger/mac/build/pyi.darwin/ComicTagger/out00-PYZ.pyz/comicvinecacher", line 142, in get_search_results
sqlite3.ProgrammingError: You must not use 8-bit bytestrings unless you use a text_factory that can interpret 8-bit bytestrings (like text_factory = str). It is highly recommended that you instead just switch your application to Unicode strings.
DP812- Posts : 74
Join date : 2012-12-08
Re: 0.9.3 - OperationalError
Looks like some bugs alright. A little context for each one would definitely be helpful to re-create it here, though. What was the input that made those errors?
Re: 0.9.3 - OperationalError
/Applications/ComicTagger.app/Contents/MacOS/ComicTagger -s -t cbl -f -o -i and then I dragged and dropped the file in question. These files also caused the GUI to hang.
DP812- Posts : 74
Join date : 2012-12-08
Re: 0.9.3 - OperationalError
Well, I think I have some idea of the root cause, but knowing the specific filenames would probably help me a lot.
It looks like one doesn't have it's issue number (if any) parsed properly, and the other might have unicode characters in the filename? Assuming that the comics don't already have tags in them, all I need are the exact filenames. Thanks!
It looks like one doesn't have it's issue number (if any) parsed properly, and the other might have unicode characters in the filename? Assuming that the comics don't already have tags in them, all I need are the exact filenames. Thanks!
Re: 0.9.3 - OperationalError
DP,
If you still know the file names of the issues that caused the last two errors that you posted, it would help me a lot to use them to test with. Just did a bit of work on managing unicode related stuff and more.
Thanks!
If you still know the file names of the issues that caused the last two errors that you posted, it would help me a lot to use them to test with. Just did a bit of work on managing unicode related stuff and more.
Thanks!
Re: 0.9.3 - OperationalError
Sorry, I'm not sure. I've gone through and tagged through so many books and I can't seem to find my list of problematic files. If I find it, I'll let you know.
DP812- Posts : 74
Join date : 2012-12-08
Re: 0.9.3 - OperationalError
Understood. For future reference, when you do encounter problems, please share filenames along with any other pertinent info, as it's likely related to the root cause of a lot of issues.
Happy New Year!
Happy New Year!
Re: 0.9.3 - OperationalError
You mean files or filenames? Because before I went through to tag everything, I renamed all my filenames to be uniform. They're all in the following format: Series Name v0 000.cbz.
DP812- Posts : 74
Join date : 2012-12-08
Re: 0.9.3 - OperationalError
I mean the actual file names. Not just the format. Then I can test what is happening, assuming your files don't already have tags.
For example, a name with non-English letters might have caused one of the problems you reported. I was testing with "El Capitán Trueno 12.cbr" to simulate what I thought might be happening in that case, but knowing the exact case would have helped.
In other situations, the problem might be that ComicTagger is choking on some data from Comic Vine, and if I know what the filename is, I can inspect the Comic Vine records that got fetched.
For example, a name with non-English letters might have caused one of the problems you reported. I was testing with "El Capitán Trueno 12.cbr" to simulate what I thought might be happening in that case, but knowing the exact case would have helped.
In other situations, the problem might be that ComicTagger is choking on some data from Comic Vine, and if I know what the filename is, I can inspect the Comic Vine records that got fetched.
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|