##// END OF EJS Templates
caches: use individual namespaces per user to prevent beaker caching problems....
caches: use individual namespaces per user to prevent beaker caching problems. - especially for mysql in case large number of data in caches there could be critical errors storing cache, and thus preventing users from authentication. This is caused by the fact that we used single namespace for ALL users. It means it grew as number of users grew reaching mysql single column limit. This changes the behaviour and now we use namespace per-user it means that each user-id will have it's own cache namespace fragmenting maximum column data to a single user cache. Which we should never reach.

File last commit:

r2487:fcee5614 default
r2572:5b07455a default
Show More
__init__.py
82 lines | 2.7 KiB | text/x-python | PythonLexer
# Copyright (C) 2016-2018 RhodeCode GmbH
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU Affero General Public License, version 3
# (only), as published by the Free Software Foundation.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU Affero General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
#
# This program is dual-licensed. If you wish to learn more about the
# RhodeCode Enterprise Edition, including its added features, Support services,
# and proprietary license terms, please see https://rhodecode.com/licenses/
import logging
from pyramid.threadlocal import get_current_registry
from rhodecode.events.base import RhodecodeEvent
log = logging.getLogger(__name__)
def trigger(event, registry=None):
"""
Helper method to send an event. This wraps the pyramid logic to send an
event.
"""
# For the first step we are using pyramids thread locals here. If the
# event mechanism works out as a good solution we should think about
# passing the registry as an argument to get rid of it.
registry = registry or get_current_registry()
registry.notify(event)
log.debug('event %s triggered using registry %s', event, registry)
# Until we can work around the problem that VCS operations do not have a
# pyramid context to work with, we send the events to integrations directly
# Later it will be possible to use regular pyramid subscribers ie:
# config.add_subscriber(
# 'rhodecode.integrations.integrations_event_handler',
# 'rhodecode.events.RhodecodeEvent')
# trigger(event, request.registry)
from rhodecode.integrations import integrations_event_handler
if isinstance(event, RhodecodeEvent):
integrations_event_handler(event)
from rhodecode.events.user import ( # noqa
UserPreCreate,
UserPostCreate,
UserPreUpdate,
UserRegistered
)
from rhodecode.events.repo import ( # noqa
RepoEvent,
RepoPreCreateEvent, RepoCreateEvent,
RepoPreDeleteEvent, RepoDeleteEvent,
RepoPrePushEvent, RepoPushEvent,
RepoPrePullEvent, RepoPullEvent,
)
from rhodecode.events.repo_group import ( # noqa
RepoGroupEvent,
RepoGroupCreateEvent,
RepoGroupUpdateEvent,
RepoGroupDeleteEvent,
)
from rhodecode.events.pullrequest import ( # noqa
PullRequestEvent,
PullRequestCreateEvent,
PullRequestUpdateEvent,
PullRequestCommentEvent,
PullRequestReviewEvent,
PullRequestMergeEvent,
PullRequestCloseEvent,
)