Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InvalidRequestError: Entity '<class 'ckanext.pages.db._Page'>' has no property 'group_id' #106

Closed
fishbone1 opened this issue Feb 16, 2021 · 3 comments · Fixed by #112
Closed

Comments

@fishbone1
Copy link

CKAN version 2.8.4
ckanext-pages commit 06d8ef5

Each single request to our CKAN instance causes lots of entries in the error log. The exception is caused when creating the navigation bar:

  (...)
  File "(...)", line 16, in block "header_site_navigation_tabs"
    {{ h.build_nav_main(
  File "/usr/lib/ckan/default/src/ckanext-pages/ckanext/pages/plugin.py", line 43, in build_pages_nav_main
    pages_list = toolkit.get_action('ckanext_pages_list')(None, {'order': True, 'private': False})
  File "/usr/lib/ckan/default/src/ckan/ckan/logic/__init__.py", line 466, in wrapped
    result = _action(context, data_dict, **kw)
  File "/usr/lib/ckan/default/src/ckanext-pages/ckanext/pages/actions.py", line 233, in pages_list
    return _pages_list(context, data_dict)
  File "/usr/lib/ckan/default/src/ckanext-pages/ckanext/pages/actions.py", line 109, in _pages_list
    out = db.Page.pages(**search)
  File "/usr/lib/ckan/default/src/ckanext-pages/ckanext/pages/db.py", line 36, in pages
    query = query.filter_by(**kw)
  File "/usr/lib/ckan/default/lib/python2.7/site-packages/sqlalchemy/orm/query.py", line 1562, in filter_by
    for key, value in kwargs.items()]
  File "/usr/lib/ckan/default/lib/python2.7/site-packages/sqlalchemy/orm/base.py", line 383, in _entity_descriptor
        (description, key)
InvalidRequestError: Entity '<class 'ckanext.pages.db._Page'>' has no property 'group_id'

The version is from 2018, but the responsible code hasn't been changed, as far as I can see.

@Zharktas
Copy link
Member

We've been seeing this too, there might be some race condition somewhere in the database initialization as usually this is fixed for us by restarting everything.

@lhuanluz
Copy link

Same problem, had to disable the plugin

@ccancellieri
Copy link

+1 we've this plugin in production, thanks to work over it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants