Medusa: [APP SUBMITTED]: TypeError: a bytes-like object is required, not 'str'

[jstorgaard]

INFO

Python Version: 3.7.5 (default, Oct 17 2019, 12:25:15) [GCC 8.3.0]
Operating System: Linux-4.9.0-11-amd64-x86_64-with
Locale: UTF-8
Branch: master
Database: 44.14
Commit: pymedusa/Medusa@918cfe7ce01808499585ffe6c1356fd5ed369f76
Link to Log: https://gist.github.com/8f765e724a442e6d91ed29584352638d

ERROR

2019-11-12 10:48:11 ERROR    TORNADO :: [918cfe7] API :: TypeError("a bytes-like object is required, not 'str'")
Traceback (most recent call last):
  File "/app/medusa/medusa/server/api/v1/core.py", line 165, in get
    out_dict = _call_dispatcher(args, kwargs)
  File "/app/medusa/medusa/server/api/v1/core.py", line 235, in call_dispatcher
    cur_out_dict = func(cur_args, cur_kwargs).run()  # call function and get response
  File "/app/medusa/medusa/server/api/v1/core.py", line 1336, in run
    proc_type=self.type
  File "/app/medusa/medusa/process_tv.py", line 65, in run
    return ProcessResult(path, process_method).process(force=force, **kwargs)
  File "/app/medusa/medusa/process_tv.py", line 188, in process
    ignore_subs=ignore_subs)
  File "/app/medusa/medusa/process_tv.py", line 378, in process_files
    self.process_media(path, self.video_files, force, is_priority, ignore_subs)
  File "/app/medusa/medusa/process_tv.py", line 599, in process_media
    self.result = processor.process()
  File "/app/medusa/medusa/post_processor.py", line 1281, in process
    notifiers.emby_notifier.update_library(ep_obj.series)
  File "/app/medusa/medusa/notifiers/emby.py", line 131, in update_library
    log.debug('EMBY: HTTP response: {0}', resp.content.replace('\n', ''))
TypeError: a bytes-like object is required, not 'str'

---

_STAFF NOTIFIED_: @pymedusa/support @pymedusa/moderators

[p0psicles]

@medariox resp.text ?

[medariox]

Yes

[noodle-]

@jstorgaard Why are you using such an outdated version of Medusa?

[jstorgaard]

@jstorgaard Why are you using such an outdated version of Medusa?

Should be pretty recent? Using latest from linuxserver/medusa.

[noodle-]

@jstorgaard While hovering over your commit in the OP it shows you're using release version 0.2.14 which has been released almost a year ago.

The latest release when running from source is 0.3.6 as seen here

And the latest docker image update (as you seem to be running?) seems to be the same, see here

I'm not saying this is the issue here btw, I'm just curious as I've seen this in a few other bug reports too. :)

[jstorgaard]

@noodle- Yeah, I'm not sure what's going on with that.
Looking at the changelog it says that a new feature of 0.3.6 is Discord notification.
I got that in the version that submitted this bug report, so it should be 0.3.6.

[medariox]

@jstorgaard
You get the notification no matter which version you are running. You should really look into updating your Medusa install, as we don't provide support for outdated versions.

[jstorgaard]

@jstorgaard
You get the notification no matter which version you are running.

It says on the release page that the Discord notification is a new feature of 0.3.6?

What docker container is up to date? I thought the one from linuxserver was?

[p0psicles]

Did you pull the latest image from linuxserver?

[jstorgaard]

Did you pull the latest image from linuxserver?

Yes
jstorgaard@docker:~/docker$ docker pull linuxserver/medusa:latest
latest: Pulling from linuxserver/medusa
Digest: sha256:60f721ee89d905f2420cd92fe0e5c90e56edc184ec1802b6cc83fab7748b34d8
Status: Image is up to date for linuxserver/medusa:latest
docker.io/linuxserver/medusa:latest

[medariox]

Oh, you are using the linuxserver image. In that case it can indeed happen that an old version is being erroneously shown. I'll see if I can get that fixed for the next release.