Skip to content
This repository has been archived by the owner on Jun 20, 2018. It is now read-only.

Condition Sets not always being registered #19

Closed
jjchoy opened this issue Aug 2, 2011 · 4 comments
Closed

Condition Sets not always being registered #19

jjchoy opened this issue Aug 2, 2011 · 4 comments

Comments

@jjchoy
Copy link

jjchoy commented Aug 2, 2011

I'm using gargoyle with nexus. It works perfectly on my development machine. On my production environment (mod-wsgi daemon mode) the condition sets only seem to be getting registered in some of the processes (at least that is what I think is happening - if I open the gargoyle admin page for a switch and keep reloading the page the conditions only show up sometimes).

I have them both in my INSTALLED APPS

INSTALLED_APPS = (
    ...,
    'nexus',
    'gargoyle',
    ...,
)

and in my urls.py:

import nexus
nexus.autodiscover()

Any ideas on what the problem could be?

@dcramer
Copy link
Collaborator

dcramer commented Aug 2, 2011

I've looked into this and don't have an answer yet. We're doing the same approach as django.contrib.admin and many other things so it's a bit confusing. Making _registry a class level variable definitely solves it, but then we have issues with isolation.

@jjchoy
Copy link
Author

jjchoy commented Aug 3, 2011

Thanks dcramer. Let me know if there is anything I can do to help out

@jjchoy jjchoy closed this as completed Aug 3, 2011
@jjchoy jjchoy reopened this Aug 3, 2011
@jjchoy
Copy link
Author

jjchoy commented Aug 3, 2011

oops, didn't mean to close it

@jjchoy
Copy link
Author

jjchoy commented Aug 12, 2011

Thanks!

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

No branches or pull requests

2 participants