Project

General

Profile

Actions

Support #7632

closed

Mentat dependencies upgrade

Added by Jakub Judiny over 1 year ago. Updated 12 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Installation
Target version:
Start date:
02/28/2023
Due date:
% Done:

0%

Estimated time:
To be discussed:
No

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.

Wiki: Mentat dependencies upgrade


Files


Related issues

Related to Mentat - Bug #7619: Flask Deprecation warningsIn Progress12/14/2022

Actions
Related to Mentat - Support #7554: The Bootstrap version used in Mentat is EOLClosedJakub Maloštik05/04/202305/04/2023

Actions
Related to Mentat - Support #7622: Forms throw TypeError in Flask-WTF 1.1.0+ClosedJakub Judiny01/18/2023

Actions
Related to Mentat - Task #7545: Review SQLAlchemy vs Flask-SQLAlchemy consolidation optionsDeferredJakub Judiny01/06/2022

Actions
Related to Mentat - Support #7642: Upgrade Flask-SQLAlchemyClosedJakub Judiny04/13/2023

Actions
Related to Mentat - Support #7643: Replace bsddb3 with berkeleydb or remove it altogetherClosedJakub Judiny04/13/2023

Actions
Related to Mentat - Support #7650: Replace nvd3 Javascript libraryIn ReviewJakub Maloštik05/02/2023

Actions
Actions #1

Updated by Jakub Judiny over 1 year ago

  • Description updated (diff)
Actions #2

Updated by Pavel Kácha over 1 year ago

  • Related to Bug #7619: Flask Deprecation warnings added
  • Related to Support #7554: The Bootstrap version used in Mentat is EOL added
Actions #3

Updated by Radko Krkoš over 1 year ago

  • Related to Support #7622: Forms throw TypeError in Flask-WTF 1.1.0+ added
Actions #4

Updated by Jakub Judiny over 1 year ago

  • Status changed from New to In Progress
Actions #5

Updated by Radko Krkoš about 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

Actions #6

Updated by Jakub Judiny about 1 year ago

  • Related to Task #7545: Review SQLAlchemy vs Flask-SQLAlchemy consolidation options added
Actions #7

Updated by Jakub Judiny about 1 year ago

Actions #8

Updated by Jakub Judiny about 1 year ago

  • Related to Support #7643: Replace bsddb3 with berkeleydb or remove it altogether added
Actions #9

Updated by Rajmund Hruška about 1 year ago

  • Status changed from In Progress to Resolved
Actions #10

Updated by Rajmund Hruška about 1 year ago

I switched to your branch and created the image from scratch with vagrant up. The GUI is broken for me.

Actions #11

Updated by Jakub Judiny about 1 year ago

  • Status changed from Feedback to In Progress
Actions #12

Updated by Jakub Judiny about 1 year ago

  • Status changed from In Progress to Resolved
Actions #13

Updated by Jakub Judiny about 1 year ago

  • Related to Support #7650: Replace nvd3 Javascript library added
Actions #14

Updated by Rajmund Hruška about 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)

Actions #15

Updated by Jakub Judiny about 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.

Actions #16

Updated by Jakub Judiny about 1 year ago

  • Status changed from In Progress to Resolved
Actions #17

Updated by Rajmund Hruška about 1 year ago

  • Target version changed from Backlog to 2.11

While working on #7651, I noticed it is possible to remove Popper.js (deprecated) and Tippy.js and instead use @popperjs/core, which we already have in our dependencies. So I removed them in e396fd45.

Actions #18

Updated by Rajmund Hruška about 1 year ago

  • Status changed from Resolved to In Review
Actions #19

Updated by Rajmund Hruška 12 months ago

  • Status changed from In Review to Closed
Actions

Also available in: Atom PDF