Support #7632
closedMentat dependencies upgrade
0%
Description
A lot of dependencies are old and pinned to some version. The goal is to check what should be upgraded and what problems could it produce.
Files
Related issues
Updated by Pavel Kácha over 1 year ago
- Related to Task #7619: Flask Deprecation warnings added
- Related to Support #7554: The Bootstrap version used in Mentat is EOL added
Updated by Radko Krkoš over 1 year ago
- Related to Support #7622: Forms throw TypeError in Flask-WTF 1.1.0+ added
Updated by Radko Krkoš over 1 year ago
The dotenv
package is an optional dependency of pyzenkit
, which is programmed in a way to handle it missing:
https://gitlab.cesnet.cz/search?search=dotenv&nav_source=navbar&project_id=637&group_id=1886&search_code=true&repository_ref=master
Updated by Jakub Judiny over 1 year ago
- Related to Task #7545: Review SQLAlchemy vs Flask-SQLAlchemy consolidation options added
Updated by Jakub Judiny over 1 year ago
- Related to Support #7642: Upgrade Flask-SQLAlchemy added
Updated by Jakub Judiny over 1 year ago
- Related to Support #7643: Replace bsddb3 with berkeleydb or remove it altogether added
Updated by Rajmund Hruška over 1 year ago
- Status changed from In Progress to Resolved
Updated by Rajmund Hruška over 1 year ago
- File Screenshot from 2023-04-24 11-08-01.png Screenshot from 2023-04-24 11-08-01.png added
- File Screenshot from 2023-04-24 11-08-23.png Screenshot from 2023-04-24 11-08-23.png added
- Status changed from Resolved to Feedback
I switched to your branch and created the image from scratch with vagrant up
. The GUI is broken for me.
Updated by Jakub Judiny over 1 year ago
- Status changed from Feedback to In Progress
Updated by Jakub Judiny over 1 year ago
- Status changed from In Progress to Resolved
Updated by Jakub Judiny over 1 year ago
- Related to Support #7650: Replace nvd3 Javascript library added
Updated by Rajmund Hruška over 1 year ago
- Status changed from Resolved to In Progress
There is some error when running pylint
which (probably) causes non-zero exit status:
.pylintrc-lib:1:0: E0015: Unrecognized option found: argument-name-hint, attr-name-hint, class-attribute-name-hint, class-name-hint, const-name-hint, function-name-hint, inlinevar-name-hint, method-name-hint, module-name-hint, variable-name-hint, no-space-check (unrecognized-option)
pylint: Command line or configuration file:1: UserWarning: Specifying exception names in the overgeneral-exceptions option without module name is deprecated and support for it will be removed in pylint 3.0. Use fully qualified name (maybe 'builtins.Exception' ?) instead.
.pylintrc-bin:1:0: E0015: Unrecognized option found: argument-name-hint, attr-name-hint, class-attribute-name-hint, class-name-hint, const-name-hint, function-name-hint, inlinevar-name-hint, method-name-hint, module-name-hint, variable-name-hint, no-space-check (unrecognized-option)
pylint: Command line or configuration file:1: UserWarning: Specifying exception names in the overgeneral-exceptions option without module name is deprecated and support for it will be removed in pylint 3.0. Use fully qualified name (maybe 'builtins.Exception' ?) instead.
Also in the change introduced in a1364b21, I think coverage
should be called from the variable like this: $(COVERAGE)
Updated by Jakub Judiny over 1 year ago
Rajmund Hruška wrote in #note-14:
There is some error when running
pylint
which (probably) causes non-zero exit status:[...]
[...]
Also in the change introduced in a1364b21, I think
coverage
should be called from the variable like this:$(COVERAGE)
I fixed the warnings, but it wasn't the cause of the non-zero exit status. The same exit code is present for example in the devel branch, so it is not anything new.
Updated by Jakub Judiny over 1 year ago
- Status changed from In Progress to Resolved
Updated by Rajmund Hruška over 1 year ago
- Target version changed from Backlog to 2.11
Updated by Rajmund Hruška over 1 year ago
- Status changed from Resolved to In Review
Updated by Rajmund Hruška over 1 year ago
- Status changed from In Review to Closed