remove upper limit #174
Draft
remove upper limit #174
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
utnapischtim
force-pushed
the
remove-upper-limit
branch
4 times, most recently
from
ae5726d
to
b9b8b3d
Compare
* it is not working anymore with localproxy and it seams not necessary
* use the proxy file instead of creating the _db variable in both files * this removes a DeprecationWarning from flask-sqlalchemy, which states that the support of the use '.db' will be removed
* the error indicates that db.init_app is not called, but it is and it works in other contexts. It may that the `db = invenio_db = shared.db` line in conftest.py is not working as expected anymore. The only found solution is this. The drawback is, if that is the only solution it has to be done also in the other packages which are using this function. With the default value it is backward compatible but as the tests indicates it may not work without adding the db parameter to the function call
* added D202, pydocstyle and black do not habe the same opinion * remove warning by using StringEncryptedType instead of EncryptedType. This removes a warning and there is further a notice in the code that the base type of EncryptedType will change in the future and it is better to replace it with StringEncryptedType
* the problem is, that assert calls an function which leads to an not moving forward test on mysql8. it works on postgresql and mysql5 but not mysql8.
* the new name better reflects the intended use
* this change makes it possible to import the MockEntryPoints from an independend file. this class is used in two tests but defined in one of them. placing it into a separated file makes it independent.
* the complete error message is "Table 'early_class' is already defined for this MetaData instance. Specify 'extend_existing=True' to redefine options and columns on an existing Table object." adding the extend_existing=True doesn't solve the problem. The error was there because of the reuse introduced by the @pytest.mark.parametrize decorator.
* the complete error message is "Table 'versioned_article_b_version' is already defined for this MetaData instance. Specify 'extend_existing=True' to redefine options and columns on an existing Table object." adding the extend_existing=True doesn't solve the problem. moving the import of the models to the top of the file did it
* this leads to the problem that the program couldn't connect to the database
utnapischtim
force-pushed
the
remove-upper-limit
branch
from
780985f
to
1b20e07
Compare
* for explanations see the comments in the code
utnapischtim
force-pushed
the
remove-upper-limit
branch
from
1b20e07
to
9d87e8b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTE
worked locally with flask>=3.0.0, werkzeug>=3.0.0, flask-alemib>=3.0.0. further updated invenio-base is necessary (otherwise flask and werkzeug couldn't be updated)
ATTENTION
tests are not independent. if tests in
test_db.pyfail tests intest_versioningfail too although they would work without problemsDISCUSSION
some fixes should be discussed so review carfully
KNOWN issues