API getVersion returning 500 error #229
Assignees
Labels
Comments
evilhero
added a commit
that referenced
this issue
Mar 27, 2020
barbequesauce
added a commit
that referenced
this issue
Mar 27, 2020
FIX(#229) API response was not being handled properly by cherrypy
|
Pulled latest and API seems to be working fine (for the calls I use) Thanks. |
|
great - do you mind closing the case please? |
barbequesauce
added a commit
that referenced
this issue
Apr 8, 2020
* FIX: default sort order not in descending order on history page * fix history default sort order * patch for carepackage to ensure removal of multiple keyed items on a single log entry * FIX: forgot the file option * FIX: fix for telegram notifs failing due to max retries exceeded, which would then lock the pp-queue * FIX: fix for DDL download breaking for some series * FIX: fix for simultaneous searches firing off when done using different search methods * FIX:(#225) If git wasn't in environment path, would accept failed output as a valid response and attempt to use that as commit/branch information * FIX: fix for incorrect error reference when encountering an SQlite error trap * FIX(#229) API response was not being handled properly by cherrypy * FIX:(#231) Carepackage fails to perform cleanup of temporary files and causes an error on Windows systems due to locked files * Fix crash if Mylar sees book that's a symlink to a nonexistant file * optional config.ini choice to use either [CVDBxxxx] or [Issue ID xxxxxx] (the default) in the notes field when metatagging. * FIX: provider_order would not respect ini settings (would tend to reorder based on code priority vs ini priority) Co-authored-by: Barbeque Sauce <saucebarbeque@hotmail.com> Co-authored-by: Bran Tyslerx <btx@mxyzptlk.net>
barbequesauce
added a commit
that referenced
this issue
Apr 23, 2020
* FIX: default sort order not in descending order on history page * fix history default sort order * patch for carepackage to ensure removal of multiple keyed items on a single log entry * FIX: forgot the file option * FIX: fix for telegram notifs failing due to max retries exceeded, which would then lock the pp-queue * FIX: fix for DDL download breaking for some series * FIX: fix for simultaneous searches firing off when done using different search methods * FIX:(#225) If git wasn't in environment path, would accept failed output as a valid response and attempt to use that as commit/branch information * FIX: fix for incorrect error reference when encountering an SQlite error trap * FIX(#229) API response was not being handled properly by cherrypy * FIX:(#231) Carepackage fails to perform cleanup of temporary files and causes an error on Windows systems due to locked files * Fix crash if Mylar sees book that's a symlink to a nonexistant file * optional config.ini choice to use either [CVDBxxxx] or [Issue ID xxxxxx] (the default) in the notes field when metatagging. * FIX: provider_order would not respect ini settings (would tend to reorder based on code priority vs ini priority) * fix popup javascript error in importresults datatables due to extraneous html * Performance Tuning - speed up weekly pull check which was locking database * fix typo in search which would cause a traceback * removed logging line that captured data * update carepackage to ensure complete removal * Eliminate endless loop in sabnzb queue (#251) * Eliminate endless loop in nzb queue * Eliminate double for loop & ensure we use the correct nzb id based on downloader configuration * Handle paused sab queue by throwing a warning * fix a crash Co-authored-by: Barbeque Sauce <saucebarbeque@hotmail.com> Co-authored-by: Bran Tyslerx <btx@mxyzptlk.net> Co-authored-by: Evan Roth <evan.roth@gmail.com> Co-authored-by: AJ Slater <aj@slater.net> Co-authored-by: mylar3 <59849447+mylar3@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
calling getVersion in the mylar API returns a 500 error
CarePackage
carepackage.zip
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: