Project

General

Profile

Actions
Copy link

Support #7632

closed

Mentat dependencies upgrade

Added by Jakub Judiny almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Jakub Judiny
Category:
Installation
Target version:
2.11
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

Download all files
Screenshot from 2023-04-24 11-08-01.png (84.7 KB) Screenshot from 2023-04-24 11-08-01.png Rajmund Hruška, 04/24/2023 11:10 AM
Screenshot from 2023-04-24 11-08-23.png (60.5 KB) Screenshot from 2023-04-24 11-08-23.png Rajmund Hruška, 04/24/2023 11:10 AM

Related issues

Related to Mentat - Task #7619: Flask Deprecation warningsClosedRajmund Hruška12/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 libraryClosedJakub Maloštik05/02/2023

Actions
Actions
Copy link
 #1

Updated by Jakub Judiny almost 2 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Pavel Kácha almost 2 years ago

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

Updated by Radko Krkoš almost 2 years ago

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

Updated by Jakub Judiny almost 2 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #5

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

Actions
Copy link
 #6

Updated by Jakub Judiny over 1 year ago

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

Updated by Jakub Judiny over 1 year ago

Actions
Copy link
 #8

Updated by Jakub Judiny over 1 year ago

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

Updated by Rajmund Hruška over 1 year ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #10

Updated by Rajmund Hruška over 1 year ago

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

Actions
Copy link
 #11

Updated by Jakub Judiny over 1 year ago

  • Status changed from Feedback to In Progress
Actions
Copy link
 #12

Updated by Jakub Judiny over 1 year ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #13

Updated by Jakub Judiny over 1 year ago

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

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)

Actions
Copy link
 #15

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.

Actions
Copy link
 #16

Updated by Jakub Judiny over 1 year ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #17

Updated by Rajmund Hruška over 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
Copy link
 #18

Updated by Rajmund Hruška over 1 year ago

  • Status changed from Resolved to In Review
Actions
Copy link
 #19

Updated by Rajmund Hruška over 1 year ago

  • Status changed from In Review to Closed
Actions
Copy link

Also available in: Atom PDF