These are chat archives for inveniosoftware/invenio
after_record_indexdue to the bulk processing - i.e. you would have to call the
after_record_indexonly after the ES bulk request succeeded - i.e. you’ll have to keep track of records which succeeeded the bulk indexing and which did not. Also, if you plan processing these immediately, you won’t actually be sure that the record is available in the ES index at that point in time….
after_before_record_indexsignal. I.e. after the
before_record_indexhas enhanced the JSON and populated with plenty of new value, we can intercept that and do further actions.
push-to-orcidwas a receiver for
after_record_enhancewhich is not fired anywhere but only in specific overlays, then users of such module would be surprised for it to not work if they don't have any enhancer. In that case they would need to create a stub enhancer just for the sake of firing the
hey guys, I am creating our db but apparently the
transaction tables are not created
SQLAlchemy-Continuum==1.2.4 installed and this is our config for the DB
SQLALCHEMY_DATABASE_URI = os.environ.get( "SQLALCHEMY_DATABASE_URI", "postgresql+psycopg2://localhost/cds") SQLALCHEMY_ECHO = False SQLALCHEMY_TRACK_MODIFICATIONS = True
invenio-oauth2serveras a requirement
pip install -e .[postgresql]right? :-)
$ pip install requirements-builder pip-tools $ requirements-builder --level=pypi setup.py > top-requirements.txt $ pip-compile top-requirements.txt > all-requirements.txt $ pip install -r all-requirements.txt $ grep SQLAlchemy-Continuum all-requirements.txt SQLAlchemy-Continuum==1.2.4
I did this before
$ pip freeze | grep SQLAl Flask-SQLAlchemy==2.1 SQLAlchemy==1.0.12 SQLAlchemy-Continuum==1.2.4 SQLAlchemy-Utils==0.32.4
I’ll try this now
SQLAlchemy-Continuumis not in
invenio-records['postgresql']in your requirements?
invenio-db[postgresql,versioning], should I add also this other one?
pytest-runnerand manually building the
PytestCMD? Is it still valid?