Open RoHei opened 1 year ago
hello @RoHei !
thank you for reporting this.
To give us a bit more details about the issue, could you share with us the version of jsonchema
package you are using inside the container ?
(you need to run pip show jsonschema
) inside the container or check the version in your pipfile-lock.json.
Did you run the installation with allow_prereleases = True (in your Pipfile) ?
Thanks for the quick reply. In the Pipfile.lock
I see this version.
"jsonschema": {
"hashes": [
"sha256:74655a97c41753163c195ac342ceb91168d6b719b123ebc1bbfa3cff6d103481",
"sha256:dae26a6aaf4b278b1d1aafd892aee9f16604971497a03c566c365e9ea4dc2c33"
],
"markers": "python_version >= '3.8'",
"version": "==4.18.0a3"
},
Furthermore, in my Pipifile, allow_prepreleases
is set to False
.
Thanks for the quick reply. In the
Pipfile.lock
I see this version."jsonschema": { "hashes": [ "sha256:74655a97c41753163c195ac342ceb91168d6b719b123ebc1bbfa3cff6d103481", "sha256:dae26a6aaf4b278b1d1aafd892aee9f16604971497a03c566c365e9ea4dc2c33" ], "markers": "python_version >= '3.8'", "version": "==4.18.0a3" },
Furthermore, in my Pipifile,
allow_prepreleases
is set toFalse
.
there is something wrong with dependency builder in your environment, because as you see the alpha version (pre release) of jsonschema was installed (despite not allowing pre-releases in your pipfile), and this alpha version is known to contain breaking changes. If you make sure you have the stable release of jsonschema dependency installed (4.17.0), the error should not appear.
This issue was automatically marked as stale.
Package version (if known): 2.2
Describe the bug
I deployed InvenioRDM using Docker container according to the docs by running:
invenio-cli containers start --lock --setup
. All containers start and the page is displayed on my virtual machine nicely (Ubuntu Server 20.04. LTS). I can also create a user and generate an API key.However, when I want to create a new record draft and click on "Save draft" or "Publish", the page returns:
As a consequence, the draft is not created/saved. However, when looking up in the docker container, I can identify the following error message that seems to be highly related as it occurrs after clicking the button:
However, I also logged in to the SQL-Database on the server but there the current user exists, so I would suppose that it is not an database-lookup issue. Also it does make no difference, if I enter creators in the template as the error always occurs.
Steps to Reproduce
Expected behavior
Expecting that the record would be saved.
Additional Information
The configuration file was only changed slightly. One section affects the allowed servers and the others the authentication, where I set:
SECURITY_LOGIN_WITHOUT_CONFIRMATION = False
, but I don't think that this is related.