automatic-ripping-machine: Clicking "Change Settings" Button in Web Portal Generates an AttributeError

Description

When I click the “Change Settings” button in the web portal I get the following error on the webpage: AttributeError: ‘Config’ object has no attribute ‘pretty_table’

Environment

Ubuntu 18.04.5 LTS running on bare metal ARM version 2.2.0-dev

Log file

Here is what is output on the webpage:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 2464, in __call__
    return self.wsgi_app(environ, start_response)
  File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 2450, in wsgi_app
    response = self.handle_exception(e)
  File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 1867, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/lib/python3.6/dist-packages/flask/_compat.py", line 39, in reraise
    raise value
  File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 2447, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 1952, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 1821, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/lib/python3.6/dist-packages/flask/_compat.py", line 39, in reraise
    raise value
  File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 1950, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 1936, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/opt/arm/arm/ui/routes.py", line 103, in changeparams
    app.logger.debug(config.pretty_table())
AttributeError: 'Config' object has no attribute 'pretty_table'

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 19 (9 by maintainers)

Commits related to this issue

Most upvoted comments

I apologise. I was mistaken, this is a bug in the coding.

I have made a mistake with the last commited pull request. That line is in the current repo, but it shouldn’t be as the models.py doesn’t have the new code to handle it.

You can edit the routes.py and remove line 103 this should fix the error.

EDIT: Also for clarity I have also made a mistake with the readme. It is incorrectly referencing the v2.2 from my own fork of the repo. This repo doesn’t have a branch v2.2 that’s the reason it’s erroring out.