Taylor Hakes

I am testing with the debug error view, so maybe related to this? https://github.com/rollbar/pyrollbar/issues/180 . Not sure because I can't see clubhouse.

Hey everyone. I am having the same issue and just came across this. It does not appear that `all` is supported out of the box `Error : UnSupportedSettingError: validator/changeset: must_exclude.all...

@luizperes I don't think this is accurate. ``` try { } // no catch nor effect handler return (type); { // escoped block } ``` You can even try it...

This is supported. You need to use the URL though. ```python SESSION_REDIS = dict( url=f"rediss://:{REDIS_SESSION_PASSWORD}@{REDIS_SESSION_HOST}:{REDIS_SESSION_PORT}/{REDIS_SESSION_DB}" ) ```

It looks like you need access to system tables to query foreign keys dynamically. Is that something we should expect? I assume some users that are running migrations may not...

Make sense. It looks like normal Django migrations make use of introspection. We can get use that get_constraints method, unless you have any objections.

What issue are you seeing? I just got it working on 2.2 a few days ago

I am seeing the same issue. Based on my testing, it appears to be caused by the `solo` setting. Does celery ack late automatically with the `solo` option on or...

Where was this fixed? I am still running into this error