canvasapi.exceptions.ResourceDoesNotExist: Not Found

[bigtendons8]

Received this error when running.

file.download(path + sanitize_filename(file.filename))
  File "/usr/local/lib/python3.12/site-packages/canvasapi/file.py", line 30, in download
    response = self._requester.request("GET", _url=self.url)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/canvasapi/requester.py", line 255, in request
    raise ResourceDoesNotExist("Not Found")
canvasapi.exceptions.ResourceDoesNotExist: Not Found

Running with Docker.

I understand this might not be being actively developed but I think it is quite a useful application

[eric8he]

What command did you run to get this error?

The URL param should just be the home/root of your org's Canvas page.

Ex.
https://canvas.YOURINSTITUTION.edu/

I got the error when I tried to put in my course ID in the URL.

[john-hix]

Hi, there. @bigtendons8 is right, this isn't a project I actively maintain. I can't even say I'll be able to respond more than this single message.

As a user, I would try constraining which courses you attempt to download would help you do a process of elimination to find out if it's a particular course that is causing the not found error. You can specify which courses to download by getting their course ID(s) from their Canvas URLs, then passing the IDs as a comma-separated list, as the README indicates.

The approach above isn't at all ideal, since your instructor(s) would have had to keep working links for everything in the course, and who does that?

As a developer, I would go for the root cause, which seems to be incomplete handling of the ResourceDoesNotExist error (it's done in a few places in the script, and - if I recall correctly - I wasn't happy with how it was done when I wrote it that way. If someone wants to open a PR that improves how those errors are handled, I'd merge it, all else being equal.

[EDIT] Specifically, we need to know why the ResourceDoesNotExist error is not getting caught. @bigtendons8 may be able to provide additional context to whomever might try to track down why the error is not caught properly.

Thanks for reports, @eric8he and @bigtendons8 .